personalnadir Posted June 27, 2022 Share Posted June 27, 2022 As Alfred scripts do not see custom PATHs and MacPorts uses /opt/local/bin as it's install location, I was wondering what the accepted solution was to making sure that Workflows support MacPort installs? Link to comment
vitor Posted June 27, 2022 Share Posted June 27, 2022 You extend the PATH yourself in your script. In bash/zsh it means adding a line at the top: export PATH="/opt/local/bin:${PATH}". Link to comment
personalnadir Posted June 28, 2022 Author Share Posted June 28, 2022 Thanks, I figured that would be the case. Was wondering if there was a global way to set it for all workflows? Link to comment
vitor Posted June 28, 2022 Share Posted June 28, 2022 There is not, by design. A predictable environment helps when sharing Workflows or using them on a different Mac. It also reduces the chance of an external Workflow breaking due to a local change. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now