9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "erik quanstrom" <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, "Ronald G Minnich" <rminnich@lanl.gov>
Subject: Re: [9fans] tab completion and command history in rc
Date: Fri,  4 Nov 2005 09:06:30 -0600	[thread overview]
Message-ID: <20051104145056.A3EC1651A4@dexter-peak.quanstro.net> (raw)
In-Reply-To: <436AF189.2080909@lanl.gov>

Ronald G Minnich <rminnich@lanl.gov> writes

| [...]  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.

global /persisitant/ history is a "must have" for me. it was the reason
i utf-8ized byron's (unmaintained?) shell. 

productivity will suffer just a little bit if you have to retype something
as a last resort. but trying to figure out that ip address you ssh'd to last 
week/month/year could waste 10 minutes. grepping persistant history is a 
big win for me.

(if you want global but non-persistant history on p9p changing the " command to look at
all your open windows wouldn't be too hard but you would have an ordering
problem; it would difficult to order the commands correctly.)

i looked at modifying rc to write commands to a history file but it
didn't seem to fit very well. maybe a hook would be better as in

fn post-cmd {
	echo $* >> $history
}

paul haahr's shell es went all the way and made the whole interactive loop a function.

erik


  parent reply	other threads:[~2005-11-04 15:06 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
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 [this message]
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=20051104145056.A3EC1651A4@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=rminnich@lanl.gov \
    /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).