-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Follow the XDG Base Directory Specification #242
Comments
+1 from me, I would really love to see this changed now while steel is in alpha/beta instead of waiting until later and making this minor usability change more complicated. |
I don't disagree, however I wasn't quite sure where "programming language files and libraries" fell under the spec - also in the meantime while I figure out how to handle this, you can set the location where steel installs things by setting the |
I guess the question then, is do steel library files go under the xdg equivalent of |
Yes, |
It depends on whether the library files are shared. I would go with ~/.local/lib/
Static, private vendor data that is compatible with all architectures.
~/.local/lib/arch-id/
Location for placing public dynamic libraries. The architecture identifier to use is
defined on Multiarch Architecture Specifiers (Tuples)[6] list.
~/.local/share/
Resources shared between multiple packages, such as fonts or artwork. |
For what it's worth I would also suggest that the history file be kept in XDG_STATE_HOME. I don't think |
XDG Base Directory Specification dictates which files should go where.
Steel currently dumps its dir to the home directory.
The text was updated successfully, but these errors were encountered: