2019-08-08 10:38:48 -0400, Greg Wooledge:
[...]
> > shopt -s failglob
> > command="echo xyz\(\)"
> > $command
> > ```
> >
> > And it was working fine. But somewhere between bash version 4 and 5 I
> > realized it generates an error:
> > no match: xyz\(\)
[...]
> And my personal response for this va
On Thu, Aug 08, 2019 at 04:33:16PM +0200, Janek Mi wrote:
> For some time in my scripts I was using something like this:
>
> ```shell
> #!/usr/bin/env bash
> shopt -s failglob
> command="echo xyz\(\)"
> $command
> ```
>
> And it was working fine. But somewhere between bash version 4 and 5 I
> rea
On 8/8/19 10:33 AM, Janek Mi wrote:
> For some time in my scripts I was using something like this:
>
> ```shell
> #!/usr/bin/env bash
> shopt -s failglob
> command="echo xyz\(\)"
> $command
> ```
>
> And it was working fine. But somewhere between bash version 4 and 5 I
> realized it generates an
For some time in my scripts I was using something like this:
```shell
#!/usr/bin/env bash
shopt -s failglob
command="echo xyz\(\)"
$command
```
And it was working fine. But somewhere between bash version 4 and 5 I
realized it generates an error:
no match: xyz\(\)
with exit code equal 1.
If I un
On 8/8/19 4:13 AM, Tomas Janousek wrote:
> Hi,
>
> On Sun, Aug 04, 2019 at 01:42:12PM -0400, Chet Ramey wrote:
>> On 8/3/19 11:05 AM, Tomas Janousek wrote:
>> I don't have or use tmux, but I'm going to guess that `kill-window' sends
>> a SIGHUP to the process group and follows it up with a SIGKILL
Hi,
On Sun, Aug 04, 2019 at 01:42:12PM -0400, Chet Ramey wrote:
> On 8/3/19 11:05 AM, Tomas Janousek wrote:
> I don't have or use tmux, but I'm going to guess that `kill-window' sends
> a SIGHUP to the process group and follows it up with a SIGKILL. The
> `source' turns off saving to history -- th
