Upgrading to bash5.1 solved the problem.
On 29.06.2021 14:26, Basin Ilya wrote:
> I'll try to build bash 5 for Cygwin and reply here
>
> On 29.06.2021 11:00, Andreas Schwab wrote:
>> On Jun 29 2021, Basin Ilya wrote:
>>
>>> However, shell-backward-kill-wo
I'll try to build bash 5 for Cygwin and reply here
On 29.06.2021 11:00, Andreas Schwab wrote:
> On Jun 29 2021, Basin Ilya wrote:
>
>> However, shell-backward-kill-word erases the word immedeately
>> preceding the caret plus it erases one additional space.
>
> Does it? Not for me.
>
> Andreas.
>
The default werase setting erases the series of white spaces before the caret,
then it erases the preceding word (without touching the spaces before the word).
I expected that shell-backward-kill-word would do the same with the difference
that the entire quoted argument would be erased.
However,
Hi.
In an attempt to capture the output of 'time' I used the process substitution
and noticed that the subshell also prints its times. Actually I this happens
when I redirect any fd, not just stderr.
#!/bin/bash
time {
sleep 0.25
exec 6> >(
sed 's/^/captured: /'
Hi list.
An attempt to open a named pipe created with mkfifo cannot be
interrupted with SIGINT, if trap ... INT installed.
(reading from an opened fifo is interruptible and similar attempt to
open a /dev/tcp socket is interruptible too)
#!/bin/bash
set -e
function errtrap {
