On Sun, 13 Oct 2024, 17:15 Oğuz, wrote:
> On Sun, Oct 13, 2024 at 3:18 AM Chet Ramey wrote:
> > You have two processes fighting over stdin.
>
> Why though? Can't bash just close the procsub's stdin when `:' returns?
>
Of course not. The operating system won't let processes meddle with each
othe
On Sun, Oct 13, 2024 at 3:18 AM Chet Ramey wrote:
> You have two processes fighting over stdin.
Why though? Can't bash just close the procsub's stdin when `:' returns?
On Okt 13 2024, Oğuz wrote:
> Why though? Can't bash just close the procsub's stdin when `:' returns?
bash has no handle on the command's stdin.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely di
A new issue popped up with these changes. After second time of suspend and
foreground with binding, the tty will not react to control keys but instead
print them on the prompt.
Repeat-By:
| start vim
ctrl-z (to suspend)
ctrl-a (bound to `fg` to bring to foregound)
ctrl-z (to suspend a 2nd t
On 10/11/24 12:49 PM, G. Branden Robinson wrote:
The docs always get some love as part of the release process. I decided
to give them a more thorough overhaul this cycle.
Shotts will have to revise his book again... ;-)
He should be anyway, shouldn't he? Bash changes from release to release,
On 10/1/24 3:54 AM, konsolebox wrote:
# declare -A x
# echo ${x@a}
A
# set -u
# echo ${x@a}
bash: x: unbound variable
Obvious workaround would be to disable `set -u` temporarily or assign
a temporary array value but that shouldn't need to be done.
I'll consider it, but I'm not eager to carve o
