| Age | Commit message (Collapse) | Author |
|
|
|
Close #4272
|
|
|
|
Close #4256
|
|
|
|
|
|
https://github.com/junegunn/fzf/pull/4231#issuecomment-2646067669
|
|
https://github.com/junegunn/fzf/pull/4231#issuecomment-2646063208
|
|
(#4231)
Close #4185
|
|
This option can be used to replace a sed or awk in the post-processing step.
ps -ef | fzf --multi --header-lines 1 | awk '{print $2}'
ps -ef | fzf --multi --header-lines 1 --accept-nth 2
This may not be a very "Unix-y" thing to do, so I've always felt that fzf
shouldn't have such an option, but I've finally changed my mind because:
* fzf can be configured with a custom delimiter that is a fixed string
or a regular expression.
* In such cases, you'd need to repeat the delimiter again in the
post-processing step.
* Also, tools like awk or sed may interpret a regular expression
differently, causing mismatches.
You can still use sed, cut, or awk if you prefer.
Close #3987
Close #1323
|
|
|
|
|
|
|
|
Close #2890
Close #1396
You can't type in queries in this mode, and the only way to trigger an
fzf search is to use `search(...)` action.
# Click header to trigger search
fzf --header '[src] [test]' --no-input --layout reverse \
--header-border bottom --input-border \
--bind 'click-header:transform-search:echo ${FZF_CLICK_HEADER_WORD:1:-1}'
|
|
|
|
e.g. {q:1}, {q:2..}
|
|
|
|
Close #4206
|
|
|
|
Close #4202
|
|
|
|
* '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
|
|
|
|
Examples:
# Border only around the header from --header-lines
seq 10 | fzf --header 'hello' --header-lines 2 --header-lines-border
# Both headers with borders
seq 10 | fzf --header 'hello' --header-lines 2 --header-border --header-lines-border
# Use 'none' to still separate two headers but without a border
seq 10 | fzf --header 'hello' --header-lines 2 --header-border --header-lines-border none --list-border
|
|
|
|
Color inheritance: border >> list-border >> gap-line
|
|
|
|
|
|
Close #4183
|
|
|
|
Example:
# Start with --nth 1, then 2, then 3, then back to the default, 1
echo 'foo foobar foobarbaz' | fzf --bind 'space:change-nth(2|3|)' --nth 1 -q foo
Close #4172
Close #3109
|
|
|
|
|
|
It draws a single line between the preview window and the rest of the
interface. i.e. automatically choose between 'left', 'right', 'top', and
'bottom' depending on the position of the preview window.
|
|
Close #4159
|
|
This commit adds the `border-native` resulting in the following:
```
--tmux[=[center|top|bottom|left|right][,SIZE[%]][,SIZE[%]][,border-native]]
```
By default, when not specified, the `-B` flag is passed to the
`tmux popup-window` command such that no border is drawn around
the tmux popup window.
When the `border-native` option is present, the `-B` flag is omitted
and the popup window is drawn using the border style configured in
the tmux config file.
Fixes #4156
Signed-off-by: Andreas Auernhammer <github@aead.dev>
Co-authored-by: Junegunn Choi <junegunn.c@gmail.com>
|
|
Close #4154
|
|
Close #4148
|
|
|
|
|
|
Co-authored-by: Martin Sabathier <martin.sabathier.ext@corys.fr>
Co-authored-by: Junegunn Choi <junegunn.c@gmail.com>
|
|
Close #4098
|
|
|
|
|
|
|
|
* fzf: Allow '{n}' to be used as the OFFSET in the preview-window flag
* man: Document using '{n}' as the OFFSET in the preview-window flag
|
|
|
|
|
|
fzf --preview 'seq 1000' --preview-window noinfo
Close #2525
|
|
|