[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#51177: 29.0.50; stop-process on pipes
From: |
Helmut Eller |
Subject: |
bug#51177: 29.0.50; stop-process on pipes |
Date: |
Sat, 16 Oct 2021 19:07:37 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
On Sat, Oct 16 2021, Eli Zaretskii wrote:
>> 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?
I would not expect that the symbol t will be called.
I would expect that accept-process-output on a process initialized with
(make-process ... :filter t)
and
(set-process-filter (make-process ...) t)
does the same.
I would expect that accept-process-output checks and maybe updates the
process-status. If the process-status hasn't changed, then the return
value of accept-process-output should be nil.
Helmut
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/10/13
- bug#51177: 29.0.50; stop-process on pipes, Lars Ingebrigtsen, 2021/10/13
- bug#51177: 29.0.50; stop-process on pipes, Eli Zaretskii, 2021/10/13
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/10/13
- bug#51177: 29.0.50; stop-process on pipes, jakanakaevangeli, 2021/10/14
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/10/14
- bug#51177: 29.0.50; stop-process on pipes, Lars Ingebrigtsen, 2021/10/14
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/10/16
- bug#51177: 29.0.50; stop-process on pipes, Eli Zaretskii, 2021/10/16
- bug#51177: 29.0.50; stop-process on pipes,
Helmut Eller <=
- bug#51177: 29.0.50; stop-process on pipes, Lars Ingebrigtsen, 2021/10/18