I loved Clarke's history/rant posting, BTW...
The other big output issue I know about is the lack of support for UTF-8.
I've written some man pages for Trend that I can build fine but when I
send the source to the R&D people in Taiwan and Nanjing, they have
trouble running them because all their s
>> produces uncertain output
>
> At this point, I'm convinced that the author has never used groff.
He probably means HTML output, and indeed, groff shows a lot of
weaknesses for this output device since nobody takes care to make mdoc
work well for hypertext. Unfortunately, I'm really swamped w
I was severely criticized in 1991-92 when I was responsible for the
HP-UX manpages because I was adding examples, splitting cp, ln, and
mv into three separate pages, and doing other things to cause the
total manpage files to expand to (gasp!) nearly 8 or 9 Mbytes and
we "needed" to keep disc consu
Ralph Corderoy wrote:
Hi Charlie,
All they're doing is putting mdocml in base to handle manpages.
http://mdocml.bsd.lv/
DESCRIPTION
mdocml is a suite of tools compiling "-mdoc", the roff macro
package
of choice for BSD manual pages, and "-man", the predominant
histo
On Tue 01 Jun 2010 at 12:48:45 PDT Ralph Corderoy wrote:
Hi Charlie,
All they're doing is putting mdocml in base to handle manpages.
http://mdocml.bsd.lv/
DESCRIPTION
mdocml is a suite of tools compiling "-mdoc", the roff macro package
of choice for BSD manual pages, and "-man"
Hi Charlie,
> All they're doing is putting mdocml in base to handle manpages.
http://mdocml.bsd.lv/
DESCRIPTION
mdocml is a suite of tools compiling "-mdoc", the roff macro package
of choice for BSD manual pages, and "-man", the predominant
historical package for UNIX manua
On Tue 01 Jun 2010 at 04:59:44 PDT Larry Kollar wrote:
Agreed. Plan9 troff is still stuck with the two-letter namespace! If
they don't want to use groff, why not Heirloom Troff from Sun? What's
the point of this anyway - GPL? NIH?
If you look at /usr/src/contrib, you'll see that the FreeB
On Tue, Jun 01, 2010 at 01:42:41PM +0200, Werner LEMBERG wrote:
>
> > Either way, groff is enough better that I wouldn't look back.
>
> It might be interesting to compare with heirloom troff which has
> native support for OpenType fonts, and which supports almost all of
> the groff extensions.
Y
On Tue, Jun 01, 2010 at 07:59:44AM -0400, Larry Kollar wrote:
> It's bad enough that Debian and its derivatives (*ubuntu) include
> only a cut-back version of groff that's barely adequate for
> formatting manpages, but at least that's easily remedied during
> installation.
Debian includes a groff-
Doug McIlroy :
> > troff pre-dates C by quite a while
>
> Actually not. C and nroff were contemporary--both debuted in 2nd edition
> Unix.
> troff came in the 3rd edition. Of course nroff was preceded by roff, and
> that by runoff; but neither of those had a | operator, which was the
> triggeri
> troff pre-dates C by quite a while
Actually not. C and nroff were contemporary--both debuted in 2nd edition Unix.
troff came in the 3rd edition. Of course nroff was preceded by roff, and
that by runoff; but neither of those had a | operator, which was the
triggering question. Certainly by the
On Tue, Jun 01, 2010 at 04:24:19PM +0400, Anton Shepelev wrote:
> Mike Bianchi:
>
> > Anton,
> > Could you just use \ to continue the macro onto your next line?
> >
> > .MyMacro FirstArg \
> > All the text that is processed by MyMacro FirstArg follows.
>
> Thanks for the hint. I tho
Me:
>
> I have made your code a bit simpler:
>
>.nr indnt 120
>.in +\n[indnt]u
>.ti -(\n[indnt]u)
>PS:\ Example of a post-scriptum, it has a hanging indent.
>.in -\n[indnt]u
I forgot to escape the \w request (first line).
Here's the corrected verstion:
.nr indnt \w'PS:
Mike Bianchi:
> Anton,
> Could you just use \ to continue the macro onto your next line?
>
> .MyMacro FirstArg \
> All the text that is processed by MyMacro FirstArg follows.
Thanks for the hint. I thought about it and con-
sidered it a sort of 'quick and dirty' (not
en
Ted Harding:
> One "hack" which might lead to what you want is to calculate an
> indent based on the width of the tag "PS: ", and then increment
> the line-indentation once the paragraph has been started (but
> you would need to reset it at the end of the paragraph):
> (Note the use of the unstret
Hi,
Larry Kollar wrote:
> It's defined in groff(7), and in sec. 5.3 of the texinfo doc. Logical
> OR is a colon:
>
> .if \n[EULA]=1:\n[EULA]=3 \{\
>
> It would have been interesting to ask Joe O why a colon instead of a
> pipe here. Anyway, I use constructs like this all the time in my docs.
P
On Tue, Jun 01, 2010 at 02:19:17PM +0400, Anton Shepelev wrote:
> I often need to typeset single hanging paragraphs
> like:
>
> PS: Example of a post-scriptum, it has a hanging
> indent.
>
> I have created a macro for this, which
>
> 1. Calculates the length of the label and
>
Larry McVoy wrote:
On Wed, May 26, 2010 at 05:09:23PM +1000, Greg 'groggy' Lehey wrote:
There's currently a discussion going on in the FreeBSD project about
replacing groff (which is part of the base system, mainly to process
man pages) with a specialized man page processor, and relegate groff
On 01/06/10 21:41:24, Werner LEMBERG wrote:
> > However, I have recently written (as a learning exercise) a macro
> > that automatically indented, nested, aligned, and numbered
> > paragraphs.
>
> This is rather easy to handle by using indirect macro calls. Here an
> outline of a solution:
Thank
> What I would oh-so-love to be able to do is
>
> .if \n[EULA]=1 || \n[EULA]=3
>
> I wandered through the groff docs and didn't see any way to do that.
>
> A) Is there a way?
Yes, of course. groff uses `:' and `&' for C's `||' and `&&'
operators. This, for example, is in m.tmac:
.if (\
> Either way, groff is enough better that I wouldn't look back.
It might be interesting to compare with heirloom troff which has
native support for OpenType fonts, and which supports almost all of
the groff extensions.
Werner
> However, I have recently written (as a learning exercise) a macro
> that automatically indented, nested, aligned, and numbered
> paragraphs. The macro takes an optional single argument:
> 1
> a
> A
> i
> I
> 0
>
>
> Arguments 1, a, A, i, and I set the type of numbering; "0" finishes
> the the
Larry McVoy wrote:
.if !\n[EULA]=0 \{\
.if !\n[EULA]=1 \{\
.if !\n[EULA]=2 \{\
.if !\n[EULA]=3 \{\
.ab No EULA defined
.\}
.\}
.\}
If I remember correctly, EULA will return 0 if not previously
defined, so you'll never reach the abort. You can do this in one line:
.if !rEULA .ab No EULA de
On 01-Jun-10 10:19:17, Anton Shepelev wrote:
> Hello, all
>
> I often need to typeset single hanging paragraphs like:
>
> PS: Example of a post-scriptum, it has a hanging
> indent.
>
> I have created a macro for this, which
>
> 1. Calculates the length of the label and
> i
Hello, all
I often need to typeset single hanging paragraphs
like:
PS: Example of a post-scriptum, it has a hanging
indent.
I have created a macro for this, which
1. Calculates the length of the label and
increments it by one,
2. Begins a variable-item list (MM's .VL)
On 01/06/10 17:49:04, ted.hard...@manchester.ac.uk wrote:
> > While you are at it, would you please include "elif" in your patch.
> There are already (as well as ".if") ".ie" for "if-else", "&" for
> "and" and ":" for "or".
>
> See 'info groff' under
>
> * Request Index::
> --> * ie:
On 01-Jun-10 04:42:55, Robert Thorsby wrote:
> On 01/06/10 14:16:28, Larry McVoy wrote:
>> What I would oh-so-love to be able to do is
>>
>> .if \n[EULA]=1 || \n[EULA]=3
>>
>> I wandered through the groff docs and didn't see any way to do that.
>>
>> A) Is there a way?
>> B) If not, if I s
27 matches
Mail list logo
