Stephen J. Turnbull wrote:
>>>> "Christoph" == Christoph Wedler
<Wedler> writes:
Christoph> Any patch that will not allow me to toggle the eol type
Christoph> of a new buffer to the dos ending (like a) is
Christoph> completely useless for me, unless undecided is
Christoph> automatically viewed as dos eol type under Windows-NT.
What's wrong with
(setq file-coding-system-alist
(append file-coding-system-alist '(("." . undecided-dos)))
as a workaround?
It doesn't work:
1. Use the above appended list
2. Open a new file foo.txt with two line of "ab".
3. You see the modeline is still "ISO8" (and
`buffer-file-coding-system' is iso-2208-8), but this would be
acceptable, although not nice (since I also see ISO8 for Unix
endings and ISO8:T for dos)
4. Save the buffer, the length is 6 bytes (i.e., Unix endings)
5. Kill the buffer, re-read it.
6. Modeline ISO8:T, and `buffer-file-coding-system' is #<coding_system
iso-2022-8-dos> -- huh?
7. delete your entry from file-coding-system-alist
8. Kill the buffer, re-read it.
9. Modeline ISO8, and `buffer-file-coding-system' is #<coding_system
iso-2022-8-unix>
BTW, I haven't seen one reason by anyone, why toggling from eol type nil
to some other (whether unix, dos or mac) is bad.
- Christoph