9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] irc tools
Date: Fri,  4 Oct 2002 20:41:46 -0400	[thread overview]
Message-ID: <a1eebf703eb33f0595aebc12b7c66804@plan9.bell-labs.com> (raw)

I'm curious what you mean about the difference between
acme and sam as a model for a chat client.  The only difference
between acme and sam windows (for the purposes of this discussion)
is that sam windows are click-to-type and acme windows aren't.
Are you claiming that moving the mouse but not clicking is
somehow worse than moving the mouse and clicking?

I'm particularly confused by your claim that "dumb terminal mode"
would mix server output and user input mid-typing, which simply
isn't true at all in Plan 9.  (It's true in Unix.)  Run:

	{sleep 5; echo -----------} &

and then type something at the next prompt but don't hit enter.

	g% {sleep 5; echo -----------} &
	g% something

becomes

	g% {sleep 5; echo -----------} &
	g% -----------
	something

the lines stay unmixed.  Sadly, the prompt doesn't move,
but you could get around that by not having a prompt, or by
telling win/rio how big the prompt is.

If I were going to build a real interactive IRC (or IM, ...) client
for Plan 9, I'd have two acme windows for each open channel,
one displaying chatter and the other taking your input a la
(probably via) win.  Almost all the pieces are there now, in fact.
I'm not sure about one-on-one chats -- I can see benefits to having
them in a single window and benefits to having them split across
two windows.

What did you have in mind in as the "sam-style" interface?

Russ


             reply	other threads:[~2002-10-05  0:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05  0:41 Russ Cox [this message]
2002-10-05 16:34 ` Jack Johnson
  -- strict thread matches above, loose matches on Subject: below --
2002-10-05  2:09 rob pike, esq.
2002-10-04  2:17 Russ Cox
2002-10-04  4:48 ` Jonathan Sergent
2002-10-04 16:40 ` Jack Johnson
2002-10-04 16:43   ` Scott Schwartz
2002-10-04 17:14     ` Jack Johnson
2002-10-04 17:24   ` andrey mirtchovski

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=a1eebf703eb33f0595aebc12b7c66804@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.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).