🚀 go-pugleaf

In article <3115@psuvax1.psu.edu> flee@gondor.psu.edu (Felix Lee) writes:
>Then there's selective-display.  (setq selective-display t) tells Emacs that
>anything after a ^M on a line should not be displayed.  Emacs's outline-mode
>uses selective-display.  It wouldn't be too hard to write an ALL work-alike.

Well, it wouldn't be difficult to write an ALL look-alike, but a
work-alike *would* be difficult, if you want to include capability to
perform 'replace-string' or 'replace-regexp' with ALL in effect.

Take, for example, a 40-line file, each line containing "Line nn", where
nn is the line number.  Consider doing 'ALL /1/' on that file in XEDIT,
followed by a 'CHANGE /Line/Fine/ * *'.  Once you displayed the entire
file again with 'ALL', you would see that only the lines with a '1' in
them had "Line" changed to "Fine"; only the displayed lines are affected
by editor operations when an ALL is in effect.

Implementing this in Emacs would involve doing a series of iterative
narrow-to-region/replace-{string,regexp} steps, which is certainly
doable, but which would also be rather slow.

Also, wrt 'selective-display' and the writing of such buffers to files,
are any C-m's originally contained in the buffer treated any differently
when written out to a file than C-m's introduced into the buffer by the
major mode?  Ie., do C-m's get converted to newlines indiscriminately?

--woodstock
-- 
	   "How did you get your mind to tilt like your hat?"

...!{decwrl|hplabs!oliveb|pur-ee|qantel|amd}!intelca!mipos3!cpocd2!nate
<domainish> :   nate@cpocd2.intel.com		ATT :    (602) 961-2037