> Mirfak is the brightest star in the constellation of Perseus,
> in which the second brightest start is ALGOL!
Fascinating! The name attests to a certain ambition, and
from what I've gathered, upon publication of a paper on
Mirfac there was a bit of back-and-forth in the journals
between the p
On Mon, 2018-12-03 at 20:36 +0100, Tadziu Hoffmann wrote:
> > the epsiode about Joe Ossanna is indeed funny, but what
> > the guy in the video is saying at that point is of course
> > total crap: very untrue in multiple respects and totally
> > irresponsible.
>
> Indeed, I did not mean to imply it
> the epsiode about Joe Ossanna is indeed funny, but what
> the guy in the video is saying at that point is of course
> total crap: very untrue in multiple respects and totally
> irresponsible.
Indeed, I did not mean to imply it was factual. But it
is entertaining. It reminded me of the legion
> Software Tools in Pascal by Brian W. Kernighan and P.J. Plauger
For what it's worth, some of the example code from the book
"Software Tools" is available from Brian Kernighan's web page.
It has a simple roff written in ratfor, which I've manually
converted slapdash into Fortran-90. Some part
> Without roff, Unix might well have disappeared.
The patent department and the AT&T president's office are the
only in-house examples I know where Unix was adopted because
of *roff.
The important adoptions, which led Berk Tague to found
a separate Unix Support Group, were mainstream telephone
ap
Ted Harding wrote:
> So, happily inspired, they developed the
> text-formatter runoff (--> roff) on Unix, and then
> demonstrated to Bell Labs how good it was at formatting
> structured documents -- in particular legal documents.
> At this point Bell Labs woke up, and adopted Unix!
Do we have any
Hello alls,
Actually, neatroff's documentation has a figure which quickly shows
where Neatroff's major layers and features are implemented in its
source tree: http://litcave.rudi.ir/neatroff.pdf#page
Pierre-Jean.
> So, if you are using a Unix/Linux system with standard
> man-pages, on a command-line terminal enter:
> man sex
> and see what you get!
I've been down this road once beefore the first time I had to write `man
finger`... =)
On Mon, 3 Dec 2018 at 05:52, Ted Harding wrote:
> One thing that does
One thing that does not seem to have been mentioned so far
(or perhaps I have overlooked it) is the role of roff
(abbreviation of "runoff", to reduce key-strokes) in
the emergence of Unix itself.
Unix was not originally developed by Bell Labs (as a
corporation) but by a group of Bell Labs people w
> It seems relevant
You're looking at the single-most accurate and complete timeline on Roff
anywhere on the web. Parts of it are vague, because the ones who invented
it hardly remembered many of the details over the decades.
It's incredible that Jerome Saltzer is still alive (right?? He was rely
Hi,
Yves Cloutier wrote on Sun, Dec 02, 2018 at 11:36:19AM -0500:
> On Sat, Dec 1, 2018 at 7:27 AM Dave Bucklin wrote:
>> I just came across this on Reddit. It seems relevant.
>> http://manpages.bsd.lv/history.html
Heh, that's funny.
> Hi Dave, thanks for this link!
And if you find errors in
Hi Dave, thanks for this link!
On Sat, Dec 1, 2018 at 7:27 AM Dave Bucklin wrote:
> I just came across this on Reddit. It seems relevant.
>
> http://manpages.bsd.lv/history.html
>
John Gardner wrote:
> Well, I assume his reasons were to have a Troff variant which supported
> right-to-left languages (which, if you think about it, is a pretty glaring
> oversight in a typesetting system...) Ali also has tonnes of other
> non-trivial projects, so his patience is obviously in gr
> Well, Ali Golhami Rudi made it a few years ago... Reimplementing a Troff
> is a task people can do if they have reasons to do so.
Well, I assume his reasons were to have a Troff variant which supported
right-to-left languages (which, if you think about it, is a pretty glaring
oversight in a type
John Gardner wrote:
> Reimplementing Troff is a task best not attempted at all.
Well, Ali Golhami Rudi made it a few years ago... Reimplementing a Troff
is a task people can do if they have reasons to do so.
> On Sat, 1 Dec 2018 at 02:37, Yves Cloutier wrote:
> > I'm in search of any documenta
Great Bertrand, I will check it out! Thanks
On Fri, Nov 30, 2018 at 6:15 PM Bertrand Garrigues <
bertrand.garrig...@laposte.net> wrote:
> Hi Yves,
>
> On Fri, Nov 30 2018 at 10:28:53 AM, Yves Cloutier
> wrote:
> > I'm in search of any documentation that provides insight into the design
> > and
I asked Brian Kernighan if he had recollections and/or documents from the early
days of nroff.
Hi, Mike --
All of the roff programs originate from Jerry Saltzer's Runoff, done for
CTSS. [nt]roff was unusual in having programmable layout (the trap
mechanism). I do
Hi Yves,
On Fri, Nov 30 2018 at 10:28:53 AM, Yves Cloutier
wrote:
> I'm in search of any documentation that provides insight into the design
> and implementation of a *roff.
>
> I know source code exists for a few implementations like Plan 9, Heirloom,
> Groff and Neatroff.
>
> However what I'm
Hi,
Tadziu Hoffmann wrote on Fri, Nov 30, 2018 at 05:48:04PM +0100:
>> You need to be a special sort of crazy (and patient, and knowledgeable) to
>> want to endure the obvious pains of reimplementing such a complex system.
> Wikipedia is amazing! It pointed me to this:
>
> https://www.youtub
lol thanks for the kind words John. Lucky for you I just pulled the "Fool"
cart from my tarot deck.
I'm not interested in re-implementing troff, its syntax, or its grammar. I
am however interested in generating troff output, without using troff.
High-level programming languages all compile down
On Fri, 30 Nov 2018, Tadziu Hoffmann wrote:
I'm in search of any documentation that provides insight
into the design and implementation of a *roff.
Not sure if this helps more than it confuses, but
perhaps looking into the "amazingly workable formatter",
an nroff-workalike written in awk, migh
Thanks for the heads up Gaius, I've just clicked the "order" button!
On Fri, Nov 30, 2018 at 11:41 AM Gaius Mulley
wrote:
> Yves Cloutier writes:
>
> > Hello,
> >
> > I'm in search of any documentation that provides insight into the design
> > and implementation of a *roff.
> >
> > I know sourc
> You need to be a special sort of crazy (and patient, and knowledgeable) to
> want to endure the obvious pains of reimplementing such a complex system.
Wikipedia is amazing! It pointed me to this:
https://www.youtube.com/watch?v=l6XQUciI-Sc&t=1h28m35s
Yves Cloutier writes:
> Hello,
>
> I'm in search of any documentation that provides insight into the design
> and implementation of a *roff.
>
> I know source code exists for a few implementations like Plan 9, Heirloom,
> Groff and Neatroff.
>
> However what I'm in search of is something a bit mo
> I'm in search of any documentation that provides insight
> into the design and implementation of a *roff.
Not sure if this helps more than it confuses, but
perhaps looking into the "amazingly workable formatter",
an nroff-workalike written in awk, might offer some
enlightenment...
There's als
Insanity. Seriously.
Reimplementing Troff is a task best not attempted at all. The grammar is
horribly complex, the language riddled with cryptic, arcane features, and
most importantly, it's not one program. It's several: the Troff pipeline
involves preprocessors, postprocessors, and bundled macro
Hello,
I'm in search of any documentation that provides insight into the design
and implementation of a *roff.
I know source code exists for a few implementations like Plan 9, Heirloom,
Groff and Neatroff.
However what I'm in search of is something a bit more high-level than
source code. Rather
27 matches
Mail list logo
