-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
runtime Data Location #584
Comments
So in a packaged installation the runtime folder would be installed into a system folder (for example I consider For builds from source we currently recommend symlinking to that directory more for convenience: it's a frequent source of friction because users forgot to specify a HELIX_RUNTIME pointing to their runtime dir. In the future I definitely think that's the wrong thing to do. I guess we could recommend that users use a symlink in |
I think it's a gray area here. Helix |
I'm in favor of changing current behavior.
Even better solution would include Helix merging config and grammars from system dirs and user dirs and having fallbacks configurable at buildtime but meh. This should be enough for most usecases. I'll make the PR, if you want. |
Those sound good to me. We could fall back to XDG_CONFIG_HOME if we need to since that's what we currently use (although it doesn't make much sense xdg spec wise). Having the grammars in the xdg data dir would also be an improvement for the failure mode described in #2023 (and IMO makes sense generally 👍 ) |
What's the status of these two PRs linked from here? Just ran into this again at #5411 (comment). |
@mmatous, would suggest to use the XDG defaults, that way, the implementation is fully XDG compliant and so no surprises. |
Neovim had a long discussion about this, and settled on using the OS-specific fallback: neovim/neovim#78 As mentioned in #6747, most XDG-compliant programs interpret the spec as such. |
Currently the runtime data is supposed to live in
~/.config/helix/runtime
, which is somewhat against the XDG spec.Files like this should normally be placed in
~/.local/share/helix/
.~/.config
should only hold user provided configuration.The text was updated successfully, but these errors were encountered: