From: John Floren <jfloren@moseslake-wa.com>
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 20:14:29 -0500 [thread overview]
Message-ID: <436AB5F5.8050703@moseslake-wa.com> (raw)
In-Reply-To: <71838305-CDB2-4CE6-87C5-8EFAA3E03FD1@mit.edu>
Rian Hunter wrote:
> Hi,
>
> I'm very very new to Plan 9 and I'm very conscious of the fact that
> things are done differently if not better than in the unix family. In
> bash and in some versions of csh and sh there is tab-completion and
> command history (you get these effects by pressing tab or up,
> respectively, on the keyboard). Does that exist in rc, or is it done in
> different way in Plan 9?
>
> Also on my keyboard my directional buttons no longer work, so in a
> terminal window running in rio it's very frustrating when I get to the
> bottom of the window and have to use the mouse to scroll down or press
> enter twice. Is there a way so that the command line always stays in
> sight in the terminal window? or, are there other key sequences I can
> use to simulate up down left and right (similar to hjkl in vi or ctrl+n
> or ctrl+p in emacs/bash).
>
> Thanks!
>
> Rian Hunter
>
Ouch. You seem to have unconsciously hit on some of the more hot-button
topics for Plan 9 users. Tab completion is partly implemented; hit
"Ctrl-f". However, as a quick foray onto #plan9 will tell you, nobody
seems to believe in tab completion, finding multiple "ls" commands and
copy-pasting to be faster. As for command history, you are expected to
find the previous command in your rc window, edit it, copy it, paste it
to the prompt, and then run it. This is obviously more efficient than
hitting the "up" arrow.
As for keeping the command line always in view, mid-click on the window
and select "scroll". I really can't help you with regard to your
directional buttons.
John Floren
--
http://nuwen.net/~digi/cluster
Jealousy is all the fun you think they have.
next prev parent reply other threads:[~2005-11-04 1:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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"
2005-11-04 1:29 Federico G. Benavento
2005-11-04 2:01 Federico G. Benavento
2005-11-04 2:30 YAMANASHI Takeshi
2005-11-04 3:08 ` Russ Cox
2005-11-04 3:42 YAMANASHI Takeshi
2005-11-04 3:45 ` Russ Cox
2005-11-04 4:01 YAMANASHI Takeshi
2005-11-04 4:27 YAMANASHI Takeshi
2005-11-04 5:28 ` Ronald G Minnich
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
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=436AB5F5.8050703@moseslake-wa.com \
--to=jfloren@moseslake-wa.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).