4 ms·
I love the idea of VSCode, but I find it rather confusing to use. The configuration of plugins is non-trivial to figure out, sure you can copy paste a bunch of
by mrweasel 8y ago
I love the idea of VSCode, but I find it rather confusing to use. The configuration of plugins is non-trivial to figure out, sure you can copy paste a bunch of stuff from the web, but how do I figure the configuration out on my own? The best answer I've come up with this far is "You don't".
Even opening file/projects is a bit weird to me.
VSCode isn't necessarily to blame for this, it's just different from TextMate and Vim. Still I've found it rather difficult to get started with.
- artimaeis 8y ago> The configuration of plugins is non-trivial to figure out, sure you can copy paste a bunch of stuff from the web, but how do I figure the configuration out on my own? For what it's worth I feel like the best way is to just explore the settings and see what's there. Ctrl-, to open settings, then you should see the default settings on the left side. Most plugin authors are pretty good about putting decent comments to explain their configurations, and the auto-complete should help to evaluate any options available. > Even opening file/projects is a bit weird to me. I've been using it 2 years now and still find the Ctrl-K Ctrl-O command to open folders awkward and nearly impossible to remember.
- ztjio 8y agoI use 'code' on CLI or drag n drop to open anything. Much easier to use/remember imo.
- parthdesai 8y ago>I've been using it 2 years now and still find the Ctrl-K Ctrl-O command to open folders awkward and nearly impossible to remember. cd path/to/folder && code . Pretty easy to remember tbh
- swah 8y agoStockholm syndrome? I remember writing (and I enjoyed doing that more than work days) hundreds of Elisp lines to configure Emacs.