fzf.vim/doc/fzf-vim.txt

279 lines
11 KiB
Text
Raw Normal View History

fzf-vim.txt fzf-vim Last change: September 20 2015
2015-08-22 23:24:19 +09:00
FZF-VIM - TABLE OF CONTENTS *fzf-vim* *fzf-vim-toc*
2015-08-22 23:18:39 +09:00
==============================================================================
fzf :heart: vim
2015-08-22 23:24:19 +09:00
Rationale
Why you should use fzf on Vim
2015-08-22 23:24:19 +09:00
Installation
Commands
Customization
Mappings
Usage
Completion helper
Reducer example
License
2015-08-22 23:18:39 +09:00
FZF :HEART: VIM *fzf-vim-fzf-heart-vim*
==============================================================================
Things you can do with {fzf}{1} and Vim.
2015-08-22 23:18:39 +09:00
{1} https://github.com/junegunn/fzf
RATIONALE *fzf-vim-rationale*
==============================================================================
{fzf}{1} in itself is not a Vim plugin, and the official repository only
provides the {basic wrapper function}{2} for Vim and it's up to the users to
write their own Vim commands with it. However, I've learned that many users of
fzf are not familiar with Vimscript and are looking for the "default"
implementation of the features they can find in the alternative Vim plugins.
This repository is a bundle of fzf-based commands and mappings extracted from
my {.vimrc}{3} to address such needs. They are not designed to be flexible or
configurable, and there's no guarantee of backward-compatibility.
2015-08-22 23:18:39 +09:00
{1} https://github.com/junegunn/fzf
{2} https://github.com/junegunn/fzf#usage-as-vim-plugin
{3} https://github.com/junegunn/dotfiles/blob/master/vimrc
WHY YOU SHOULD USE FZF ON VIM *fzf-vim-why-you-should-use-fzf-on-vim*
==============================================================================
Because you can and you love fzf.
fzf runs asynchronously and can be orders of magnitude faster than similar Vim
plugins. However, the benefit may not be noticeable if the size of the input
is small, which is the case for many of the commands provided here.
Nevertheless I wrote them anyway since it's really easy to implement custom
selector with fzf.
fzf is an independent command-line program and thus requires an external
terminal emulator when on GVim. You may or may not like the experience. Also
note that fzf currently does not compile on Windows.
2015-08-22 23:18:39 +09:00
INSTALLATION *fzf-vim-installation*
==============================================================================
Using {vim-plug}{4}:
>
Plug 'junegunn/fzf', { 'dir': '~/.fzf', 'do': 'yes \| ./install' }
Plug 'junegunn/fzf.vim'
<
{4} https://github.com/junegunn/vim-plug
COMMANDS *fzf-vim-commands*
==============================================================================
2015-12-14 12:25:42 +09:00
-----------------+-------------------------------------------------------------------
2015-08-22 23:18:39 +09:00
Command | List ~
2015-12-14 12:25:42 +09:00
-----------------+-------------------------------------------------------------------
2015-08-22 23:18:39 +09:00
`Files[PATH]` | Files (similar to `:FZF` )
`GFiles [OPTS]` | Git files (git ls-files)
`GFiles?` | Git files (git status)
2015-08-22 23:18:39 +09:00
`Buffers` | Open buffers
`Colors` | Color schemes
2015-12-14 12:25:42 +09:00
`Ag[PATTERN]` | {ag}{5} search result (ALT-A to select all, ALT-D to deselect all)
`Lines [QUERY]` | Lines in loaded buffers
`BLines [QUERY]` | Lines in the current buffer
`Tags[QUERY]` | Tags in the project ( `ctags-R` )
`BTags[QUERY]` | Tags in the current buffer
2015-08-28 17:49:50 +09:00
`Marks` | Marks
`Windows` | Windows
2015-08-22 23:18:39 +09:00
`LocatePATTERN` | `locate` command output
`History` | `v:oldfiles` and open buffers
`History:` | Command history
`History/` | Search history
2015-08-22 23:18:39 +09:00
`Snippets` | Snippets ({UltiSnips}{6})
2015-09-20 02:58:14 +09:00
`Commits` | Git commits (requires {fugitive.vim}{7})
2015-09-20 14:51:06 +09:00
`BCommits` | Git commits for the current buffer
2015-09-01 00:59:06 +09:00
`Commands` | Commands
`Maps` | Normal mode mappings
`Helptags` | Help tags [1]
2016-04-03 08:48:22 +02:00
`Filetypes` | File types
2015-12-14 12:25:42 +09:00
-----------------+-------------------------------------------------------------------
2015-08-22 23:18:39 +09:00
- Most commands support CTRL-T / CTRL-X / CTRL-V key bindings to open in a new
2015-09-30 18:42:48 +09:00
tab, a new split, or in a new vertical split
2015-08-22 23:18:39 +09:00
- Bang-versions of the commands (e.g. `Ag!`) will open fzf in fullscreen
2015-09-30 18:42:48 +09:00
- You can set `g:fzf_command_prefix` to give the same prefix to the commands
- e.g. `let g:fzf_command_prefix = 'Fzf'` and you have `FzfFiles`, etc.
2015-08-22 23:18:39 +09:00
(1: `Helptags` will shadow the command of the same name from {pathogen}{8}.
But its functionality is still available via `call pathogen#helptags()`.)
2015-08-22 23:18:39 +09:00
{5} https://github.com/ggreer/the_silver_searcher
{6} https://github.com/SirVer/ultisnips
{7} https://github.com/tpope/vim-fugitive
{8} https://github.com/tpope/vim-pathogen
2015-08-22 23:18:39 +09:00
< Customization >_____________________________________________________________~
*fzf-vim-customization*
*g:fzf_action* *g:fzf_layout* *g:fzf_colors* *g:fzf_commits_log_options*
Global options~
2015-08-22 23:18:39 +09:00
>
" This is the default extra key bindings
let g:fzf_action = {
\ 'ctrl-t': 'tab split',
\ 'ctrl-x': 'split',
\ 'ctrl-v': 'vsplit' }
" Default fzf layout
2016-03-11 01:15:28 +09:00
" - down / up / left / right
let g:fzf_layout = { 'down': '~40%' }
2015-09-06 00:58:45 +09:00
2016-07-02 20:32:24 +09:00
" In Neovim, you can set up fzf window using a Vim command
let g:fzf_layout = { 'window': 'enew' }
let g:fzf_layout = { 'window': '-tabnew' }
" Customize fzf colors to match your color scheme
let g:fzf_colors =
\ { 'fg': ['fg', 'Normal'],
\ 'bg': ['bg', 'Normal'],
\ 'hl': ['fg', 'Comment'],
\ 'fg+': ['fg', 'CursorLine', 'CursorColumn', 'Normal'],
\ 'bg+': ['bg', 'CursorLine', 'CursorColumn'],
\ 'hl+': ['fg', 'Statement'],
\ 'info': ['fg', 'PreProc'],
\ 'prompt': ['fg', 'Conditional'],
\ 'pointer': ['fg', 'Exception'],
\ 'marker': ['fg', 'Keyword'],
\ 'spinner': ['fg', 'Label'],
\ 'header': ['fg', 'Comment'] }
" Enable per-command history.
" CTRL-N and CTRL-P will be automatically bound to next-history and
" previous-history instead of down and up. If you don't like the change,
" explicitly bind the keys to down and up in your $FZF_DEFAULT_OPTS.
let g:fzf_history_dir = '~/.local/share/fzf-history'
<
Command-local options~
>
2016-06-24 00:45:54 +09:00
" [Files] Extra options for fzf
" e.g. File preview using coderay (http://coderay.rubychan.de/)
let g:fzf_files_options =
\ '--preview "(coderay {} || cat {}) 2> /dev/null | head -'.&lines.'"'
2016-03-11 01:15:28 +09:00
" [Buffers] Jump to the existing window if possible
let g:fzf_buffers_jump = 1
" [[B]Commits] Customize the options used by 'git log':
let g:fzf_commits_log_options = \
'--graph --color=always --format="%C(auto)%h%d %s %C(black)%C(bold)%cr"'
" [Tags] Command to generate tags file
let g:fzf_tags_command = 'ctags -R'
2016-06-24 00:36:16 +09:00
" [Commands] --expect expression for directly executing the command
2016-06-24 00:45:54 +09:00
let g:fzf_commands_expect = 'alt-enter,ctrl-x'
<
Advanced customization using autoload functions~
You can use autoload functions to define your own commands.
>
2016-09-27 02:01:40 +09:00
" git grep
command! -bang -nargs=* GGrep
\ call fzf#vim#grep('git grep --line-number '.shellescape(<q-args>), 0, <bang>0)
" We use VimEnter event so that the code is run after fzf.vim is loaded
2015-09-25 11:45:16 +09:00
autocmd VimEnter * command! Colors
\ call fzf#vim#colors({'left': '15%', 'options': '--reverse --margin 30%,0'})
2015-08-22 23:18:39 +09:00
<
2015-08-22 23:18:39 +09:00
MAPPINGS *fzf-vim-mappings*
==============================================================================
2015-08-23 04:23:16 +09:00
---------------------------------+------------------------------------------
Mapping | Description ~
---------------------------------+------------------------------------------
<plug>(fzf-maps-n) | Normal mode mappings
<plug>(fzf-maps-i) | Insert mode mappings
<plug>(fzf-maps-x) | Visual mode mappings
<plug>(fzf-maps-o) | Operator-pending mappings
2015-08-23 04:23:16 +09:00
<plug>(fzf-complete-word) | `cat/usr/share/dict/words`
<plug>(fzf-complete-path) | Path completion using `find` (file + dir)
<plug>(fzf-complete-file) | File completion using `find`
<plug>(fzf-complete-file-ag) | File completion using `ag`
<plug>(fzf-complete-line) | Line completion (all open buffers)
<plug>(fzf-complete-buffer-line) | Line completion (current buffer only)
---------------------------------+------------------------------------------
2015-08-22 23:18:39 +09:00
< Usage >_____________________________________________________________________~
*fzf-vim-usage*
>
" Mapping selecting mappings
nmap <leader><tab> <plug>(fzf-maps-n)
xmap <leader><tab> <plug>(fzf-maps-x)
omap <leader><tab> <plug>(fzf-maps-o)
" Insert mode completion
2015-08-22 23:18:39 +09:00
imap <c-x><c-k> <plug>(fzf-complete-word)
imap <c-x><c-f> <plug>(fzf-complete-path)
imap <c-x><c-j> <plug>(fzf-complete-file-ag)
2015-08-23 04:23:16 +09:00
imap <c-x><c-l> <plug>(fzf-complete-line)
2015-09-06 00:58:45 +09:00
" Advanced customization using autoload functions
inoremap <expr> <c-x><c-k> fzf#vim#complete#word({'left': '15%'})
2015-08-22 23:18:39 +09:00
<
< Completion helper >_________________________________________________________~
*fzf-vim-completion-helper*
`fzf#complete` is a helper function for creating custom fuzzy completion using
fzf. If the first parameter is a command string or a Vim list, it will be used
as the source.
>
" Replace the default dictionary completion with fzf-based fuzzy completion
inoremap <expr> <c-x><c-k> fzf#complete('cat /usr/share/dict/words')
<
For advanced uses, you can pass an options dictionary to the function. The set
of options is pretty much identical to that for `fzf#run` only with the
following exceptions:
- `reducer` (funcref)
- Reducer transforms the output lines of fzf into a single string value
- `prefix` (string or funcref; default: `\k*$`)
2015-08-22 23:18:39 +09:00
- Regular expression pattern to extract the completion prefix
- Or a function to extract completion prefix
2015-08-22 23:18:39 +09:00
- Both `source` and `options` can be given as funcrefs that take the completion
prefix as the argument and return the final value
- `sink` or `sink*` are not allowed
Reducer example~
*fzf-vim-reducer-example*
>
function! s:make_sentence(lines)
return substitute(join(a:lines), '^.', '\=toupper(submatch(0))', '').'.'
endfunction
inoremap <expr> <c-x><c-s> fzf#complete({
\ 'source': 'cat /usr/share/dict/words',
\ 'reducer': function('<sid>make_sentence'),
\ 'options': '--multi --reverse --margin 15%,0',
\ 'left': 20})
<
LICENSE *fzf-vim-license*
==============================================================================
MIT
==============================================================================
vim:tw=78:sw=2:ts=2:ft=help:norl:nowrap: