From: "Federico Benavento" <benavento@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Developing in plan9
Date: Fri, 23 Feb 2007 23:45:06 +0100 [thread overview]
Message-ID: <32d987d50702231445o66c4b6abg525c7610fb37d32e@mail.gmail.com> (raw)
In-Reply-To: <45DF6A29.9050605@gmail.com>
hola,
I think nemo's intro is what you're looking for:
http://plan9.escet.urjc.es/who/nemo/9.intro.pdf
On 2/23/07, Keith Poole <keith.poole@gmail.com> wrote:
> Hi,
>
> I've been interested in plan 9 for a while now & I've recently installed
> it on my MacBook Pro (under Parallels) and I've been digging around in
> it (setting up networking, getting used to acme, etc), but now I want to
> look into developing programs. Are there any good starting points for this?
>
> Cheers
>
> Keith
>
--
Federico G. Benavento
prev parent reply other threads:[~2007-02-23 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 22:26 Keith Poole
2007-02-23 22:41 ` Robert Ball
2007-02-23 22:45 ` Robert Ball
2007-02-23 22:45 ` Federico Benavento [this message]
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=32d987d50702231445o66c4b6abg525c7610fb37d32e@mail.gmail.com \
--to=benavento@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).