Garbled view when using FZF with additional qf formatter plugin

[ajitid]

Neovim version (nvim -v | head -n1)

NVIM v0.7.0-dev+1109-gfaeff49cb

Operating system/version

Ubuntu 21.04 on WSL2

How to reproduce the issue

1. Install https://gitlab.com/yorickpeterse/nvim-pqf
2. Put items in quick fix list

3. Now open fzf using zf keybinding

Expected behavior

Text in FZF list should be same as what we see in quick fix list

Actual behavior

Garbled text is being seen (notice many {m, [m and numbers across the list)

This, as you previously mentioned, could be related to concealing.

[kevinhwang91]

The reason is nvim-pqf using conceal to hide {}<> chars. The items as a source for fzf is not supported conceal for now, I will try to fix if I have times.

[kevinhwang91]

Please try dev branch.

[ajitid]

I can still see those messy characters. Here's the output:

[kevinhwang91]

Make sure you have changed the dev branch and updated the code. I have tested under clean ENV with docker is fine, only load nvim-bqf, fzf and nvim-pqf.git.

[ajitid]

What docker image did you use?

[kevinhwang91]

anatolelucet/neovim:0.6.0

[ajitid]

Can confirm bqf dev branch works fine w/ standalone image, it must be something in my config. Thanks for resolving it!

[kevinhwang91]

Waiting for your solution, maybe some potential bugs I haven't thought about.

[ajitid]

@kevinhwang91 so I removed all other plugins, even removed the whole config, updated fzf, updated neovim — but I still couldn't reproduce the right behavaior on my machine, Guess I'll have to adjust to it 🤷‍♂️

[kevinhwang91]

I also can't reproduce the screenshot you provided. main branch only with the issue for extra {, I think you should check out the fzf and your terminal ansi escape code.

FYI: you can debug bqf by yourself if you want.

1. tail -f ~/.cache/nvim/bqf.log
2. Add log.warn(processed_line) under */nvim-bqf/lua/bqf/filter/fzf.lua:172
3. BQF_LOG=warn nvim and reproduce the issue and get the log.

[ajitid]

So the culprit was my default shell, Fish. I did chsh and switched to bash and now it works fine.

Oddly, when I switched to fish from bash, it worked too. I have dozens of stuff configured in Fish, it could be one of startup settings

[kevinhwang91]

Thanks for your feedback, I have merged the patch.

[wodesuck]

@ajitid I found that should be a bug of fzf, and I fix it in junegunn/fzf#2828

[ajitid]

Oh, thank you so much @wodesuck!