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

[Chet Ramey]

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
> > 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.

Thanks. I probably could have figured it out, but I figured I'd go to the
expert.

That eliminates the warning, but unfortunately produces output that looks
like this

       ~.nr need_eo_h 1 NAME
       bash - GNU Bourne-Again SHell

       ~.nr need_eo_h 1 SYNOPSIS
       bash [options] [command_string | file]

So something weird is happening with .SH. It doesn't matter whether I set
it to 0 or 1 in bash.1. I'll just hold off on these definitions for now.

Chet

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/