Interesting read, I've been using Vim for some 18 years myself and I was completely unaware of fzf. However, I'm curious if you know `rg` (aka. ripgrep): https://github.com/BurntSushi/ripgrep In my experience it's markedly faster than `ag` (which is markedly faster than `grep`).
Vim after 15 Years
31–40 of 176 posts
Re: Vim after 15 Years
#32Earlier quoted context omitted.
I've been using i3 for years now. I experienced the same pain. Mac hijacks a lot of the child vm keybindings. I didn't have this problem with windows as the host os. But that doesn't really make sense. Best of luck with the transition. Posting from a thinkpad, with i3, pycharm and vim right now :).
How are you posting on HN from vim?
Re: Vim after 15 Years
#33Vim, apparently, is the new emacs. /me ducks and runs out of the room
Re: Vim after 15 Years
#34I have an almost identical setup as that described in this post. Being in the terminal and integrating with tmux is a wonderful environment - lightweight and immersive. And all these Vim plugins are of such good quality - are Vim plugin authors perhaps of a different, geekier, ilk? So it's a shame that vanilla Vim is restricted to its special modal editing paradigm, there's so much more to it than that.
BTW I post this on HN everytime I see a gushing Vim thread, apologies if you've seen it before.
PS I'm also working on refactoring my tmux keybindings that do a similar thing - SHIFT+ARROW to select, CTRL+C to copy, CTRL+D to select the current word, etc, etc.
Re: Vim after 15 Years
#35Interesting read, I've been using Vim for some 18 years myself and I was completely unaware of fzf. However, I'm curious if you know `rg` (aka. ripgrep): https://github.com/BurntSushi/ripgrep In my experience it's markedly faster than `ag` (which is markedly faster than `grep`).
I work at VS Code and we recently switched to ripgrep for quick open and search. Even searching in Chromium source takes only a few seconds. Pretty impressive speed.
Re: Vim after 15 Years
#36Interesting read, I've been using Vim for some 18 years myself and I was completely unaware of fzf. However, I'm curious if you know `rg` (aka. ripgrep): https://github.com/BurntSushi/ripgrep In my experience it's markedly faster than `ag` (which is markedly faster than `grep`).
http://owen.cymru/fzf-ripgrep-navigate-with-bash-faster-than...
https://medium.com/@crashybang/supercharge-vim-with-fzf-and-...
fzf is lifechanger inside and outside Vim. I now use it for almost everything.
Selfpromotion: I have made a Vim plugin for searching and playing iTunes Library based on fzf.
Re: Vim after 15 Years
#37I had another pane autorunning something when it detected src file changes (inotify). So you just :w, and it happens. The method in this blog could do this: just add :w to the mapping. The blog method might seem hacky in using up and enter, but this makes it easy to modify the command you want to run.
I also wanted to try using kakoune (http://kakoune.org/) but found that for day to day stuff I was far to reliant on my vim setup. Since beomming more reliant on the shell this is now more feasible and I've got a lot more flexibility.
Re: Vim after 15 Years
#38I'm an avid tmux+neovim user, too, though working with Reason is a lot easier in VS Code. Making the switch from actual vim to fake vim (ie JS emulation) sucks. Recently, VSCodeVim merged #1725 to add actual neovim as an editor - it's using NeoVim's embedding API so you're using neovim to edit the text file inside of VSCode's chrome, including all of VSCode's type hints and popups. Info here: https://github.com/VSCod…
To be clear (as the guy behind these efforts), what was merged was a PR to let Neovim handle Ex-commands. This by itself was already pretty cool. In The PR for full neovim integration is the one you linked. It's more than just making it work with your existing .vimrc file: it's making it work with most vim plugins, leveraging the neovim runtime to make macros run faster, etc.
Re: Vim after 15 Years
#39Interesting read, I've been using Vim for some 18 years myself and I was completely unaware of fzf. However, I'm curious if you know `rg` (aka. ripgrep): https://github.com/BurntSushi/ripgrep In my experience it's markedly faster than `ag` (which is markedly faster than `grep`).
Something faster than ag? Honestly had no idea. I've been so happy with ag.