FWIW - EDTF works just fine as do the PASE based editors.
In both cases I have found issues with CR/LF messing things up, especially with bash scripts not being executable with CR/LF on the shebang line.
This got resolved once I discovered the dos2unix command.
Dos2unix fixes up files and converts to UNIX format.
Wish I had known about this when I started editing IFS files that cared about LF vs CR/LF.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>
------------------------------
message: 6
date: Sun, 2 Apr 2023 18:42:30 -0600
from: Jack Woehr via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: Re: edtf of httpd.conf corrupting file
Probably what really happened here is that in editing the file the other
person changed the line ending and whatever settings EDTF was operating
under didn't handle it correctly.
But that gets back to the point I've been making rather forcefully in my
other postings.
It's hopeless to "always have edited the file with EDTF". From now on,
that's just dangerous, because you may be the last person in reach of your
files to be using that cumbersome tool.
The things you'll have to pay attention to and learn about the relationship
between how EDTF treats a file and how modern editors treat a file
requires more work than learning to use a modern editor.
So save your employer some money and yourself some grief and move on from
EDTF.
midrange.com
