From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: [9fans] history
Date: Fri, 7 Jul 2006 17:21:46 +0200 [thread overview]
Message-ID: <24c7ea3c3360f3668dc81cffd93760fa@lsub.org> (raw)
Russ sent this time ago:
; cat /bin/"
#!/bin/rc
rfork en
if(test -r /mnt/acme/acme/body)
bind /mnt/acme/acme/body /dev/text
PROMPT=';+[ ]+'
fn cmds {
grep '^'$PROMPT /dev/text | sed 's/^/ /'
}
switch($#*) {
case 0
cmds | tail -1
case *
cmds | grep '^ '$PROMPT^$"*
}
: > > I agree. This is an annoyance for me. I also wish rc would get *some*
: > > kind of history; if I want to re-run troff after making a change to a
: > > file, it's faster to type "!!" than to select the previous command,
: > > snarfing, pasting, clicking at the end of the line, and hitting enter.
: > >
: >
: > There is a command 'Send' in the Menu. Not that this is a
: > counter-argument, I am just pointing out things ;-)
next reply other threads:[~2006-07-07 15:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 15:21 Fco. J. Ballesteros [this message]
2006-07-07 16:16 ` Skip Tavakkolian
-- strict thread matches above, loose matches on Subject: below --
2002-01-22 20:43 rob pike
2000-11-14 21:39 [9fans] History presotto
2000-11-14 21:46 ` Boyd Roberts
2000-11-14 20:45 Richard Miller
2000-11-14 19:12 anothy
2000-11-14 19:37 ` Boyd Roberts
2000-11-14 17:21 rog
2000-11-14 14:28 rob pike
2000-11-14 15:12 ` Boyd Roberts
2000-11-09 18:34 rob pike
2000-11-09 16:39 forsyth
2000-11-10 9:35 ` Douglas A. Gwyn
2000-11-14 9:33 ` George Michaelson
2000-11-14 9:51 ` Boyd Roberts
2000-11-14 15:50 ` Douglas A. Gwyn
2000-11-14 16:13 ` Boyd Roberts
2000-11-09 16:15 rog
2000-11-09 15:26 ` Boyd Roberts
2000-11-09 14:01 rob pike
2000-11-09 14:50 ` Boyd Roberts
2000-11-09 15:20 ` Axel Belinfante
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=24c7ea3c3360f3668dc81cffd93760fa@lsub.org \
--to=nemo@lsub.org \
--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).