Path: utzoo!attcan!uunet!samsung!usc!apple!voder!dtg.nsc.com!waggoner From: waggoner@dtg.nsc.com (Mark Waggoner) Newsgroups: comp.sys.amiga.tech Subject: Re: Handlers (AUX: users should try ComMan 1.3's CNX:serial.device!) Message-ID: <403@icebox.nsc.com> Date: 13 Apr 90 17:35:44 GMT References: <1990Apr11.151918.3110@cat.fulcrum.bt.co.uk> <3244@moondance.cs.uq.oz.au> Reply-To: waggoner@icebox.UUCP (Mark Waggoner) Organization: National Semiconductor, Santa Clara Lines: 24 In article <3244@moondance.cs.uq.oz.au> thyssen@batserver.cs.uq.oz.au writes: > I am currently useing the NEWCON: handler for my console input >But I also have ConMan's PIP: device to do the piping in the ARP ASH >I would like to use ConMan for the console as well (to save the memory used >by NEWCON: ) by I ABSOULUTELY CAN NOT STAND conman's history list >I don't mind the idea of only one copy of repeated commands in the history >list - prefer it in fact. But I must have the last command I execute >as the last command on the history list. This conman does not do. You can set conman to behave almost as you desire. Conman includes a program to set conman options, which I believe is called setcman. One of the options is for conman to keep a true history. It will then put every command on the history buffer, even if it is a repeated command. You get the last command you executed at the end of the history list, but you lose the advantage of having only a single copy of the command in the list. -- Mark Waggoner Santa Clara, CA (408) 721-6306 waggoner@dtg.nsc.com Unofficially representing National Semiconductor Local Area Networks Group Officially misrepresenting myself.