From: Aaron Jensen <aaronjensen@gmail.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: mail@daniel-mendler.de, 38024@debbugs.gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>,
joaotavora@gmail.com
Subject: bug#38024: Remove icomplete workaround
Date: Mon, 1 Nov 2021 11:33:44 -0400 [thread overview]
Message-ID: <CAHyO48zOG7kFdaZrxYeqLTp_c0V3z+6Cp=gUybBN8UZg7XdzPA@mail.gmail.com> (raw)
In-Reply-To: <87ilxckywn.fsf@gmail.com>
On Mon, Nov 1, 2021 at 5:28 AM Kévin Le Gouguec
<kevin.legouguec@gmail.com> wrote:
>
> Hey Aaron,
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > Aaron Jensen [2021-10-31 20:49:23] wrote:
> >>
> >> Would it be possible to remove it? I'm ccing the original reporter and
> >> fixer in case they are able to shed more light on this or test without
> >> the fix to see if they can reproduce it.
> >>
> >> I've attached a patch if we are good to remove it.
> >
> > Thanks, I just pushed your patch to `master`.
> > We'll see if the problem comes back, and if so, we'll have to try and
> > fix it better.
>
> Congrats on your investigation work; I wish I could shed more light on
> what this workaround was meant to accomplish. I've tried to reproduce
> my original issue, but so far I was not successful.
>
> If my initial report can be trusted, the bug happened (1) back when the
> development branch was 27.0.50 (commit 61fb521481) (2) on an old
> battered laptop that I can no longer power on without disturbing loud
> fan demons.
>
> 26.3 no longer compiles on my end[1], so all I could do was try to
> reproduce on master, where the workaround has been reverted, on other
> computers I have lying around. The symptoms have not resurfaced yet,
> so… I'll go with a timid, yet hopeful "yay" 🙂
Thank you for confirming. Hopefully that's the last of it!
Best,
Aaron
prev parent reply other threads:[~2021-11-01 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHyO48wYzmHL0FEc9e3peZXzHdxOSwoF4da3Qvjd2XyWvPqoMg@mail.gmail.com>
2021-11-01 2:38 ` bug#38024: Remove icomplete workaround Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-01 3:55 ` Aaron Jensen
2021-11-01 9:28 ` Kévin Le Gouguec
2021-11-01 15:33 ` Aaron Jensen [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='CAHyO48zOG7kFdaZrxYeqLTp_c0V3z+6Cp=gUybBN8UZg7XdzPA@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=38024@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=kevin.legouguec@gmail.com \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
/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).