From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "dieter@duenenhof-wilhelm.de" <dieter@duenenhof-wilhelm.de>,
"corwin@bru.st" <corwin@bru.st>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : emacs-28 windows binaries available from alpha
Date: Sun, 6 Feb 2022 17:08:40 +0000 [thread overview]
Message-ID: <SJ0PR10MB54888DD58AF4667BA90E8E8FF32B9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83leyoz6qp.fsf@gnu.org>
> > > > Isn't that what's happening?
> > > > It tries to load the ELC.
> > >
> > > Happening where?
> >
> > In the problem I reported. I thought Corwin was
> > suggesting that it didn't try to load the ELC
> > and then compile it to ELN.
>
> In the problem you reported here:...
> indeed Emacs didn't try to compile the .elc file to a .eln.
>
> Like I said: yours was a different situation, not
> the one about which Dieter asked his question.
I'm not really interested in a fruitless
back & forth. A final attempt to clarify
what seems to have confused you about my
"Isn't that what's happening?" question.
I didn't reply to a question from Dieter.
I replied to a post by Corwin, who seemed
to be saying that Emacs didn't try to
load the ELC. Whether or not that's what
Corwin said or meant isn't at issue. I'm
explaining why I asked him that question
at that point.
https://lists.gnu.org/archive/html/emacs-devel/2022-02/msg00201.html
https://lists.gnu.org/archive/html/emacs-devel/2022-02/msg00203.html
Yours was apparently a different part of the
overall discussion, with Dieter (?). You
then jumped in to ask me about my "Isn't that
what's happening?" reply to Corwin, with your
"Happening where?". I replied to clarify, in
the context of my reply to Corwin.
Perhaps your idea of "what's happening" was
something different from what I referred to.
IOW, perhaps we simply misunderstood what
each other was talking about.
How about we don't waste any more time on
this back & forth. Fair enough?
next prev parent reply other threads:[~2022-02-06 17:08 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 18:54 emacs-28 windows binaries available from alpha Corwin Brust
2022-02-04 22:08 ` [External] : " Drew Adams
2022-02-04 22:12 ` Drew Adams
2022-02-04 23:10 ` Corwin Brust
2022-02-05 1:28 ` Drew Adams
2022-02-05 4:35 ` Corwin Brust
2022-02-05 7:43 ` Eli Zaretskii
2022-02-05 8:48 ` Corwin Brust
2022-02-05 9:15 ` Eli Zaretskii
2022-02-05 18:16 ` Drew Adams
2022-02-05 7:25 ` Eli Zaretskii
2022-02-05 9:22 ` H. Dieter Wilhelm
2022-02-05 9:40 ` Eli Zaretskii
2022-02-05 16:49 ` H. Dieter Wilhelm
2022-02-05 17:54 ` Eli Zaretskii
2022-02-05 19:25 ` H. Dieter Wilhelm
2022-02-05 19:47 ` Eli Zaretskii
2022-02-05 21:11 ` H. Dieter Wilhelm
2022-02-05 22:56 ` Corwin Brust
2022-02-06 0:10 ` Drew Adams
2022-02-06 8:22 ` Eli Zaretskii
2022-02-06 8:51 ` Drew Adams
2022-02-06 9:25 ` Eli Zaretskii
2022-02-06 17:08 ` Drew Adams [this message]
2022-02-06 17:33 ` Eli Zaretskii
2022-02-06 8:18 ` Eli Zaretskii
2022-02-05 10:10 ` Eli Zaretskii
2022-02-06 3:11 ` Corwin Brust
2022-02-06 6:57 ` Drew Adams
2022-02-06 9:11 ` Eli Zaretskii
2022-02-06 17:07 ` Drew Adams
2022-02-09 19:08 ` Eli Zaretskii
2022-02-09 21:03 ` Andrea Corallo
2022-02-10 5:52 ` Eli Zaretskii
2022-02-10 8:56 ` Andrea Corallo
2022-02-10 12:13 ` Eli Zaretskii
2022-02-10 13:36 ` Andrea Corallo
2022-02-10 17:15 ` Eli Zaretskii
2022-02-10 18:34 ` Andrea Corallo
2022-02-11 8:29 ` Eli Zaretskii
2022-02-11 9:16 ` Andrea Corallo
2022-02-11 9:21 ` Andrea Corallo
2022-02-11 11:31 ` Eli Zaretskii
2022-02-11 14:16 ` Andrea Corallo
2022-02-11 14:33 ` Eli Zaretskii
2022-02-11 14:38 ` Andrea Corallo
2022-02-11 11:30 ` Eli Zaretskii
2022-02-11 14:18 ` Andrea Corallo
2022-02-11 14:35 ` Eli Zaretskii
2022-02-11 14:44 ` Andrea Corallo
2022-02-11 15:16 ` Eli Zaretskii
2022-02-14 10:25 ` Andrea Corallo
2022-02-10 22:50 ` Corwin Brust
2022-02-06 0:33 ` Corwin Brust
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=SJ0PR10MB54888DD58AF4667BA90E8E8FF32B9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=corwin@bru.st \
--cc=dieter@duenenhof-wilhelm.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).