Re: [Groff] redefine .IP and .TP ?

[Tadziu Hoffmann]

> I don't want to use .TP as it's already used for the general 
> options and I didn't wanted to mix it to avoid confusion.

I don't understand your reluctance to use TP and your preference
for IP, since in the PWB manpage macros IP is in fact defined in
terms of TP: IP puts its first argument on the next input line
and invokes TP with its second argument.  Also, TP allows you to
bolden/italicize the tag using a macro instead of \f-escapes.

> -option1=<value>
>       Balds fkjsd dfksjdfksjd fsdfkj.
> 
>       EXAMPLES: -alang de,hu       description1
> (^no spaces ^italic ^not italic    ^always same indentation)
>                 -alang ja          description2
> 
> -option2=<value>
>       dkflsdkfösldkfösl sdlfkö lsdkf.

As far as I know there's no provision for having the tags of two
"nested" tagged paragraphs on the *same* output line.  This is
only possible using stupid tricks like reverse spacing, which
does not work with all versions of nroff.  (groff -Tascii is
okay.)

Example:

.TH "funny" "1" "2002-09-04" "Junk"
.SH "NAME"
funny \- strange stuff with manual pages
.SH "SYNOPSIS"
.nr i \w'\fBfunny\fP '
.in +\niu
.ti -\niu
.ad l
.B funny
.RI [ option1 ]
.RI [ option2 ]
.RI [ option3 ]
.RI [ option4 ]
.in
.ad b
.SH "DESCRIPTION"
This manual pages contains some interesting
layout constructs for writing manual pages.
.SH "OPTIONS"
.\" Note: tag has to be *one* input line
.TP 4
.BR \-squiggle [ =\fIargument\fP ]
This option is ignored and has no effect.
.I argument
can take arbitrary values.
.IP
.I Examples:
.RS 15
.PD 0-1
.TP 5
.B foo
well-known argument.
.PD 0
.TP
.B bar
other well-known argument.
.RE
.PD
.TP
.B \-gurgle
Causes the computer to sputter for a certain amount of time.