From: Kaushal Modi <kaushal.modi@gmail.com>
To: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Understanding why mode keyword shouldn't be used for minor modes in .dir-locals.el
Date: Mon, 24 Dec 2018 11:06:38 -0500 [thread overview]
Message-ID: <CAFyQvY2pEz8KuvAPQH7-c1Be-jQbvscFgJX0ePtc=jLwdHaXPQ@mail.gmail.com> (raw)
Hello,
From the manual node (emacs) Specifying File Variables:
> Do not use the ‘mode’ keyword for minor modes. To enable or disable
a minor mode in a local variables list, use the ‘eval’ keyword with a
Lisp expression that runs the mode command (*note Minor Modes::).
Though, I have been using (mode . auto-fill) in my .dir-locals.el for ages,
and it works great. And it's less verbose than (eval . (auto-fill-mode)).
So I'd like to understand why the manual suggests *not* to use the mode
keyword for minor modes.
Thanks.
--
Kaushal Modi
next reply other threads:[~2018-12-24 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 16:06 Kaushal Modi [this message]
2018-12-24 18:20 ` Understanding why mode keyword shouldn't be used for minor modes in .dir-locals.el Glenn Morris
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='CAFyQvY2pEz8KuvAPQH7-c1Be-jQbvscFgJX0ePtc=jLwdHaXPQ@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).