If you place a space at the start of a line, it causes a break.
If preceded by \& (a non-printing space), that should suppress it.
Clarke
Michael(tm) Smith wrote:
Clarke Echols <[EMAIL PROTECTED]>, 2008-02-25 20:56 -0700:
.PP
For more information, see the preceding section (\c
.t-
Clarke Echols <[EMAIL PROTECTED]>, 2008-02-25 20:56 -0700:
> .PP
> For more information, see the preceding section (\c
> .t-or-n "Description\c" "DESCRIPTION\c"
> ) or the
> .t-or-n "Introduction" "INTRODUCTION"
> section for this document.
>
> Also I should not have put
Hi Ralph,
> @2008-02-23 11:24 +:
>
> Hi Michael,
>
> > What I mean is that I'd like to be able to do something like this:
> >
> > For more information, see the \n[troff]Description\n[troff]
> > \n[nroff]DESCRIPTION\n[nroff] section.
>
> Use Werner's macro idea but maybe add in
>
>
Oops,
Missed one:
.PP
For more information, see the preceding section (\c
.t-or-n "Description\c" "DESCRIPTION\c"
) or the
.t-or-n "Introduction" "INTRODUCTION"
section for this document.
Also I should not have put the \c escapes in the second .t-or-n
line.
"He who talks by t
Michael(tm) Smith wrote:
The particular problem I run into with using a request for this is
that when the term I wanted to have alternative strings for is
immediately preceded and/or followed by a punctuation mark. For
example, a user might have DocBook source (which my app needs to
convert t
Werner LEMBERG <[EMAIL PROTECTED]>, 2008-02-23 09:31 +0100:
> > What I mean is that I'd like to be able to do something like this:
> >
> > For more information, see the \n[troff]Description\n[troff]
> > \n[nroff]DESCRIPTION\n[nroff] section.
>
> There are no inline conditionals in groff. Yo
> What I had been searching for in the index was "TTY". So maybe what
> would help would be an index entry like "TTY, conditional output
> for" (or something).
Done. Thanks for the suggestion.
Werner
Dorai Sitaram <[EMAIL PROTECTED]> writes:
> Given a .JOBNAME request in the input document, groff -Thtml creates
> multiple output HTML files, splitting the input at every .NH 1 and
> .SH.
>
> Groff's ms's .SH takes an optional numeric argument n whereby .SH n
> typesets in a style (font size) si
Given a .JOBNAME request in the input document, groff -Thtml creates multiple
output HTML files, splitting the input at every .NH 1 and .SH.
Groff's ms's .SH takes an optional numeric argument n whereby .SH n typesets in
a style (font size) similar to .NH n. (By default, n = 1.)
I think that
Am Sonntag, den 24.02.2008, 10:54 +0100 schrieb Werner LEMBERG:
> > I have a problem with man-pages written by the PSI3 projects. Man
> > throws a warning about a macro the manpage authors wrote.
> >
> > However I don't know GROFF well enough to track the issue down. All
> > I can say is, that th
> Is there a way I could modify it so that the filled box
> extends all the way across the whole line length? (i.e.,
> from the left margin / page offset to the right margin).
Sure. You mean like this?:
(If the boxed text itself uses .in, you may need to save the
indent of the surrounding text in
11 matches
Mail list logo
