From: baldwin@vitanuova.com
To: 9fans@cse.psu.edu
Subject: [9fans] sam & rio
Date: Sat, 31 Mar 2001 00:51:25 -0500 [thread overview]
Message-ID: <20010331055126.9EB1C199FA@mail.cse.psu.edu> (raw)
rob mentions the danger of having two interfaces being almost the same
but different as an argument against having DEL act differently in sam
and rio.
i'll just mention my major point of frustration on this topic: the
lack of chorded cut/paste in sam. i am so used to do this in rio and
acme that i have become almost crippled in sam. the lack of
auto-scroll° and selecting off the top or bottom of the window round
out my list of annoying diffs between sam and rio/acme.
luckily, with the addition of the sam command language to acme, i now
have no reason to use sam†. now if acme only did "win" windows as well
as rio (how i miss the input/output point distinction), i might not
run rio either‡.
° why doesn't auto-scroll work with the middle and right buttons?
† splitting front-end from back-end is still useful for slow links.
‡ of course, graphing programs must still be run from rio.
next reply other threads:[~2001-03-31 5:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 5:51 baldwin [this message]
2001-03-31 12:34 rob pike
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=20010331055126.9EB1C199FA@mail.cse.psu.edu \
--to=baldwin@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).