You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently during the development, I use a custom make command to copy the executable to the workflow directory to test it. This works well, but since the Alfred workflows directory might have a different path on other developer's machine my command won't be really useful for them.
Another solution is to find a way to determine a path of the Alfred workflows directory. Then my script could be used by other developers. Though, by now I've found no easy way to determine the path.
The text was updated successfully, but these errors were encountered:
Currently during the development, I use a custom make command to copy the executable to the workflow directory to test it. This works well, but since the Alfred workflows directory might have a different path on other developer's machine my command won't be really useful for them.
We could use alfred CLI tool and its link command for that (thanks @nikitavoloboev for the suggestion!).
Another solution is to find a way to determine a path of the Alfred workflows directory. Then my script could be used by other developers. Though, by now I've found no easy way to determine the path.
The text was updated successfully, but these errors were encountered: