Replies: 3 comments
-
I also got this problem, I use yazi and helix on nushell and I can't use hx with yazi.toml. I hope someone know how to fix this! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Have you tried to describe the whole path for hx , rather than just binary name. Sometimes the executable don't be in the global path |
Beta Was this translation helpful? Give feedback.
0 replies
-
I just fix it lmao, I use 'helix' in $EDITOR instead of hx in .bashrc |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I use nushell as my shell, and have recently decided to give helix a try for a month. I've run into a weird issue, and I'm not sure where the problem lies.
Context
Host: Macbook Pro (M2 Pro) 14.7.1 Sonoma
Helix version:
helix 25.01.1 (e7ac2fcd)
Nushell version:
0.101.0
Helix and nushell installed from nixpkgs (nix-darwin).
The problem
This morning when I went to do a
git pull
- I got this error when git was prompting me with an editor to edit/save my merge commit message:Additionally, if I try to open a text file in
yazi
, I get this error:hx
is definitely on my path:and I can launch/use hx normally.
I also have
hx
exported as myEDITOR
:and can run evaluate it, e.g. this works:
^($env.EDITOR) README.md
will open README.md in helix without issue.Does anybody have any thoughts/has experienced this before?
EDIT:
Things work fine if I use
nvim
e.g.:EDITOR=nvim sops nixos/secrets.yaml
EDIT2:
I tested this out on my desktop PC (running nixOS) and everything appears fine. Seems to be some strange interplay between macOS/nushell/helix.
Beta Was this translation helpful? Give feedback.
All reactions