From: Juri Linkov <juri@jurta.org>
To: pandyacus@sbcglobal.net
Cc: Tom Tromey <tromey@redhat.com>, Dan Nicolaescu <dann@ics.uci.edu>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: dir-locals.el take precedence over user's mode-hook changes
Date: Sat, 03 Jan 2009 02:45:59 +0200 [thread overview]
Message-ID: <87y6xtb9co.fsf@jurta.org> (raw)
In-Reply-To: <85555.70425.qm@web83204.mail.mud.yahoo.com> (Chetan Pandya's message of "Wed, 31 Dec 2008 15:50:07 -0800 (PST)")
>> > > auto-fill-mode will not be turned on for that elisp file.
>> >
>> > Yes, that's a more general problem. I'd be inclined to change it so
>> > that the minor mode is unconditionally turned ON rather than toggled.
>>
>> Please do that, this is a long standing issue...
>
> Isn't this going against what the documentation says? Minor modes are
> supposed to be preferences and the user may or may not want those
> modes turned on automatically.
This is not going against the documentation that says in
(info "(emacs) Specifying File Variables"):
You can use the `mode' "variable" to set minor modes as well as the
major modes; in fact, you can use it more than once, first to set the
major mode and then to set minor modes which are specific to particular
buffers. But most minor modes should not be specified in the file at
all, because they represent user preferences.
First, it says "to *set* minor modes" instead "to *toggle* minor modes".
So it is safe to fix the behavior according to the documentation
to set minor modes unconditionally.
Second, it says that *most* minor modes should not be specified
in the file. However, it is justified to set bug-reference-mode
as a directory-wide setting for a project.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-01-03 0:45 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 [this message]
2008-12-31 16:39 ` Richard M Stallman
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=87y6xtb9co.fsf@jurta.org \
--to=juri@jurta.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pandyacus@sbcglobal.net \
--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).