Re: bug w/file-coding & processes
Darryl Okahata <darrylo(a)sr.hp.com> writes:
Unfortunately, `nil' represents the "binary" coding
system. If
`coding-system-for-read' is `undecided' when subprocess input is
read, the first few (512?) bytes are examined to determine the
This is what the Lispref says
Coding System Types
-------------------
`nil'
`autodetect'
Automatic conversion. XEmacs attempts to detect the coding system
used in the file.
So it at least used to be correct (the lispref doesn't know about
'undecided). Given that is almost the only documentation there is
about this stuff would it be possible to update the documentation
first?
Jan
BTW nil == undecided is used is used in many more places and probably
even it 3rd party code.