Re: mbox coding system?
Andy Piper <andy(a)xemacs.org> writes:
At 09:44 AM 4/18/00 +0200, Hrvoje Niksic wrote:
>When I try to C-x C-f my system mailbox (for inspection purposes,
>thanks for asking), I get this error:
>
> Signaling: (wrong-number-of-arguments convert-mbox-coding-system 2)
> signal(wrong-number-of-arguments (convert-mbox-coding-system 2))
> byte-code("..." [kill-buffer buf signal data] 3)
> find-file-noselect("/var/spool/mail/hniksic")
> find-file("/var/spool/mail/hniksic" nil)
> call-interactively(find-file)
>
>WTF?
This looks suspiciously like the buffer tabs / progress gauge. No
idea why.
It's not. I've now looked at it, and I'm amazed at the bogosity of
the code that actually causes the trouble.
What it tries to do is, take a look at each separate message in a
mailbox, and charset-decode it. Does it look at MIME headers? No.
Does it do anything useful? Of course not. Is it enabled ("rammed
down my indignant, bleating throat") by default? But of course!
Everyone repeat after me: mailboxes are *text files*. If they need
decoding, it will be done by the thingies called "mail readers". It's
one of those "don't try this at home" things.
Patch that eradicates the misfeature will follow shortly.