Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

[G. Branden Robinson]

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
> troff: /usr/local/src/bash/bash-20230728/doc/bash.1:26: warning: numeric
> expression expected (got a special character)
> 
> Where line 26 is the
> 
> .if \n(.g:(\(.f=0) \{\
> 
> test. This is macOS running groff-1.22.4 from MacPorts.

Sorry about that.  I fat-fingered it.

An 'n' is needed after the second backslash, because we're interpolating
a register value.

$ uname -a
Darwin gcc104.fsffrance.org 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 
20:20:05 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8101 arm64
$ groff --version | head -n 1
GNU groff version 1.19.2
$ cat <<EOF | groff -ww
> .if \n(.g:(\n(.f=0) .tm this is groff or mandoc
> EOF
this is groff or mandoc

No syntax goof and no warning here.  (-ww turns on _all_ warnings.)

\n(xx is 50-year-old syntax and supported by all *roffs.

I apologize for my clumsiness.

Regards,
Branden

signature.asc
Description: PGP signature