Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead of drawing the window border in Vim using an extra window,
extend the --border option so that we do can it natively.
Close #2223
Fix #2184
|
|
The new default is
{ 'window' : { 'width': 0.9, 'height': 0.6, 'highlight': 'Normal' } }
The default highlight group for the border of the popup window is
'Comment', but 'Normal' seems to be a safer choice.
If you prefer the previous default, add this to your Vim configuration file:
let g:fzf_layout = { 'down': '40%' }
(fzf will fall back to this if popup window is not supported)
|
|
|
|
Fix https://github.com/junegunn/fzf.vim/issues/1116
|
|
|
|
Preserve current directory in case current directory is changed by others
after the call of s:open
Co-authored-by: Junegunn Choi <junegunn.c@gmail.com>
|
|
Fix #2093
And we'll phase out height specification with `~` prefix.
|
|
Vim 8.1.2371
https://github.com/vim/vim/commit/05ad5ff0ab34ed9a5296dedd420ca81698b8ce22
Nvim 0.4.0
https://github.com/neovim/neovim/commit/9a1675b065394734ddaef91a314896028e2b1d46
|
|
Fix #2087
|
|
* No need to restore &wfw and &wfh when using popup window
Co-authored-by: lacygoill <lacygoill@lacygoill.me>
Co-authored-by: Junegunn Choi <junegunn.c@gmail.com>
|
|
Fix #2038
|
|
e.g.
if exists('$TMUX')
let g:fzf_layout = { 'tmux': '-p90%,60%' }
else
let g:fzf_layout = { 'window': { 'width': 0.9, 'height': 0.6 } }
endif
|
|
Invoking fzf from an existing Vim popup terminal is a special case.
It requires some new code to avoid E994 from being raised and the user
being stuck in a non-closable popup window.
Fix #1916
|
|
Fix #1418
e.g.
call fzf#run({'source': [1, 2, 3], 'down': '~50%', 'options': "--border --header $'1\n2'"})
|
|
https://github.com/junegunn/fzf.vim/issues/943
https://github.com/junegunn/fzf.vim/issues/959
|
|
Close #1874
|
|
|
|
|
|
e.g.
let g:fzf_layout = { 'window': { 'width': 0.4, 'height': 1, 'xoffset': 0, 'border': 'right' } }
let g:fzf_layout = { 'window': { 'width': 0.4, 'height': 1, 'xoffset': 1, 'border': 'left' } }
let g:fzf_layout = { 'window': { 'width': 1, 'height': 0.5, 'yoffset': 1, 'border': 'top' } }
let g:fzf_layout = { 'window': { 'width': 1, 'height': 0.5, 'yoffset': 0, 'border': 'bottom' } }
|
|
Revert the change introduced in #552. It seems that the startup time
difference between bash and fish is not much of an issue now.
> time bash -c 'date'
Thu Feb 13 21:15:03 KST 2020
real 0m0.008s
user 0m0.003s
sys 0m0.003s
> time fish -c 'date'
Thu Feb 13 21:15:05 KST 2020
real 0m0.014s
user 0m0.007s
sys 0m0.006s
When we explicitly *pipe* $FZF_DEFAULT_COMMAND instead of making fzf
internally start the process ($FZF_DEFAULT_COMMAND | fzf), fzf may hang
if the input process doesn't quickly process SIGPIPE and abort.
Also, fzf#vim#grep temporarily swaps $FZF_DEFAULT_COMMAND instead of
setting 'sink' so fzf can kill the default command on 'reload'.
https://github.com/junegunn/fzf.vim/issues/927
However, because of the "pipe conversion", the trick wasn't working as
expected.
https://github.com/junegunn/fzf.vim/blob/467c3277884240f7b5430f8f4d600e3415c38f3b/autoload/fzf/vim.vim#L720-L726
We can go even further and always set $FZF_DEFAULT_COMMAND instead of
piping source command.
|
|
Credits to @jiangjianshan
|
|
Close #1856
Close #1857
|
|
|
|
Close https://github.com/junegunn/fzf.vim/issues/942
|
|
|
|
e.g.
let g:fzf_layout = { 'window': { 'width': 0.9, 'height': 0.6 } }
Based on the code from https://github.com/junegunn/fzf.vim/issues/821#issuecomment-581273191
by @lacygoill.
|
|
|
|
|
|
Truecolor does not work on default Windows terminal.
It is a problem in neovim GUIs.
https://github.com/sainnhe/edge/issues/5#issuecomment-565748240
|
|
* Add MSYS2 support as a vim plugin
Add &shellcmdflag and TERM environment variable treatment.
- Make &shellcmdflag `/C` when &shell turns into `cmd.exe`
- Delete %TERM% environment variable before fzf execution
* Change shellescape default value depending on s:is_win flag
* Make TERM environment empty only when gui is running
* Stop checking &shell in fzf#shellescape function
This funcion's behavior is controlled by only if it is Windows or not.
So there is no need to check &shell.
* Take neovim into consideration when to set shellcmdflag
* Add &shellxquote control
|
|
Backport https://github.com/junegunn/vim-plug/pull/913
|
|
In recent Nvim versions, an "Error running ..." message is shown even for normal
use cases, such as:
:Files
<c-\><c-n>
:close
Closing the window will :bwipeout! the terminal buffer, because fzf sets
bufhiden=wipe.
When deleting the terminal buffer while fzf is still running, Nvim sends SIGHUP.
This happens for quite some time already, but the bug only manifests since this
commit:
https://github.com/neovim/neovim/commit/939d9053b
It's The Right Thing to do when the application exited due to a signal.
Before that commit, no "Error running ..." message was shown, because 1 (instead
of 128 + 1 == SIGHUP) was returned which the exit handler in fzf.vim treats as
"NO MATCH".
|
|
https://github.com/junegunn/vim-plug/pull/891
|
|
https://github.com/junegunn/vim-plug/pull/888
|
|
By @gh4w and @janlazo
See https://github.com/junegunn/vim-plug/commit/68b31a4a66ec945ff299db25a8a6382cd48edf14
|
|
Fix https://github.com/junegunn/fzf.vim/issues/855
|
|
(i.e. spawn xterm)
|
|
Close #1539
|
|
Close #1535
|
|
Close #1356
Related:
- #612
- https://github.com/junegunn/fzf.vim/issues/308
|
|
Close #1085
Close #1086
Close https://github.com/junegunn/fzf.vim/issues/678
|
|
Close #1288
|
|
Close #1268
|