This displays the buffer(s) in this case, which is useful when FZF got
stuck, and you have to manually remove the buffer.

https://github.com/junegunn/fzf.vim/issues/327
https://github.com/junegunn/fzf.vim/issues/317

Close https://github.com/junegunn/fzf.vim/issues/308

- call fzf#run({'source': "echo '!'"})
- call fzf#run({'source': "echo '!'", 'down': '40%'})

Close https://github.com/junegunn/fzf.vim/issues/315

Close #847. Patch submitted by @wontoncc.

Close https://github.com/junegunn/fzf.vim/issues/309

To override --height option in FZF_DEFAULT_OPTS

Exposing the `b:fzf` variable will be useful to get information about
which command is being executed on the current fzf window. With that,
now, it's possible to use the current command name on the statusline:

```viml
au User FzfStatusLine call <SID>fzf_statusline()

function! s:fzf_statusline()
  let fzf_cmd_name = get(b:fzf, 'name', 'FZF')
  let &l:statusline = '> '.fzf_cmd_name
endfunction
```

https://github.com/junegunn/fzf.vim/issues/296

Also revert the workaround in Vim plugin introduced in fa7c8977.

Related: #814

Close #814

Not grouping commands to avoid errors on non-standard shells.

Later versions of Vim/Nvim handle `:edit <dir>` inside try-catch.

https://github.com/vim/vim/commit/e13b9afe1283f5ae43232b5992372a0eb570666c
https://github.com/vim/vim/pull/1375

- Use noshellslash for strict path expansion in fzf#run and s:cmd
  (shellescape depends on shellslash)
- Double-quote the fzf command for cmd.exe
- Add fzf#shellescape to encapsulate the logic
- Close #786

With a `bufhidden=wipe` buffer (e.g. vim-startify) the buffer would not
exist anymore, resulting in an error.

Close https://github.com/junegunn/fzf.vim/issues/265

Close #711

Close #699

Related #642

Fix #520
Fix junegunn/fzf.vim#42

fzf#wrap([name string,] [opts dict,] [fullscreen boolean])

Fix #183

Close junegunn/fzf.vim#173 and #630