GNU bug report logs - #16846
24.3.50.1; Info 48.2.4.1 Specifying File Variables

Previous Next

Full log

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

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 16846 <at> debbugs.gnu.org
Subject: Re: bug#16846: acknowledged by developer ()
Date: Mon, 24 Feb 2014 14:42:58 +0100

Am 24.02.2014 13:50, schrieb Juanma Barranquero:
> On Mon, Feb 24, 2014 at 1:49 PM, Andreas Röhler
> <andreas.roehler <at> easy-emacs.de> wrote:
>
>>   It works but sends an error.
>
> As it would if you instead of
>
>    -*- variable: value -*-
>
> put
>
>    This line is here just to mess with the interpreter
>
> So, if you don't want to mess with the program that process the file,
> follow the file's intended conventions. Nothing to do with file
> variables.

Please tell me, what's the difference between this example and the one given in the info:


     -*- mode: MODENAME; VAR: VALUE; ... -*-

beside specified just one?

>
>> Sending the error upon working code is a bug.
>
> No, its not. That line is not valid elisp.
>
>> Or you say: a single file local setting needs to be commented, more of them
>> not.
>
> Sorry, I don't understand you.
>
>> If a comment is needed, it's a docu-bug.
>
> As I already said, if you think the info manual needs to be more
> explicit about the implicit (but obvious) need to respect the
> conventions of the kind of file you're writing (whether source code,
> or any other kind), please file a bug report saying so.
>

This was done with #16846

Previous Next

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