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

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

[積丹尼 Dan Jacobson]

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.

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

[Eli Zaretskii]

> From: 積丹尼 Dan Jacobson
> 	<jidanni@jidanni.org>
> Date: Sat, 19 Jan 2019 08:58:39 +0800
> 
> 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.

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

[Glenn Morris]

This is the third time you've reported this.

You can avoid this by checking
https://debbugs.gnu.org/cgi/pkgreport.cgi?submitter=jidanni%40jidanni.org
before you post.

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

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@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.

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

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#6615: document how to specify the current filename in Local Variables

[jidanni]

(info "(emacs) Specifying File Variables")
(info "(emacs) Safe File Variables")
Should say how to do
http://permalink.gmane.org/gmane.emacs.bugs/8844
correctly, and why there IS NO WAY to specify the current filename,
without a big hassle, even though there is just as much risk as if one
hardwired it into the file.

bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file"

[積丹尼 Dan Jacobson]

>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
LI> Eli Zaretskii <eliz@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.

bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file"

[Robert Pluim]

>>>>> On Wed, 02 Oct 2019 03:44:37 +0800, 積丹尼 Dan Jacobson <jidanni@jidanni.org> said:

>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
    LI> Eli Zaretskii <eliz@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.

How about this instead:

    before-hack-local-variables-hook is a variable defined in `files.el'.
    Its value is (c-before-hack-hook)

      This variable may be risky if used as a file-local variable.
      Probably introduced at or before Emacs version 23.1.

    Documentation:
    Normal hook run before setting file-local variables.
    It is called after checking for unsafe/risky variables and
    setting `file-local-variables-alist', and before applying the
    variables stored in `file-local-variables-alist'.  A hook
    function is allowed to change the contents of this alist.

    This hook is called only if there is at least one file-local
    variable to set.

bug#34130: bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file"

[積丹尼 Dan Jacobson]

>>>>> "RP" == Robert Pluim <rpluim@gmail.com> writes:

RP> How about this instead:

RP>     before-hack-local-variables-hook is a variable defined in `files.el'...

All I know is you need to add a paragraph explaining whatever workaround
recipe that is to (info "(emacs) Specifying File Variables"):

"You can even refer to the current file name using local variables!
Here's how: ...

bug#6615: bug#34130: bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file"

[Robert Pluim]

>>>>> On Thu, 03 Oct 2019 03:11:13 +0800, 積丹尼 Dan Jacobson <jidanni@jidanni.org> said:

>>>>> "RP" == Robert Pluim <rpluim@gmail.com> writes:
    RP> How about this instead:

    RP> before-hack-local-variables-hook is a variable defined in `files.el'...

    積丹尼> All I know is you need to add a paragraph explaining whatever workaround
    積丹尼> recipe that is to (info "(emacs) Specifying File Variables"):

    積丹尼> "You can even refer to the current file name using local variables!
    積丹尼> Here's how: ...

Not really, because itʼs not restricted to just that, you can do whatever
you want in the hook.

Robert

bug#34130: bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file"

[積丹尼 Dan Jacobson]

Whatever you are proposing is too complex.

@CURRENT_FILE@ should just refer to the current file, no hacks needed.

bug#6615: bug#34130: bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file"

[Robert Pluim]

>>>>> 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.

You propose @CURRENT_FILE@, someone else will prefer $..$, someone
else again will want a different set of variables available. This is
why the 'eval' functionality exists, which you donʼt want to use,
hence the proposal to use the hook.

Robert

bug#6615: bug#34130: bug#6615: bug#34130: Specifying File Variables: mention why can't specify "current file"

[積丹尼 Dan Jacobson]

>>>>> "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