Re: coding-system for drafts

[kai.grossjohann@uni-duisburg.de (Kai Großjohann)]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> I see.  That's a good idea.  Perhaps we can abolish the variable
> mm-auto-save-coding-system and set the default value for
> message-draft-coding-system to frumple (or iso-2022-7bit).

Yes, maybe.  Hm.  Oh, yes, new auto-saves will always have the
cookie.  So no problem.

(But what happens for XEmacsen which do not interpret the cookie?
Are there such versions?)

> Since not to bind the value for coding-system-for-read is
> required to utilize that function, what should we do if there is
> no such header?  Or isn't there nothing to do?

Binding coding-system-for-read is not good because it takes
precedence over everything else.  But if we could find a way to
specify the coding system that has LOWER precedence than the coding
cookie, then we can do that.

Maybe it works via auto-coding-alist?  No, that takes precedence.  So
we should use file-coding-system-alist.  Do you think that might work?

> In addition, it is required that the coding header should be
> untouchable by a user.  In order to ensure it, we will add the
> header using write-contents-hooks and remove it before starting
> edit of a draft.  Haven't I made a mistake in my idea?

That would work.

Another idea is to narrow the buffer so that point-min is after the
header.  But that might be more fragile.

Does auto-saving run write-contents-hooks?

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)