-
Notifications
You must be signed in to change notification settings - Fork 38
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
Allow overriding or disabling Ctrl+T keybinding in shell #268
Comments
Will add an option to configure the default bindings with something like: tv init zsh --bind-history 'C-r' --bind-smart-completion 'C-t' |
that would be very useful ❤️ |
Would be cool if we can get an option to disable the shell-history search hotkey |
Is it the same thing that @logoff was asking for? It would be nice to be able to customize the commands (like I might be wrong, but I think @logoff was saying that if you hit Current workaround is this:
but maybe it would be nice to have something like Like if I try with a fake
|
after #313 it is now possible to configure the keybindings for shell autocomplete and command history through the configuration file, but only for I will try to make the feature more generic in the days to come and possibly have a look at command line options as well |
With #313, is it possible to disable the |
Not yet, but you could just bind it to something you never use in the meantime so that it doesn't get in your way. |
This is great! Any ETA on when you're planning to release? |
I'm releasing 0.10.1 tomorrow |
Working like a charm, thanks! |
Description
When I execute in the shell
Ctrl+T
, I get this error:I guess this happens because the shell integration is expecting a command here. However, I use fzf-file-widget as generic option for any command.
Would it be possible to override
Ctrl+T
keybinding? I don't find the way.Example
Just press
Ctrl+T
in the shell.Expected behavior
Television allowing changing shell keybinding, or at least disabling some particular keybindings.
Actual behavior
I get the described error.
Environment
The text was updated successfully, but these errors were encountered: