From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 10483@debbugs.gnu.org, haj@posteo.de
Subject: bug#10483: [PATCH] cperl-mode: Avoid endless loop
Date: Fri, 04 Sep 2020 14:34:54 +0300 [thread overview]
Message-ID: <83r1rhu65d.fsf@gnu.org> (raw)
In-Reply-To: <87lfhpddsf.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 04 Sep 2020 12:41:52 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: haj@posteo.de, 10483@debbugs.gnu.org
> Date: Fri, 04 Sep 2020 12:41:52 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I don't think I understand what's missing in what we have already.
> > The equivalent of 'fork' is 'start-process', and the equivalent of
> > 'waitpid' is a test of what 'process-status' returns.
>
> waitpid waits until a process changes status, doesn't it? In Emacs Lisp
> we have to write a loop over `process-status', which adds latency and
> just doesn't seem very elegant.
But the advantage of a loop is that you can do something while you
wait. Whereas if you expose waitpid to Lisp, the Lisp program which
calls it will be parked inside the call, and the entire Emacs session
will stall. Or what am I missing?
next prev parent reply other threads:[~2020-09-04 11:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 0:02 bug#10483: 24.0.92; cperl-indent-exp hangs Eric Hanchrow
2020-08-31 17:06 ` bug#10483: [PATCH] cperl-mode: Avoid endless loop Harald Jörg
2020-08-31 17:24 ` Eli Zaretskii
2020-08-31 18:08 ` Harald Jörg
2020-08-31 18:49 ` Eli Zaretskii
2020-08-31 21:23 ` Stefan Kangas
2020-09-01 16:12 ` Harald Jörg
2020-09-04 3:17 ` Lars Ingebrigtsen
2020-09-04 7:15 ` Eli Zaretskii
2020-09-04 10:41 ` Lars Ingebrigtsen
2020-09-04 10:51 ` Andreas Schwab
2020-09-04 10:55 ` Lars Ingebrigtsen
2020-09-04 11:36 ` Eli Zaretskii
2020-09-04 12:00 ` Lars Ingebrigtsen
2020-09-04 12:05 ` Andreas Schwab
2020-09-04 11:34 ` Eli Zaretskii [this message]
2020-09-04 11:59 ` Lars Ingebrigtsen
2020-09-04 12:28 ` Eli Zaretskii
2020-09-04 12:36 ` Lars Ingebrigtsen
2020-09-04 12:09 ` Andreas Schwab
2020-10-05 18:30 ` bug#10483: [PATCH] Fix a bogus test introduced by treating (Bug#10483) Harald Jörg
2020-10-06 1:40 ` 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=83r1rhu65d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10483@debbugs.gnu.org \
--cc=haj@posteo.de \
--cc=larsi@gnus.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.