unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Helmut Eller <eller.helmut@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 51177@debbugs.gnu.org
Subject: bug#51177: 29.0.50; stop-process on pipes
Date: Thu, 11 Nov 2021 20:47:57 +0100	[thread overview]
Message-ID: <m2bl2qa2z6.fsf@gmail.com> (raw)
In-Reply-To: <m2y26xqo1q.fsf@gmail.com>

I have another problem with stopped output.  In this example:

;;; -*- lexical-binding:t -*-

(ert-deftest test-read-after-exit ()
  (let* ((output "")
	 (filter (lambda (p s) (setq output (concat output s))))
	 (sentinel (lambda (p _)
		     (set-process-filter p filter)
		     (while (accept-process-output p 0))))
	 (proc (make-process :command '("printf" "foo")
			     :name "test-proc"
			     :filter t
			     :sentinel sentinel
			     :connection-type 'pipe)))
    (while (process-live-p proc)
      (accept-process-output proc 0.2))
    (set-process-filter proc filter)
    (while (accept-process-output proc 0))
    (should (equal output "foo"))))

the filter function is never called.

We could say that reading the process's output after the process has
terminated is an unreasonable request.  However, I would like to propose
that, in status_notify, the sentinel function should be called before
closing the file descriptors.  That way, the sentinel can read the
buffered output as suggested in the example.

Helmut





  parent reply	other threads:[~2021-11-11 19: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
2021-10-16 17:07               ` Helmut Eller
2021-10-18  6:58                 ` Lars Ingebrigtsen
2021-11-11 19:47 ` Helmut Eller [this message]
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=m2bl2qa2z6.fsf@gmail.com \
    --to=eller.helmut@gmail.com \
    --cc=51177@debbugs.gnu.org \
    --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).