← Back to Upcase

CtrlP sometimes displays === NO ENTRIES ===

I have one project which when running CtrlP 9 out of 10 times will display === NO ENTRIES === immediately before I type anything.

Has anyone experienced this before or know a way to troubleshoot this bug?

Really slows productivity within this one project.

Clearing the CtrlP cache didn’t resolve the issue.

My dotfiles can be found here; https://github.com/notrab/dotfiles

@notrab

I had this same issue for the longest time. A real productivity kill for sure.

In my case it turned out to be lines in my .agignore file causing the behavior. I’m still unclear why, but I needed to change lines referencing nested directories to include a leading forward slash. e.g., app/assets/fonts to /app/assets/fonts.

I don’t see an .agignore file in your dotfiles, so that may not be it. If nothing else, hopefully this will get you looking in the right direction.

Good luck.

1 Like

Could it be this line? It looks like it plays with the starting directory for CtrlP.

let g:ctrlp_working_path_mode = 0

Hey @notrab I was having problems with CtrlP as well and I installed fzf … which is honestly the best fuzzy finder on earth… its a lot simpler to install than command-t and works better than CtrlP I would highly recommend it!

1 Like