From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: monnier@iro.umontreal.ca, 20640@debbugs.gnu.org
Subject: bug#20640: 24.5; lexical-binding should work like a normal file-local variable
Date: Sun, 11 Sep 2016 22:25:54 +0300 [thread overview]
Message-ID: <83r38q9r25.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkTGu95+4kMj9JxDvMRb8oSu6CMfvj2fOh0YpU9Hz8jTJw@mail.gmail.com> (message from Philipp Stephani on Sun, 11 Sep 2016 18:04:13 +0000)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 11 Sep 2016 18:04:13 +0000
> Cc: 20640@debbugs.gnu.org
>
> Stefan Monnier <monnier@iro.umontreal.ca> schrieb am Mo., 22. Juni 2015 um 17:57 Uhr:
>
> > 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.
>
> I'm not talking about file-local variables in general. I'm talking
> about the "coding:" pseudo-variable.
>
> No matter how we choose to call it: My argument stands, reading such pseudo-variables from the end of the
> file is desirable, useful, and has negligible disadvantages. Or do we have evidence that users routinely read
> very large (gigabyte-sized) Elisp files from non-seekable sources?
Guys, is this really such a big deal to justify changes in an area
which was not touched in eons? Just let the sleeping dogs lie.
prev parent reply other threads:[~2016-09-11 19:25 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
2015-06-22 15:56 ` Stefan Monnier
2016-09-11 18:04 ` Philipp Stephani
2016-09-11 19:25 ` Eli Zaretskii [this message]
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=83r38q9r25.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20640@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@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).