From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: jidanni@jidanni.org, 9301@debbugs.gnu.org
Subject: bug#9301: dired-sort-toggle-or-edit should also mention -o and -g
Date: Sun, 11 Sep 2011 17:50:45 +0200 [thread overview]
Message-ID: <m24o0jgjsa.fsf@igel.home> (raw)
In-Reply-To: <m3bourqeqh.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 11 Sep 2011 17:29:42 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> This is still not a good idea. How is -g special wrt. to the options
>> that may imply -l? The requirement that the options should include -l
>> is simple and does not need any amendment.
>
> Because saying "include -l" sounds like you really need to have the
> full, complete "-l" output, and then it turns out that you don't, which
> makes me happy, because I hate the full "-l" output in dired buffers.
> :-)
There is nothing that prevents you from using any additional options.
> Perhaps the string should be more wishy-washy? "must be a sort-of full
> listing, like -l or the like"? Too long, though.
Exactly. Saying "(must include -l)" is simple and clear, and fully
correct.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-09-11 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 19:41 bug#9301: dired-sort-toggle-or-edit should also mention -o and -g jidanni
2011-09-11 2:29 ` Lars Magne Ingebrigtsen
2011-09-11 7:18 ` Andreas Schwab
2011-09-11 14:55 ` Lars Magne Ingebrigtsen
2011-09-11 15:29 ` Andreas Schwab
2011-09-11 15:29 ` Lars Magne Ingebrigtsen
2011-09-11 15:50 ` Andreas Schwab [this message]
2011-09-11 15:57 ` Lars Magne Ingebrigtsen
2011-09-11 16:14 ` Andreas Schwab
2011-09-11 16:18 ` Lars Magne Ingebrigtsen
2011-09-11 16:43 ` Andreas Schwab
2011-09-11 16:43 ` Lars Magne Ingebrigtsen
2011-09-11 16:53 ` Andreas Schwab
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=m24o0jgjsa.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=9301@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.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).