From: "Christopher R. Carlen"
Subject: Re: Anyone using Spice OPUS?
Date: Wed, 02 Oct 2002 09:46:26 -0700
Organization: Sandia National Laboratories, Albuquerque, NM USA
References: <3D9A6307.1040800@BOGUS.earthlink.net> <_FEm9.97658$S32.firstname.lastname@example.org>
NNTP-Posting-Date: Wed, 2 Oct 2002 16:45:26 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
> "Chris Carlen" wrote in message
>> ... I hated the Berkeley SPICE too, because it didn't have command
>> line editing, which any respectable modern program ought to have at
>> least, if it dares to be a CLI program in the first place.
> SPICE has been a CLI program since its inception (maybe before your
> conception?), long before the advent of cheap terminals that could
> display anything more than ASCII.
No, what I'm talking about is editing the commands on the command line,
like a modern shell such as Bash can do.
The Berkeley SPICE I think could handle backspace, but perhaps not even.
I seem to recal having to scrap my commands if I made a mistake in the
middle, because attempting to backspace would make escape sequences get
into the command line. This might have been a result of some
configuration problem, but I didn't want to track it down. Expecting
the cursor to backspace when you backspace, to delete when you delete,
etc. is not unreasonable. But most command line environments don't
guarantee this, aka, DOSEDIT.
In UNIX/Linux, the Bash shell provides this functionality built in,
fortunately. But SPICE does not.
Spice OPUS seems to have added this minor change, which results in a
huge useability increase. Particularly being able to
up-arrow/down-arrow to scroll through the command history.
Christopher R. Carlen
Principal Laser/Optical Technologist
Sandia National Laboratories CA USA