From: Allen Wang <allenhw1996@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 60810@debbugs.gnu.org
Subject: bug#60810: 30.0.50; `while-no-input' in GUI(macOS) is much slower than emacs -nw
Date: Sun, 15 Jan 2023 12:48:59 -0800 [thread overview]
Message-ID: <CAE=LL-3dcbKQ4GqrsdErPgeK9k9VRRiX4c=yge2SxuXPXrdxiw@mail.gmail.com> (raw)
In-Reply-To: <874jssb0e1.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
Thank you for the quick response and the info. Sounds like this can't be
fixed easily; I'll see if polling-period works for me.
On Sun, Jan 15, 2023 at 1:41 AM Po Lu <luangruo@yahoo.com> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Does NS use a separate thread to handle input events?
>
> Unfortunately not.
>
> > If so, could that separate thread set quit-flag when we are under
> > throw-on-input, if it detects a suitable input event? The w32 port
> > does that, see signal_user_input in w32fns.c. This should allow the
> > Lisp thread detect that input is pending in a more timely fashion.
>
> I understand that approach, it's taken in the Android port as well.
> Unfortunately, it cannot work because the NS port currently runs in the
> same thread that Lisp runs in.
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 1245 bytes --]
prev parent reply other threads:[~2023-01-15 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 8:07 bug#60810: 30.0.50; `while-no-input' in GUI(macOS) is much slower than emacs -nw Allen Wang
2023-01-15 1:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-15 7:08 ` Eli Zaretskii
2023-01-15 9:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-15 20:48 ` Allen Wang [this message]
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='CAE=LL-3dcbKQ4GqrsdErPgeK9k9VRRiX4c=yge2SxuXPXrdxiw@mail.gmail.com' \
--to=allenhw1996@gmail.com \
--cc=60810@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.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.