From: "Robert I. Eachus" <rieachus@comcast.net>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 8181@debbugs.gnu.org
Subject: bug#8181: 23.2; Dired on Windows 7
Date: Sat, 05 Mar 2011 19:40:34 -0500 [thread overview]
Message-ID: <4D72D802.7080805@comcast.net> (raw)
In-Reply-To: <AANLkTikmpAkuVX2AMq5OzegWjDBtSzogkNwJJhTkeh0O@mail.gmail.com>
On 3/5/2011 7:08 PM, Lennart Borgman wrote:
> On Sat, Mar 5, 2011 at 11:55 PM, Robert I. Eachus<rieachus@comcast.net> wrote:
>> Choosing Open Directory from the File menu opens a standard (Windows 7)
>> window that allows you to walk the directory tree, but there is no way
>> to open a directory in dired mode that I can find. Cx d on the other
>> hand opens an emacs buffer in dired mode. (Normal behavior)
> See `use-file-dialog'
Thanks for the quick answer, but I think you may be missing the point.
First the File menu choice Open Directory, says that the keyboard
equivalent is C-x d. But the two are completely different in behavior.
Second, if you do use the menu option, there is no way to select a
directory, even though you can navigate through them.
I ran into this by accident, browsing through a large C source library.
I used Cx d nine times (or a dozen) before I went to use the menu since
I had a cup in my left hand. I then wanted to see if I would get a
dired buffer when I selected a directory, but instead I found that there
is either no way to select a directory, or the choice gets silently lost.
It is not a big deal for me. Even if I am drinking something hot, I can
type Cx d with my right hand. If nothing gets done I may submit a fix
sometime when I am not in the process of digesting the source of a
different application.
next prev parent reply other threads:[~2011-03-06 0:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 4:15 bug#8191: Patch to fix bug#8181: 23.2; Dired on Windows 7 Ben Key
2011-03-07 5:37 ` bug#8181: " Juanma Barranquero
2011-03-07 15:56 ` Ben Key
2011-03-07 18:06 ` Juanma Barranquero
2011-03-07 19:54 ` Juanma Barranquero
2011-03-07 20:16 ` Chong Yidong
2011-03-07 20:24 ` Juanma Barranquero
2011-03-07 20:59 ` Chong Yidong
2011-03-07 21:17 ` Juanma Barranquero
2011-03-05 22:55 ` Robert I. Eachus
2011-03-06 0:08 ` Lennart Borgman
2011-03-06 0:40 ` Robert I. Eachus [this message]
2011-03-06 0:42 ` Lennart Borgman
2011-03-06 3:30 ` Juanma Barranquero
2011-03-07 14:19 ` Jason Rumney
2011-03-06 13:14 ` Dani Moncayo
2011-03-06 14:17 ` Eli Zaretskii
2011-03-06 16:04 ` Ben Key
2011-03-06 20:28 ` Juanma Barranquero
2011-03-07 14:31 ` Jason Rumney
2011-03-07 16:19 ` Ben Key
2011-03-07 18:09 ` Juanma Barranquero
2011-03-07 23:04 ` Jason Rumney
2011-03-07 14:28 ` Jason Rumney
[not found] ` <handler.8181.D8181.129953268524792.notifdone@debbugs.gnu.org>
2011-03-08 1:58 ` bug#8181: closed (Re: bug#8181: Patch to fix bug#8181: 23.2; Dired on Windows 7) Robert I. Eachus
2011-03-08 2:24 ` Juanma Barranquero
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=4D72D802.7080805@comcast.net \
--to=rieachus@comcast.net \
--cc=8181@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
/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).