Re: [hackers] [st][PATCH 1/1] fix a problem that the standard streams are unexpectedly closed

2021-08-24 Thread Hiltjo Posthuma
On Tue, Aug 24, 2021 at 06:25:05AM +0900, Koichi Murase wrote: > In the current implementation, the slave PTY (assigned to the variable > `s') is always closed after duplicating it to file descriptors of > standard streams (0, 1, and 2). However, when the allocated slave PTY > `s' is already one o

[hackers] [st][PATCH 1/1] fix a problem that the standard streams are unexpectedly closed

2021-08-23 Thread Koichi Murase
In the current implementation, the slave PTY (assigned to the variable `s') is always closed after duplicating it to file descriptors of standard streams (0, 1, and 2). However, when the allocated slave PTY `s' is already one of 0, 1, or 2, this causes unexpected closing of a standard stream. The

[hackers] [st][PATCH 1/1] fix a problem that the standard streams are unexpectedly closed

2021-08-23 Thread Koichi Murase
In the current implementation, the slave PTY (assigned to the variable `s') is always closed after duplicating it to file descriptors of standard streams (0, 1, and 2). However, when the allocated slave PTY `s' is already one of 0, 1, or 2, this causes unexpected closing of a standard stream. The

[hackers] [st][PATCH 1/1] fix a problem that the standard streams are unexpectedly closed

2021-08-23 Thread Koichi Murase
After the advice from Alex Pilon, I update the commit message and resend the patch using `git send-email'. Here's the description of this fix (which is essentially the same as the previous post https://lists.suckless.org/hackers/2108/17978.html). Problem: When st is started with fd 0, 1, and 2