At 01:37 PM 12/6/01 +0100, Christoph.Wedler(a)sap.com wrote:
> No, I don't think toggle-buffer-file-coding-system should
change the
> default EOL type.
OK, I expected this. The point is that EOL type nil doesn't mean some
default EOL type (which you could customize somewhere), it means
auto-detect (if the info files are correct) and auto-detect when saving
the buffer means XEmacs' way which is the Unix file ending.
Thus, in the current XEmacs on Windows-NT, you have to do the following
to produce a file with CRLF endings:
1. open the file, write some text
2. save it
3. kill the buffer
4. load the same file
5. M-x toggle-buffer-file-coding-system
6. insert & delete a char
7. save it
I hope that everybody agrees that this is somewhat annoying.
It is but its difficult to do something that works in all cases. I guess if
we only did it for windows-nt that would be somewhat ok. I specifically do
not want this to happen under cygwin.
":t". Yup, that's quite cryptic. But hey, I didn't
make _that_
change. I don't see where it can be done in Lisp. But it should be
able to do this in Lisp, since some people want to have the space....
Its in the C-code.
To other remarks:
* "Toggling" Unix -> Dos -> Mac -> ... doesn't seem to be what
people
really need. Ok, there could be a variable... But it should affect
Agreed.
also the existing command M-x toggle-buffer-file-coding-system.
Agreed.
* EOL-Type menu: hm, a bit too much stuff for such a small thing
(with
the button-2 thing I just wanted to avoid people asking me how to do
this in XEmacs...)
A menu is less cryptic, I would be concerned if this could happen just by
random clicking of the mouse.
* To whether I should call toggle-buffer-file-coding-system in my
mouse
funciton: yes, that's why I wanted to make the changes in
toggle-buffer-file-coding-system.
Right
andy