From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Steve Youngs <steve@sxemacs.org>
Cc: emacs-devel@gnu.org, Richard Stallman <rms@gnu.org>,
Dima Kogan <dima@secretsauce.net>
Subject: Re: Can we expand the valid location of "Local Variables" ?
Date: Sat, 14 Mar 2020 03:07:30 -0400 [thread overview]
Message-ID: <jwv5zf7pgb5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <microsoft-free.87zhcjwkg3.fsf@steveyoungs.com> (Steve Youngs's message of "Sat, 14 Mar 2020 15:54:04 +1000")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/x-markdown; coding=UTF-8, Size: 686 bytes --]
> How about some form of "include" mechanism:
>
> Local Variables:
> @include: FILENAME
> End:
Sounds OK, yes.
> I would suggest implementing that with the same care, considerations,
> and restrictions as has `eval' for Locals
Indeed. There be dragons.
> Mind you, if your Local Vars sections are getting so out of hand that
> they warrant having a whole extra file to store them, you should probably
> re-think what you're doing. :-)
I think such an @include directive can be useful not just for large
sections but also to avoid duplicating settings (i.e. a kind of
alternative to .dir-locals.el, not tied to the directory hierarchy).
Stefan
next prev parent reply other threads:[~2020-03-14 7:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 20:56 Can we expand the valid location of "Local Variables" ? Dima Kogan
2020-03-10 21:39 ` Stefan Monnier
2020-03-10 23:44 ` Dima Kogan
2020-03-11 2:01 ` Stefan Monnier
2020-03-22 23:08 ` Dima Kogan
2020-03-23 8:25 ` Robert Pluim
2020-03-23 14:17 ` Eli Zaretskii
2020-03-23 15:28 ` Robert Pluim
2020-03-23 15:54 ` Eli Zaretskii
2020-03-23 17:03 ` Dima Kogan
2020-03-23 17:24 ` Stefan Monnier
2020-03-24 2:20 ` Richard Stallman
2020-03-12 2:26 ` Richard Stallman
2020-03-14 5:54 ` Steve Youngs
2020-03-14 7:07 ` Stefan Monnier [this message]
2020-03-15 3:08 ` Richard Stallman
2020-03-15 6:41 ` Steve Youngs
2020-03-16 3:36 ` Richard Stallman
2020-03-23 15:56 ` Yuri Khan
2020-03-23 16:55 ` Dima Kogan
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=jwv5zf7pgb5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dima@secretsauce.net \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=steve@sxemacs.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.
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.