From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] 'wall' messages
Date: Thu, 9 Oct 2003 11:29:48 +1000 [thread overview]
Message-ID: <023801c38e04$db6f3e60$c901a8c0@cc77109e> (raw)
In-Reply-To: <49d88ae4feaba4506f44c00cc1ec5fe6@collyer.net>
Geoff, you spoil all the fun. I was waiting for screeds and
screeds of kernel code that scrummages around in everyones
namespace looking for places to write, and trying real hard
to only write to each place once. And of course causing a
horrible mess to every window running anything but just rc.
Anyhow your code is shorter than Jim's speculations.
brucee
----- Original Message -----
From: "Geoff Collyer" <geoff@collyer.net>
To: <9fans@cse.psu.edu>
Sent: Thursday, October 09, 2003 10:31 AM
Subject: Re: [9fans] 'wall' messages
> Okay, here are implementations of write and wall in under 100 lines.
> I haven't used this code heavily but it worked when I last did. You
> run `postwrite' in its own cpu-server window, which makes you
> reachable via write or wall by others on that cpu server.
etc
next prev parent reply other threads:[~2003-10-09 1:29 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 0:30 mirtchov
2003-10-07 0:33 ` boyd
2003-10-07 0:35 ` jmk
2003-10-07 2:28 ` Jim Choate
2003-10-07 2:27 ` boyd
2003-10-07 2:54 ` Jim Choate
2003-10-07 2:30 ` [9fans] A final question on regex Jim Choate
2003-10-07 3:08 ` [9fans] 'wall' messages Bruce Ellis
2003-10-07 3:11 ` boyd
2003-10-07 3:31 ` Jim Choate
2003-10-07 4:04 ` andrey mirtchovski
2003-10-07 4:17 ` Jim Choate
2003-10-07 4:23 ` [9fans] A fine point on 'lazy update' Jim Choate
2003-10-07 4:25 ` [9fans] 'wall' messages andrey mirtchovski
2003-10-07 13:56 ` Jim Choate
2003-10-07 14:09 ` mirtchov
2003-10-07 14:19 ` Dan Cross
2003-10-07 17:27 ` Ralph Corderoy
2003-10-07 9:50 ` Bruce Ellis
2003-10-07 10:41 ` Lucio De Re
2003-10-07 11:27 ` Bruce Ellis
2003-10-07 11:52 ` Lucio De Re
2003-10-07 12:10 ` boyd
2003-10-08 1:43 ` okamoto
2003-10-07 13:15 ` matt
2003-10-07 12:33 ` Lucio De Re
2003-10-07 14:09 ` Dan Cross
2003-10-07 13:40 ` Jim Choate
2003-10-08 8:39 ` Douglas A. Gwyn
2003-10-08 13:40 ` Jim Choate
2003-10-07 13:49 ` Jim Choate
2003-10-07 21:35 ` Bruce Ellis
2003-10-07 22:07 ` Joel Salomon
2003-10-08 5:34 ` Jim Choate
2003-10-08 5:48 ` Jim Choate
2003-10-08 14:21 ` rog
2003-10-08 18:14 ` David Presotto
2003-10-08 18:52 ` mirtchov
2003-10-09 15:07 ` rog
2003-10-09 15:10 ` David Presotto
2003-10-08 17:40 ` a
2003-10-07 22:38 ` boyd
2003-10-08 9:36 ` Ralph Corderoy
2003-10-08 13:57 ` Dan Cross
2003-10-07 23:19 ` a
2003-10-08 2:35 ` Jim Choate
2003-10-08 2:42 ` Bruce Ellis
2003-10-08 2:52 ` Jim Choate
2003-10-08 14:46 ` rt
2003-10-09 0:31 ` Geoff Collyer
2003-10-09 1:29 ` Bruce Ellis [this message]
2003-10-09 18:36 ` rog
2003-10-09 22:32 ` Geoff Collyer
2003-10-08 9:36 ` Ralph Corderoy
2003-10-08 13:38 ` Jim Choate
2003-10-08 17:02 ` a
2003-10-08 14:24 ` rt
2003-10-08 15:10 ` Jim Choate
2003-10-08 15:47 ` rt
2003-10-08 21:53 ` Charles Forsyth
2003-10-08 22:59 ` Jim Choate
2003-10-07 3:48 ` Dan Cross
2003-10-07 3:51 ` boyd
2003-10-07 4:09 ` Jim Choate
2003-10-07 4:15 ` boyd
2003-10-07 2:37 YAMANASHI Takeshi
2003-10-07 2:41 ` boyd
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='023801c38e04$db6f3e60$c901a8c0@cc77109e' \
--to=brucee@chunder.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).