Skip to content
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

[discuss] place runtime folder in ~/.local/helix or ~/.cache/helix instead of ~/.config/helix #4498

Closed
hh9527 opened this issue Oct 28, 2022 · 1 comment
Labels
C-enhancement Category: Improvements R-duplicate Duplicated issue: please refer to the linked issue

Comments

@hh9527
Copy link
Contributor

hh9527 commented Oct 28, 2022

My ~/.config in under git control, I have to configure .gitignore to avoid upload/download tree-sitter sources and *.so.

I think the more reasonale approach is

  • only keep config.toml languages.toml inside ~/.config/helix
  • make all other files into ~/.local/helix

and one more step, for one who need to workspace-level customize (for example: tree-sitter grammar developer)

we can config addtional runtime path in $workspace/.helix/config

# merged into runtime file lookup path with high priority
additional-runtime-path = ["./workspace-level-runtime-folder"]

finally behaviour:

helix merge config.toml & languages.toml in the following order:

  • workspace-level: $workspace/.helix/
  • user-level: ~/.config/helix/
  • system-level: /etc/helix/
  • distribution-level (always readonly) : /usr/local/helix/

and lookup runtime files in the following order:

  • workspace-level: following values of additional-runtime-path in merged config.toml
  • user-level: ~/.local/helix/runtime/
  • distribution-level: /usr/local/helix/runtime/

alternative: use .cache instead .local
reason: runtime somehow could be seen as a build-cache of languages.toml

@hh9527 hh9527 added the C-enhancement Category: Improvements label Oct 28, 2022
@the-mikedavis
Copy link
Member

Duplicate of #584

@the-mikedavis the-mikedavis marked this as a duplicate of #584 Oct 28, 2022
@the-mikedavis the-mikedavis closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2022
@the-mikedavis the-mikedavis added the R-duplicate Duplicated issue: please refer to the linked issue label Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: Improvements R-duplicate Duplicated issue: please refer to the linked issue
Projects
None yet
Development

No branches or pull requests

2 participants