Re: Coding system for outgoing mail

[Kenichi Handa]

In article <200208221941.g7MJfoo01752@localhost.localdomain>, 
konrad.hinsen@laposte.net writes:
>>  Thank you, but even with that file, I can't reproduce the bug.
>>  
>>  Is "signature-file" the actual file name?

> No, it is ".signature", but I considered it safer not to send it under
> that reserved name.

Thank you for considering that.  But, as file name sometimes
does affect how it is read, I wanted to know the exact file
name.

But, as far as seeing these values in your emacs:

>>      file-coding-system-alist
>>      auto-coding-alist
>>      auto-coding-regexp-alist

I see no reason why inserting that file makes the buffer
unibyte.  I still can't reproduce it with setting those
values exactly as yours.

You wrote:
>>  o Can you reproduce the bug when you start Emacs with "-q
>>    --no-site-file"?

> No. I went through my .emacs line by line to find out what the
> cause is, and it turns out to be the line

>    (setq mail-signature t)

> Then I disabled that line and checked what happens when I insert
> the signature by hand (C-c C-w). Before inserting the signature,
> describe-coding-system says "none, use default". After inserting
> the signature, it says "no conversion (binary)".

What happens if you insert the signature file by this?
        C-x i ~/.signature RET

And what happens if you start emacs with -q --no-site-file
and type C-c C-w to insert the signature file?

Do they also change buffer-file-coding-system?

Do they also change buffer-file-coding-system when you
insert it not in *mail* buffer, but *scratch* buffer?

And, to which function C-c C-w is bound, and in which file
that function is defined?  In my case, it is
`mail-signature' defined in lisp/mail/sendmail.el.

---
Ken'ichi HANDA
handa@etl.go.jp