From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Stefan Kangas <stefan@marxist.se>
Cc: 44854@debbugs.gnu.org
Subject: bug#44854: [PATCH] Add lexical-binding cookie to autoload files
Date: Tue, 24 Nov 2020 14:39:20 -0800 (PST) [thread overview]
Message-ID: <29cb4bf9-35eb-40df-b487-bfd622d2c665@default> (raw)
In-Reply-To: <jwv1rgiifmd.fsf-monnier+emacs@gnu.org>
> AFAIK, this is a typical example of Drew's reaction to a suggested change: oppose it without even the vaguest understanding of what the change is about.
>
> I recommend you ignore his deluge of messages which tend to just hijack
> the discussion or at least derail it.
(Ignoring the ad hominem attack. Ideas please, not
people.)
I tried to understand it. I looked at the patch and
the source code. I asked what files this applies to.
I got no explanation of what this really does (or why).
Is it so obvious what the effect is? It wasn't/isn't
to me.
And I said from the very beginning that I wasn't sure
I understand it, and I asked for clarification.
I responded to the question asking if anyone has a
problem with the proposed change, by saying that IF
my understanding of it is correct (and I stated my
understanding) THEN yes, I would object.
FWIW, Eli too asked what the benefits are - what this
is really for. Haven't seen an answer to that either.
(I'm not suggesting that Eli, like me, had difficulty
understanding what this does.)
next prev parent reply other threads:[~2020-11-24 22:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 19:34 bug#44854: [PATCH] Add lexical-binding cookie to autoload files Stefan Kangas
2020-11-24 20:21 ` Eli Zaretskii
2020-11-24 20:46 ` Stefan Kangas
2020-11-24 20:54 ` Drew Adams
2020-11-24 21:05 ` Stefan Kangas
2020-11-24 21:22 ` Drew Adams
2020-11-24 21:57 ` Stefan Monnier
2020-11-24 22:39 ` Drew Adams [this message]
2020-11-24 21:04 ` Eli Zaretskii
2020-11-24 21:35 ` Stefan Kangas
2020-11-24 21:43 ` Drew Adams
2020-11-25 7:23 ` Lars Ingebrigtsen
2020-11-25 15:02 ` Eli Zaretskii
2020-11-25 15:08 ` Lars Ingebrigtsen
2020-11-25 16:40 ` Stefan Monnier
2020-11-25 17:30 ` Eli Zaretskii
2020-11-25 17:54 ` Stefan Monnier
2020-11-25 18:22 ` Eli Zaretskii
2020-11-25 18:56 ` Stefan Monnier
2020-11-25 19:01 ` Philipp Stephani
2020-11-25 19:15 ` Eli Zaretskii
2020-11-25 19:12 ` Eli Zaretskii
2020-11-25 19:35 ` Philipp Stephani
2020-11-25 20:00 ` Eli Zaretskii
2020-11-25 20:06 ` Stefan Monnier
2020-11-25 20:27 ` Eli Zaretskii
2020-11-25 21:07 ` Stefan Kangas
2020-11-26 14:02 ` Eli Zaretskii
2020-11-27 22:39 ` Andy Moreton
2020-11-28 7:59 ` Eli Zaretskii
2020-11-29 10:30 ` Lars Ingebrigtsen
2020-12-02 13:51 ` Stefan Kangas
2020-11-25 20:53 ` Stefan Kangas
2020-11-24 20:24 ` Drew Adams
2020-11-24 21:05 ` Stefan Kangas
2020-11-24 21:28 ` Drew Adams
2020-11-24 21:58 ` Stefan Monnier
2020-12-31 5:39 ` Lars Ingebrigtsen
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=29cb4bf9-35eb-40df-b487-bfd622d2c665@default \
--to=drew.adams@oracle.com \
--cc=44854@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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).