9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skipt@real.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Adding history to Rio's windows
Date: Sat, 30 Sep 2000 04:02:29 -0700	[thread overview]
Message-ID: <3.0.5.32.20000930040229.00adfd20@mail.real.com> (raw)
In-Reply-To: <009e01c02a8c$6498d6e0$97036887@cs.belllabs.com>

After reading the discussions here, I am coming around to your point of view.

Has anything like this next idea been considered?
Use 'pipefile' and a pair of cooperating filters to interpret some
keyboard input as scrolling through the input history. The output
filter would supply the history item.

At 10:30 PM 9/29/00 -0400, rob pike wrote:
>I'm of two minds on this topic.  It's nice to make it easy to redo commands,
>but I've never seen a suggested design, including this one, that feels
>easy enough to beat a simpler, less invasive keyboard-driven history
>mechanism. Muck up the button 2 menu and you'll have a lot to answer
>for.  It might be worth trying, but be honest with the result, and toss it
>if the gain isn't worth the cost in menu navigation.  You *will* make cut
>and paste harder to use.  I agonized about adding "plumb" to the button
>two menu, and finally decided to do it because it provided something
>entirely new.  There are other ways to provide history, however.
>
>-rob
> 
>
>
>




  reply	other threads:[~2000-09-30 11:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <skipt@real.com>
2000-09-28 23:07 ` Skip Tavakkolian
2000-09-28 23:06   ` Boyd Roberts
2000-09-29  4:48     ` Skip Tavakkolian
2000-09-29 20:44       ` Boyd Roberts
2000-09-30  2:30         ` rob pike
2000-09-30 11:02           ` Skip Tavakkolian [this message]
2000-09-28 23:29   ` Scott Schwartz
2000-10-01  0:25   ` Richard Uhtenwoldt
     [not found] <rsc@plan9.bell-labs.com>
2000-09-29  5:01 ` Russ Cox
2000-09-29  5:26   ` Scott Schwartz
2000-09-29 20:52   ` 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=3.0.5.32.20000930040229.00adfd20@mail.real.com \
    --to=skipt@real.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).