Replies: 1 comment 2 replies
-
|
The current recommended way is via a bootstrap script for users, and Metals should probably follow suit for consistency |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I happened across this PR:
https://github.com/scalameta/metals/pull/8034/changes
As I read it, to run mill commands, metals;
As far as I can tell, this strategy follows the recommendations set out in mills own documentation.
https://mill-build.org/mill/cli/installation-ide.html
But a brief discord conversation didn't seem to generate universal happiness with this solution.
Suggestions to get mill on the path included,
https://mill-build.org/mill/cli/installation-ide.html#_global_installation
https://github.com/com-lihaoyi/homebrew-mill
but it's not clear these are relevant for metals, which follows the strategy above and does not, I believe, use the
PATH.My question, is whether there is a universal consensus on how metals should launch mill?
My reading of the PR and mill's docs, is that metals assumes the user has followed mill's documentation and prefers that approach. Metals falls back to it's own fallback script otherwise. This seems reasonable - from what I can tell, the existing solution makes sense, but the discussion is recorded for posterity.
Beta Was this translation helpful? Give feedback.
All reactions