10 years of love for Emacs undone by a week in VSCode.
Last week, I wrote about Why I won’t be switching to VSCode any time soon. Then Cunningham’s law kicked in, I learned about some killer features, got tips on some config, and gave VSCode another chance.
plus then you can slowly learn to become hopelessly dependent on this feature: pic.twitter.com/U0kUwijD6j
— Jason Miller 🦊⚛ (@_developit) November 3, 2017
That was the one. The feature that made me try VSCode for real. You can hover any function or variable, press command, and see its definition in a little popup. Or jump straight to the code.
I think I have the perfect config going, and I’d share it with you, but I don’t know how. Mainly I focused on getting a clean interface where code dominates.
Blank slate with a bunch of code. The status bar is subtle, no activity bar, no cruft to the left or right of the code. No ugly vertical lines showing indentation.
Change indicators still show up as subtle green or blue lines.
Here’s some stuff that still annoys me 👇
- tabs are huge, and there doesn’t seem to be a config for that
- pressing Tab inserts a tab
- changing Tab to “line indent” works okay-ish, but not quite. I’d like to indent to automatic correct indentation instead of having to press it multiple times. When cursor is in indent space, tab should jump to beginning of line, when cursor is in code space, tab should indent or do nothing.
- I installed emacs keybindings to preserve muscle memory, and now jump-to-line shortcut doesn’t work
cmd+Pmagic search can be annoyingly dumb sometimes, and the UI struggles with long file paths. Shows beginning of path instead of the important stuff
cmd+Oshortcut isn’t context aware. Opens UI at last visited folder instead of at current file
- no good shortcut for “jump back to previous file” that I can find
Any ideas? @ me
PS: You should also follow me on twitter 👉 here.
It's where I go to shoot the shit about programming.