all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Trey Ethan Harris <treyharris@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 13697@debbugs.gnu.org
Subject: bug#13697: A way to tell if Emacs can interact with the user
Date: Wed, 3 Apr 2019 19:25:11 -0400	[thread overview]
Message-ID: <CALKJ+EvjE7++2wgdjC+0n=fEupzszAvBpko6n+HgLiz+KShZUw@mail.gmail.com> (raw)
In-Reply-To: <87ef6ig0kl.fsf_-_@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

On Wed, Apr 3, 2019 at 6:56 PM Noam Postavsky npostavs@gmail.com
<http://mailto:npostavs@gmail.com> wrote:


>
> Hmm, I'm not sure where all these threads you're talking about will come
> from.  Emacs is still mostly single-threaded, and we still have stuff
> like Bug#25214 "Interacting with user from threads other than the
> primary" open.
>
Curious; when I start Emacs interactively and it gets stuck on, say, a
desktop lock file (the most common thing that interrupts startup for me),
initialization continues even as the yes-or-no-p waits. I assumed that
meant there was threading. If it does not, then can whatever asynchronicity
does let this continuation happen be substituted for “threads” in my
suggestion above?

[-- Attachment #2: Type: text/html, Size: 3200 bytes --]

  reply	other threads:[~2019-04-03 23:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 17:02 bug#13697: A way to tell if Emacs can interact with the user Glenn Morris
2019-04-03 21:01 ` bug#13697: Reopening Trey Ethan Harris
2019-04-03 22:56   ` bug#13697: A way to tell if Emacs can interact with the user Noam Postavsky
2019-04-03 23:25     ` Trey Ethan Harris [this message]
2019-04-04 12:59   ` bug#13697: Reopening Eli Zaretskii
2021-02-13  9:31 ` bug#13697: A way to tell if Emacs can interact with the user Glenn Morris
2021-02-13 11:38   ` Lars Ingebrigtsen

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='CALKJ+EvjE7++2wgdjC+0n=fEupzszAvBpko6n+HgLiz+KShZUw@mail.gmail.com' \
    --to=treyharris@gmail.com \
    --cc=13697@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    /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.