When I started at Bell Labs in 1983, we had nroff/mmx and then there
was troff that was only for typesetting. We wrote all the docs in nroff
then used troff to format this text for a typesetter and made any
necessary formatting changes on bluelines.
Pretty soon after that, we got device-independe
Hi Charlie,
> You'd have to ask the author of mdocml what he means by that. I'd be
> interested in hearing the answer too.
He replied privately off-list, having seen the list post. I wouldn't
like to pass it on here unless he gives the OK.
> I didn't join this thread to make (or defend) those
Hello
Some of you seems to be Unix veterans. I bought my first computer in
2005. Before this date I did not know how to power on it :).
But I am forty two years old and I know something about other things
and I am able to draw an analogy.
In several occasions, I've attempted to show my point o
Mike Bianchi:
> When I do need something special or "improved" then I make my own macro
> and carry it around with me. I have my own MM macros that I
> have carried around for decades, going back to my days at Bell Labs.
I wonder, how do you 'deploy' your own MM macros?
Just pick the ones y
Hi Anton,
> I can manage a two-part macro like .(MyPS and .)MyPS, so I could
> reset the indent upon exit. But I don't know how to do it using only
> one macro. I probably have to 'subscribe' to some 'call-back' macro
> that gets called every time a paragraph (in groff's sense) ends. Does
Ralph Corderoy:
> Hi Anton,
>
> > I can manage a two-part macro like .(MyPS and .)MyPS, so I could
> > reset the indent upon exit. But I don't know how to do it using only
> > one macro. I probably have to 'subscribe' to some 'call-back' macro
> > that gets called every time a paragraph (
Meg McRoberts wrote:
Does anyone know the history of mmx? When I started, mmx was the
command we used to produce formatted ASCII text from source that
used the *roff macros. I got the idea that it was an older tool which
was being linked to nroff at about that time...
I seem to remember rea
Larry Kollar wrote:
> Meg McRoberts wrote:
> > Does anyone know the history of mmx? When I started, mmx was the
> > command we used to produce formatted ASCII text from source that
> > used the *roff macros. I got the idea that it was an older tool
> > which was being linked to nroff at about th
Hi,
Clarke and I had a brief off-list conversation about having a larger
space after the end of sentences, etc., in HTML. IIRC, he suggested a
no-break space, ` ', followed by a normal space. The problem with
this is that if it should fall at the end of an output line that has a
straight right
> The other big output issue I know about is the lack of support for
> UTF-8.
Recent versions support UTF-8, at least for `simple' languages like
Latin, Russian, or Greek.
Werner
The user-defined .EOP macro in mgm overrides the normal end of page
processing, but there's no convenient way to invoke said normal
processing if one merely wants to augment it rather than completely
replacing it. It seems to me that it would be better to pre-define .EOP
to do the normal end of pa
On Wed, Jun 02, 2010 at 11:36:32AM -0400, Larry Jones wrote:
> The user-defined .EOP macro in mgm overrides the normal end of page
> processing, but there's no convenient way to invoke said normal
> processing if one merely wants to augment it rather than completely
> replacing it. It seems to me
> I can manage a two-part macro like .(MyPS and .)MyPS,
> so I could reset the indent upon exit. But I don't know how
> to do it using only one macro. I probably have to 'subscribe'
> to some 'call-back' macro that gets called every time a
> paragraph (in groff's sense) ends. Does groff o
Mike Bianchi writes:
>
> 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 hadn't considered that use case; I assumed that people
who define .EOP leave it def
Tadziu Hoffmann:
>
>> I can manage a two-part macro like .(MyPS and .)MyPS,
>> so I could reset the indent upon exit. But I don't know how
>> to do it using only one macro. I probably have to 'subscribe'
>> to some 'call-back' macro that gets called every time a
>> paragraph (in groff's
On Wednesday 02 June 2010 03:04:47 Larry Kollar wrote:
> > It runs slowly
>
> And that statement pretty much casts everything else you say into
> question. "Runs slowly" compared to what? I haven't found any general-
> purpose formatter that even comes close to groff, speed-wise, and
> don't
> Now I am prying into the implementation of the .TP macro
> in MAN...
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). Tha
17 matches
Mail list logo
