I use vscode with the nim plugin on Win10, targeting wsl ubuntu via the vscode 
remote development plugin. I tried Nim last year and it wasn't great, I didn't 
have any intellisense or plugin running capabilities since I was using wsl (my 
win install had it's own problems), but with remote development now it's just 
awesome and everything installed and worked perfectly this time around.

I use code runner's custom command via F9 to run nim files statically, that's 
the fastest method I've tried and the output is very tidily presented. If I 
need user input or supplied args I use the vscode vimter plugin, it quickly 
opens up a pop-up neovim window in the terminal ready to take args and run, and 
when you exit it disappears and you're back where you were in the editor. Also 
very handy if you need some quick vim capabilities...I set up vscode-vim as 
well which is handy at times but it doesn't target your .vimrc so it's always 
way behind on my mappings. I use wsl and vim8 in cmder as well, vscode doesn't 
quite do full screen terminal.

The vscode terminal is the best console I've found for for cutting and pasting 
text easily, although cmder is much lighter and can run 
wsl/git-bash/cmd/whatever in separate tabs no problem. I just use whichever 
suits the task.

But yeah, I love using Nim on vscode now, big-arse memory footprint and all... 
:)

Reply via email to