Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!dimacs.rutgers.edu!aramis.rutgers.edu!paul.rutgers.edu!njin!njitgw.njit.edu!hertz.njit.edu!ken From: ken@hertz.njit.edu (ken ng cccc) Newsgroups: comp.editors Subject: Re: Xedit is better than vi and emacs Message-ID: <1991May2.122705.20209@njitgw.njit.edu> Date: 2 May 91 12:27:05 GMT References: <1991Apr26.155233.7486@chinet.chi.il.us> <1991May1.184113.14519@sbcs.sunysb.edu> Sender: news@njit.edu Organization: New Jersey Institute of Technology, Newark, N.J. Lines: 22 Nntp-Posting-Host: hertz.njit.edu In article <1991May1.184113.14519@sbcs.sunysb.edu> jallen@eeserv1.ic.sunysb.edu (Joseph Allen) writes: >In article might as well reply to netnews, it's the usual editor war writes: [edit ken@hertz talking about selective line displays in editors] :>GNU Emacs got things like that: :Plus don't forget CTAGS. If the reason you need all this hiding stuff is to :find what function args are, just use the ctags system present in most unix :editors. (and in this case windows are very usefull- one opens with the :function you want already in it). Showing function arguements is JUST ONE of the MANY possible uses of the XEDIT 'all' command, it is also an easy one to show why I find it useful. CTAGS sounds like a specific program to solve a specific problem. The GNU Emacs solution sounds like a GENERAL PURPOSE way to solve the problem, which will always tend to be my preference. Now, I know GNU Emacs has online documentation, but I'd still like to purchase a hardcopy manual for it somewhere. Hopefully the money will go toward supporting the GNU effort. Anyone know where I can get one? Kenneth Ng "No problem, this is how you make it" -- R. Barclay, ST: TNG