On 7/28/23 1:51 PM, Martin D Kealey wrote:
On the other hand, since everyone has now had 36+ years to update their
scripts to get rid of backticks, maybe it's time to start issuing a warning
when they're used at all? 🤪
There's no reason to use `` over $(...), but that form is still a required
On 7/27/23 4:31 AM, Denys Vlasenko wrote:
Try these two commands:
$ echo "Date: `date #comment`"
Date: Thu Jul 27 10:28:13 CEST 2023
$ echo "Date: $(date #comment)"
)"
Date: Thu Jul 27 10:27:58 CEST 2023
As you see, #comment is handled differently in `` and $().
Yes. There's a hint in the
Hi Chet,
At 2023-07-29T13:16:55-0400, Chet Ramey wrote:
> On 7/28/23 3:28 PM, G. Branden Robinson wrote:
> > Sorry about that. I fat-fingered it.
> >
> > An 'n' is needed after the second backslash, because we're interpolating
> > a register value.
>
> Thanks. I probably could have figured it o
On 7/28/23 3:28 PM, G. Branden Robinson wrote:
Hi Chet,
At 2023-07-28T15:15:48-0400, Chet Ramey wrote:
Applying the patch without any other changes to bash.1 results in
$ groff -Tascii -P -c -I/usr/local/src/bash/bash-20230728/doc -man
/usr/local/src/bash/bash-20230728/doc/bash.1 > bash.0
trof
Chet Ramey wrote in
<2fd2ed52-3272-3433-6179-164bc5122...@case.edu>:
...
|> At 2023-07-26T10:47:05+0200, Thomas ten Cate wrote:
|>> In the bash manual page (`man bash`), the ASCII tilde character '~'
|>> (0x7e) is replaced by the Unicode character '˜' (U+02DC SMALL TILDE):
|>>
|>> $ ma
Steffen Nurpmeso wrote in
<20230729002703.lasps%stef...@sdaoden.eu>:
|Chet Ramey wrote in
| <2fd2ed52-3272-3433-6179-164bc5122...@case.edu>:
| ...
||> At 2023-07-26T10:47:05+0200, Thomas ten Cate wrote:
||>> In the bash manual page (`man bash`), the ASCII tilde character '~'
||>> (0x7e) is
