From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IRC
Date: Wed, 28 Nov 2001 14:51:10 +0000 [thread overview]
Message-ID: <20011128144451.F173819A64@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 189 bytes --]
the way i sometimes structure this is similar to acme's: to have the usual connection directory
with clone (or new) and an index. a ctl request sets a name that shows up in the index.
[-- Attachment #2: Type: message/rfc822, Size: 2316 bytes --]
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IRC
Date: Wed, 28 Nov 2001 14:14:02 +0000
Message-ID: <200111281414.fASEE2T57818@devil.lucid>
On Wednesday 28 November 2001 13:27, you wrote:
> why not do it the plan 9 way, if you're going to write a complete client
> anyway? ircfs? sounds right, doesn it?
>
> $ ircfs <mynick> <myserver>
> $ cd /irc/#mychan1
> $ echo "hi all" >> data
> $ cat topic
> $ ls # /who #mychan1
>
> (in a different window)
> $ cd /irc/#mychan2
> $ #...
>
> andrey
irc channel names are invalid plan9 file names
You are now talking on #/\/\/\_Hey_/\/\/\#
http://www.rfc.net/rfc1459.html
I've spent a few hours thinking about it but never came up with an elegant
solution that I liked.
next reply other threads:[~2001-11-28 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 14:51 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 16:55 [9fans] fossil gone :) andrey mirtchovski
2003-08-18 18:18 ` [9fans] IRC Skip Tavakkolian
2003-08-18 18:32 ` andrey mirtchovski
2003-08-18 22:02 ` Jim Choate
2001-11-28 15:43 Jonathan Sergent
2001-11-29 11:25 ` josh d
2001-11-28 15:06 Fco.J.Ballesteros
2001-11-28 15:06 rog
2001-11-28 16:10 ` Boyd Roberts
2001-11-28 23:32 ` Jason Gurtz
2001-11-23 14:31 Jonathan Sergent
2001-11-28 9:52 ` josh d
2001-11-28 13:27 ` Andrey A Mirtchovski
2001-11-28 14:14 ` Matt
2001-11-23 9:34 Rob Clews
2001-11-23 10:22 ` Matt
2001-11-23 12:23 ` Boyd Roberts
2001-11-23 15:30 ` andrey
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=20011128144451.F173819A64@mail.cse.psu.edu \
--to=forsyth@vitanuova.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).