> Ah, yes. In the manpage macros, this works similarly: all
> paragraph macros reset the indent to what it "should" be
> (so that any ".in" invocations within a paragraph will be
> undone at the beginning of the next paragraph). That is,
> ".TP" absolutely sets the indent to "something" + "extra"
Hi Anton,
> The trap is set by .it 1 an-trap, so I why is it
> fired after the section text even is it was passed
> to .SH as parameter? Are macro parameters handled
> as input lines?
No, I think you'll find it's this line,
. if \\n[.$] \&\\$*
that's placing any parameters as `input'.
> Ah, yes. In the manpage macros, this works similarly: all
> paragraph macros reset the indent to what it "should" be
> (so that any ".in" invocations within a paragraph will be
> undone at the beginning of the next paragraph). That is,
> ".TP" absolutely sets the indent to "something" + "extra"
On 3 Jun 2010 at 10:01, Ralph Corderoy wrote:
>
> Hi Anton,
>
> > The trap is set by .it 1 an-trap, so I why is it
> > fired after the section text even is it was passed
> > to .SH as parameter? Are macro parameters handled
> > as input lines?
>
> No, I think you'll find it's this line,
>
>
Maybe this document will be of interest for the
readers of this thread:
http://2009.asiabsdcon.org/papers/abc2009-P6B-paper.pdf
Anton
It's a reminder never to use BSD... On a cursory reading,
it wasn't clear how mdocml produces printable output.
I've found -man excellent, and also very simple to use,
and if the page is written properly produces very good
printed copy. In conjunction with viewers such as TkMan,
very quick for sc
> "DMW" == Denis M Wilson writes:
DMW> It's a reminder never to use BSD... On a cursory reading,
DMW> it wasn't clear how mdocml produces printable output.
My impression is that they don't intend it to, that those who want
printable output should install groff (or perhaps heirloom?) from
the
On Thu 03 Jun 2010 at 14:36:25 PDT James Cloos wrote:
"DMW" == Denis M Wilson writes:
DMW> It's a reminder never to use BSD... On a cursory reading,
DMW> it wasn't clear how mdocml produces printable output.
My impression is that they don't intend it to, that those who want
printable output s
>> As I read your description, the current syntax is:
>> Define .EOP to change end-of-page processing.
>> Undefine .EOP to restore the default end-of-page processing.
>
> Good point.
I second this.
> It wouldn't be a big deal to define (and document) another macro for
> the standard e
