From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: bruce.connor.am@gmail.com, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 9145e79: * lisp/files.el: Don't allow customization of dir-locals sorting
Date: Tue, 10 Nov 2015 18:32:57 +0200 [thread overview]
Message-ID: <837flpn7ba.fsf@gnu.org> (raw)
In-Reply-To: <m2d1vij5y7.fsf@Vulcan.attlocal.net>
> From: John Wiegley <jwiegley@gmail.com>
> Cc: Artur Malabarba <bruce.connor.am@gmail.com>, Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 10 Nov 2015 06:16:00 -0800
>
> >>>>> Artur Malabarba <bruce.connor.am@gmail.com> writes:
>
> > In retrospect, this is not a good idea for the same reason that
> > `dir-locals-file' is a defconst, because it is important that this
> > behaviour be "uniform across different environments and users".
> > Sure, the user can still change the sorting with a hack, but we
> > shouldn't encourage them to change it.
>
> I'm inclined to agree with this; but did you mention it to Eli also, who had
> suggested using version<? I think string< is the right behavior, but since we
> had discussed it, I'd like to hear from him too.
I didn't suggest using version<, at least not directly. I said that
if people who use Unix startup scripts are used to this order, I have
no objection to using string< in our similar features.
next prev parent reply other threads:[~2015-11-10 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151110122714.8693.7725@vcs.savannah.gnu.org>
[not found] ` <E1Zw815-0002Gt-E0@vcs.savannah.gnu.org>
2015-11-10 14:16 ` [Emacs-diffs] master 9145e79: * lisp/files.el: Don't allow customization of dir-locals sorting John Wiegley
2015-11-10 15:49 ` Artur Malabarba
2015-11-10 16:32 ` Eli Zaretskii [this message]
2015-11-10 16:34 ` John Wiegley
2015-11-11 0:37 ` Juri Linkov
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=837flpn7ba.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.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 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.