* bug#5239: 23.1.50; compile-command Local Variables must be after mode
@ 2009-12-17 19:02 jidanni
2009-12-17 23:46 ` Juri Linkov
0 siblings, 1 reply; 3+ messages in thread
From: jidanni @ 2009-12-17 19:02 UTC (permalink / raw)
To: emacs-pretest-bug
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)
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#5239: 23.1.50; compile-command Local Variables must be after mode
2009-12-17 19:02 bug#5239: 23.1.50; compile-command Local Variables must be after mode jidanni
@ 2009-12-17 23:46 ` Juri Linkov
2009-12-18 0:25 ` jidanni
0 siblings, 1 reply; 3+ messages in thread
From: Juri Linkov @ 2009-12-17 23:46 UTC (permalink / raw)
To: jidanni; +Cc: 5239
> 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/
^ permalink raw reply [flat|nested] 3+ messages in thread* bug#5239: 23.1.50; compile-command Local Variables must be after mode
2009-12-17 23:46 ` Juri Linkov
@ 2009-12-18 0:25 ` jidanni
0 siblings, 0 replies; 3+ messages in thread
From: jidanni @ 2009-12-18 0:25 UTC (permalink / raw)
To: juri; +Cc: 5239
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...".
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-12-18 0:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-17 19:02 bug#5239: 23.1.50; compile-command Local Variables must be after mode jidanni
2009-12-17 23:46 ` Juri Linkov
2009-12-18 0:25 ` jidanni
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.