From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: sergio.pokrovskij@gmail.com, 17489@debbugs.gnu.org
Subject: bug#17489: 24.3; Major mode spec in .dir-locals.el breaks dired
Date: Wed, 14 May 2014 22:38:02 +0300 [thread overview]
Message-ID: <838uq4nobp.fsf@gnu.org> (raw)
In-Reply-To: <9bfvkcgp6m.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: sergio.pokrovskij@gmail.com, 17489@debbugs.gnu.org
> Date: Wed, 14 May 2014 15:01:21 -0400
>
> Well, it really doesn't make sense AFAICS, but ok then, you don't want
> the special-case solution of simply ignoring a `mode' dir-locals in
> non-file buffers.
It's not that I don't want that. I actually am quite indifferent to
this, because I think dir-locals, in its current design, is too
restrictive, and therefore I'm simply not interested.
I just think that adding these implied conditions is a slippery slope,
because different people want to do different things with dir-locals.
> So then we are back to http://debbugs.gnu.org/13685, which would let
> people choose.
That looks better, since it at least makes the user's desire
explicit. Why not implement it?
next prev parent reply other threads:[~2014-05-14 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 7:14 bug#17489: 24.3; Major mode spec in .dir-locals.el breaks dired Sergio Pokrovskij
2014-05-14 15:10 ` Eli Zaretskii
2014-05-14 16:56 ` Stefan Monnier
2014-05-14 17:24 ` Sergio Pokrovskij
2014-05-14 17:31 ` Glenn Morris
2014-05-14 17:38 ` Glenn Morris
2014-05-14 18:20 ` Eli Zaretskii
2014-05-14 18:29 ` Glenn Morris
2014-05-14 18:40 ` Eli Zaretskii
2014-05-14 19:01 ` Glenn Morris
2014-05-14 19:38 ` Eli Zaretskii [this message]
2014-05-14 19:40 ` Glenn Morris
2022-02-22 14:29 ` Lars Ingebrigtsen
2014-05-14 18:17 ` Eli Zaretskii
2014-05-15 0:39 ` Sergio Pokrovskij
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=838uq4nobp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17489@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=sergio.pokrovskij@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 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).