all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noah Friedman <noah@splode.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19494@debbugs.gnu.org, Noah Friedman <friedman@splode.com>
Subject: bug#19494: 25.0.50; infinite loop in readable_event on master branch
Date: Tue, 20 Jul 2021 01:47:34 -0700 (PDT)	[thread overview]
Message-ID: <eac04875-7333-4c04-854e-75135844ab8a@splode.com> (raw)
In-Reply-To: <877dhuqeat.fsf@gnus.org>

I'll have to go dig around and get back to you; I've forgotten the context and what I might have done about it.

*From: *Lars Ingebrigtsen <larsi@gnus.org>
*To: *Noah Friedman <friedman@splode.com>
*CC: *eliz@gnu.org; 19494@debbugs.gnu.org
*Date: *Jul 13, 2021 11:06:36
*Subject: *Re: bug#19494: 25.0.50; infinite loop in readable_event on master branch

> Noah Friedman <friedman@splode.com> writes:
> 
>>> Why do you need that code, and in a timer on top of that?  It looks
>>> strangely, and probably papers over some bug, either one that existed
>>> in the past or maybe even an existing one.  If that bug still exists,
>>> a bug report will be appreciated.
>> 
>> It's very old code, circa 1995.  Since it predates the v21 redisplay engine
>> rewrite, I have no idea if it's still necessary; I'm testing that now.
> 
> This was six years ago -- are you still seeing this issue in more recent
> Emacs versions?
> 





  reply	other threads:[~2021-07-20  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03  3:18 bug#19494: 25.0.50; infinite loop in readable_event on master branch Noah Friedman
2015-01-03  8:17 ` Eli Zaretskii
2015-01-07 21:08   ` Noah Friedman
2021-07-13 18:06     ` Lars Ingebrigtsen
2021-07-20  8:47       ` Noah Friedman [this message]
2021-08-19 13:21         ` Lars Ingebrigtsen
2021-08-27 20:38           ` Noah Friedman
2021-08-28 15:07             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eac04875-7333-4c04-854e-75135844ab8a@splode.com \
    --to=noah@splode.com \
    --cc=19494@debbugs.gnu.org \
    --cc=friedman@splode.com \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.