all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dick <dick.r.chiang@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Why does this thread code crash my emacs?
Date: Sat, 16 Oct 2021 14:12:13 +0300	[thread overview]
Message-ID: <83tuhhgr5e.fsf@gnu.org> (raw)
In-Reply-To: <87k0idfdgi.fsf@dick> (message from dick on Sat, 16 Oct 2021 06:53:17 -0400)

> From: dick <dick.r.chiang@gmail.com>
> 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.



  reply	other threads:[~2021-10-16 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 16:04 Why does this thread code crash my emacs? Derek Davies
2021-10-15 18:45 ` dick
2021-10-15 19:17   ` Eli Zaretskii
2021-10-15 19:56     ` dick
2021-10-16  7:06       ` tomas
2021-10-16  7:19       ` Eli Zaretskii
2021-10-16 10:53         ` dick
2021-10-16 11:12           ` Eli Zaretskii [this message]
2021-10-15 19:01 ` Eli Zaretskii
2021-10-15 22:17   ` Derek Davies
2021-10-16  0:08     ` dick
2021-10-16 11:51   ` 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=83tuhhgr5e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dick.r.chiang@gmail.com \
    --cc=emacs-devel@gnu.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.