9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] APE paper
Date: Thu,  4 Mar 2004 22:59:15 -0500	[thread overview]
Message-ID: <851fb32466b581046773b125730ca4d7@plan9.bell-labs.com> (raw)
In-Reply-To: <200403050352.i253qeto074116@adat.davidashen.net>

[-- Attachment #1: Type: text/plain, Size: 68 bytes --]

I know, I'm working on ms2html.c now to figure out what's happening.

[-- Attachment #2: Type: message/rfc822, Size: 2652 bytes --]

From: David Tolpin <dvd@davidashen.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] APE paper
Date: Fri, 5 Mar 2004 07:52:40 +0400 (AMT)
Message-ID: <200403050352.i253qeto074116@adat.davidashen.net>

> I'm remaking everything in /sys/doc, just in case.  You might see things
> in transition of you look over the next few minutes.
>

It contains all the text it needs, but something is still wrong.
The second sentence in paragraph about Pcc  contains

#include <tt>#include &lt;&lt;I&gt;file&lt;/I&gt;&gt;</tt>, displayed
as #include <<I>file</I>>; later in the same paragraph, markup formed
by 'tt' tags become unbalanced, with many extraneous <tt> tags inserted,
as one of results, the rest of paragraph after word 'objtype' is
printed in fixed-width font.

  parent reply	other threads:[~2004-03-05  3:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05  0:01 David Tolpin
2004-03-05  0:23 ` rob pike, esq.
2004-03-05  1:05 ` David Presotto
2004-03-05  1:08   ` David Presotto
2004-03-05  3:52     ` David Tolpin
2004-03-05  3:08       ` andrey mirtchovski
2004-03-05  3:59       ` David Presotto [this message]
2004-03-05  6:26       ` Kenji Okamoto
2004-03-05 11:56         ` David Presotto
2004-03-05  1:28 ` bs
2004-03-05  4:16 David Presotto
2004-03-05  5:18 ` Rob Pike

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=851fb32466b581046773b125730ca4d7@plan9.bell-labs.com \
    --to=presotto@closedmind.org \
    --cc=9fans@cse.psu.edu \
    /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).