6 ms·
Somebody should tell that to the Rust people. They have a .cargo and a .rustup folder in ~, plus an extra heavy target folder for every project. Would be much n
by jenadine 4y ago
Somebody should tell that to the Rust people. They have a .cargo and a .rustup folder in ~, plus an extra heavy target folder for every project. Would be much nicer if they put the cache one .cache
But they don't seem to care
https://github.com/rust-lang/cargo/issues/1734 https://github.com/rust-lang/cargo/issues/1734
https://github.com/rust-lang/rfcs/pull/1615 https://github.com/rust-lang/rfcs/pull/1615
https://github.com/rust-lang/cargo/pull/9178 https://github.com/rust-lang/cargo/pull/9178
- senden9 4y agoYou can also use the environment file linked in that blog post to tell Rust to follow the XDG standard. Not perfect because it is not the default behaviour but it is doable.
- happymellon 4y agoI put it in another comment, but if you are Rusting on Linux, you can use boxxy to fix bad behaving applications. https://github.com/queer/boxxy https://github.com/queer/boxxy
- agilob 4y agoSomebody should tell this to go people. They just create me a non-hidden directory `~/go`
- vetinari 4y agoexport GOPATH=~/Projects/go Has been like this since forever.
- xdennis 4y agoBeing like that for a long time is not a justification for terrible defaults.
- pasc1878 4y agoThat is a better default than a hidden directory. It is obvious and so you can set GOPATH Also works better on Windows where .path is not hidden Also it seems Rob Pike one of the creators of Go and involved with early UNIX thinks that . making hidden files was a mistake. Quote via XahLee http://xahlee.info/UnixResource_dir/writ/unix_origin_of_dot_filename.html http://xahlee.info/UnixResource_dir/writ/unix_origin_of_dot_... - original was Google+ so not existing now.
- tough 4y agoI hate it when I forget to show hidden files on mac. They had a kb shortcut for it
- hanche 4y agoThey still do: Shift-Command-period toggles hidden files visibility.
- RMPR 4y agoAnd then you have a french layout where it's impossible to fire this keyboard shortcut.
- hanche 4y agoOy. That surprised me. I am quite familiar with the notion of common keyboard shortcut that I can't get on my Norwegian keyboard. Command-(left/right) square bracket is very common, but at least that is usually associated with a menu item so I can assign a different shortcut. But now I learned that on a French keyboard, period is shift-semicolon!? Which makes me wonder: Do the French use the semicolon more often than the period? Oh well, once in a while it sucks not to be American. ;-)
- arghwhat 4y agoSure, hidden folders are a mistake, but less of a mistake than not adhering to standardized folder structures and just littering in people's home folders.
- unnah 4y agoAt least for rust applications of your own, you can use the library https://github.com/dirs-dev/directories-rs https://github.com/dirs-dev/directories-rs to follow XDG on Linux as well as platform conventions on Mac and Windows.
- epage 4y ago> But they don't seem to care While I've not fully dug into all of those links, that is rarely the case and it makes the conversations harder when people over simplify situations like this. Generally, I've found when people make assumptions like this, the underlying requirements are a lot more involved and its not a high enough priority for the small group of overtaxed individuals.
- jenadine 4y agoYou're right. I apologize. The fact that there was a PR actually shows that some people care.
- kzrdude 4y agoThere are 200 thumbs up? And a lot of those are rust people who care.
- stametseater 4y agoIn my experience, the usual reason for a project not using the XDG Base Dir spec is because somebody on the project simply doesn't like it, particularly XDG_CONFIG_HOME defaulting to $HOME/.config. Resistance to the XDG Base Dir spec really does seem to be rooted in personal preference, I've never seen an objection to it on any technical basis. The best arguments against it that I've seen are "many other projects don't use this spec, so why should we?" (e.g. our project should be the last to adopt it.. but why?) and arguments along the lines of "XDG_BIN_HOME isn't in the spec, therefore we shouldn't use XDG_CONFIG_HOME", which just seems like a lame excuse.
- bobthebuilders 4y agoXDG_BIN_HOME is crucial, without it, not supporting the spec seems like the right call. Better to deal with the status quo until updates happen than to get stuck in bikeshed hell.
- stametseater 4y ago