From: storm@cua.dk (Kim F. Storm)
Cc: David Reitter <david.reitter@gmail.com>, emacs-devel@gnu.org
Subject: Re: Minibuffer change breaks ido
Date: Wed, 07 Dec 2005 10:23:29 +0100 [thread overview]
Message-ID: <m3acfdz2em.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87acfeio7e.fsf@pacem.orebokech.com> (Romain Francoise's message of "Tue, 06 Dec 2005 10:12:21 +0100")
Romain Francoise <romain@orebokech.com> writes:
> 2005-12-02 David Reitter <david.reitter@gmail.com>
>
> breaks the installation of ido's minibuffer maps: all the "magic"
> actions that ido normally binds in the minibuffer are no longer bound.
I have installed a fix to ido. Thank you.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-12-07 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 9:12 Minibuffer change breaks ido Romain Francoise
2005-12-07 9:23 ` Kim F. Storm [this message]
2005-12-07 10:22 ` Romain Francoise
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=m3acfdz2em.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=david.reitter@gmail.com \
--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).