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

[G. Branden Robinson]

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 out, but I figured I'd go to
> the expert.

The expert has let you down twice now.  :(

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

That _is_ weird.  I'll set aside some time to do this properly with a
dump of the page before and after to ensure no undesired changes.

This _looked_ like it should be trivial.  I should have known better.

Regards,
Branden

signature.asc
Description: PGP signature