From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16533@debbugs.gnu.org, markus.triska@gmx.at
Subject: bug#16533: 24.3.50; "s" no longer works as documented in dired
Date: Sat, 25 Jan 2014 20:31:44 -0500 [thread overview]
Message-ID: <j7y523le9r.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8361p8cnll.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 Jan 2014 13:22:46 +0200")
Eli Zaretskii wrote:
> The problem here seems to be that dired-sort-toggle blindly adds the
> "-t" flag to dired-actual-switches, although in this case the sorting
> is not by date at all. I don't understand the logic here; it seems
> like dired-sort-toggle assumes without testing that the directory is
> sorted either by date or by name, which is of course false.
>
> Is it a portable assumption that the last switch that determines the
> sorting order overrides all the previous ones? If so, ls-lisp.el
> should be fixed to implement that requirement. But if not, we need to
> fix dired.el not to put more than one sorting option into
> dired-actual-switches. In particular, the logic in dired-sort-toggle
> seems to be flawed.
Duh, I seem to have been very thick here, since the original report
seems clear now. I guess I missed the 'then press "s"'.
I guess it is not a portable assumption, since presumably whatever
crappy ls Mac OS X uses does not work that way.
Prior to r101356, dired-sort-toggle removed dired-ls-sorting-switches.
Now it seems not to. That change was made to fix another bug,
http://debbugs.gnu.org/6987
next prev parent reply other threads:[~2014-01-26 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 0:33 bug#16533: 24.3.50; "s" no longer works as documented in dired Markus Triska
2014-01-24 3:10 ` Glenn Morris
2014-01-24 3:13 ` Glenn Morris
2014-01-24 17:23 ` Markus Triska
2014-01-24 18:32 ` Glenn Morris
2014-01-25 11:22 ` Eli Zaretskii
2014-01-26 1:31 ` Glenn Morris [this message]
2014-01-25 11:02 ` 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=j7y523le9r.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=16533@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=markus.triska@gmx.at \
/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.