-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Shell commands #547
Shell commands #547
Conversation
What is causing the check failure? |
I think it's just a github failure, re-running tests now. |
I think on POSIX systems we can follow Kakoune's lead: it looks for a |
Should I do anything with the command's stderr? |
Maybe you can log it? |
Instead of unwrapping potential errors, I think I might want to log an error, display a message, and return? |
`shell` will no longer panic if: * The user-configured shell cannot be found * The shell command does not output UTF-8
Addresses #75.
I've added a config option for
shell
which would be set likeshell = ["bash", "-c"]
,but the code does not currently use it because command functions are not able to access config currently. As such, the code is only able to fall back tocmd /C
on Windows andsh -c
otherwise.Currently, the command's stderr isn't handled.$
, which pipes each selection into the command, deleting the selection if the command exits with a nonzero exit status.Shell command completionsconfig.toml
.