Weird tags (<bi>, <bn>, <bp>) in CtrlPBuffer list

[danielbprice]

This has to be user error but I'm stumped. I'm new to ctrl-p, as I'm looking for something to help manage buffers more easily. When I run :CtrlPBuffer the output is "marked up" with HTML-type tags. I don't know why, or how to make them go away. I'm on debian stretch with vim version 8.0.707. Here is what it looks like:

I've cut my .vimrc back to an empty file and the problem persists.

I'm running ctrlp from commit:

commit 88abbcb926a415b789ff648cbdc86ed4b353bfc1
Merge: 8db39ec d62bbc5
Author: mattn <mattn.jp@gmail.com>
Date:   Mon Jan 15 18:31:49 2018 +0900

I'm using vim8 'pack' package management, and this is the only plugin I have.

[mattn]

Do you use ctrlp_user_command?

[DmitryBochkarev]

@mattn I have the same issue with neovim. ctrlp_user_command is not set.
I disabled manually s:has_conceal in https://github.com/ctrlpvim/ctrlp.vim/blob/master/autoload/ctrlp.vim?utf8=%E2%9C%93#L175 now it works.

[npupko]

@mattn I have the same issue with simple init.vim:

call plug#begin()
  Plug 'ctrlpvim/ctrlp.vim'
call plug#end()
syntax off

It becomes difficult to use the plugin. Maybe I can help with solving this problem?

commit 43cc73b8e7d4ab45f17118573eb81fd45704b989
Author: Takahiro Yoshihara <tacahiroy@gmail.com>
Date:   Thu Jun 28 09:15:34 2018 +0900

[mattn]

Could you please show me your tags file?

[npupko]

@mattn I do not quite understand how this is connected. Are you talking about the files that I generate with the ctags command? I have different files for different projects (obviously). Or we are talking about different things?

[mattn]

I still not understand how to reproduce.

[npupko]

@mattn
Just create new vimrc only with CtrlP plugin and without syntax highlighting (‘syntax off’). Open a pair of any buffers, and select the buffers tab.
You will see these weird tags

[mattn]

I don't see it. Do you use neovim? What version?

[npupko]

@mattn

OS: MacOS High Sierra
Tmux 2.7 + iTerm 2
NVIM v0.3.1
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/mac/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/tmp/neovim-20180721-48604-1emkq4l/neovim-0.3.1/build/config -I/tmp/neovim-20180721-48604-1emkq4l/neovim-0.3.1/src -I/usr/local/include -I/usr/local/opt/gettext/include -I/usr/include -I/tmp/neovim-20180721-48604-1emkq4l/neovim-0.3.1/build/src/nvim/auto -I/tmp/neovim-20180721-48604-1emkq4l/neovim-0.3.1/build/include
Compiled by brew@HighSierra.local

Features: +acl +iconv +jemalloc +tui

[danielbprice]

@npupko I feel your pain. I reported this originally, and for me it doesn't happen anymore. (I'm still on debian stretch, still running vim 8.0.707). I'm not sure what I changed, because I didn't notice right away when it got fixed. For what it's worth, for a long time I had my ~/.vim behind a symlink, and that caused a lot of weird and subtle problems for several different plugins. So if by chance you have that, I'd try getting rid of it.

[mattn]

@npupko do you use older version?

it seems to be fixed in #445 already.

[npupko]

@mattn As I said above, I use only latest versions
#419 (comment)

[mattn]

@npupko I mean what version of neovim do you use.

[npupko]

@mattn I use Neovim 0.3.1
#419 (comment)