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
We should detect that this is going on and adjust the executables accordingly automatically. Virtually never would the user want to run any globally available executable if it is locally bundled with the project.
While something like this already seems to exist for cask other tools are missing.
Is this something we would want to push to the flycheck org as separate packages or even to flycheck itself? I think there's a great value in having these things just working without the users having to mess around with exec paths and stuff.
The text was updated successfully, but these errors were encountered:
I have to repeat the same code all over again and again in my personal configuration to update paths to use local installations.
(example)
We should detect that this is going on and adjust the executables accordingly automatically. Virtually never would the user want to run any globally available executable if it is locally bundled with the project.
While something like this already seems to exist for cask other tools are missing.
Is this something we would want to push to the flycheck org as separate packages or even to flycheck itself? I think there's a great value in having these things just working without the users having to mess around with exec paths and stuff.
The text was updated successfully, but these errors were encountered: