The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: tuhs@tuhs.org
Subject: [TUHS] Fwd: Writer's Workbench on Plan 9/9front
Date: Wed, 13 Jan 2021 17:15:13 -0500	[thread overview]
Message-ID: <411F7BC7-2D98-48A1-9448-740969D3AE8F@stanleylieber.com> (raw)
In-Reply-To: <12DBBA7F05B2CD6CC86BB30EC598B641@sirjofri.de>

fyi


-------- Original Message --------
From: joel@sirjofri.de
Sent: January 13, 2021 11:30:31 AM EST
To: sl@stanleylieber.com
Subject: Writer's Workbench on Plan 9/9front

Hello TUHS,

I don't know if that mail arrives since I'm not subscribed to the tuhs
mailing list.  I just thought this might be interesting to some of
you, especially since I noticed there are some threads about the
writer's workbench.

Some weeks ago I started porting V10 wwb tools to 9front (which is a
fork of Plan 9).  I have still many things to do and currently only
limited time, but the greater tools (style, diction and suggest) work.

Most code worked fine, btw, only minor changes needed.  Especially
implicit C declarations and missing #includes.  Comparison with the
original code in the archive is possible.

I also tried porting (or rewriting) the shell scripts in rc, and made
mkfiles that better fit the Plan 9 build systems.  I also included
acme commands, they also translate the locations into the plumber
format for the files (filename:line).

Here's a link to the git repository (yes, we have a native git
implementation now): https://git.sr.ht/~sirjofri/wwb9

sirjofri



           reply	other threads:[~2021-01-13 22:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <12DBBA7F05B2CD6CC86BB30EC598B641@sirjofri.de>]

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=411F7BC7-2D98-48A1-9448-740969D3AE8F@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=tuhs@tuhs.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).