I can confirm that the patch resolves all the issues I had.
Thank you very much for your help, it is very appreciated.
On 10/15/24 11:08 AM, Thomas Oettli wrote:
> Got it, I just backported your patch to Bash 5.2 and it fixed the issue on
> my build host.
> I will roll out the patched version to a
On 10/15/24 11:08 AM, Thomas Oettli wrote:
Got it, I just backported your patch to Bash 5.2 and it fixed the issue on
my build host.
I will roll out the patched version to all my hosts this weekend and keep
you noticed if anything strange happens.
BTW: will this patch be backported to previous
?
Von: Chet Ramey
Gesendet: Dienstag, 15. Oktober 2024 16:24
An: Thomas Oettli ; bug-bash@gnu.org
Cc: chet.ra...@case.edu
Betreff: [EXT] Re: AW: Re: AW: Re: read command sometimes misses newline on
timeout
CAUTION: This email originated from outside the SFS organization. Do not follow
On 10/15/24 10:06 AM, Thomas Oettli wrote:
That sounds promising. Is the fix somewhere accessible for me? I would gladly
test it.
I pushed it to the devel branch this morning.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocra
That sounds promising. Is the fix somewhere accessible for me? I would gladly
test it.
- Thomas
On 10/7/24 9:49 AM, Thomas Oettli wrote:
I agree with you, but it should never happen that read returns timeout,
also returns the full line and has already read the newline character.
If that happens, there is no way for the script to decide what to do.
I think I found the problem and fixed it
On 10/7/24 9:49 AM, Thomas Oettli wrote:
I agree with you, but it should never happen that read returns timeout,
also returns the full line and has already read the newline character.
I don't see how that can happen, given how the code is structured. It's
possible for the shell to read all the
