unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Glenn Morris <rgm@gnu.org>
Cc: 20640@debbugs.gnu.org
Subject: bug#20640: 24.5; lexical-binding should work like a normal file-local variable
Date: Sun, 21 Jun 2015 20:08:52 +0000	[thread overview]
Message-ID: <CAArVCkSL2zxP=dFkWO37vAf=-oBGK9pKE12uUeGJ7U15GgrO7w@mail.gmail.com> (raw)
In-Reply-To: <jwvvbfeaj79.fsf-monnier+emacsbugs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> schrieb am Mi., 27. Mai 2015 um
03:49 Uhr:

> > Even if the code were to check for "coding:" (which we already have to
> > scan the end of the file for) and "lexical-binding:" in the same pass?
>
> The check for "coding:" is a misdesign, indeed.  I think we should use
> some utf-8 tell-tale sign at the beginning of *.el files to eliminate
> the need to check for "coding:" (and to go through
> load-with-code-conversion) in the normal case.  It could be a utf-8 BOM
> or something like that.  Ideally we could give extra meaning to this
> marker so it not only means "uses utf-8" but also "uses
> lexical-scoping", so that we can have a future where we don't need to
> add "lexical-binding:t" to every file.
>
>
>
I don't think this is a misdesign. In most cases files are either seekable
or small enough so that reading the variables from the end is tolerable. I
prefer the end of files for local variables because they tend to be less
important than the actual content.

[-- Attachment #2: Type: text/html, Size: 1421 bytes --]

  reply	other threads:[~2015-06-21 20:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 10:19 bug#20640: 24.5; lexical-binding should work like a normal file-local variable Philipp Stephani
2015-05-25  1:59 ` Stefan Monnier
2015-05-25 20:33   ` Daniel Colascione
2015-05-25 22:55     ` Stefan Monnier
2015-05-26  1:06       ` Glenn Morris
2015-05-26 17:12         ` Stefan Monnier
2015-05-26 20:53           ` Glenn Morris
2015-05-27  1:49             ` Stefan Monnier
2015-06-21 20:08               ` Philipp Stephani [this message]
2015-06-22 15:56                 ` Stefan Monnier
2016-09-11 18:04                   ` Philipp Stephani
2016-09-11 19:25                     ` Eli Zaretskii

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='CAArVCkSL2zxP=dFkWO37vAf=-oBGK9pKE12uUeGJ7U15GgrO7w@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=20640@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@gnu.org \
    /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).