unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: tromey@redhat.com, dann@ics.uci.edu, monnier@iro.umontreal.ca,
	emacs-devel@gnu.org
Subject: Re: dir-locals.el take precedence over user's mode-hook changes
Date: Wed, 31 Dec 2008 11:39:40 -0500	[thread overview]
Message-ID: <E1LI46e-0005Rd-9Z@fencepost.gnu.org> (raw)
In-Reply-To: <87sko5dxko.fsf@jurta.org> (message from Juri Linkov on Wed, 31 Dec 2008 01:59:03 +0200)

    Maybe something like

    ;; Pre-Local Variables:
    ;; End:

    for variables set before mode hook or

    ;; Post-Local Variables:
    ;; End:

    after mode hook.

If we want to put such a feature in the file, this is a clean spec for
it.  However, putting it in the file has the consequence that it
specifies the same ordering for all users who visit the file.  Is that
ok?  We would need to look at use cases.

I also wonder whether the need for such a feature is enough to justify
the complexity it would add to the Emacs Manual.





  parent reply	other threads:[~2008-12-31 16:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-24 18:31 dir-locals.el take precedence over user's mode-hook changes Stefan Monnier
2008-12-24 19:03 ` Dan Nicolaescu
2008-12-24 20:31   ` Tom Tromey
2008-12-24 20:52     ` Juri Linkov
2008-12-30 17:20       ` Stefan Monnier
2008-12-30 23:59         ` Juri Linkov
2008-12-31  1:43           ` Stefan Monnier
2008-12-31  1:54           ` Dan Nicolaescu
2008-12-31 12:28             ` Juri Linkov
2008-12-31 16:17               ` Dan Nicolaescu
2008-12-31 17:27                 ` Stefan Monnier
2008-12-31 21:41                   ` Dan Nicolaescu
2008-12-31 23:50                     ` Chetan Pandya
2009-01-03  0:45                       ` Juri Linkov
2008-12-31 16:39           ` Richard M Stallman [this message]
2008-12-25  4:49   ` Miles Bader

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=E1LI46e-0005Rd-9Z@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=tromey@redhat.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).