Re: Minor mistake in Bash manual

[Robert Elz]

    Date:        Mon, 11 Mar 2019 23:15:14 -0500
    From:        Todd Lehman <tsl@xeow.com>
    Message-ID:  <D72E32E0-DF85-46E0-91B4-3DA20C8BD3B8@xeow.com>

  | In any case, please fix as you see fit.

First, to make one thing clear, I have nothing whatever to do
with maintaining bash (for reasons unrelated to anything here,
I won't even go close to its source code) - I maintain a different
shell, and am here as when (genuine) bash bugs are reported, they're
usually in some obscure use case, and I can use those examples to
check what the shell I do maintain does, and perhaps fix some bugs
before they're even noticed...

But in that context I also deal with shell documentation, and face
the same issue as you have reported.

  | (But I'm sure you will agree that the current state of that example
  | cannot stand.

Yes, I was not suggesting that nothing be done.   And I'm sure that
Chet will fix it, one way or another, when he gets the opportunity.

  | It is a flagrant violation of sanity to include the period inside
  | the verbatim text block. :-)

As I recall, from back when I used to care more, the English style
guides take some trouble to discuss how to deal with punctuation when
it comes to including (short, or long) quotes from other sources, to
avoid this kind of ambiguity.   For some obscure reason (perhaps related
to them mostly being written in the middle 20th century, or before)
they don't spend a lot of time discussing how to include code samples
that one might want to cut and paste from an HTML or PDF format file
and use as shell (etc) input...

kre