This project is mirrored from https://github.com/junegunn/fzf.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
- Dec 13, 2019
-
-
Junegunn Choi authored
-
- Dec 12, 2019
-
-
Junegunn Choi authored
Close #1776
-
Junegunn Choi authored
-
Junegunn Choi authored
Backport https://github.com/junegunn/vim-plug/pull/913
-
- Dec 09, 2019
-
-
Junegunn Choi authored
-
- Dec 07, 2019
-
-
Junegunn Choi authored
Close #1787 Related #1364
-
- Dec 06, 2019
-
-
Junegunn Choi authored
-
Junegunn Choi authored
If the command template doesn't have any placeholder expressions. : | fzf --bind 'space:reload:seq 10'
-
Henré Botha authored
This commit fixes a bug where lines that declare multiple hostnames get omitted from completion entirely if one of the hostnames matches *. For example: Host foo.com bar.dev baz.*
-
Junegunn Choi authored
-
David Gray authored
Close #1783
-
- Dec 05, 2019
-
-
Junegunn Choi authored
Close #1707 Close #1779
-
infokiller authored
-
John Purnell authored
* Update completion.bash * Update completion.zsh
-
Junegunn Choi authored
-
- Dec 01, 2019
-
-
Junegunn Choi authored
Added NixOS instruction. Close #1731
-
midchildan authored
The zsh version of the cd widget sets the variable `dir` to the path of the target directory before invoking `cd`. This causes zsh to treat the target directory as a named directory, which has the effect of zsh substituting '%~' with '~dir' instead of the proper path when it performs prompt expansion. This commit will cause the widget to unset `dir` before redrawing the prompt to fix this issue. Details of zsh prompt expansion can be found in: http://zsh.sourceforge.net/Doc/Release/Prompt-Expansion.html
-
- Nov 29, 2019
-
-
Junegunn Choi authored
-
- Nov 23, 2019
-
-
Junegunn Choi authored
-
- Nov 21, 2019
-
-
Junegunn Choi authored
-
Junegunn Choi authored
# Note + prefix in the second bind expression fzf --bind u:up --bind u:+up fzf --bind u:up+up
-
Junegunn Choi authored
-
- Nov 16, 2019
-
-
Jan Edmund Lazo authored
-
Junegunn Choi authored
-
- Nov 15, 2019
-
-
Junegunn Choi authored
-
Junegunn Choi authored
-
Junegunn Choi authored
-
Junegunn Choi authored
Close #1699
- Nov 14, 2019
-
-
Junegunn Choi authored
Close #1738
-
Junegunn Choi authored
Close #1752
-
- Nov 13, 2019
-
-
Junegunn Choi authored
-
- Nov 12, 2019
-
-
Junegunn Choi authored
-
- Nov 11, 2019
-
-
Junegunn Choi authored
-
Marco Hinz authored
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".
-
Junegunn Choi authored
-
Junegunn Choi authored
-
Junegunn Choi authored
-
- Nov 10, 2019
-
-
Junegunn Choi authored
-
Junegunn Choi authored
# Reload input list with different sources seq 10 | fzf --bind 'ctrl-a:reload(seq 100),ctrl-b:reload(seq 1000)' # Reload as you type seq 10 | fzf --bind 'change:reload:seq {q}' --phony # Integration with ripgrep RG_PREFIX="rg --column --line-number --no-heading --color=always --smart-case " INITIAL_QUERY="" FZF_DEFAULT_COMMAND="$RG_PREFIX '$INITIAL_QUERY'" \ fzf --bind "change:reload:$RG_PREFIX {q} || true" \ --ansi --phony --query "$INITIAL_QUERY" Close #751 Close #965 Close #974 Close #1736 Related #1723
-