Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!wuarchive!udel!sbcs!eeserv1.ic.sunysb.edu!jallen
From: jallen@eeserv1.ic.sunysb.edu (Joseph Allen)
Newsgroups: comp.editors
Subject: Re: Xedit is better than vi and emacs
Message-ID: <1991May1.184113.14519@sbcs.sunysb.edu>
Date: 1 May 91 18:41:13 GMT
References: <1991Apr24.155049.21710@njitgw.njit.edu> <1991Apr26.155233.7486@chinet.chi.il.us> <DANJ1.91Apr28061619@cbnewse.ATT.COM>
Sender: usenet@sbcs.sunysb.edu (Usenet poster)
Organization: State University of New York at Stony Brook
Lines: 22

In article <DANJ1.91Apr28061619@cbnewse.ATT.COM> might as well reply to netnews, it's the usual editor war writes:
>In article <1991Apr24.155049.21710@njitgw.njit.edu> ken@hertz.njit.edu (ken ng cccc) writes:
>>Instead of scrolling through the actual function source code each and every
>>time, if you could hide or close off certain sections of code from being
>>presently displayable, you could find the functions easier.  If you were
>>not sure how function 'foo' works, you could open up/display the text that
>>was hidden.
>
>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).

--
#define h 23 /* Height */         /* jallen@ic.sunysb.edu (129.49.12.74) */
#define w 79 /* Width */                       /* Amazing */
int i,r,b[]={-w,w,1,-1},d,a[w*h];m(p){a[p]=2;while(d=(p>2*w?!a[p-w-w]?1:0:0)|(
p<w*(h-2)?!a[p+w+w]?2:0:0)|(p%w!=w-2?!a[p+2]?4:0:0)|(p%w!=1?!a[p-2]?8:0:0)){do
i=3&(r=(r*57+1))/d;while(!(d&(1<<i)));a[p+b[i]]=2;m(p+2*b[i]);}}main(){r=time(
0L);m(w+1);for(i=0;i%w?0:printf("\n"),i!=w*h;i++)printf("#\0 "+a[i]);}