-
Notifications
You must be signed in to change notification settings - Fork 2
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
Emacs emulator option #12
Comments
Sounds like user error 🔥 |
Is this just emacs key mapping or does the editor need to emulate emacs? |
EMACs_Commands.txt contains the commands that new RPC team members learn. A desired feature is emacs.txt is the standard RPC .emacs cfg file (renamed so that GitHub would upload it). The RPC uses the following mods:
gnu-emacs.txt is the .gnu-emacs file (also renamed so that it could be uploaded). |
Almost everything in the
They would have to be replaced with a normal Modifier+Key code The other solution is to implement our own key handler, in which case we can use any pattern. It's not possible to use VS Code marketplace extensions directly. The monaco editor is simply one of the many components that make VS Code, and extensions require the full VS Code to work. |
Commenting as a vi user here. Does this mean that the following would need to be replaced with a different key combo?
|
If we go with electron menu accelerator patterns, then yes. So if we expect all these to be implemented, it would make more sense to write our own key handler to avoid these limitations. |
The goal is not to slow down the editors that already know Emacs, so it looks like we need our own key handler. |
Is it expected for users to be able to set what the Control or Meta key is? It's common to accept Control and Meta interchangeably as there's no Meta key on Windows. However, some examples you listed have different commands for both Control and Meta. Is there a full list of commands expected to work? |
Users should be able to set the Control key. There is not a requirement to set the Meta key. The team uses Esc for the Meta key, but some team members use the Caps Lock for Control, another uses the Windows button. At a minimum, the commands listed in EMACs_Commands.txt should be supported. |
Many team members are very proficient with Emacs and use it to edit RFCXML currently. The editor should offer an option of using an Emacs extension (like the Emacs extensions available in the VS Code marketplace). It should be optional because not all team members use Emacs.
The text was updated successfully, but these errors were encountered: