Because this release will have some documentation changes, I'll be working on a non-master branch. Tests are welcome.

Native --tmux integration

• Implement native tmux integration #3787

# --tmux [center|top|bottom|left|right][,SIZE[%]][,SIZE[%]]

# Center, 50% width 50% height
fzf --tmux center

# Center, 80% width and height
fzf --tmux 80%

# Center ,100% width and 50% height
fzf --tmux 100%,50%

# Left, 40% width
fzf --tmux left,40%

# Left, 40% width, 90% height
fzf --tmux left,40%,90%

# Top, 40% height
fzf --tmux top,40%

# Top, 90% height, 40% height
fzf --tmux top,90%,40%

New defaults for pointer and marker

fzf --tmux 30% --multi

fzf --tmux 30% --multi --color gutter:-1

fzf --tmux 30% --multi --no-color

• The previous defaults (>) wouldn't look nice with multi-line display
• These Unicode bars look nice with or without the gutter and feel kind of modern

Multi-line display of multi-line items

rg -p bash | perl -0777 -pe 's/\n\n/\n\0/gm' | fzf --read0 --ansi --multi --highlight-line --reverse --tmux 70%

Following NO_COLOR protocol

• https://no-color.org/

If $NO_COLOR environment variable is set to a non-empty value, fzf will default to --no-color mode.

Git bash (mintty) support

fzf now works on Git bash out of the box via winpty. However, --height option doesn't work.

Embedded man page

You can run fzf --man to see the man page. This simplifies the distribution.

Windows terminals don't seem to render ▏ correctly. Going to use │ for marker instead.

apply -n2..,.. only when there are numbers

Do you think my earlier comment about the marker is an issue, or should it be left to the user to change the marker in their FZF_DEFAULT_OPTS?

#3807 (comment)

The problem is only reproducible when using the font you mentioned, which has to be installed manually, right? If that's the case, I think it's fine, and we should probably report the problem to the font maintainers.

I'm just guessing here, but most people who care enough about their terminal experience to even install a custom font are probably using different terminal emulators.

The problem is only reproducible when using the font you mentioned, which has to be installed manually, right?

Right, but I did not test all of them, just a random sample. The one mentioned remains the only one.

Increasing the line spacing also fixed it for me.