From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] tcl 9p support? (via tcl vfs?)
Date: Sat, 11 Mar 2006 11:06:57 -0600 [thread overview]
Message-ID: <a4e6962a0603110906q3c193effsf5189d657f5f64ac@mail.gmail.com> (raw)
In-Reply-To: <200603110911.k2B9BY708977@zamenhof.cs.utwente.nl>
On 3/11/06, Axel Belinfante <Axel.Belinfante@cs.utwente.nl> wrote:
> Only recently I discovered that there is vfs support in tcl.
> Any informed opinions on how involved it would be to extend
> it with 9p support?
>
A 9P server library in tcl is something I've wanted for some time --
I'd like 9P server bindings for lots of script languages, but tcl
always seemed to be a good fit for file-system control interfaces (and
I already have a bunch of stuff written in it too).
-eric
next prev parent reply other threads:[~2006-03-11 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 9:11 Axel Belinfante
2006-03-11 9:40 ` Charles Forsyth
2006-03-11 17:06 ` Eric Van Hensbergen [this message]
2006-03-15 22:40 ` Axel Belinfante
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=a4e6962a0603110906q3c193effsf5189d657f5f64ac@mail.gmail.com \
--to=ericvh@gmail.com \
--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).