9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Humm <hummsmith42@gmail.com>
To: 9front@9front.org
Subject: [9front] 9front Programmer's Manual
Date: Fri, 6 Aug 2021 14:08:41 +0200	[thread overview]
Message-ID: <YQ0mSRCblZvISAnb@beryllium.local> (raw)

(Just for fun, I played around a little with the manual, changing it 
to a “9front Programmer’s Manual” (with actually functioning build 
system).  I haven’t changed the contents of the papers and didn’t do 
much with the man pages.  Files describing the changes and a tarball 
with the changed files are at /n/disk/humm/docs .)

I would like to know/discuss the future of the Plan 9 Programmer’s 
Manual in 9front.  Currently, besides changed man pages and the 
addition of the nupas paper, it still is the same as 4E’s manual.  As 
far as I know, the only versions of it in print are sl’s rainbow books 
(at which I haven’t looked yet).

What I think might be okay options are (1) deleting everything having 
to do with putting the papers and manual pages together to a big 
Programmer’s Manual for print, (2) replacing that mechanism by a new 
one for just the man pages (akin to the rainbow books, if I actually 
understand what’s in them), and (3) fixing it up for a two-volume 
9front Programmer’s Manual.  Additionally, I imagine papers could be 
updated for 9front (as if someone would actually do that).

So, what’s the situation?  Are there any plans other than continuing 
to let it rot?

-- 
Humm

             reply	other threads:[~2021-08-06 12:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 12:08 Humm [this message]
2021-08-06 13:37 ` qwx
2021-08-06 15:00   ` Humm
2021-08-06 13:49 ` qwx
2021-08-06 15:05 ` ori
2021-08-06 19:30   ` Stuart Morrow
2021-08-07  4:52   ` sirjofri
2021-08-20 11:26   ` Stuart Morrow
2021-08-06 15:06 ` Stanley Lieber
2021-08-06 19:34   ` Stuart Morrow
2021-08-07 11:37   ` Humm

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=YQ0mSRCblZvISAnb@beryllium.local \
    --to=hummsmith42@gmail.com \
    --cc=9front@9front.org \
    /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).