| Age | Commit message (Collapse) | Author |
|
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
|
|
Fix #1205
|
|
Close #1172
|
|
The issue is fixed in https://github.com/vim/vim/commit/1232624ae5b56c167c5982a2620f736c4bbc19ef
|
|
Close #1152
msys2 terminal Vim assumes that it runs in mintty
so `:terminal` uses `TERM=xterm`.
fzf doesn't support `TERM=xterm` on Windows.
|
|
Close #1066
Close #1068
|
|
Close #1055
|
|
Prevents the following case:
before pathshorten - /usr/bin
after pathshorten - /u/bin
piped to cmd.exe - U:/bin
|
|
Port of https://github.com/junegunn/fzf.vim/commit/e7928d154aad71e530daf5c17733275da5732680
Since :FZF does not enable preview window, we determine based on full
&columns instead of &columns / 2.
|
|
Temporary workaround for non-Windows environment
Reference:
https://github.com/vim/vim/issues/1998
https://github.com/junegunn/fzf/pull/1019#issuecomment-327008348
|
|
IMPORTANT:
cmd.exe and powershell are fine in default Windows terminal.
cmd.exe prompt is broken on ConEmu because it natively supports ucs-2 only.
utf-16 support is exclusive to .Net (ie. powershell).
utf-8 supports requires chcp, external program, but does not fix the cmd.exe prompt.
Use powershell on ConEmu to avoid corrupted text on display
|
|
Requirements:
- compiled with +terminal
- has patch-8.0.995
- has('gui_running') returns 1
|
|
|
|
Original Patch: https://github.com/junegunn/fzf/commit/a9bf29b65ec36d9caa7298aad0322fba8cb3e130
|
|
|
|
Close #1031
|
|
Previously a command like `echo a && echo b` would get transformed into
`echo a && echo b | fzf`, which only pipes the output of the second
command. Adding parentheses around the source command avoids this issue,
and works on both Unix and Windows.
|
|
Close #1023
|
|
|
|
https://github.com/junegunn/fzf.vim/issues/185
|
|
Close #1005
|
|
Close #1000
|
|
https://github.com/junegunn/fzf.vim/issues/396#issuecomment-317214036
One can override the setting on FileType fzf autocmd.
|
|
Fix https://github.com/junegunn/fzf.vim/issues/404
Thanks to @janlazo.
|
|
Related: #960 (relative filepaths)
|
|
Related #960, #552
|
|
See https://github.com/junegunn/fzf/pull/933#discussion_r120011934
Close https://github.com/junegunn/fzf.vim/pull/386
|
|
|
|
|