Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!mordor!lll-tis!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: DME space optimizations
Message-ID: <8706270249.AA03832@cory.Berkeley.EDU>
Date: Fri, 26-Jun-87 22:49:40 EDT
Article-I.D.: cory.8706270249.AA03832
Posted: Fri Jun 26 22:49:40 1987
Date-Received: Sat, 27-Jun-87 14:02:01 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 23


	My philosophy has always been "you get what you see"... and you
simply can't *see* spaces at the end of a line... or whether space within
a line is part of a TAB, or really is a space.  Thus, DME will convert tabs
to spaces on load, and optimally re-tab on save (this can be turned on or
off).  DME inherently removes tailing spaces.

	And, as Doug mentioned, it would take a lot of work for me to
change this, and frankly, I have neither the desire or the time to do so.
I *like* those features.  That's the way the cookie crumbles.... You'll just
have to use a different editor if you intend to futz around with UUENCODED 
files.  Of course, anybody can get the source and modify their own personal
copy, but I will not tolerate somebody second-sourcing a modified DME to
any mass medium.

AND INCIDENTLY, you actually *can* edit uuencoded files with DME... uudecode
ignores anything beyond the last specified column, so you simply tack on 
some random character, say 'X' in the appropriate column after every line.
You can even write a subroutine to do it.. find begin, down, block start,
find end, up, block end, goto top of block, while in block { move to column 62
write the character 'X' and go down a line }.

				-Matt