From: Eli Zaretskii <eliz@gnu.org>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: larsi@gnus.org, 51177@debbugs.gnu.org, jakanakaevangeli@chiru.no
Subject: bug#51177: 29.0.50; stop-process on pipes
Date: Sat, 16 Oct 2021 19:47:31 +0300 [thread overview]
Message-ID: <83fst0hq70.fsf@gnu.org> (raw)
In-Reply-To: <m2fst1aqfx.fsf@gmail.com> (message from Helmut Eller on Sat, 16 Oct 2021 18:24:02 +0200)
> From: Helmut Eller <eller.helmut@gmail.com>
> Date: Sat, 16 Oct 2021 18:24:02 +0200
> Cc: 51177@debbugs.gnu.org, jakanakaevangeli@chiru.no
>
> On Thu, Oct 14 2021, Lars Ingebrigtsen wrote:
>
> > Helmut Eller <eller.helmut@gmail.com> writes:
> >
> >> I did not read the docstring but I did read the manual. This feature is
> >> not described in the manual. At least not near set-process-filter.
> >
> > Yup. I've now documented the t value in the manual in emacs-28.
>
> The t value also doesn't seem be handled correctly by make-process:
>
> (ert-deftest test-filter=t ()
> (let ((p (make-process :command '("dd" "if=/dev/zero" "count=0")
> :name "foo"
> :filter t)))
> ;;(set-process-filter p t)
> (while (eq (process-status p) 'run)
> (accept-process-output p))))
>
> when executed with
>
> emacs -Q --batch -l test.el -f ert-run-tests-batch-and-exit
>
> produces:
>
> Running 1 tests (2021-10-16 18:21:53+0200, selector ‘t’)
> Test test-filter=t backtrace:
> t(#<process foo> "0+0 records in\n0+0 records out\n")
> accept-process-output(#<process foo>)
What do we expect to happen when a Lisp program calls
accept-process-output on a process that is stopped?
next prev parent reply other threads:[~2021-10-16 16:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 9:20 bug#51177: 29.0.50; stop-process on pipes Helmut Eller
2021-10-13 11:45 ` Lars Ingebrigtsen
2021-10-13 13:39 ` Helmut Eller
2021-10-13 13:01 ` Eli Zaretskii
2021-10-13 14:04 ` Helmut Eller
2021-10-14 7:51 ` jakanakaevangeli
2021-10-14 8:00 ` Helmut Eller
2021-10-14 11:10 ` Lars Ingebrigtsen
2021-10-16 16:24 ` Helmut Eller
2021-10-16 16:47 ` Eli Zaretskii [this message]
2021-10-16 17:07 ` Helmut Eller
2021-10-18 6:58 ` Lars Ingebrigtsen
2021-11-11 19:47 ` Helmut Eller
2021-11-12 3:35 ` Lars Ingebrigtsen
2021-11-12 5:13 ` Helmut Eller
2021-11-12 6:30 ` Lars Ingebrigtsen
2021-11-12 7:21 ` Eli Zaretskii
2021-11-12 8:28 ` Helmut Eller
2021-11-12 12:00 ` Eli Zaretskii
2021-11-12 12:34 ` Helmut Eller
2021-11-12 13:05 ` Eli Zaretskii
2021-11-12 13:26 ` Helmut Eller
2021-11-12 12:58 ` Helmut Eller
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fst0hq70.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51177@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
--cc=jakanakaevangeli@chiru.no \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).