Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-ses!hp-ptp!davem
From: davem@hp-ptp.HP.COM (Dave_Medlicott)
Newsgroups: comp.sys.hp
Subject: Re: CI.STK history function
Message-ID: <1320032@hp-ptp.HP.COM>
Date: 20 Feb 90 22:52:54 GMT
References: <1990Feb19.235123.5458@sjuphil.uucp>
Organization: HP Pacific Technology Park - Sunnyvale, Ca.
Lines: 76

Tor Lillqvist writes:

> \begin{flame}
> 
> This guy must be joking...  Has he really tried Emacs (or vi) editing
> mode in ksh (or bash)?  I don't understand how he can claim that
> RTE-A's pathetic command stack is better.

  I'm not really sure why a flame is needed. He is merely stating a
  preference; one which I share.

> 
> - CI: only works on HP terminals, and if EnqAck handshake
>   enabled
> - ksh: works on any terminal described by terminfo

  This is true. The command stack reads what is written on the
  screen NOT what was in its input buffer. Thus a terminal that
  can send the entire line is required.

> - CI: only uses the terminal's local editing capabilities
>   (wordprocessor-like fashion, sure...  if you call edit/1000 a
>   wordprocessor) 
> - ksh: you can move to end of line with Control-e, over a word with
>   Meta-f, etc.  Numeric args (Control-U, Meta-[1-9] work, too.

  This is true for the most part, however, the CI command stack 
  can use ctrl A to position to the 1st character in a line and
  ctrl Z to position to the end of the line.

> - CI: no searching
> - ksh: Control-R searches for command matching string

  This is not true. Under CI you can use the /.pattern format to search for 
  patterns. Patterns can also have imbedded wildcards. You can also specify
  that the first command that matches the pattern be executed.

> - CI: if the command line you want to re-execute was longer that 80
>   chars, tough...
> - ksh: scrolls horizontally

    The CI command line buffer has been extended to 256 characters.

> That said above for ksh also goes for bash (the GNU Bourne Again
> Shell), only more so.  Let's hope the next version will compile and
> work well on HP-UX systems, too.
> 
> \end{flame}
> -- 
> Tor Lillqvist,
> working, but not speaking, for the Technical Research Centre of Finland

  Some of the other reasons why I like the CI stack better:

	1) Only one copy of a command is stored in the command stack i.e.
	   if I enter the same command twice in a row, only one copy is
	   saved.

	2) Placing the cursor on a line and then hitting ctrl K puts
	   the line into an execute buffer. Hitting ctrl Q then quits
	   screen mode and begins executing commands in the order they
	   were entered into the execute buffer.

	3) Hitting ctrl D deletes the line the cursor is on from your
	   command stack (thus preventing garbage from building up in
	   your stack).

	4) The CI / command displays an entire screen (size is user definable)
	   of commands, not just the most recent command. This makes it much
	   easier to find that one command you're looking for.


	Again, these are only my personal preferences. 

Dave Medlicott 
davem@hpdstma