Re: Horrible term-mode problems on upgrade to 21.4
On 13 May 2001, Hrvoje Niksic gibbered:
Nix <$}xinix{$(a)esperi.demon.co.uk> writes:
> What is *not* correct is XEmacs picking up on the CR/LFs and translating
> them to LFs!
Thanks for the analysis. I've successfully repeated the bug in my
Mule-enabled XEmacs, and I see the same problem.
Good, it's not my bizarre roll-yer-own Linux install that's breaking it
then. (That's rare. ;) )
(set-buffer-process-coding-system 'binary 'binary))
Great, that's gone into the term-exec-hook in the site-start here, and
my users are happy (and impressed by the speed of the response :) )
> I'd fix term-mode, if it wasn't that setting the
> `buffer-file-coding-system' to `no-conversion'
That's because `no-conversion' actually means "no charset
conversion". Line endings still get converted. (Yes, it's
Ah.
confusing. It will probably be changed in one of the future
releases.)
I dunno, it makes a kind of sense; the line ending conversion is in a
different dimension to the charset conversion (LF / CRLF / CR, versus
ISO-foo / KOI8-R / US-ASCII / who-knows-what)...
--
`LARTing lusers is supposed to be satisfying. This is just tedious. The
silly shite I'm doing now is like trying to toothpick to death a Black
Knight made of jelly.' --- RDD