🚀 go-pugleaf

In article <1992Dec09.165917.7074@cadlab.sublink.org> martelli@cadlab.sublink.org (Alex Martelli) writes:
>jmd@muppet.bt.co.uk (John Downey) writes:
>	...
>:The behaviour you describe should only be happening if there are extra
>:carriage returns in the file. Why are you putting extra carriage
>:returns in a text file?
>
>A good reason could be to obtain any kind of overstriking more rapidly
>than with backspaces when the textfile is later cat'ted to a dumb printer.
>For example, if you do have a dumb printer, try printing a few lines like:

Yeah, but this is not really answering his question.  The real reason to
put CR's in a file is to get CR's into a macro.  My .exrc file has a ton
of them.  I'm having a *very* hard time getting xvi to understand fairly
common vi macros (like those kept in the archives described in this
newsgroup.)  Even worse than not understanding CR's inside a line is the
fact that xvi won't let you put ESC's in a macro.  It insists on
cancelling the colon command.  This is unacceptable.  I had to go into
the source to remove this feature to get any reasonably fancy macros to
parse.  I've given up getting the word completion macros to work.

I really like xvi.  I'm using it right now.  It's much better than
elvis.  I also own the MKS toolkit, but I still use xvi for almost all my
editing, since I love the multiple windowing features.  Unfortunately,
for sophisticated macro commands I still have to go back to MKS's vi.  I
really do wish that you could beef up the macro handling.  Use Eric
Bowles's word completion macros for a test case.  If you could handle
those, I can stop using MKS vi for good.

rog.