🚀 go-pugleaf

>From EAK@MIT-MC Tue Nov  3 11:07:11 1981
I've not yet read the article, but it sounds like even if
conceptually his system is no more than an editor and document
compiler as you say, implementing it efficiently or naturally in
an existing editor might be difficult.  You clearly don't want to
Scribe the whole document just to get the .OTL file.  Here
perhaps better control over redisplay(*) could help.  For
example, even the simple hack described in an editor presented at
the SIGPLAN text manipulation conference where all lines with
indentation > X are not displayed would be useful for working
with some kinds of outlines.  Also, the ability to put structure
data in the file that isn't displayed might be nice.  Therefore
I'd like hear of ideas for making the decision of what to display
flexible so that you can play with ideas such as these without
writing a whole new editor (which at least dampens my enthusiasm
sometimes).  Btw, is everyone on the list familiar with NLS?

(*) someone might jump on me for using "redisplay" in this fashion, but
I don't have a better word, and I think you know what I'm getting
at.

[P.S. from JQJ:  Mark Chilenskas has pointed out to me that one such
 display editor with indentation hack is IBM's SPF (Structured Program
 Facility).]