-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Feature Request] Keybindings depending on the filetype #2518
Comments
With chaining i.e "F5": "command:fexec make|command:fexec dotnet build|command:fexec zig build",
"F7": "command:fexec zig ast-check {f}",
"Shift-F5": "command:fexec zig test {f}|command:fexec dotnet test" things get really weird in case of the quickfix plugin, when binding build action is desired. "*.cs": {
"F5": "command:fexec dotnet build",
"Shift-F5": "command:fexec dotnet test",
},
"*.zig": {
"F5": "command:fexec zig build",
"F7": "command:fexec zig ast-check {f}",
"Shift-F5": "command:fexec zig test {f}",
}, |
you can bind your script |
Keybindings depending on the filetype to have build actions and quickfix plugin work together nicely
Depending on the file type, it might be better to bind the same key to a different command.
I.e with quickfix, depending on the filetype the user might want to execute a different command.
I know about chaining commands with
,
, |,
&` but that's not the same thing.The snippet below raises some error when running micro
Error
The text was updated successfully, but these errors were encountered: