[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
From: |
Eli Zaretskii |
Subject: |
bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit |
Date: |
Tue, 26 Feb 2019 20:27:55 +0200 |
> 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.
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, (continued)
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/24
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/24
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/25
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/25
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit,
Eli Zaretskii <=