2 ms·
One thing is to make the keyboard shortcuts better. Get rid of the ancient and archaic method of Ctrl-C to start a command chord. Reserve that for basic comman
by blackrock 6y ago
One thing is to make the keyboard shortcuts better.
Get rid of the ancient and archaic method of Ctrl-C to start a command chord. Reserve that for basic commands like copy and paste.
Instead, use the slash, Ctrl-/ to start a command chord. This way, you can use all the nifty shortcuts you want, and still not interfere with common commands.
Another feature is to use Ctrl-Spacebar to allow a search of command aliases.
Like, highlight your words, then hit Ctrl-Spacebar, then type “upper”, and it’ll do a dynamic search for all matches, and one of those matches is to make the selection uppercase.
This can be useful for all types of commands and personalized macros.
But then, the other problem for Emacs, is that Visual Studio Code is pretty damn good. And it also works on Linux. Its memory footprint is really high, taking about 85 MBs of RAM, but Emacs takes like 30 MBs, so it’s less than 3x more, for much better features. But, it’s not like I’m using a 20 year old laptop anymore.
- samatman 6y ago> Instead, use the slash, Ctrl-/ to start a command chord This has an obscure problem, of which you were no doubt unaware. In the terminal, Ctrl-/ sends backspace. Emacs isn't commonly used in the terminal anymore, but it can't become useless in the terminal, and this change would make it useless. Unfortunately this is a non-starter.
- blackrock 6y agoThen use the dot: Ctrl-.
- samatman 6y ago^. just sends . The ASCII page on Wikipedia does a good job of explaining what all these limitations are about. There's CSI-u mode, and I believe terminal emacs understands it if you enable it, but, yeah. There's a lot of legacy to support when your program is older than Unix.