3 ms·
I would probably just implement vscode but for the terminal. Emacs shortcuts already work by default in vscode for the most part.
by the_clarence 2y ago
I would probably just implement vscode but for the terminal. Emacs shortcuts already work by default in vscode for the most part.
- sshine 2y agoWhile Emacs is recognisable for its shortcuts, it is hardly a defining feature. Example: Doom Emacs adds Vim shortcuts, and it is still distinctly Emacs. I think of VSCode as “Emacs, but JavaScript instead of Elisp.” That’s one thing I would not choose, in spite of the good things VSCode brings to the table.
- School-Cotton 2y agoCan I hit one key combination to edit the JavaScript corresponding to any vscode command, debug it and possibly modify it however I want? If not, it’s not really comparable to emacs IMO.
- sshine 2y agoThat's a fair point. What I meant is that the runtime is arbitrarily extensible at runtime. But I don't assume that people actually do what you describe.
- skydhash 2y agoVSCode is notepad with plugins, built upon a web engine. Comparing it to Emacs is a huge disservice to Emacs.
- the_clarence 2y agoYou re kidding right.
- School-Cotton 2y agoNone of the main selling points of emacs have anything to do with its shortcuts or using it in the terminal. Plenty of emacs users (including me) rarely or never use it in the terminal. It’s a GUI editor just like vscode is. I think this misconception comes from the fact that (1) people often compare emacs and vim, and (2) vim is usually used in the terminal. But emacs and vim are really categorically different things so I think the “emacs vs. vim” meme kinda doesn’t make sense.