[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Inconsistencies regarding nil coding-system
From: |
Eli Zaretskii |
Subject: |
Inconsistencies regarding nil coding-system |
Date: |
Sat, 11 Dec 2010 12:33:06 +0200 |
(coding-system-change-eol-conversion nil 'unix) => nil
(coding-system-change-text-conversion 'latin-1-dos nil) => undecided-dos
(coding-system-base nil) => no-conversion
When primitives that encode/decode text accept nil as their
coding-system argument, they use `undecided' (AFAIK). So the second
result above looks reasonable, but the first and the last are
inconsistent, and the last one is downright surprising.
Any reasons not to change coding-system-change-eol-conversion and
coding-system-base to consistently treat nil as `undecided'? (If
agreed to, I suggest to make this change only on the trunk, not on the
release branch.)
- Inconsistencies regarding nil coding-system, Eli Zaretskii, 2010/12/11
- Inconsistencies regarding nil coding-system,
Eli Zaretskii <=
- Re: Inconsistencies regarding nil coding-system, Kenichi Handa, 2010/12/13
- Re: Inconsistencies regarding nil coding-system, Eli Zaretskii, 2010/12/13
- Re: Inconsistencies regarding nil coding-system, Kenichi Handa, 2010/12/13
- Re: Inconsistencies regarding nil coding-system, Eli Zaretskii, 2010/12/13
- Re: Inconsistencies regarding nil coding-system, Kenichi Handa, 2010/12/13
- Re: Inconsistencies regarding nil coding-system, Kenichi Handa, 2010/12/14
- Re: Inconsistencies regarding nil coding-system, Eli Zaretskii, 2010/12/14
- Re: Inconsistencies regarding nil coding-system, Kenichi Handa, 2010/12/14