GNU bug report logs - #34130
Specifying File Variables: mention why can't specify "current file"

Previous Next

Package: emacs;

Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>

Date: Sat, 19 Jan 2019 06:38:01 UTC

Severity: wishlist

Merged with 6615, 29451, 35373

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 34130 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>, 6615 <at> debbugs.gnu.org
Subject: bug#34130: Specifying File Variables: mention why can't specify "current file"
Date: Wed, 02 Oct 2019 03:44:37 +0800
>>>>> "LI" == Lars Ingebrigtsen <larsi <at> gnus.org> writes:
LI> Eli Zaretskii <eliz <at> gnu.org> writes:

>>> On (info "(emacs) Specifying File Variables")
>>> at
>>> 
>>> # Local Variables:
>>> # compile-command: "cc foo.c -Dfoo=bar -Dhack=whatever \
>>> #   -Dmumble=blaah"
>>> # End:
>>> 
>>> do also mention why there is absolutely no way to say "<<<current file>>>",
>>> $$$${current_file} etc. if one wanted to, instead of needing to hardwire
>>> the filename (foo.c) of the file (foo.c) into the file (foo.c) itself! Thanks.
>> 
>> Is something wrong with using buffer-file-name?  You could create
>> compile-command by using 'eval', which can accept Emacs functions.

LI> Indeed, so I don't think there's anything here to be fixed.  Closing.

eval needs to be whitelisted as a safe local variable, creating a security hole.




This bug report was last modified 5 years and 229 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.