Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!purdue!mentor.cc.purdue.edu!waylacm2
From: waylacm2@mentor.cc.purdue.edu (Mooch)
Newsgroups: comp.binaries.ibm.pc.d
Subject: WCED -vs- CED
Message-ID: <11357@mentor.cc.purdue.edu>
Date: 26 Apr 91 16:15:09 GMT
Reply-To: waylacm2@mentor.cc.purdue.edu (Mooch)
Organization: Purdue University
Lines: 22


    Did anyone else look at WCED and receive a few surprises?  
I put it together thinking that it might be a newer version of
CED that i have used for years.  Close, but no prize for second.
What i did find was a good program to do command editing and
history and (pleasantly suprising) filename completion.  The last
was especially happy since i'm currently using two programs to 
accomplish a similar effect, namely command line history and
filename completion.
    What i didn't find was any mechonism at all for command 
aliasing (synonyms).  This was a great disapointment.  CED (or WCED)
with command editing, history and aliasing (all of which CED
has) as well as filename completion (WCED has it) would be a
truly wonderful utility.
    Oh well, back to buoying myself up with yet more pieces of
shattered hopes.

-- 
 _ _ _                | waylacm2@mentor.sage.cc.edu  (Greg Mowczko)
' ) ) )            /  | 
 / / / _________. /_  |  The music fills my head
/ ' (_(_) (_) (__/ /_ |  Loud enough to wake the dead.