As a side question, wouldn't it make more sense if read -d"" -t 0 makes the read in raw mode? Or is it carved in stone for historical reasons? If so, then couldn't we maybe some time in the future get a new "-T 0" option that could do a read in raw mode? Because, as things are now, one has no way to check from within a tight loop whether some key has been pressed -- not without a wasteful timeout option, or without an expensive external call to set the term raw.
Re: CORRECTED: Bug in the read command
pourko--- via Bug reports for the GNU Bourne Again SHell Wed, 17 Sep 2025 09:03:35 -0700
- CORRECTED: Bug i... pourko--- via Bug reports for the GNU Bourne Again SHell
- Re: CORRECT... Chet Ramey
- Re: COR... pourko--- via Bug reports for the GNU Bourne Again SHell
- Re: COR... pourko--- via Bug reports for the GNU Bourne Again SHell
- Re: COR... pourko--- via Bug reports for the GNU Bourne Again SHell
- Re: CORRECT... pourko--- via Bug reports for the GNU Bourne Again SHell
- Re: CORRECT... pourko2--- via Bug reports for the GNU Bourne Again SHell
