From: Eli Zaretskii <eliz@gnu.org>
To: leo <dev@halloleo.hailmail.net>
Cc: 28807@debbugs.gnu.org
Subject: bug#28807: 25.2; dired-actual-switches` and .dir-locals.el
Date: Fri, 13 Oct 2017 12:09:09 +0300 [thread overview]
Message-ID: <83wp3zjtxm.fsf@gnu.org> (raw)
In-Reply-To: <2681E59F-31EA-45BF-A6CF-A9486B4FE12D@halloleo.hailmail.net> (message from leo on Fri, 13 Oct 2017 19:16:08 +1100)
> From: leo <dev@halloleo.hailmail.net>
> Date: Fri, 13 Oct 2017 19:16:08 +1100
>
> ;;; Directory Local Variables
> ;;; For more information see (info "(emacs) Directory Variables")
>
> ((dired-mode .
> ((dired-actual-switches . "-laht")
> (subdirs . nil))))
>
> * Create a subirectory `subdir` inside `mydir`
> * Create some files with different timestamp and different names in there.
>
> Bug 1: .dir-locals.el not applied the first time
> ================================================
>
> * Launch `emacs -Q`
> * Open `mydir` via `M-x find-file` as a dired buffer
> * Observe that `mydir` is **not** in date order sorted
> * Kill `mydir` buffer.
> * Open again `mydir` via `M-x find-file` as a dired buffer
> * Observe that `mydir` **is** in date order sorted (as it should be)
>
> Bug 2: (subdirs . nil) rule not obeyed
> ======================================
>
> * Stay in that `emacs -Q` session
> * Kill `mydir` buffer.
> * Open `mydir/subdir` via `M-x find-file` as a dired buffer
> * Observe that `mydir` **is** in date order sorted (as it **not** should be)
I think this is because both settings take their effect before the
Dired mode is turned on in the buffer. IOW, these customizations
simply cannot have the desired effect, as they are conditioned on
the wrong condition.
next prev parent reply other threads:[~2017-10-13 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 8:16 bug#28807: 25.2; dired-actual-switches` and .dir-locals.el leo
2017-10-13 9:09 ` Eli Zaretskii [this message]
2017-10-14 8:49 ` leo
2021-07-04 14:14 ` Lars Ingebrigtsen
2021-07-05 1:28 ` leo
2021-07-05 13:33 ` Lars Ingebrigtsen
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=83wp3zjtxm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28807@debbugs.gnu.org \
--cc=dev@halloleo.hailmail.net \
/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).