On Sat, Nov 20, 2004 at 07:22:05PM +0100, Alfred M. Szmidt wrote:
> Guessing which lines are continuations and which are new lines is
> darned tricky, and the rules help2man uses are intended to deal
> with the majority of cases.
>
>I don't know how help2man does this in detail, but wouldn't
>I don't know how help2man does this in detail, but wouldn't it
>work just to see if the next line as a option (either, -s or
>--short). And assume that if doesn't, that it is a continuation?
>This would solve all cases I think.
Perhaps, although it's been my experience that muckin
Guessing which lines are continuations and which are new lines is
darned tricky, and the rules help2man uses are intended to deal
with the majority of cases.
I don't know how help2man does this in detail, but wouldn't it work
just to see if the next line as a option (either, -s or --short
On Fri, Nov 19, 2004 at 11:12:39PM +0100, Alfred M. Szmidt wrote:
>help2man produces spurious blank newlines if you indented the --help
>text like this:
>
> --sort=WORDextension -X, none -U, size -S, time -t,
> version -v
>
Bah, screwed up in writting the email addy to the help2man bug mailing
list.
--- Start of forwarded message ---
From: "Alfred M. Szmidt" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Fri, 19 Nov 2004 23:09:07 +0100
Cc:
Subject: help2man and indent
Hi,
help2man produces spurious blank newlines if you indented the --help
text like this:
--sort=WORDextension -X, none -U, size -S, time -t,
version -v
status -c, time -t, atime -u, access -u, use -u
The output that he
