From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] tab completion and command history in rc
Date: Thu, 3 Nov 2005 22:28:41 -0700 [thread overview]
Message-ID: <436AF189.2080909@lanl.gov> (raw)
In-Reply-To: <fc73b7d828b678708affd1677c1c022a@orthanc.cc.titech.ac.jp>
I don't think that rc and the rio interface and all that are the be-all
and end-all of interfaces. Neither are X11, Emacs, and bash. It's all a
work in progress, all the time. There are features from each I miss on
the other.
On Linux, I find myself trying to mouse into the middle of a window and
type text; and of course there's all the other Plan 9 bits you don't get
on Unix that you miss a lot. I pound the keyboard a lot. I go through a
lot of keyboards. One advantage of buying clusters is you have lots of
keyboards lying around.
I get really annoyed that up and down arrow act very differently than
right and left arrow in acme. I get annoyed that acme is focus follows
mouse, and rio is not (well, andrey built me a rio with focus follows
mouse for linux, and I love it). On Plan 9, I still miss command
history that spans instances of the shell. Sorry, that's not "Plan 9
PC", but it's my preference.
So, Rian, if there's stuff you find you miss on Plan 9, it may be you
have not learned a "Plan 9" way to do things, or it may be that Plan 9
environment is lacking in some way. I think many of us take a guilty
pleasure in ^F. I know I do. What else might we like from the unix world
that we don't talk about? It would be interesting to see.
ron
next prev parent reply other threads:[~2005-11-04 5:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 4:27 YAMANASHI Takeshi
2005-11-04 5:28 ` Ronald G Minnich [this message]
2005-11-04 4:41 ` Matthew J. Sottile
2005-11-04 5:26 ` Jack Johnson
2005-11-04 8:50 ` lucio
2005-11-04 15:06 ` erik quanstrom
2005-11-04 15:24 ` Axel Belinfante
2005-11-04 15:29 ` erik quanstrom
2005-11-04 15:26 ` Charles Forsyth
2005-11-04 15:54 ` erik quanstrom
2005-11-05 9:20 ` Charles Forsyth
2005-11-04 16:27 ` Russ Cox
2005-12-09 1:58 ` erik quanstrom
2005-11-05 8:54 ` Scott Schwartz
2005-11-05 12:13 ` erik quanstrom
2005-11-05 16:01 ` Ronald G Minnich
[not found] <000201c5e0e5$bbd617f0$14aaa8c0@utelsystems.local>
2005-11-04 6:46 ` Nils O. Selåsdal
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 4:01 YAMANASHI Takeshi
2005-11-04 3:42 YAMANASHI Takeshi
2005-11-04 3:45 ` Russ Cox
2005-11-04 2:30 YAMANASHI Takeshi
2005-11-04 3:08 ` Russ Cox
2005-11-04 2:01 Federico G. Benavento
2005-11-04 1:29 Federico G. Benavento
2005-11-04 0:59 Rian Hunter
2005-11-04 1:06 ` Uriel
2005-11-04 1:07 ` Russ Cox
2005-11-04 1:14 ` John Floren
2005-11-04 1:22 ` Russ Cox
2005-11-04 1:22 ` Uriel
2005-11-04 1:27 ` Uriel
2005-11-04 2:02 ` Russ Cox
2005-11-04 1:56 ` Rian Hunter
2005-11-04 2:08 ` Skip Tavakkolian
2005-11-04 9:20 ` William Staniewicz
[not found] ` <000001c5e0e1$76791f80$14aaa8c0@utelsystems.local>
2005-11-04 6:58 ` Nils O. Selåsdal
2005-11-04 1:23 ` Paul Lalonde
2005-11-04 9:02 ` Scott Schwartz
2005-11-04 15:13 ` "Nils O. Selåsdal"
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=436AF189.2080909@lanl.gov \
--to=rminnich@lanl.gov \
--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).