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, "Charles Forsyth" <forsyth@terzarima.net>
Subject: Re: [9fans] tab completion and command history in rc
Date: Fri,  4 Nov 2005 09:54:27 -0600	[thread overview]
Message-ID: <20051104155427.3DDF2651A5@dexter-peak.quanstro.net> (raw)
In-Reply-To: <4de996c231bf40b13bbc757f65e4b64b@terzarima.net>

i thought about that. it really seems like the "right" solution in
once sense. it moves history completely out of the purview of 
the shell. the bonus is that you would have history for every application.

the downside is that you would have history for every application. that's
explicitly not what i want. the input to ed/sam -d editing sessions interleaved
with mail and rc commands doesn't seem very useful to me.

rio thus "feels" to me like the wrong level at which to implement this 
functionality.

to summarize:

a. rio doesn't know if the input is an rc command or input to, say, sam -d.

b. it would be nice to improve on the old history mechanism; rio doesn't have
enough information to do this. e.g.

	1. syntax errors shouldn't be logged to the history
	2. multiline statements should be recalled as a unit.

for me (a) would be a big problem. (b) hasn't been solved in a
decade, so i guess i can live with it. ;-)

- erik

Charles Forsyth <forsyth@terzarima.net> writes

| 
| > 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
| 
| why not have rio log what you type, or put something between
| your keyboard and rio?


  reply	other threads:[~2005-11-04 15:54 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
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 [this message]
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=20051104155427.3DDF2651A5@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=forsyth@terzarima.net \
    /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).