3 ms·

Probably the best second person POV story I've ever read. Very funny and I got a kick out of it. As a relatively new part time vim user (about a year), I felt p

by jjice 6y ago

Probably the best second person POV story I've ever read. Very funny and I got a kick out of it. As a relatively new part time vim user (about a year), I felt portions of this. I still use VSCode for a handful of tasks, but Vim has taken over more and more. This past semester I had to SSH into our CS servers for my OS class, and the way my group would work was usually me sharing my screen and us peer programming. There were multiple occasions my group partners would stop me and ask how dude something like remove a full line, put it in a register, and pasted it at the bottom of the file so fast. ddgp I love the reactions to it, because people get excited and I encourage them to try him themselves. I'm also very much an amateur when it comes to vim. I love seeing vim masters in action, it's so interesting. I think I'll forever remain the right eyed character who asks "how did you do that?", and it's that sense of wonder that makes me love vim.

barbs 6y ago
Not to be too pedantic but shouldn't that be ddGp? Also, have you tried the Vim plugin for VSCode?
- IggleSniggle 6y ago
  I've tried the Vim plugin for VSCode a few times personally, but I don't trust it. It's incomplete, and it has its own secondary understanding of history that can get you into trouble when it interacts poorly with VSCode's own history. Anyway, that was my experience for my short time using it. I'm curious if there are any longtime vim users using VSCode with the Vim plugin, and if so, what are their experiences, and why do they use VSCode with a Vim plugin instead of just using vim itself?
  - BadInformatics 6y ago
    I used to, but switched to https://github.com/asvetliakov/vscode-neovim https://github.com/asvetliakov/vscode-neovim. It's much faster, doesn't lag the editor at all and has less of an impedance mismatch because it uses Neovim under the hood instead of trying to emulate functionality from scratch. There are a few reasons why I use a vim plugin instead of vim proper for most day-day work: 1. I do plenty of data science-y stuff that requires support for good visuals. Vim's support here is pretty lackluster and Jupyter's Vim mode sucks. VS Code has a great interactive mode with full autocomplete and a dedicated window that records plots/output history. 2. Language servers and LSP plugins are so much easier to manage. I rarely if ever have to babysit updates and I don't have to install a bunch of system-wide dependencies to get certain ones to build. 3. Making the above (and all other fancy VS Code functionality) work on multiple remote machines is a breeze. The normal Vim workflow would require cloning dotfiles (not a big deal), running setup with something like GNU Stow (almost never installed) and then futzing around with LSP plugins as in 2). 4. Built-in rendering of rich docstrings/doc pages (think Markdown, Sphinx RST). I want to say certain extensions/languages support LaTeX as well, which would be a bear to read in Vim.
    - IggleSniggle 6y ago
      I know a lot of folks don't read comments over a week old, but just in case you do, just want to say: THANK YOU. I took the plunge tonight into neovim/vscode-neovim and it is the solution I've been wanting without knowing it was what I wanted.
scns 6y ago
s/ddgp/ddGp/g ftfy
IggleSniggle 6y ago
I think I'm probably at a similar stage with regards to vim usage. I have mixed feelings about it, but it seems that VSCode has spread itself into my consciousness in the way that I had hoped vim would. With VSCode, I know how to quickly select a word, jump the selection to a multiselect, and rapidly selection by words or lines that I wish to edit simultaneously, all without touching the mouse. It's gotten to the point where selecting or jumping a word with alt-arrow is reflexive instead of `w`, where `ctrl-D` and `alt-down` are more reflexive than the more composable alternatives in vim. This ALL was supposed to be vim! Damn you VSCode! I wouldn't be bothered by this except I compose Unix tools quite a bit, so it's like I'm maintaining two separate working environments. If I had just started with vim (or emacs) from the get-go, then these two worlds would eventually meet. I've even got my own handful of extensions to send things from VSCode to the integrated terminal and back as a sort of poor substitute for the things that emacs and vim have been doing for decades. I'm pretty sure that I'm an idiot.

by jjice 6y ago

barbs 6y ago

Not to be too pedantic but shouldn't that be ddGp? Also, have you tried the Vim plugin for VSCode?

IggleSniggle 6y ago
I've tried the Vim plugin for VSCode a few times personally, but I don't trust it. It's incomplete, and it has its own secondary understanding of history that can get you into trouble when it interacts poorly with VSCode's own history. Anyway, that was my experience for my short time using it. I'm curious if there are any longtime vim users using VSCode with the Vim plugin, and if so, what are their experiences, and why do they use VSCode with a Vim plugin instead of just using vim itself?
- BadInformatics 6y ago
  I used to, but switched to https://github.com/asvetliakov/vscode-neovim https://github.com/asvetliakov/vscode-neovim. It's much faster, doesn't lag the editor at all and has less of an impedance mismatch because it uses Neovim under the hood instead of trying to emulate functionality from scratch. There are a few reasons why I use a vim plugin instead of vim proper for most day-day work: 1. I do plenty of data science-y stuff that requires support for good visuals. Vim's support here is pretty lackluster and Jupyter's Vim mode sucks. VS Code has a great interactive mode with full autocomplete and a dedicated window that records plots/output history. 2. Language servers and LSP plugins are so much easier to manage. I rarely if ever have to babysit updates and I don't have to install a bunch of system-wide dependencies to get certain ones to build. 3. Making the above (and all other fancy VS Code functionality) work on multiple remote machines is a breeze. The normal Vim workflow would require cloning dotfiles (not a big deal), running setup with something like GNU Stow (almost never installed) and then futzing around with LSP plugins as in 2). 4. Built-in rendering of rich docstrings/doc pages (think Markdown, Sphinx RST). I want to say certain extensions/languages support LaTeX as well, which would be a bear to read in Vim.
  - IggleSniggle 6y ago
    I know a lot of folks don't read comments over a week old, but just in case you do, just want to say: THANK YOU. I took the plunge tonight into neovim/vscode-neovim and it is the solution I've been wanting without knowing it was what I wanted.

scns 6y ago

s/ddgp/ddGp/g ftfy

IggleSniggle 6y ago

I think I'm probably at a similar stage with regards to vim usage. I have mixed feelings about it, but it seems that VSCode has spread itself into my consciousness in the way that I had hoped vim would. With VSCode, I know how to quickly select a word, jump the selection to a multiselect, and rapidly selection by words or lines that I wish to edit simultaneously, all without touching the mouse. It's gotten to the point where selecting or jumping a word with alt-arrow is reflexive instead of `w`, where `ctrl-D` and `alt-down` are more reflexive than the more composable alternatives in vim. This ALL was supposed to be vim! Damn you VSCode! I wouldn't be bothered by this except I compose Unix tools quite a bit, so it's like I'm maintaining two separate working environments. If I had just started with vim (or emacs) from the get-go, then these two worlds would eventually meet. I've even got my own handful of extensions to send things from VSCode to the integrated terminal and back as a sort of poor substitute for the things that emacs and vim have been doing for decades. I'm pretty sure that I'm an idiot.