Re: File coding
Ar an séiú lá de mí Bealtaine, scríobh Sean MacLennan:
With the release of "garlic" and "ginger", I have
decided to try 21.5
again. I have solved most of my problems but one still remains: file
coding.
I compiled without mule, but --with-file-coding. Is --with-file-coding
even still supported?
It’s actually impossible to turn it off with configure in 21.5. What you’re
looking for is this paragraph in the Internals manual:
configure changes
=================
* file-coding always compiled in. eol detection is off by default on
unix, non-mule, but can be enabled with configure option
`--with-default-eol-detection' or command-line flag `-eol'.
Anyway, all files are considered "binary" and I no longer
get text
mode for DOS files. Is there something I am missing? Do I have to
enable mule for simple text files?
I tried `set-file-coding-system', but it no longer seems to work
as expected (i.e. as it worked in 21.4). I can set raw-text-dos, and it
marks my buffer as edited (kinda scary), but the display still shows
all the CRs and I see no change.
That has always been the case, set-file-coding-system doesn’t and never has
re-read the file from disk using the new coding system, which would be
necessary for the CRs to go away.
I noticed there where a lot more codings, did I pick the wrong one?
I don’t think so, it’s probably that you need --with-default-eol-detection.
--
“Apart from the nine-banded armadillo, man is the only natural host of
Mycobacterium leprae, although it can be grown in the footpads of mice.”
-- Kumar & Clark, Clinical Medicine, summarising improbable leprosy research
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta