3 ms·
> Emacs does these things right in a way that virtually every other IDE-like editor does wrong. ? > the wrong way VSCode handles File / Open by default ?
by jodrellblank 6y ago
> Emacs does these things right in a way that virtually every other IDE-like editor does wrong.
?
> the wrong way VSCode handles File / Open by default
?
- bitwize 6y agoRight: Electric indent. Tab at beginning of line automatically indents line to desired depth. Editor's guess at indentation level is almost never wrong, and the exact level is configurable. Wrong: Hit return and the next line is automatically indented; other than that you're on your own. Right: Flash the opening bracket or quote when you type the closing bracket or quote. Wrong: "Helpfully" close opening brackets or quotes, but do not provide Paredit-like structured editing features, leaving the user to accidentally type spurious extra brackets/quotes. (Some IDEs skip over the preinserted closing mark when you type the same mark with point on the closing mark. But they're woefully inconsistent about this and Visual Studio Code does not do this.) Right: Visiting a file does not otherwise affect editor state. Wrong: All state for the editing session in the current window is clobbered when you do File / Open from the menu. User must spawn a new window in order to preserve editing state in this window.
- jodrellblank 6y agoQuietly pleased to find I agree with your wrongs, especially “helpfully” adding a closing pair item, but sad I haven’t used something that does them better.