The best way to use ag from within Vim seems to be ack.vim, which is misleading since ag.vim is deprecated, but ack.vim supports both ack and ag.Īck.vim gives you an :Ack command, which takes arguments in the same way as running ag from the command line, except that it opens the QuickFix window with the list of search results: Searching & the QuickFix windowĪg is the new ack, which was the new grep. Maybe it could treat characters before underscores as the first character so typing something like f b b q would highlight a file like foo_bar_baz_quux.js. This would be great for searching tags since class names are often camel no matter which language you’re writing. In IntelliJ, for example, if you want to open the class FooFactoryGeneratorBean you hit Cmd-o and type F F G B Enter to open it (the first letter of each part of the class name). While FZF and Ctrl-P and other editors support fuzzy searching for pathnames, I’m really hoping that someone will create a first-character search for Vim. It works well but is much slower than the terminal in large codebases (~1m files). I was going to write about how the one big drawback to fzf is that it’s an external command and doesn’t work with MacVim, but now it does! Support has been recently added by using the new native terminals in Vim 8. Source /usr/local/opt/fzf/shell/completion.zshįi # fzf via local installation if thenįi # fzf + ag configuration if _has fzf & _has ag then export FZF_DEFAULT_COMMAND = 'ag -nocolor -g ""' export FZF_CTRL_T_COMMAND = " $FZF_DEFAULT_COMMAND" export FZF_ALT_C_COMMAND = " $FZF_DEFAULT_COMMAND" export FZF_DEFAULT_OPTS = ' The FZF environment variables are also used when fzf is called from within Vim: # fzf via Homebrew if then source /usr/local/opt/fzf/shell/key-bindings.zsh And since I’ve configured fzf to use ag, it’ll ignore anything excluded by. In Zsh, I can hit Ctrl-t to instantly fuzzy-find any file in the current directory. agignore files so you no longer need to keep a giant wildignore string in your vimrc.įzf works in the shell as well and comes with bindings for Zsh, Bash, and the Fish shell. When using fzf, make sure to tell it to use ag, a grep/ ack replacement called the Silver Searcher. I practically never use tabs - more on that later - so it’s important that I can switch my focus to something I’m thinking of with as little friction as possible. The most useful commands are :Buffers, :Files, and :Tags, which I’ve bound to and, t and, r respectively: nmap :Buffers īinding is important because I live and breathe buffers.
Macvim customize colors guifg install#
Simply follow the installation instructions (basically brew install fzf on macOS with Homebrew) and install the additional fzf.vim plugin for badass lightspeed functionality.įzf comes with a basic Vim plugin but its functionality is minimal, so fzf.vim was created to provide all of the functionality you would expect. fzf, however, shows no speed difference between files or tags - it’s blazingly fast either way.
Macvim customize colors guifg pro#
Ctrl-P used to do okay on a 30,000-file codebase on my 2013-era MacBook Pro but started to slow down during a search on an enormous tags file to the point of being unusable. Fuzzy-finding is so useful that it’s become a standard feature on modern text editors.įor years Ctrl-P has been the reigning fuzzy-finding champ, but a new tool, fzf, is faster and more forgiving when trying to find one file or tag among thousands. TextMate and Sublime Text showed us that the fastest way to find a file is by fuzzy finding, which means typing parts of a filename or path or tag or whatever you’re looking for, sometimes even if the characters aren’t adjacent or you making a spelling error. I also have a separate install script for updating and installing Vim plugins.
0 kommentar(er)
