unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 20739@debbugs.gnu.org
Subject: bug#20739: 25.0.50; Dired switches have no effect when explicit list of files provided
Date: Sat, 06 Jun 2015 12:36:31 +0300	[thread overview]
Message-ID: <837frhnppc.fsf@gnu.org> (raw)
In-Reply-To: <3362479c-11a3-4559-88d6-666f03933440@default>

> Date: Fri, 5 Jun 2015 01:34:40 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> 
> emacs -Q
> 
> Given two files whose names are a.el and b.el, with b.el more recent
> than a.el.
> 
> M-: (dired '("foo" "a.el" "b.el") "-lstF")
> 
> The files are listed in alphabetic order, not by date as specified by
> arg SWITCHES and as indicated in the mode line.

No, they are listed in the order in which you specified them in the
list passed as the first argument to 'dired'.  That just happened to
coincide with alphabetic order in your case.

You evidently expected 'dired' to apply the order-related options in
switches to the entire list of files.  But that's not what 'dired'
does when it is called with its 1st argument a list.  What it does is
invoke 'insert-directory' with each of the files in the list, in
order, passing it the value of switches.  So when calling 'dired' in
this manner, the order-related switches have no effect whatsoever.

I've updated the doc string to mention this peculiarity.

> Hitting `s' any number of times has no effect on the order of the
> files.

For the same reason.





  parent reply	other threads:[~2015-06-06  9:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05  8:34 bug#20739: 25.0.50; Dired switches have no effect when explicit list of files provided Drew Adams
2015-06-05 14:25 ` Eli Zaretskii
2015-06-06  9:36 ` Eli Zaretskii [this message]
     [not found] <<3362479c-11a3-4559-88d6-666f03933440@default>
     [not found] ` <<831thqp704.fsf@gnu.org>
2015-06-05 14:56   ` Drew Adams
     [not found] ` <<837frhnppc.fsf@gnu.org>
2015-06-06 18:43   ` Drew Adams
2015-06-06 19:27     ` Eli Zaretskii
     [not found] <<f0b49ecc-7301-4ec9-b339-a3f8a65c553c@default>
     [not found] ` <<83oaksmyc8.fsf@gnu.org>
2015-06-06 21:57   ` Drew Adams
2015-06-06 22:21     ` Drew Adams
2015-06-07 14:39     ` Eli Zaretskii
2015-06-09 15:09     ` Drew Adams
     [not found]   ` <<f33db93f-7f6c-4aee-90e4-566d7e93b228@default>
     [not found]     ` <<83fv63mvkj.fsf@gnu.org>
2015-06-07 17:34       ` Drew Adams
2015-06-07 19:09         ` Eli Zaretskii
     [not found] <<186494c2-6958-42eb-a351-6543237bfb75@default>
     [not found] ` <<838ubvmj2s.fsf@gnu.org>
2015-06-07 19:33   ` Drew Adams
2015-06-07 19:55     ` Eli Zaretskii
     [not found]   ` <<99d84238-3b80-4778-a248-7063a7e6b3df@default>
     [not found]     ` <<834mmjmgyu.fsf@gnu.org>
2015-06-08  1:58       ` Drew Adams

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=837frhnppc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20739@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).