From: Greg Shubin <gshubin@sonic.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Perl5 & kenji arisawa's perl question
Date: Thu, 9 Nov 2000 09:33:03 +0000 [thread overview]
Message-ID: <3A09AE3B.8ABB4D07@sonic.net> (raw)
In-Reply-To: <20001108183912.5957A199E3@mail.cse.psu.edu>
Russ Cox wrote:
> Dodging the C++ bomb shell (quiet, Boyd!), I think I
> would summarize my view of the feeling by saying that
> Plan 9 provides you with a new perspective on how
> to implement various things that in Unix are taken
> for granted as the ``only way to fly''.
>
> The bash features you cite are a great example: instead of
> endowing the shell with command completion, history
> using arrow keys, and emacs command editing, Plan 9 puts
> roughly equivalent capabilities in the hands of the window
> system: you can edit any text in any rio window, cut, paste,
> etc. The feel is different, but now it applies to _all_ applications,
> not just the shell, and without requiring everything to link
> against the GNU readline library.
In my limited experience with Plan 9, I found the "history" just about
useless compared with bash. With bash, I can let the computer grep a few
thousand lines of history, and select whatever is appropriate. With the
Plan 9 cut and paste, I have to visually search, then move from the
keyboard to the mouse and back. Plus I only get a page or two of history.
Also, does Plan 9/rc have [command | filename] completion? I haven't
found it yet. (maybe I should RTFM?)
next prev parent reply other threads:[~2000-11-09 9:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 18:39 Russ Cox
2000-11-08 22:34 ` Boyd Roberts
2000-11-08 22:59 ` andrey mirtchovski
2000-11-08 23:15 ` Boyd Roberts
2000-11-09 4:23 ` [9fans] C++ (Was: Re: Perl5 & kenji arisawa's perl question) Lucio De Re
2000-11-09 7:45 ` [9fans] Re: Perl5 & kenji arisawa's perl question Steve Kilbane
2000-11-09 9:33 ` Greg Shubin [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 18:54 bwc
2000-11-09 17:44 anothy
2000-11-09 19:15 ` Boyd Roberts
2000-11-09 16:51 Dave Atkin
2000-11-09 21:52 ` Steve Kilbane
2000-11-09 22:00 ` Boyd Roberts
2000-11-09 16:10 erik quanstrom
2000-11-09 15:29 rog
2000-11-09 14:42 ` Boyd Roberts
2000-11-09 13:48 bwc
2000-11-08 18:35 David Gordon Hogan
2000-11-08 16:45 rog
2000-11-08 22:06 ` Boyd Roberts
2000-11-08 15:57 forsyth
2000-11-08 15:36 anothy
2000-11-08 13:56 rog
2000-11-08 13:11 ` Boyd Roberts
2000-11-07 23:30 anothy
2000-11-07 16:24 Re[2]: " steve.simon
2000-11-07 16:44 ` Boyd Roberts
2000-11-07 18:30 ` Douglas A. Gwyn
2000-11-07 18:58 ` Boyd Roberts
2000-11-08 9:23 ` George Michaelson
2000-11-08 12:38 ` Boyd Roberts
2000-11-08 18:13 ` Greg Shubin
2000-11-08 22:27 ` Boyd Roberts
2000-11-06 16:17 forsyth
2000-11-06 8:08 nigel
2000-11-05 7:34 [9fans] " andrey mirtchovski
2000-11-05 9:31 ` [9fans] Re: Perl5 & " arisawa
2000-11-06 8:03 ` Jonathan Sergent
2000-11-06 15:45 ` Scott Schwartz
2000-11-06 15:51 ` Boyd Roberts
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=3A09AE3B.8ABB4D07@sonic.net \
--to=gshubin@sonic.net \
--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).