minibuffer-avoid-prompt and ido

minibuffer-avoid-prompt and ido

[Klaus Zeitler]

I've added minibuffer-avoid-prompt to minibuffer-prompt-properties with:
(setq minibuffer-prompt-properties
      (append minibuffer-prompt-properties
              (list 'point-entered 'minibuffer-avoid-prompt)))

It looks as if the normal file commands (like find-file, write-file) treat the
prompt differently as ido commands do. For example comparing write-file with
ido-write-file, in both cases the mini-buffer starts with:
"Write file: <default-directory>_"
The 'normal' write-file prompt allows to move the mouse pointer (e.g. for cut
and paste) into the default directory, but ido-write-file doesn't. Is there a
specific reason why ido doesn't allow access to the default directory?

-- 
 ------------------------------------------
|  Klaus Zeitler      Lucent Technologies  |
|  Email:             kzeitler@lucent.com  |
 ------------------------------------------
---
It is very difficult to prophesy, especially when it pertains to the future.

Re: minibuffer-avoid-prompt and ido

[Kim F. Storm]

Klaus Zeitler <kzeitler@lucent.com> writes:

> I've added minibuffer-avoid-prompt to minibuffer-prompt-properties with:
> (setq minibuffer-prompt-properties
>       (append minibuffer-prompt-properties
>               (list 'point-entered 'minibuffer-avoid-prompt)))
>
> It looks as if the normal file commands (like find-file, write-file) treat the
> prompt differently as ido commands do. For example comparing write-file with
> ido-write-file, in both cases the mini-buffer starts with:
> "Write file: <default-directory>_"
> The 'normal' write-file prompt allows to move the mouse pointer (e.g. for cut
> and paste) into the default directory, but ido-write-file doesn't. Is there a
> specific reason why ido doesn't allow access to the default directory?

Because with ido there are no trivial commands you can use to move into the prompt.

If you need this, use C-x C-w C-e to enter ido edit mode, and then
copy /paste as you like, and continue with RET.

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