all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: monnier@iro.umontreal.ca, 34535@debbugs.gnu.org
Subject: bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
Date: Tue, 26 Feb 2019 20:27:55 +0200	[thread overview]
Message-ID: <83r2bul80k.fsf@gnu.org> (raw)
In-Reply-To: <8736oa4fzu.fsf@web.de> (message from Michael Heerdegen on Tue, 26 Feb 2019 18:27:33 +0100)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: monnier@iro.umontreal.ca,  34535@debbugs.gnu.org
> Date: Tue, 26 Feb 2019 18:27:33 +0100
> 
> This seems only to happen after several hours of suspended ram sleep.  I
> just waited this time to see if it ends, and after ~10 seconds, CPU
> usage went to nearly zero and everything was good.  I'm not sure if
> Emacs is to blame for anything, though I didn't see this before.  When
> it happens the next time, I'll have a look if other programs are
> responding.

OK, thanks.  I guess I will soon push the change after all.





  reply	other threads:[~2019-02-26 18:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 22:29 bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit Michael Heerdegen
2019-02-22 16:08 ` Eli Zaretskii
2019-02-22 20:09   ` Eli Zaretskii
2019-02-22 20:25     ` Eli Zaretskii
2019-02-23  4:27   ` Michael Heerdegen
2019-02-23  8:21     ` Eli Zaretskii
2019-02-23 15:13       ` Stefan Monnier
2019-02-23 16:54         ` Eli Zaretskii
2019-02-24  7:16       ` Michael Heerdegen
2019-02-24 16:06         ` Eli Zaretskii
2019-02-25  7:09       ` Michael Heerdegen
2019-02-25 15:33         ` Eli Zaretskii
2019-02-26  9:56           ` Michael Heerdegen
2019-02-26 15:26             ` Eli Zaretskii
2019-02-26 17:27             ` Michael Heerdegen
2019-02-26 18:27               ` Eli Zaretskii [this message]
2019-03-01 10:21                 ` Eli Zaretskii

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=83r2bul80k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34535@debbugs.gnu.org \
    --cc=michael_heerdegen@web.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 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.