From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dima Kogan <lists@dima.secretsauce.net>
Cc: emacs-devel@gnu.org
Subject: Re: Can we expand the valid location of "Local Variables" ?
Date: Tue, 10 Mar 2020 22:01:27 -0400 [thread overview]
Message-ID: <jwvpndjr6u7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mu8nbwr7.fsf@dima.secretsauce.net> (Dima Kogan's message of "Tue, 10 Mar 2020 16:44:44 -0700")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/x-markdown; coding=UTF-8, Size: 1222 bytes --]
> OK. I can write such a patch. Is there an upside to not documenting it?
> If we REALLY don't want people touching this variable, then why not
> leave the hardcoded 3000?
I said "variable" just because we don't have constants, but really the
way I see it, it should be a constant: if you put your variables further
than that, it won't work with an Emacs that hasn't been
customized accordingly.
> Oof. I COULD do that, but that feels like it makes an already-ugly thing
> even uglier. I sent a separate email to the org mailing list about maybe
> upstreaming some of the advices, but the general idea doesn't seem
> unreasonable to me: we already allow a block to define some custom
> variables, so customizing the behavior of some functions doesn't seem
> crazy.
Putting a large amount of code this way is a major problem security-wise.
If you're the only one looking at this file and it's code you wrote,
then there's no problem security-wise, but then again you could just
put that code in your ~/.emacs instead.
If it's not your own code or if you share this file with others, then
it's a security hassle and you'd be better off moving that code to some
package on which your file will depend.
Stefan
next prev parent reply other threads:[~2020-03-11 2:01 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 [this message]
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
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=jwvpndjr6u7.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=lists@dima.secretsauce.net \
/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.