From: Benjamin Riefenstahl <firstname.lastname@example.org>
Subject: Re: [9front] New user
Date: Sat, 01 Jan 2022 18:56:37 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <Yc4OWgzKjR1Ul2kv@beryllium.local> (Humm's message of "Thu, 30 Dec 2021 19:54:02 +0000")
> Quoth Benjamin Riefenstahl:
>>Besides trying out the native stuff, I have started a personal project
>>to get Tcl to run.
> Isn’t there a Tcl port in fgb’s contrib? (That means you do `9fs
> 9pio` (read /rc/bin/9fs) and look at
> /n/9pio/contrib/fgb/root/sys/src/^(lib cmd)/^tcl.)
Right, that is the basis of what I am doing. First there was a problem
with the 64 bit version (seems fgb worked on 32 bit at the time), that
was a Tcl problem. Than I moved it to a recent version of Tcl and now I
am trying to get through the Tcl test suite. And as I said, that turns
up some limitations.
> (Also, why?)
For fun, to learn about Plan 9 and to give back a bit to my favorite
> APE was not yet thrown out of 9front. Generally bugfixes are good.
> Yep, APE is old and quite unmaintained. I recommend looking at
> https://git.sr.ht/~ft/npe .
Thinks for that pointer, I have just seen that, too. It looks quite
limited, though, even compared to APE.
next prev parent reply other threads:[~2022-01-01 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 18:41 Benjamin Riefenstahl
2021-12-30 19:54 ` Humm
2022-01-01 16:56 ` Benjamin Riefenstahl [this message]
2021-12-30 20:32 ` theinicke
2021-12-30 20:45 ` ori
2021-12-30 22:00 ` qwx
2022-01-01 17:03 ` Benjamin Riefenstahl
2022-02-27 0:11 [9front] new user thinktankworkspaces
2022-02-27 3:51 ` Alex Musolino
2022-02-27 3:56 ` Alex Musolino
2022-02-27 5:41 ` thinktankworkspaces
2022-03-08 13:28 ` Alex Musolino
2022-03-10 3:58 ` thinktankworkspaces
2022-03-10 4:12 ` Alex Musolino
2022-03-10 4:42 ` Stanley Lieber
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).