(Win32 version) Files save with DOS CRLF linefeeds and/or /n line endings -- bad for Cygwin stuff.
Submitted by on Friday, 8 May, 2009 - 03:05
Maybe I'm missing something.
Is there a Buffer or Global Options setting in the present stable version to prevent either of these from happening when saving a file? If there isn't one, adding one would put jEdit ahead of the (lite versions of the) commercial developer-oriented text editors and definitely ahead of those emacs and vim clones that are still around for Windows and Mac OS X.
The whack-n's are particularly annoying when they appear in shell scripts in Cygwin and other Linux/Unix-es.
A cross-platform text editor should default with cross-platform file-write settings, imo, and as Mac and Windows both glom onto LF (without any /n ornamentation), logically that's the better, if not best, choice for a default.
Again, my opinion.
If I'm missing a hint or a clue as to the settings, please let me know.
BZT
Is there a Buffer or Global Options setting in the present stable version to prevent either of these from happening when saving a file? If there isn't one, adding one would put jEdit ahead of the (lite versions of the) commercial developer-oriented text editors and definitely ahead of those emacs and vim clones that are still around for Windows and Mac OS X.
The whack-n's are particularly annoying when they appear in shell scripts in Cygwin and other Linux/Unix-es.
A cross-platform text editor should default with cross-platform file-write settings, imo, and as Mac and Windows both glom onto LF (without any /n ornamentation), logically that's the better, if not best, choice for a default.
Again, my opinion.
If I'm missing a hint or a clue as to the settings, please let me know.
BZT
