rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: matty@cs.su.oz.au (James Matthew Farrow)
To: dschieb@muse.CV.NRAO.EDU
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: $history on plan 9
Date: Sat, 5 Jun 1993 06:26:47 -0400	[thread overview]
Message-ID: <19930605202647.22292.frobozz@orthanc.cs.su.OZ.AU> (raw)
In-Reply-To: <9306041753.AA10693@muse.cv.nrao.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=X-utf-2, Size: 3028 bytes --]

    From:	dschieb@muse.CV.NRAO.EDU (Darrell Schiebel)
    Message-Id: <9306041753.AA10693@muse.cv.nrao.edu>
    Subject: Re: $history on plan 9
    To:	rc@hawkwind.utcs.toronto.edu
    Date:	Fri, 4 Jun 1993 13:53:33 -0400
    
    
    > P.S. The '9term' program gives the look and feel of 8.5 in an
    > X environment. ftp to ftp.cs.su.oz.au:/pub/matty/9term and get
    > the stuff there. It's neat.    
    
    	Thanks for all of the information. I compiled '9term' and it is pretty
    	nice. However, I haven't been able to find a "history" mechanism that
    	would warrant removing the '$history' hook... perhaps I've missed it.
    	The only thing that is close is the 'bkwd' search on the third button,
    	and it doesn't seem to support regular expressions. I like the 
    	GNU-readline approach much better.
    
    	It seems that the most interesting part of '9term', unicode support,
    	is not available, at least I assume it is not. The missing piece seems
    	to be the fonts, the protection on 
    
    		'ftp.cs.su.oz.au:/matty/unicode/libXg.utf.fonts.tar.Z'
    
    	is '-rw-------'. Too bad.
    
    	If I've missed something here, please let me know. 
    
    							thanks,
    							Darrell Schiebel

I'm currently trying to avoid legal wrangles over whether or not I'm
allowed to distribute the font images.  I mailed Charles Bigelow a
few weeks back but have not had a reply yet.  I'm about to mail him
again to find out what's going on.  Meanwhile at least some images
won't have that problem because I'm preparing some myself.

I've found with history that most of the time you're working in
the immediate context, so you can see the command or it's only a
page away.  For the times when it's not I have a simple command (gh --
grep history) which greps the history file associated with the current
window and a global file for this month and prints hits.  Either way
it ends up on the screen and you can just edit it and `send.'

I've found that I couldn't (or wouldn't like to) do away with
$history for the second reason.  It's too convenient.  I've found
9term and 8.5 seem to be incredible useful from the point of view of
the `malleability' of the text on the screen.  (How many times have
you just wanted to add that `-g' flag to a 5 line cc line output by
make and been foiled by xterm inserting CRs at the end of each line?)
You still want the history, 'though, for the commands slip that out
of your local context.  I know not having history when I log in on
Plan 9 is a pain although I'm still using Unix more than Plan 9 at
the moment so I can't say what a different it makes.  It just seems
awkward not having it there when you're used to it.

					Matty.
--
James Matthew Farrow                    | "For in that moment I beheld the ruin
matty@cs.su.OZ.AU                       | of my existence.  My world fell dark
Basser Department of Computer Science   | and my life became a shallow dream.
Sydney University - FAX: +61 2 692 3838 | `Odi et amo. Excrucior.'" - Tlindah



  reply	other threads:[~1993-06-05 10:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-06-04 17:53 Darrell Schiebel
1993-06-05 10:26 ` James Matthew Farrow [this message]
1993-06-06 16:20   ` mycroft
1993-06-06 18:34     ` Scott Schwartz
  -- strict thread matches above, loose matches on Subject: below --
1993-06-05  0:27 Scott Schwartz
1993-06-04 18:00 Arnold Robbins
1993-06-03 21:57 Byron Rakitzis
1993-06-03 19:51 Arnold Robbins
1993-06-03 19:35 Darrell Schiebel
1993-06-03 19:24 Steve_Kilbane

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=19930605202647.22292.frobozz@orthanc.cs.su.OZ.AU \
    --to=matty@cs.su.oz.au \
    --cc=dschieb@muse.CV.NRAO.EDU \
    --cc=rc@hawkwind.utcs.toronto.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).