From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 6615@debbugs.gnu.org, 34130@debbugs.gnu.org
Subject: bug#6615: bug#34130: bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file"
Date: Sat, 05 Oct 2019 01:44:31 +0800 [thread overview]
Message-ID: <871rvs2yo0.8.fsf@jidanni.org> (raw)
In-Reply-To: <87iq4ljpr0.fsf@jidanni.org>
>>>>> "RP" == Robert Pluim <rpluim@gmail.com> writes:
>>>>> On Fri, 04 Oct 2019 16:11:17 +0800, 積丹尼 Dan Jacobson <jidanni@jidanni.org> said:
積丹尼> Whatever you are proposing is too complex.
積丹尼> @CURRENT_FILE@ should just refer to the current file, no hacks needed.
RP> You propose @CURRENT_FILE@, someone else will prefer $..$, someone
RP> else again will want a different set of variables available. This is
RP> why the 'eval' functionality exists, which you donʼt want to use,
RP> hence the proposal to use the hook.
OK, please post what the INFO page would say
(easy instructions that even I could follow)
and I'll give it a spin. Any how about just
(setq current-file-local-variable "$CUR_FIL$")
for .emacs...
P.S., Dear Lars, To: doesn't mean you:
https://debbugs.gnu.org/cgi-bin/bugreport.cgi?bug=37591
prev parent reply other threads:[~2019-10-04 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 0:58 bug#34130: Specifying File Variables: mention why can't specify "current file" 積丹尼 Dan Jacobson
2019-01-19 7:24 ` Eli Zaretskii
2019-01-19 11:26 ` Glenn Morris
2019-10-01 19:28 ` Lars Ingebrigtsen
2010-07-12 4:19 ` bug#6615: document how to specify the current filename in Local Variables jidanni
2019-10-01 19:44 ` bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file" 積丹尼 Dan Jacobson
2019-10-02 11:48 ` Robert Pluim
2019-10-02 19:11 ` bug#34130: " 積丹尼 Dan Jacobson
2019-10-03 8:25 ` bug#6615: " Robert Pluim
2019-10-04 8:11 ` 積丹尼 Dan Jacobson
2019-10-04 8:37 ` bug#6615: " Robert Pluim
2019-10-04 17:44 ` 積丹尼 Dan Jacobson [this message]
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=871rvs2yo0.8.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=34130@debbugs.gnu.org \
--cc=6615@debbugs.gnu.org \
--cc=larsi@gnus.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 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).