9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rian Hunter <rian@MIT.EDU>
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:56:44 -0500	[thread overview]
Message-ID: <A13C6C4D-BD9E-478F-9683-09E54AA12D9C@mit.edu> (raw)
In-Reply-To: <20051104012235.GE28449@server4.lensbuddy.com>

Disclaimer:

Please don't take me the wrong way, I spent a large portion of today  
reading the Plan 9 papers and the descriptions behind sam and rc, as  
well as various man pages. I guess I didn't think to look in the  
window(1) man page for the answers to my question was because i  
thought this would be implemented in rc than in rio (basically  
because that's how its done in unix). I credit this blunder to still  
having a very unixish perception of Plan 9.

I knew about mouse-chording/send from reading doc on Acme, but I  
didn't realize it was also used in rio. Once I become more familiar  
with this interface I can see myself liking it a lot. As for now I'm  
still grumpy when I have to remove my hands from the home position on  
the keyboard, but i know that new ideas and innovation require change  
and challenge to old de factos and standards.

Thanks for your patience and immediate replies!

Rian Hunter

On Nov 3, 2005, at 8:22 PM, Uriel wrote:

> On Thu, Nov 03, 2005 at 08:14:29PM -0500, John Floren wrote:
>> 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.
> No need to copy/paste(and if you do, do it mouse-chording), you can  
> use
> "Send" directly.
>
> Edit any line in your window, double click at the start or end of the
> line to select it, and then Middle-click->Send; is a very common and
> useful idiom(note that in the default profile your shell prompt is
> defined as a NOP function precisely for this).
>
> This are all FAQs, I think for the most part are well documented in  
> the
> papers, man pages and the Wiki; and of course lots of material and in
> the 9fans archives.
>
> The Plan 9 community can be friendly or harsh, but reading the docs is
> always well worth the time.
>
> uriel



  parent reply	other threads:[~2005-11-04  1:56 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
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 [this message]
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=A13C6C4D-BD9E-478F-9683-09E54AA12D9C@mit.edu \
    --to=rian@mit.edu \
    --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).