-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
Add Keybindings support #151
Comments
I second this. Keybindings and shortcut support would be useful. Think of what links has got for example. As far as I know there is not even a shortcut to go the address bar in carbonyl. Best would be configurable shortcuts. |
Ditto for me. The real draw of carbonyl is not needing to fire up a graphical environment just to use necessary services whose designers assumed that everyone has Google Chrome installed. I do not have a mouse and I don't know whether anyone else has touchscreen support without logging into a desktop environment, but I certainly don't. I would use browsh, but they seem to have the same problem: scrolling up and down is the only interaction available from the keyboard. |
I hope there will be hotkeys like in Vimium extension |
+1 this feature is absolutely a must-have |
Hi @fathyb I think there should be 2 solutions for this: Either a nix-like configuration file where keys represent some string actions(Toggle address bar)/keybindings(). Cornlang is a great minimal alternative for this written in rust: https://cornlang.dev/ Or you can utilize ron and expose the Struct/Trait methods directly: https://github.com/extrawurst/gitui/blob/master/vim_style_key_config.ron I'd love to have this feature as well. This could be super useful for using carbonyl as my TUI rendering engine. Esentially I can build dev tools like AI chat interfaces that could be written once as a web application, then used in the terminal with carbonyl under the hood or a localhost website. |
Is there a way to use keybindings to interact with carbonyl instead of using mouse? (like on browsh)
The text was updated successfully, but these errors were encountered: