From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Richard Copley <rcopley@gmail.com>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: RE: [PATCH] Really prevent quitting in sensitive contexts
Date: Sat, 14 Mar 2020 08:31:03 -0700 (PDT) [thread overview]
Message-ID: <95675eb0-df8f-4d99-b108-cb5140691d5f@default> (raw)
In-Reply-To: <jwvftedut8x.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
Attached.
> > Stefan, will you please consider configuring your system to send email
> > to the lists as plain text? Recently your messages have "Content-type:
> > text/markdown".
>
> Hmm... that's odd... I did that a few months ago but then had to revert
> it because of the number of broken MUAs out there.
> Can you forward me one of the recent ones?
[-- Attachment #2: Type: message/rfc822, Size: 1620 bytes --]
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 00:07:30 -0700 (PDT)
Message-ID: <jwv5zf7pgb5.fsf-monnier+emacs@gnu.org>
[-- Attachment #2.1: Untitled.txt --]
[-- Type: text/x-markdown, Size: 710 bytes --]
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 00:07:30 -0700 (PDT)
Message-ID: <jwv5zf7pgb5.fsf-monnier+emacs@gnu.org>
> 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 15:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 2:05 [PATCH] Really prevent quitting in sensitive contexts Daniel Colascione
2020-03-12 2:20 ` Stefan Monnier
2020-03-12 2:32 ` Daniel Colascione
2020-03-12 10:07 ` Michael Albinus
2020-03-12 10:21 ` Robert Pluim
2020-03-12 10:33 ` Michael Albinus
2020-03-13 10:00 ` Michael Albinus
2020-04-14 6:56 ` Daniel Colascione
2020-04-14 8:40 ` Michael Albinus
2020-03-12 3:29 ` Óscar Fuentes
2020-03-12 7:21 ` Eli Zaretskii
2020-03-12 13:31 ` Richard Copley
2020-03-12 17:36 ` Drew Adams
2020-03-12 22:06 ` Stefan Monnier
2020-03-12 23:14 ` Richard Copley
2020-03-12 23:35 ` Stefan Monnier
2020-03-12 23:56 ` Richard Copley
2020-03-14 15:31 ` Drew Adams [this message]
2020-03-14 18:21 ` Stefan Monnier
2020-03-14 18:36 ` Drew Adams
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=95675eb0-df8f-4d99-b108-cb5140691d5f@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rcopley@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 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).