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: Sun, 23 Feb 2014 09:49:09 +0100 [thread overview]
Message-ID: <5309B605.5000900@easy-emacs.de> (raw)
In-Reply-To: <CAAeL0SQN_Z3MhOcJgWYYqkXObdFR3x_KG_JUOupRGEhPw+=LOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
Am 22.02.2014 23:43, schrieb Juanma Barranquero:
> On Sat, Feb 22, 2014 at 9:50 PM, Andreas Röhler
> <andreas.roehler@easy-emacs.de> wrote:
>
>> This bug is about Info files
>
> I don't think there is a bug. That info node talks about the format of
> the file variables, but of course says nothing about the format of the
> contents of your file. If your file is text, perhaps just
>
> -*- variable: value -*-
>
> in the first line is perfectly acceptable.
Do you want file-local variables restrict to text-mode?
Doesn't make sense for me.
If the file contains C
> source code, or elisp, or another data format to be digested by some
> external processor, it should already be clear that the file variables
> must be acceptable to these external processors. You can't expect to
> have
>
> -*- mode: c -*-
>
> as the first line of a C file and compile it with GCC without getting an error.
>
We must not discuss possible other bugs here. Let's stay with the reported one.
> That said, the same node that you quote already says:
>
> Here is an example first line that specifies Lisp mode and sets two
> variables with numeric values:
>
> ;; -*- mode: Lisp; fill-column: 75; comment-column: 50; -*-
>
> and a little later:
>
> In shell scripts, the first line is used to identify the script
> interpreter, so you cannot put any local variables there. To
> accommodate this, Emacs looks for local variable specifications in the
> _second_ line if the first line specifies an interpreter. The same is
> true for man pages which start with the magic string `'\"' to specify a
> list of troff preprocessors (not all do, however).
>
> which clearly suggests that the file variables must also be acceptable
> to the consumer of the file.
It rather says: implementation is not that straightforward as it could/should be.
It's at Emacs, when sending code, to clear its artistics before.
>
>> , the former report was about a wrong compiler warning.
>
> Which was, in fact, not wrong at all.
>
Attach foo1.png - happens when evaluating a buffer with contents:
;;;;;;
-*- lexical-binding: t -*-
(setq foo 1)
;;;;;;
[-- Attachment #2: foo1.png --]
[-- Type: image/png, Size: 48359 bytes --]
next prev parent reply other threads:[~2014-02-23 8:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5309B605.5000900@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 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.