Re: IDO doesn't honor confirm-nonexistent-file-or-buffer

[storm@cua.dk (Kim F. Storm)]

Tassilo Horn <tassilo@member.fsf.org> writes:

> storm@cua.dk (Kim F. Storm) writes:
>
> Hi Kim,
>
>>> Basically yes, but I like the standard visual feedback and usage much
>>> better, e.g. no y-or-n-p but a [confirm] after the minibuffer input
>>> and another RET finds the nonexistent file or buffer.  This is not
>>> disturbing at all, while the y-or-n-p is: No matter my decision, I
>>> always have to move fingers to either y or n.
>>
>> I see - and agree.  Try the following patch instead:
>
> Yes, this is much better.  But there's one difference with the standard
> behavior.  Ido always wants a confirmation if the file or buffer doesn't
> exist.  The default setting of confirm-nonexistent-file-or-buffer is
> after-completion, and then you are asked only to confirm if the last
> command was a completion command.  The current ido behavior equivalent
> to setting this variable to t (which I do anyway).  But probably ido
> should be as compatible with the standard behavior as far as possible.

In a way ido is always trying to complete what you type, so in what 
ido command/key should after-completion apply to ?  E.g. TAB is rarely
used in ido (at least I don't use it much).

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk