unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 16846@debbugs.gnu.org
Subject: bug#16846: acknowledged by developer ()
Date: Mon, 24 Feb 2014 14:42:58 +0100	[thread overview]
Message-ID: <530B4C62.4080600@easy-emacs.de> (raw)
In-Reply-To: <CAAeL0SR6HaaLgV5naxUbin_fLojg2__gktc4C+OWCzvAcTCeNw@mail.gmail.com>

Am 24.02.2014 13:50, schrieb Juanma Barranquero:
> On Mon, Feb 24, 2014 at 1:49 PM, Andreas Röhler
> <andreas.roehler@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






  reply	other threads:[~2014-02-24 13:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAeL0SQhpQm-Lqak3LadUxpJMXqKLG-Gkn4b+OZfLiJbs9cq8A@mail.gmail.com>
2014-02-22 20:11 ` bug#16846: 24.3.50.1; Info 48.2.4.1 Specifying File Variables Andreas Röhler
2014-02-22 20:29   ` Juanma Barranquero
     [not found]   ` <handler.16846.C.13931015541026.notifdonectrl.1@debbugs.gnu.org>
2014-02-22 20:50     ` bug#16846: acknowledged by developer () Andreas Röhler
2014-02-22 22:43       ` Juanma Barranquero
2014-02-23  8:49         ` Andreas Röhler
2014-02-23 11:07           ` Juanma Barranquero
2014-02-24 12:49             ` Andreas Röhler
2014-02-24 12:50               ` Juanma Barranquero
2014-02-24 13:42                 ` Andreas Röhler [this message]
2014-02-24 13:41               ` Nicolas Richard
2014-02-24 15:59                 ` Andreas Röhler
2014-02-24 16:06                   ` Nicolas Richard
2014-02-24 16:49                     ` Andreas Röhler
     [not found] ` <handler.s.C.13931015541026.transcript@debbugs.gnu.org>
2014-02-22 20:42   ` bug#16846: [debbugs-tracker] Processed: your mail Glenn Morris

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=530B4C62.4080600@easy-emacs.de \
    --to=andreas.roehler@easy-emacs.de \
    --cc=16846@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    /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).