[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#51177: 29.0.50; stop-process on pipes
From: |
Eli Zaretskii |
Subject: |
bug#51177: 29.0.50; stop-process on pipes |
Date: |
Fri, 12 Nov 2021 09:21:45 +0200 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 12 Nov 2021 07:30:45 +0100
> Cc: 51177@debbugs.gnu.org
>
> As for the patch itself, I'd worry that a subtle change in semantics
> here would break stuff (and this is an area that's full of notoriously
> subtle things), but perhaps it's OK. Anybody have an opinion here?
First, the patch included an fprintf that should probably be removed.
And second, I'd prefer to have a variable exposed to Lisp to control
this behavior, so that if someone finds some strange consequences, we
could ask them to flip the variable and see if the problem goes away.
My main worry is what happens if we try reading from a pipe to a
process that died, and so its end of the pipe could be closed. Was
this patch tested when process-connection-type is nil?
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/11/11
- bug#51177: 29.0.50; stop-process on pipes, Lars Ingebrigtsen, 2021/11/11
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/11/12
- bug#51177: 29.0.50; stop-process on pipes, Lars Ingebrigtsen, 2021/11/12
- bug#51177: 29.0.50; stop-process on pipes,
Eli Zaretskii <=
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/11/12
- bug#51177: 29.0.50; stop-process on pipes, Eli Zaretskii, 2021/11/12
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/11/12
- bug#51177: 29.0.50; stop-process on pipes, Eli Zaretskii, 2021/11/12
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/11/12
- bug#51177: 29.0.50; stop-process on pipes, Helmut Eller, 2021/11/12