[zenspider]

I'm still not sold on ido... I'm trying it out again, but thus far there are enough annoyances that I don't think I can activate it full-time. I may, however, use their completing read function standalone tho for other things I do.

So far, I've found that autotest.el + file-cache + ffap + some advice for ffap (see my emacswiki page) does 80-90% of what I need on a daily basis.

[litewulf]

Out of curiosity, what are the annoyances you have with it?

[ajross]

I'm in the same boat. And the number one annoyance is that it's not keystroke compatible. I have the standard editting keys in my fingers for loading files (C-x C-f C-a C-k pathprefix TAB path TAB etc..). That stuff breaks with ido and I get stalled and have to compose myself and figure out what I'm doing.

Wouldn't it have been possible to preserve both the classic editability of the path string and have fuzzy matching?

[zenspider]

that is CERTAINLY some of it... wtf were they thinking when they decided to take the regular find-file TAB key and replace it with RET???

to answer the question above: it is VERY intrusive. I've finally set it up to only ever take 1 line only, but even then it is a huge departure from the norm. The key incompatibility is a huge issue. The fact that all my muscle memory (17 years) is dead using it.

I have this peculiar belief that C-x C-f RET should _always_ open the parent dir of the current buffer's file. ido threw that out the window. Now that will load the alphabetically first file in the dir. Lame.

There are others, but I don't remember them currently.