Skip to content
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

Commands for everything #44

Open
arthurbacci opened this issue Mar 30, 2021 · 5 comments
Open

Commands for everything #44

arthurbacci opened this issue Mar 30, 2021 · 5 comments
Labels
enhancement New feature or request

Comments

@arthurbacci
Copy link
Owner

Set everything to be based on commands, like in the config_dialog, and the key bindings would be just a bind to the command, like Emacs.

@arthurbacci
Copy link
Owner Author

This would make it easier to add key binding customization.

@arthurbacci arthurbacci added the enhancement New feature or request label Mar 30, 2021
@bynect
Copy link
Contributor

bynect commented Mar 31, 2021

Adding commands like scroll-to, find, jump-end, and other way to navigate the file would be super cool

@arthurbacci
Copy link
Owner Author

It might not be the best idea to make everything a command. For example, supposing we have a "delete-selected-line" command, it's easy to delete multiple lines using the key. However, if we move the cursor just once the last command will now be the cursor movement, and not "delete-selected-line" anymore. If the cursor movement isn't considered as a command it makes it a lot easier to delete multiple lines using that command.

@bynect
Copy link
Contributor

bynect commented Oct 28, 2024

It might not be the best idea to make everything a command. For example, supposing we have a "delete-selected-line" command, it's easy to delete multiple lines using the key. However, if we move the cursor just once the last command will now be the cursor movement, and not "delete-selected-line" anymore. If the cursor movement isn't considered as a command it makes it a lot easier to delete multiple lines using that command.

Maybe a different history for movements and commands? So you can redo operation or jump back around

@arthurbacci
Copy link
Owner Author

Maybe a different history for movements and commands? So you can redo operation or jump back around

Should work, but I will try to merge #66 before starting to work on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants