| Age | Commit message (Collapse) | Author |
|---|
|
Fix #4453
|
|
|
|
Co-authored-by: Junegunn Choi <junegunn.c@gmail.com>
|
|
Close #2563
|
|
* 'pathname' is a new tiebreak option for prioritizing matches occurring
in the file name of the path.
* `--scheme=path` will automatically set `--tiebreak=pathname,length`.
* fzf will automatically choose `path` scheme when the input is a TTY device,
where fzf would start its built-in walker or run `$FZF_DEFAULT_COMMAND`
which is usually a command for listing files.
Close #4191
|
|
|
|
Close #3980
|
|
|
|
A spec can have `exit` callback that is called with the exit status of fzf.
This can be used to clean up temporary resources or restore the original
state when fzf is closed without a selection.
|
|
|
|
Co-authored-by: Junegunn Choi <junegunn.c@gmail.com>
|
|
|
|
|
|
* Git Bash Mintty: only use cmd.exe if winpty missing
Addresses https://github.com/junegunn/fzf/issues/3809
* preferably use term in Git Bash for popup window
See https://github.com/junegunn/fzf/pull/3811#issuecomment-2124241321
|
|
|
|
|
|
|
|
* make :FZF work in Vim from Git Bash
Despite its title 'Calling fzf#run with a list as source fail (n)vim is used from git bash' the issue in
https://github.com/junegunn/fzf/issues/3777
of running `:FZF` in Vim in Git Bash was apparently only fixed for Neovim in Git Bash on Windows 11, but not for Vim from Git Bash.
In view of this, replacing /C by ///C might be considered a universal fix.
This PR just proposes the patch in https://github.com/junegunn/fzf/issues/1983 that still seems open.
In view of the fourth item in the most recent 2.45.0 https://github.com/git-for-windows/build-extra/blob/main/ReleaseNotes.md#known-issues little seems to have changed regarding path conversion of arguments containing forward slashes
* prefer doubling slashed instead of generic env. var
If MSYS_NO_PATHCONV=1 is used, then all arguments are preserved, in particular possibly paths passed in s:command.
Therefore, only avoid converting `/C` from `cmd` to a path.
|
|
|
|
Fix #3777
|
|
And simplify the argument escaping code. Fix #3764.
This may breaks some existing use cases, but the mode causes too much
trouble when escaping arguments and it makes some things not possible.
# Now you can pass special characters to rg process without any escaping problems: &|<>()@^%!
fzf --ansi --disabled --bind "change:reload:rg --column --line-number --no-heading --color=always --smart-case -- {q}"
# No sudden expansion of the arguments on '!'
fzf --disabled --preview "echo {q} {n} {}" --query "&|<>()@^%!" --prompt "&|<>()@^%!"
|
|
Fix #3620
|
|
|
|
Fix #3415
|
|
Fix #3318
|
|
|
|
Co-authored-by: Pavel Sarlov <psarlov@asteasolutions.com>
Co-authored-by: Junegunn Choi <junegunn.c@gmail.com>
|
|
Prepend the border options so that the user can override them in
'options' entry of the spec.
|
|
|
|
|
|
|
|
* 'rounded' on non-Windows platforms
* 'sharp' on Windows
|
|
Instead of NormalFloat.
https://github.com/junegunn/fzf/issues/3035#issuecomment-1305094043
|
|
In Neovim, the foreground and background colors of a floating window
defaults to those of Pmenu highlight group, which yields unexpected
results.
This commit makes the colors of fzf window defaults to those of 'Normal'
group (or 'NormalFloat' if defined), by ignoring Pmenu group.
Then the colors can be configured via --color option of fzf.
NOTE: An error from setwinvar call is ignored because the exact
behavior of &winhighlight with an empty target group is not clearly
documented.
Close #3035
Close https://github.com/junegunn/fzf.vim/issues/1431
See https://github.com/neovim/neovim/pull/9722#discussion_r264777602
|
|
|
|
&shell is guaranteed to be cmd.exe on windows because we call s:use_sh()
|
|
Fix #2992
|
|
|
|
Should handle powershell.exe as well
Fix https://github.com/junegunn/fzf.vim/issues/1411
|
|
|
|
- Replace fzf#shellescape with shellescape
- Prepend command with '&' in powershell to deal with quoted exe
|
|
Fix #2877
|
|
`shellescape()` behavior is different when `shell=fish`, so we should set `shell` before calling `shellescape()`, otherwise an unexpected result may occur (e.g. https://github.com/kevinhwang91/nvim-bqf/issues/56).
Co-authored-by: Junegunn Choi <junegunn.c@gmail.com>
|
|
Fix #2676
|
|
For Vim 8.0.1831 and below
* https://github.com/vim/vim/issues/1116
Fix https://github.com/junegunn/fzf.vim/issues/1301
|
|
https://github.com/junegunn/fzf.vim/issues/1329
|
|
So that it's easier to add a sinklist function to a spec dictionary.
let spec = { 'source': source, 'options': ['--preview', preview] }
function spec.sinklist(matches)
echom string(a:matches)
endfunction
call fzf#run(fzf#wrap(spec))
|
|
See #2495
|
|
When 'down' layout was used on regular Vim on terminal, fzf would open
below the editor using `--height` option. This was the only case where
terminal buffer was not used (the code was written when Vim didn't have
builtin terminal) and this exception has been a constant source of
confusion.
This commit makes fzf open in a terminal buffer even in that case.
|
|
So that fzf can finish immediately even when the input process doesn't
handle SIGPIPE and keeps running.
Fix #2481
|
