From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Many bugs in eqn(1)
Date: Wed, 13 Aug 2014 13:34:36 +0200 [thread overview]
Message-ID: <CAOEdRO3astiUUUkwB0DkNn5aGOjKRXMfMH2VdmNOd18+5wGT0g@mail.gmail.com> (raw)
In-Reply-To: <1179414908.1374571.1407927433550.JavaMail.ngmail@webmail06.arcor-online.net>
On 13 August 2014 12:57, Carsten Kunze <carsten.kunze@arcor.de> wrote:
> Since nobody seems to use troff on P9 I regarded it as off-topic.
The traffic is low enough to discuss any matter related to p9(p) here,
I believe. And it can be used as a back-reference in the future.
>> http://9fans.net/archive/?q=sykora+eqn&go=Grep
>
> I can't believe that TeX should not produce better results, but
> thats really OT...
I don't understand what you mean.
>> I'd rather say that p9p software is the source these days.
>
> Really? Ok, if I compare the sources it looks like this. Is this
> true for troff only or for p9p in general?
>
> So p9 troff posts may be better done on the p9p list?
I think whoever uses p9p reads this list.
I personally even don't know there is a special p9p list.
>> troff is a macro language.
>
> This I completely don't understand. If someone has much time
> and uses only low level requests than the word "macro" should
> be improper?
>
> What is not a macro language, i.e. what do you suggest to use instead?
>
>> Page makeup by postprocessing text formatter output
>> by Kernighan & Wyk
>
> I also do not understand that. It is possible to write very good macro
> packages for troff. Also TeX can produce very good documents. Ok,
> this is OT again.
Just read the document.
And it is not only about producing good documents meaning
good-looking. It's about scalability and readability, too.
Nobody would tell you LaTeX is readable. PlainTeX is, but
by itself, it doesn't know much (like plain troff).
Twisting a macro language around is often difficult, has many
pitfalls, may be difficult to debug, and if it grows beyond a certain
level, it collapses. That's at least what I think.
Ruda
next prev parent reply other threads:[~2014-08-13 11:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 10:57 Carsten Kunze
2014-08-13 11:34 ` Rudolf Sykora [this message]
2014-08-13 12:16 ` Carsten Kunze
2014-08-13 13:13 ` Rudolf Sykora
2014-08-13 13:46 ` tlaronde
2014-08-13 13:31 ` Carsten Kunze
2014-08-13 18:11 ` Steve Simon
2014-08-13 18:47 ` Carsten Kunze
2014-08-13 19:37 ` Steve Simon
2014-08-13 20:09 ` Carsten Kunze
2014-08-14 6:53 ` Steve Simon
2014-08-14 15:01 ` erik quanstrom
[not found] <1209878384.1371392.1407919054269.JavaMail.ngmail@webmail06.arcor-online.net>
2014-08-13 9:52 ` Rudolf Sykora
2014-08-13 10:30 ` cam
2014-08-13 10:43 ` tlaronde
2014-08-13 12:22 ` Carsten Kunze
2014-08-13 13:36 ` tlaronde
-- strict thread matches above, loose matches on Subject: below --
2014-08-12 15:41 Carsten Kunze
2014-08-12 20:46 ` Steve Simon
2014-08-12 21:02 ` Carsten Kunze
2014-08-12 21:08 ` Steve Simon
2014-08-13 7:56 ` Rudolf Sykora
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOEdRO3astiUUUkwB0DkNn5aGOjKRXMfMH2VdmNOd18+5wGT0g@mail.gmail.com \
--to=rudolf.sykora@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).