9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam & rio
Date: Sat, 31 Mar 2001 07:34:55 -0500	[thread overview]
Message-ID: <20010331123458.69F66199E3@mail.cse.psu.edu> (raw)

I regret that sam doesn't do chorded cut and paste, and have tried
several times to fix that deficiency, but the split design of sam
causes a division of labor that makes chording very difficult.  The
same applies to scrolling when selecting.

On the other hand, I find the monolithic design of acme limits its
ability to do some other things, such as work well over slow links.

If win worked as a file system serving /dev/cons itself, it would
behave a little better, but there would still be a race between where
acme puts stuff and where win thinks it is.  That is fixable by
extending acme's external interface somewhat, but at that point you've
built three levels of file system serving /dev/cons and it seems like
overkill to me.  My solution is not to run win much, either.  I always
thought of it as an expedient workaround.  Acme iself is already a
shell.

-rob




             reply	other threads:[~2001-03-31 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-31 12:34 rob pike [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-31  5:51 baldwin

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=20010331123458.69F66199E3@mail.cse.psu.edu \
    --to=rob@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).