9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] irc tools
Date: Fri,  4 Oct 2002 10:14:26 -0700	[thread overview]
Message-ID: <3D9DCC72.1040909@nas.com> (raw)
In-Reply-To: <20021004164359.3333.qmail@g.bio.cse.psu.edu>

Scott Schwartz wrote:
> | ... and the closest I can envision (without
> | more caffeine) is an inverted sam interface,
>
> Not acme?

No, not acme.

The problem with acme and IRC (as I see it) is that your input goes
wherever the cursor happens to lie, so if you want to change modes (from
one server to another, or from public to private), you have to not only
move the cursor, but provide a facility in each window to separate the
user input from the server output, or live with the dumb terminal mode
of mixing the two mid-typing (which in traditional Plan 9 parlance can
be confusing, if you're used to editing a command before submitting it).

If you segregate the commands to the server from the server output in
acme, then you have to have a command to switch the server/person/window
to which you would like to direct the current message.

Conversely, sam-style the streams from the various sources are free to
keep doing their thing while you compose your thoughts, and changing
active windows meshes nicely with the modal change in discussions (if
you're prone to having more than one discussion at once).

-Jack



  reply	other threads:[~2002-10-04 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2002-10-04 17:24   ` andrey mirtchovski
2002-10-05  0:41 Russ Cox
2002-10-05 16:34 ` Jack Johnson
2002-10-05  2:09 rob pike, esq.

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=3D9DCC72.1040909@nas.com \
    --to=fragment@nas.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).