From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: noloader@gmail.com, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: Hang in make check
Date: Tue, 30 Mar 2021 17:33:27 +0300 [thread overview]
Message-ID: <83k0pok8y0.fsf@gnu.org> (raw)
In-Reply-To: <87tuos4tl1.fsf@igel.home> (message from Andreas Schwab on Tue, 30 Mar 2021 16:14:18 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, noloader@gmail.com,
> emacs-devel@gnu.org
> Date: Tue, 30 Mar 2021 16:14:18 +0200
>
> On Mär 30 2021, Eli Zaretskii wrote:
>
> > Yes. It's actually worse: _because_ the getchar call hangs, Emacs
> > doesn't get to running the timer function at all.
> >
> > So I think the code needs to be modified, or maybe simply disabled
> > when system-configuration-features includes neither DBUS nor NOTIFY
> > nor THREADS.
>
> Perhaps that getchar call should be removed altogether?
How will keyboard input be received then in those configurations?
This is a corner use case -- why would someone build Emacs with all
those features disabled, and then want to run the test suite? I'm not
sure we should bother too much about that case.
next prev parent reply other threads:[~2021-03-30 14:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 22:14 Hang in make check Jeffrey Walton
2021-03-28 8:27 ` Michael Albinus
2021-03-28 9:02 ` Jeffrey Walton
2021-03-28 12:14 ` Michael Albinus
2021-03-28 17:28 ` Jeffrey Walton
2021-03-28 19:11 ` Michael Albinus
2021-03-28 19:20 ` Lars Ingebrigtsen
2021-03-28 19:33 ` Jeffrey Walton
2021-03-28 19:42 ` Lars Ingebrigtsen
2021-03-28 19:51 ` Lars Ingebrigtsen
2021-03-29 4:48 ` Eli Zaretskii
2021-03-29 11:00 ` Lars Ingebrigtsen
2021-03-29 11:04 ` Eli Zaretskii
2021-03-29 11:24 ` Eli Zaretskii
2021-03-30 13:29 ` Lars Ingebrigtsen
2021-03-30 13:46 ` Eli Zaretskii
2021-03-30 14:14 ` Andreas Schwab
2021-03-30 14:33 ` Eli Zaretskii [this message]
2021-03-30 15:16 ` Andreas Schwab
2021-03-30 15:33 ` 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
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=83k0pok8y0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=noloader@gmail.com \
--cc=schwab@linux-m68k.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).