unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: minibuffer-avoid-prompt and ido
Date: Sat, 12 Aug 2006 01:25:06 +0200	[thread overview]
Message-ID: <m31wrm26ul.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <q5gveozn6co.fsf@sfsw51.de.lucent.com> (Klaus Zeitler's message of "Fri, 11 Aug 2006 08:17:59 +0200")

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

      reply	other threads:[~2006-08-11 23:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11  6:17 minibuffer-avoid-prompt and ido Klaus Zeitler
2006-08-11 23:25 ` Kim F. Storm [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m31wrm26ul.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).