slc@hoptoad.uucp (Steve Costa) (05/17/87)
I just found ConMan (alternate console manager with history & enhanced editing) on a local bulletin board and I like its features. However, I don't know how to make it work on my startup CLI (that is, it works only on stuff opened after it is called). Is this possible, or do I have to close the initial CLI and start a new one? I haven't yet been able to make my initial CLI go away, apparently because if a CLI starts some other stuff, its window won't disappear. So, if it's necessary to do this to get conman to work, what is necessary in my startup-sequence to allow the first CLI window to close?
hrlaser@pnet02.UUCP (05/20/87)
Here's how to get Conman going, open up a NewCLI, and have the NewCLI
still be numbered 1> , and yet get rid of your original CLI so that
Conman will function and you're not left with a do-nothing window...
The following is the tail-end of my startup-sequence:
conman
run wait 3+
newcli "con:0/0/640/200/HarvDos" <--(cuz I like a full screen window)
endcli >nil:
The second line is the trick! This suggestion came to me from one of
the members of the Plink AmigaZone (whose name I unfortunately did not
remember), but this will make your initial CLI go away, and open the
new one with the 1> prompt with Conman up and running!
Harv Laser
PeopleLink: CBM*HARV
UUCP: {akgua!crash, hplabs!hp-sdd!crash}!gryphon!pnet02!hrlaser
INET: hrlaser@pnet02.CTS.COM