From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Why does this thread code crash my emacs? Date: Sat, 16 Oct 2021 14:12:13 +0300 Message-ID: <83tuhhgr5e.fsf@gnu.org> References: <87pms6jmuk.fsf@ddavies.net> <87mtnajfdm.fsf@dick> <83lf2uhzd3.fsf@gnu.org> <877deegiz5.fsf@dick> <83bl3pigi1.fsf@gnu.org> <87k0idfdgi.fsf@dick> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5388"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: dick Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 16 13:13:18 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mbhcs-0001Di-24 for ged-emacs-devel@m.gmane-mx.org; Sat, 16 Oct 2021 13:13:18 +0200 Original-Received: from localhost ([::1]:52174 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mbhcq-0006De-66 for ged-emacs-devel@m.gmane-mx.org; Sat, 16 Oct 2021 07:13:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36730) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbhbp-0005W9-Gv for emacs-devel@gnu.org; Sat, 16 Oct 2021 07:12:13 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45652) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mbhbp-0000eP-8Y; Sat, 16 Oct 2021 07:12:13 -0400 Original-Received: from [87.69.77.57] (port=4789 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mbhbo-0002GO-Mp; Sat, 16 Oct 2021 07:12:13 -0400 In-Reply-To: <87k0idfdgi.fsf@dick> (message from dick on Sat, 16 Oct 2021 06:53:17 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:277167 Archived-At: > From: dick > Cc: emacs-devel@gnu.org > Date: Sat, 16 Oct 2021 06:53:17 -0400 > > > But the facts are the OP's recipe proves that a non-main thread _can_ wait > > for input. > > It does not. Of course, it does: it calls read_char. > Try typing into the *Hanoi* buffer. It does not stop the Hanoi as > it would if it were running in main thread. And why is that? > > If you do care, why does it matter what you did in your private fork > > Narcissism of course. Why does anyone do anything for no pay? The more > serious answer is I am using emacs-devel as a recruiting mechanism to show > what's possible under a maintainer who: > > 1. much prefers a PR-based workflow with automated CI, superior changeset > management, conversation visibility, commit and line citation, but equally > poor search > > 2. is unafraid to address problems at their root, quite distinct from the > current committee's timorous "a stopgap patch here and a stopgap there" > approach. Let's talk in a year or 5 or 10 and see where did your fork get under such a maintainer.