From: Sven Joachim <svenjoac@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 153@emacsbugs.donarmstrong.com, emacs-pretest-bug@gnu.org,
173-done@emacsbugs.donarmstrong.com, rfrancoise@debian.org
Subject: Re: 23.0.60; Minibuffer for M-x dired broken
Date: Fri, 02 May 2008 21:45:04 +0200 [thread overview]
Message-ID: <87r6ckbidb.fsf@gmx.de> (raw)
In-Reply-To: <jwvfxt0vd10.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 02 May 2008 13:20:28 -0400")
On 2008-05-02 19:20 +0200, Stefan Monnier wrote:
>>> Start Emacs somewhere, e.g. in your home directory, and type C-x d
>>> /usr. The original part of the filename is not greyed out as it's
>>> supposed to be with file-name-shadow-mode enabled, and if you press RET,
>>> you get an error message:
>>>
>>> Reading directory: no such file or directory, /home/sven/usr
>
> Thanks, should be fixed now,
Yes, thank you (closing bug #173). BTW, I just discovered your comments
on bug #153. They missed me because
a) you did not CC me, and I am not subscribed to the Emacs bug tracker;
b) I did not even know that I submitted a bug report (it was just a
question sent to emacs-devel, and you seem to have resent it to
submit@emacsbugs.donarmstrong.com).
I do quite like the latest completion code, but can imagine that other
people might find it a bit confusing. Also, if a directory has no
non-trivial subdirectories, C-x d TAB completes to . and .., which is
probably less useful than immediately listing all possible file name
completions.
Sven
next prev parent reply other threads:[~2008-05-02 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 5:43 23.0.60; Minibuffer for M-x dired broken Sven Joachim
2008-05-01 6:28 ` Sven Joachim
2008-05-02 17:20 ` Stefan Monnier
2008-05-02 19:45 ` Sven Joachim [this message]
2008-05-03 1:25 ` Stefan Monnier
2008-05-13 5:18 ` Stefan Monnier
2008-05-13 6:44 ` Sven Joachim
[not found] ` <87ej86hfdp.fsf@gmx.de>
2008-05-13 8:40 ` Stefan Monnier
2008-05-13 9:01 ` Sven Joachim
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=87r6ckbidb.fsf@gmx.de \
--to=svenjoac@gmx.de \
--cc=153@emacsbugs.donarmstrong.com \
--cc=173-done@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rfrancoise@debian.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).