Re: [PATCH] Document imperfections in POSIX/sh compatibility

[Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>]

dana wrote on Sat, Apr 17, 2021 at 23:50:11 -0500:
> On 14 Apr 2021, at 07:38, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> > s/where/when/ ?
> 
> I guess so
> 
> On 14 Apr 2021, at 07:38, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> > s/chapter/Chapter/.
> 
> I'd specifically checked to see if there was a preference here and found that
> the FAQ itself uses lower-case. Should i go against that?

No; consistency comes first.

> On 14 Apr 2021, at 07:38, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> > There is some relevant information in §3 as well, specifically, in 3.31
> > "Why does my bash script report an error when I run it under zsh?".
> > However, that question hasn't been published yet, so perhaps we should
> > just move it to §2.
> 
> Looking at the contents of the two chapters, it does seem like moving it might
> make sense. I can do that

That'd be great.

> On 14 Apr 2021, at 07:38, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> > The space in "Chapter 2" should be a non-breaking one.  An nbsp() macro
> > was added to yodl in 4.02.00, which is the version I have, but when I
> > try to use it (without worrying about compatibility to older versions,
> > for the sake of testing), I just get «expn.yo:36: No macro: nbsp(...)».
> 
> So what would you suggest? I only have yodl 3.05, and i can't find any
> instances of 'nbsp' or '00a0' or $'\u00a0' in Doc/ or Etc/ to use as
> precedent. Should i just use a literal nbsp?

I suppose we could try that and see if someone complains it breaks their
build.  (Feel free to blame me ;-))  Or we could just put a literal
space (plus or minus a «COMMENT(TODO: )»).

> On 14 Apr 2021, at 07:38, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> wrote:
> > s/http/https/
> 
> I also based that on existing precedent. Maybe i should do another patch to
> find-and-replace them throughout the docs

*nod*

Thanks, dana.

Daniel