GNU bug report logs - #5239
23.1.50; compile-command Local Variables must be after mode

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 5239 in the body.
You can then email your comments to 5239 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: emacs-pretest-bug <at> gnu.org
Subject: 23.1.50; compile-command Local Variables must be after mode
Date: Fri, 18 Dec 2009 03:02:32 +0800

In the docstring of compile-command, you might want to emphasize that
one must set it _after_ "mode". Wrong:

# Local Variables:
# compile-command: "set -xnue .crontab `basename $PWD`; scp $1 $2:; ssh $2 crontab $1;\
# ls $PWD/$1|cpiome"
# mode: Shell-script
# End:

or else it just gets thrown away. Better yet, don't throw it away.
(emacs-snapshot package, version 1:20091128-1)

Message #8 received at 5239 <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: juri <at> jurta.org
Cc: 5239 <at> debbugs.gnu.org
Subject: Re: bug#5239: 23.1.50;
	compile-command Local Variables must be after mode
Date: Fri, 18 Dec 2009 08:25:45 +0800

JL> This is already documented in (info "(emacs) Specifying File Variables"):

JL>      If `mode' is used to set a major mode, it should be the first
JL>   "variable" in the list.  Otherwise, the entries that precede it will
JL>   usually be ignored, since most modes kill all local variables as part
JL>   of their initialization.

JL> It makes no sense to duplicate this information in the docstrings of
JL> every variable that may be used in Local Variables.

OK, then the "responsible" thing to do would be to emit a warning if detected:
"mode used after others, see info page...".

Message #11 received at 5239 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> jurta.org>
To: jidanni <at> jidanni.org
Cc: 5239 <at> debbugs.gnu.org
Subject: Re: bug#5239: 23.1.50;
	compile-command Local Variables must be after mode
Date: Fri, 18 Dec 2009 01:46:00 +0200

> In the docstring of compile-command, you might want to emphasize that
> one must set it _after_ "mode". Wrong:
>
> # Local_Variables:
> # compile-command: "set -xnue .crontab `basename $PWD`; scp $1 $2:; ssh $2 crontab $1;\
> # ls $PWD/$1|cpiome"
> # mode: Shell-script
> # End:
>
> or else it just gets thrown away. Better yet, don't throw it away.

This is already documented in (info "(emacs) Specifying File Variables"):

     If `mode' is used to set a major mode, it should be the first
  "variable" in the list.  Otherwise, the entries that precede it will
  usually be ignored, since most modes kill all local variables as part
  of their initialization.

It makes no sense to duplicate this information in the docstrings of
every variable that may be used in Local Variables.

-- 
Juri Linkov
http://www.jurta.org/emacs/

Previous Next

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