ctrlpvim / ctrlp.vim

Active fork of kien/ctrlp.vim—Fuzzy file, buffer, mru, tag, etc finder.
ctrlpvim.github.com/ctrlp.vim
Other
5.56k stars 259 forks source link

Some files don't show up #398

Open ulidtko opened 6 years ago

ulidtko commented 6 years ago

Many of my files have stopped appearing in the list.

At all.

^D, clearing cache, skimming around the README and guides... No remedy yet!

They are there, on the filesystem, find finds them in two seconds.

== NO ENTRIES == in ctrlp.vim.

How do I even start troubleshooting this? What means of debug do you have?

Why in the world do I stumble upon deleted comments in sorta-relevant issues like #387 ?

Is this repo okay and well??

mattn commented 6 years ago

No your informations. Please show me way to reproduce. directory structure,and files, OS, version of vim.

On 9/1/17, Maxim Ivanov notifications@github.com wrote:

Many of my files have stopped appearing in the list.

At all.

^D, clearing cache, skimming around the README and guides... No remedy yet!

They are there, on the filesystem, find finds them in two seconds.

== NO ENTRIES == in ctrlp.vim.

How do I even start troubleshooting this? What means of debug do you have?

Why in the world do I stumble upon deleted comments in sorta-relevant issues like #387 ?

Is this repo okay and well??

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/ctrlpvim/ctrlp.vim/issues/398

--

ulidtko commented 6 years ago

Do you expect me to dump the whole project tree in here or what. It's kinda confidential, y'know?

OS - no problem, Ubuntu 16.04.3 x86_64.

:version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:44:48)
Included patches: 1-1689
Extra patches: 8.0.0056
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by pkg-vim-maintainers@lists.alioth.debian.org
Huge version without GUI.  Features included (+) or not (-):
+acl             -clipboard       +dialog_con      +file_in_path    +job             +menu            -mouse_sysmouse  +persistent_undo +scrollbind      -tcl             +visual          -xim
+arabic          +cmdline_compl   +diff            +find_in_path    +jumplist        +mksession       +mouse_urxvt     +postscript      +signs           +terminfo        +visualextra     -xsmp
+autocmd         +cmdline_hist    +digraphs        +float           +keymap          +modify_fname    +mouse_xterm     +printer         +smartindent     +termresponse    +viminfo         -xterm_clipboard
-balloon_eval    +cmdline_info    -dnd             +folding         +langmap         +mouse           +multi_byte      +profile         +startuptime     +textobjects     +vreplace        -xterm_save
-browse          +comments        -ebcdic          -footer          +libcall         -mouseshape      +multi_lang      -python          +statusline      +timers          +wildignore      -xpm
++builtin_terms  +conceal         +emacs_tags      +fork()          +linebreak       +mouse_dec       -mzscheme        +python3         -sun_workshop    +title           +wildmenu
+byte_offset     +cryptv          +eval            +gettext         +lispindent      +mouse_gpm       +netbeans_intg   +quickfix        +syntax          -toolbar         +windows
+channel         +cscope          +ex_extra        -hangul_input    +listcmds        -mouse_jsbterm   +packages        +reltime         +tag_binary      +user_commands   +writebackup
+cindent         +cursorbind      +extra_search    +iconv           +localmap        +mouse_netterm   +path_extra      +rightleft       +tag_old_static  +vertsplit       -X11
-clientserver    +cursorshape     +farsi           +insert_expand   -lua             +mouse_sgr       -perl            -ruby            -tag_any_white   +virtualedit     -xfontset
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim        -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl     -L/usr/lib/python3.5/config-3.5m-x86_64-li
nux-gnu -lpython3.5m -lpthread -ldl -lutil -lm

One of the problematic filenames is nothing really special: two files src/apps/rest_api/commands/status/GetStatusCommand.{cc,hh} relative to project root at $PWD.

I stand in there at the root, run bare vim hoping for a quick-open of this rather long-ish pathname, hit Ctrl P, wait a bit, type GetStatus and get == NO ENTRIES ==. Peculiarly, while I wait, the little counter goes 171, then 2664, then disappears. Every run the same numbers. I think I can remember (but don't take my memory for a fact), that some months earlier, while this all worked alright, the counter went way over 4000 something.

Can I somehow inspect the cached filelist of the plugin? Or enable debug traces, I dun'know. Apparently the filelist gets incomplete, but no idea how or why.

mattn commented 6 years ago

No, only filenames.

On 9/14/17, Maxim Ivanov notifications@github.com wrote:

Do you expect me to dump the whole project tree in here or what. It's kinda confidential, y'know?

OS - no problem, Ubuntu 16.04.3 x86_64.

:version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 24 2016 16:44:48)
Included patches: 1-1689
Extra patches: 8.0.0056
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by pkg-vim-maintainers@lists.alioth.debian.org
Huge version without GUI.  Features included (+) or not (-):
+acl             -clipboard       +dialog_con      +file_in_path    +job
        +menu            -mouse_sysmouse  +persistent_undo +scrollbind
-tcl             +visual          -xim
+arabic          +cmdline_compl   +diff            +find_in_path
+jumplist        +mksession       +mouse_urxvt     +postscript      +signs
        +terminfo        +visualextra     -xsmp
+autocmd         +cmdline_hist    +digraphs        +float           +keymap
        +modify_fname    +mouse_xterm     +printer         +smartindent
+termresponse    +viminfo         -xterm_clipboard
-balloon_eval    +cmdline_info    -dnd             +folding         +langmap
        +mouse           +multi_byte      +profile         +startuptime
+textobjects     +vreplace        -xterm_save
-browse          +comments        -ebcdic          -footer          +libcall
        -mouseshape      +multi_lang      -python          +statusline
+timers          +wildignore      -xpm
++builtin_terms  +conceal         +emacs_tags      +fork()
+linebreak       +mouse_dec       -mzscheme        +python3
-sun_workshop    +title           +wildmenu
+byte_offset     +cryptv          +eval            +gettext
+lispindent      +mouse_gpm       +netbeans_intg   +quickfix        +syntax
        -toolbar         +windows
+channel         +cscope          +ex_extra        -hangul_input
+listcmds        -mouse_jsbterm   +packages        +reltime
+tag_binary      +user_commands   +writebackup
+cindent         +cursorbind      +extra_search    +iconv
+localmap        +mouse_netterm   +path_extra      +rightleft
+tag_old_static  +vertsplit       -X11
-clientserver    +cursorshape     +farsi           +insert_expand   -lua
        +mouse_sgr       -perl            -ruby            -tag_any_white
+virtualedit     -xfontset
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H   -Wdate-time  -g -O2 -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1
Linking: gcc   -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now
-Wl,--as-needed -o vim        -lm -ltinfo -lnsl  -lselinux  -lacl -lattr
-lgpm -ldl     -L/usr/lib/python3.5/config-3.5m-x86_64-li
nux-gnu -lpython3.5m -lpthread -ldl -lutil -lm

One of the problematic filenames is nothing really special: two files src/apps/rest_api/commands/status/GetStatusCommand.{cc,hh} relative to project root at $PWD.

I stand in there at the root, run bare vim hoping for a quick-open of this rather long-ish pathname, hit Ctrl P, wait a bit, type GetStatus and get == NO ENTRIES ==. Peculiarly, while I wait, the little counter goes 171, then 2664, then disappears. Every run the same numbers. I think I can remember (but don't take my memory for a fact), that some months earlier, while this all worked alright, the counter went way over 4000 something.

Can I somehow inspect the cached filelist of the plugin? Or enable debug traces, I dun'know. Apparently the filelist gets incomplete, but no idea how or why.

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/ctrlpvim/ctrlp.vim/issues/398#issuecomment-329400671

--

i-give-up commented 6 years ago

Hm perhaps there's something going on with one of the following