From: Phil Sainty <psainty@orcon.net.nz>
To: yary <not.com@gmail.com>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15577 <15577@debbugs.gnu.org>
Subject: bug#15577: 24.3; dir-local variables not applied when switching major-mode
Date: Mon, 21 Oct 2013 02:38:59 +1300 [thread overview]
Message-ID: <5263DCF3.7070501@orcon.net.nz> (raw)
In-Reply-To: <CAG2CFAbtEy2kQ=iXYmct9stzde8U1g+NQ_mWGgA+yb_=igHkiw@mail.gmail.com>
I've been experimenting with this today (along the lines of
http://lists.gnu.org/archive/html/bug-gnu-emacs/2013-10/msg00534.html )
and one of the things I noticed which I'd not previously considered
was the major mode switches which happen every time you enter the
minibuffer.
I expect that we should make an exception for those mode changes, as
(a) that is going to be a far more frequent occurrence -- and for
people who enable local variable processing for tramp buffers, probably
annoyingly expensive to boot -- but more importantly (b) there surely
aren't any actual use-cases for dir/file locals in the minibuffer?
Does that sound sensible?
-Phil
next prev parent reply other threads:[~2013-10-20 13:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 20:14 bug#15577: 24.3; dir-local variables not applied when switching major-mode yary
2013-10-09 21:42 ` Glenn Morris
2013-10-10 18:34 ` yary
2013-10-10 21:27 ` Glenn Morris
2013-10-10 21:52 ` Stefan Monnier
2013-10-10 23:12 ` yary
2013-10-14 18:41 ` yary
2013-10-16 14:26 ` yary
2013-10-18 15:43 ` yary
2013-10-19 1:18 ` Stefan Monnier
2013-10-19 19:08 ` yary
2013-10-19 21:55 ` Stefan Monnier
2013-10-20 13:00 ` yary
2013-10-20 13:38 ` Phil Sainty [this message]
2013-10-21 13:11 ` Stefan Monnier
2013-10-21 13:23 ` yary
2013-10-21 14:23 ` Stefan Monnier
2013-10-21 21:58 ` Phil Sainty
2013-10-18 16:29 ` Phil Sainty
[not found] ` <mailman.3789.1381430919.10748.bug-gnu-emacs@gnu.org>
2016-05-05 11:26 ` Alan Mackenzie
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=5263DCF3.7070501@orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=15577@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=not.com@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.