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

Instructions to link runtime on Linux/macOS can have a bad result #7230

Closed
rseymour opened this issue Jun 4, 2023 · 0 comments · Fixed by #7231
Closed

Instructions to link runtime on Linux/macOS can have a bad result #7230

rseymour opened this issue Jun 4, 2023 · 0 comments · Fixed by #7231

Comments

@rseymour
Copy link
Contributor

rseymour commented Jun 4, 2023

The docs recommend the command:

ln -s $PWD/runtime ~/.config/helix/runtime

Which works if and only if you don't already have a ~/.config/helix/runtime So for folks going from a package install to a source install, they get an automatically broken runtime directory. ie they'll end up with something like:

~/.config/helix/runtime/runtime

This can be fixed with something like:
ln -Ts $PWD/runtime ~/.config/helix/runtime which fails if ~/.config/helix/runtime already exists, at which point the user could delete it or something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant