-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider using dirs-dev
instead of putting everything in $HOME/.bloop
#1844
Comments
I think that makes sense, I doubt there is any real reason why it necessarily is done via .bloop in home directory. Though the only problem is |
I think it shouldn't be a problem right? Since it's a config file I'd just expect it to look for |
Maybe not, yeah. So probably not blockers to do that. |
Funny enough, I just realized that Bloop actually has everything that is needed to start just utilizing this, but it's not used by everything. You can see this in bloop/shared/src/main/scala/bloop/io/Paths.scala Lines 25 to 31 in 931ce1b
So for the config stuff mentioned above we literally need to just start using it. |
That's pretty typical in the repo, loads of things were done by one person only team, so it's expected that some stuff might be leftover 😓 |
Lately I've been trying to clean up my
$HOME
dir and have been noticing that a lot of the Scala ecosystem stick stuff in$HOME
. Looking around in Bloop I see thatdefaultBloopDirectory
is$HOME/.bloop
.bloop/bloopgun/src/main/scala/bloop/bloopgun/util/Environment.scala
Line 26 in efc8d62
There are probably other places this is set as well, but I wonder if instead it'd be better to rely on something like
dirs-dev
to handle this more correctly and place these things in the appropriate places instead of polluting the users home directory. I know this might break some stuff so we could also use$HOME/.bloop
for a while as a fallback, but default to the correct places viadirs-dev
.Do you think this would be possible, or do you see any issues with this?
The text was updated successfully, but these errors were encountered: