\" at the end of the line. I haven't tested that.
> -.nr pdf-ht (p;\\2)/' \
> +awk '/^Page size:/ {print ".nr pdf-wid (p;"$3")"; \
I'm noting that the original regular expression allows for zero or more
spaces between "Page" and
shell
interpreter or the existance of the /bin directory.
And since most shells don't *enforce* POSIX compliance when running in
sh mode, just shifting to whatever shell impersonates sh might give
a developer a false sense of thinking they're writing a "portable
shell script". T
the best bet is to insert a literal newline somehow,
after the \ like the Makefile *tries* to do. How to do that properly is
unfortunately beyond me as I don't grock Make quoting rules very well.
>
> I've only tested with OpenBSD sed.
>
> >
> > Sed doesn’t tell me
ne in the Makefile should look like
DOC_GROFF = $(DOC_SED) -e '1i\' -e '.lf 1 $<' $< | $(DOC_GROFF_ONLY)
That is, break the single expression string up into two.
I've only tested with OpenBSD sed.
>
> Sed doesn’t tell me its version but the man pages says March 27, 2017.
>
> Greetings
>
> Axel
--
Andreas (Kusalananda) Kähäri
SciLifeLab, NBIS, ICM
Uppsala University, Sweden
.
t; Can someone check if this is true?
Renders ok to me. Does the user know that most of the text is supposed
to *read* as "garbage", i.e. the classic placeholder "Lorem ipsum" text?
Are they expecting a real text?
--
Andreas (Kusalananda) Kähäri
SciLifeLab, NBIS, ICM
Uppsala University, Sweden
.
On Thu, Aug 22, 2019 at 04:00:08PM -0400, James K. Lowden wrote:
> On Wed, 21 Aug 2019 15:15:19 -0400
> "T. Kurt Bond" wrote:
>
> > And it has .QS/.QE, which get the indent from the QI register
>
> It does?
>
> $ man groff_ms | grep -c QS
> 0
>
> --jkl
>
Yes,
$ man groff_ms |
