Re: File coding
there's no good reason other than paranoia. i was planning on making it
mandatory, and simply setting all coding systems to `binary' under unix. if you
could create a patch like this, and test it under unix and make sure that no
files, process i/o, etc. ever gets interpreted any other way than binary, then i
will approve it and i think others will be ok with it. [we've already discussed
this issue and came up with an agreement something like this.]
"Alastair J. Houghton" wrote:
Why is compilation of file-coding.c an option? I'd like it
to be a non-optional, for all sorts of reasons - but in
particular because my encode/decode stuff will otherwise
have to include lots of #ifdef FILE_CODING's. I also think
that it would be better to have it enabled on ordinary
UNIX XEmacs, because then UNIX people won't break DOS,
Windows or Mac text files for users of other less capable
software.
Regards,
Alastair.
____________________________________________________________
Alastair Houghton ajhoughton(a)lineone.net
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also http://www.666.com/ben/chronic-pain/