I'm trying to read a directory path using ido-read-directory-name
to prompt in the minibuffer. I have (ido-everywhere t)
and (ido-enable-flex-matching t)
enabled, and I'm running emacs 24.5.1.
I expect ido-read-directory-name
to behave like ido-read-file-name
, by showing all possible flex matches in the minibuffer. I expect it to show me ONLY directory name matches (not file name matches), since I'm reading for directory names.
But instead of showing matches in the minibuffer, it shows only [.]
after the current directory match, like so /usr/bin/[.]
, which is not what I want.
If I hit TAB once, potential directory matches are displayed in a regular emacs buffer (named "Ido Completions"), as emacs normally does for Apropos, Help, describe-function matches, etc. The buffer says "Potential matches: " and displays a lonely single dot.
If I hit TAB a second time, the single dot is replaced with a full list of potential directory matches, and is displayed in the "Ido Completions" buffer as Emacs normally does. Seeing that, I can start typing a desired match, and the minibuffer will eventually match it.
Sometimes if I type a single letter in the minibuffer, and then backspace to erase it, the usual (nice) flex match display shows up, with something like this ../blah/blah/dir/{. | match1/ | match2/ | ...}
showing. From this, I'm thinking that ido-read-directory-name
knows how to properly show directory matches in the minibuffer, but for some reason is not doing it by default.
Why doesn't ido-read-directory-name
display the possible directory matches in the minibuffer? Is there some variable that I might have set wrong? (I looked at the 50? possible ido-* variables with describe-variable, but couldn't see anything. Ditto for searching the SO forums, and the net.
I love ido-read-file-name
, but ido-read-directory seems to exhibit very different behavior for me. Ideas to try, anyone? Thanks