🚀 go-pugleaf

In article <580@kunivv1.sci.kun.nl>, ge@kunivv1.sci.kun.nl (Ge' Weijers) writes:
: ken@argus.UUCP (Kenneth Ng) writes:
: [Stuff about folding editors deleted]
: >Hm, is that like the xedit (VM/CMS) 'exclude' command?
[edit]
: Something like that. If xedit were smart enough to find the end of a procedure/
: module if I point at the beginning, AND it would give some indication what it
: was hiding (the procedure header, for instance), AND it could save this along
: with the text it would be a folding editor. A lot of macro-hacking would probably
: do it.

Hm, the programming standards here dictate a documentation block of what
I generally term useless junk which I don't need to see when I'm coming on
from home at 1200 baud (yes I'm deprived).  When my xedit session fires up,
it checks if its a C source, if so it hides the documentation block for me
automantically.  I can see that its hidden because of the jump in the line
numbers, or I can do a 'shadow on' to see exactly where the lines are being
hidden and how many are hidden.  If I just issue 'file', the entire contents
are saved.  If I issue 'put' only the display contents are saved to file.
How hard is it?  The code fragment follows:

'extract/filetype'
if filetype == 'C' then do
   'top'
   'locate/$documenter'
   'exclude /$documenter'
   end

I don't consider that a lot of macro hacking.

Sometimes the Great Satan (IBM) does come up with a good idea.


Kenneth Ng: Post office: NJIT - CCCC, Newark New Jersey  07102
uucp rutgers!andromeda!galaxy!argus!ken
bitnet(prefered) ken@orion.bitnet

-- 
Kenneth Ng: Post office: NJIT - CCCC, Newark New Jersey  07102
uucp !andromeda!argus!ken *** NOT ken@bellcore.uucp ***
bitnet(prefered) ken@orion.bitnet