Hello,
I would like to know, if there is a standard column width, when I use
the .TS macro? The problem is, that the result of the following code is
wrapped text in the second column (independent from MANWIDTH), even if I
use expand:
.TS
expand allbox;
ll.
T{
"0x1000"
T} T{
Disable AGP 4
Am Montag, den 13.03.2006, 07:48 +0100 schrieb Werner LEMBERG:
> > I would like to know, if there is a standard column width, when I use
> > the .TS macro?
>
> Yes. If there are N columns, and a text block spans C columns, the
> default width of this text block is
>
> \n[.l]*C/(N+1)
>
> I've
Am Donnerstag, den 04.01.2007, 17:58 +0900 schrieb Michael(tm) Smith:
> Related to some current discussions on the list, I wanted to
> mention a few projects I'm aware of that have authored their
> man-page documentation in DocBook and used the DocBook Project
> XSLT stylesheets to generate man-pag
Hello,
Can you guys point me to a statement (or simply give it), which is the
preferred preprocessor syntax for groff? Is it
.\"
or
'\"
Unfortunately groff_man(7) tells about the first and the related info
page talks about the latter. Is there some preferred form?
Regards, Daniel
Hello,
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 the warning is thrown for lines with the .pN macro,
which is defined earlier. Y
Am Samstag, den 23.02.2008, 20:39 -0700 schrieb Clarke Echols:
> I looked at the macro definition, and everything in it seems to
> be related to testing and defining strings. Thus I see no reason
> why the formatter would complain. Obviously there must be something
> in the file being processed t
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
Am Mittwoch, den 11.02.2009, 08:20 +0100 schrieb Werner LEMBERG:
> > I'm testing some groff source with non-GNU troff in an OpenSolaris/
> > SunOS 5.11 environment and noticed a problem. I'm using \(aq in the
> > source to represent straight apostrophes, but when I view the TTY
> > output, no apost
