From: jidanni@jidanni.org
To: help-gnu-emacs@gnu.org
Subject: Re: how to reference the current *.el file in elisp
Date: Tue, 30 Jun 2009 09:29:43 +0800 [thread overview]
Message-ID: <87eit2zeyg.fsf@jidanni.org> (raw)
In-Reply-To: barmar-647DEB.23105428062009@news.eternal-september.org
> How do I do things like
> # Local Variables:
> # compile-command: (concat "blarfowitz --nizbotize" buffer-file-name)
> # End:
> without being asked about risky variables, or hard wiring buffer-file-name?
BM> if you want to customize risky local variables, see the
BM> safe-local-variables-p function.
OK, I read that, and (info "(emacs) Safe File Variables")
but I still don't get why buffer-file-name is so unsafe... OK, maybe one
can set it to /etc/passwd and cause one to zap that file... Anyway, in
perl or sh there is the handy
$PROGRAM_NAME
$0 Contains the name of the program being executed.
So why in "Local Variables" stanzas is there no way to refer to the
current file being edited, without setting off all kinds of fire alarms,
or being forced to whitelist something because it is dangerous, thus
exposing myself to danger elsewhere. See also
http://groups.google.com/groups/search?as_umsgid=mailman.597.1244940108.2239.help-gnu-emacs@gnu.org
next prev parent reply other threads:[~2009-06-30 1:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1223.1245903674.2239.help-gnu-emacs@gnu.org>
2009-06-25 5:49 ` how to reference the current *.el file in elisp Xah Lee
2009-06-25 7:23 ` Barry Margolin
2009-06-25 11:49 ` Harry Putnam
2009-06-25 12:30 ` Lennart Borgman
2009-06-25 23:43 ` Harry Putnam
[not found] ` <mailman.1237.1245930608.2239.help-gnu-emacs@gnu.org>
2009-06-25 12:18 ` Pascal J. Bourguignon
2009-06-26 2:24 ` Barry Margolin
2009-06-28 0:44 ` jidanni
2009-06-29 3:10 ` Barry Margolin
2009-06-30 1:29 ` jidanni [this message]
2009-06-30 3:30 ` Barry Margolin
[not found] <mailman.1712.1246572015.2239.help-gnu-emacs@gnu.org>
2009-07-08 9:30 ` Anselm Helbig
2009-07-02 12:48 jidanni
-- strict thread matches above, loose matches on Subject: below --
2009-06-25 4:20 Harry Putnam
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=87eit2zeyg.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--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.
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.