Saw similar thread for emacs & vim and decided to open one for an editor I use daily to write code in, VS Code.
I use quite a few extensions mostly to write Go & TypeScript with Monokai Night theme and Vim mode.
What does your setup look like?
Aside from a number of settings that I’ve changed. I use the following extensions.
Some settings changes:
File type support:
Nothing by deliberate choice, but I install the syntax highlighting plugins when prompted.
That said, it’s obviously not my main editor/IDE - it’s my trusty fallback IDE for all my non-main languages at the time (since a few years). It’s good enough to just use it, and I say that as someone with quite a vimrc.
Language-agnostic, I’ve got:
And language-specific, I’ve got:
I like code spell, but I can’t figure out how to make it ignore package names or stuff in comments or strings.
I have a very low-tech solution of just very aggressively adding that kind of stuff to the workspace’s spell check dictionary. In general, it treats FooBarBaz as foo, bar, and baz, but there are exceptions that I neither understand nor care to find out, so I just add FooBarBaz and move on with my life.
I do that for my solo projects but feel bad cluttering up team projects. It also bugs me that it seems like setting I just can’t figure out.
Can anybody tell me how to disable the “preview tab” state, where you click on something once in the explorer (or more importantly open it with cmd-p), and it opens but in a “preview” tab that will be replaced? Or better yet, I’d like to promote “preview” tabs (I’m probably using the wrong term here) into real tabs once you’ve had it open and/or focused for a few minutes?
I haven’t figured out how to disable, but I did learn double click opens for real. Now I use lame open on purpose for files I just want to preview.
I wish the function was reversed.
You can disable “preview” mode entirely with this setting:
…or just from Quick Open with this one:
If you save the file (cmd+s) it will make the tab permanent. If I understand what you meant.
That’s a useful trick I need to keep in mind, chur.
Saving works—there’s also a command to just keep the file open named “View: Keep Editor” (workbench.action.keepEditor). The default keyboard shortcut is ⌘K Enter.
I’ve disables preview, it’s annoying (see other comments for details). As for “promoting” you can double click on the tab to do that.
The vim mode in VSCode with the neovim backend is actually surprisingly good, the least awkward vi emulation I’ve found yet.
I’m now a fan of Ayu Adapta theme, combined with City Light Gray icons, yes, Vim mode.
To give a bit of context as to where VS Code fits into my development workflow: I use Xcode for iOS development as using anything else feels masochistic, when I need to make quick edits to config files or scripts I use vi, and for basically everything else I use VS Code.
I’ve also made a few settings tweaks to hide the useless “Open Editors” sidebar section,
You can find my VSCode Setup here and here is my settings-file.
I use vscode a lot, mostly for typescript/css/html, but sometimes for C# too (though I still mostly use real VS for that).
Just curious: What makes you open VS rather than VS Code? I use Rider on MacOS because the R#-like functionality gives me a great productivity boost.
We use some third party tools that only have VS plugins. Unit testing support for .NET Framework (as opposed to .NET Core) seems sketchy in VS Code, too. Plus, if I’m completely honest, VS is just better at a lot of things like large scale refactoring.
Once we switch to Core, I think the delta will narrow and VSCode may be a viable full time option.
Not sure where mine fits in the scheme of typical VS Code customisation but it works well for me.
Typical Rust + JS setup I’d guess ?
I found this thread pretty useful with encouraging me to finally see if I could disable a lot of my bugbears with Code, in particular preview.
A useful setting if you’re on a retina / high-DPI screen:
“Broken” would be the one word to describe my setup. I keep getting “extension host terminated unexpectedly” :|
I have all my vscode config in source control:
Settings, keybindings, snippets:
I use the “Spacegray Eighties Dark” theme with some color customizations (comments should be highly visible; bright green, not dull gray!) and Fantasque Sans Mono for my font (highly recommended).
Notable extensions include GitLens, Peacock, Rewrap, Dash (to integrate with https://kapeli.com/dash, which is awesome), Bracket Pair Colorizer 2, and Bookmarks, plus a bunch of language-specific extensions, like Python, Go, Prettier, etc.
I use Chromodynamics theme together with VSCode Great Icons. And from functional side besides various language extensions, I often use(in order of usage/usefulness): Code Spell Checker, GitLens, Ungit, Todo Tree and hexdump
Keybindings mostly vanilla, besides a few which were used by my desktop environment.
I don’t use many extensions, mostly because everything I want is already built-in! The three extensions I have installed:
Solarized Light/Railgun, VsCodeVim (without the neovim stuff), language support for JS/C#/OCaml. I don’t like VsCodeVim a lot, but the only other vim emulation extension that’s in a decent enough state is amVim and that also has its fair share of annoyances and bugs. I started writing one myself in OCaml with BuckleScript… but you know how these things go.