From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Glenn Morris <rgm@gnu.org>
Cc: 9039@debbugs.gnu.org
Subject: bug#9039: 24.0.50; dired "f" fails on directory that begins with a space
Date: Wed, 13 Jul 2011 11:03:46 -0700 [thread overview]
Message-ID: <86aacihxbx.fsf@red.stonehenge.com> (raw)
In-Reply-To: <03oc0yawrg.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 13 Jul 2011 13:57:55 -0400")
>>>>> "GM" == Glenn Morris <rgm@gnu.org> writes:
GM> I've improved the manual and the doc of dired-use-ls-dired, as well
GM> as making dired give a message the first time it it used if --dired
GM> is not found to be supported. Personally, I'm inclined to close this
GM> report now.
What I'm confused about is if setting the other switch always does the
right thing (and faster, without forking), why would dired *ever* use
"ls --dired"?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
next prev parent reply other threads:[~2011-07-13 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 2:21 bug#9039: 24.0.50; dired "f" fails on directory that begins with a space merlyn
2011-07-10 2:33 ` Glenn Morris
2011-07-10 2:38 ` Randal L. Schwartz
2011-07-10 2:42 ` Glenn Morris
2011-07-10 2:45 ` Glenn Morris
2011-07-10 2:46 ` Randal L. Schwartz
2011-07-10 3:02 ` Eli Zaretskii
2011-07-10 3:08 ` Randal L. Schwartz
2011-07-13 17:57 ` Glenn Morris
2011-07-13 18:03 ` Randal L. Schwartz [this message]
2011-07-13 18:05 ` Glenn Morris
2011-07-13 18:11 ` Randal L. Schwartz
2011-07-10 4:43 ` Glenn Morris
2011-07-13 10:02 ` Manuel Giraud
2011-07-13 18:05 ` Randal L. Schwartz
2011-07-13 19:21 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86aacihxbx.fsf@red.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=9039@debbugs.gnu.org \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.