Re: coding-system for drafts

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

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> In <84znsv52f5.fsf@crybaby.uni-duisburg.de>
>>>>>>	kai.grossjohann@uni-duisburg.de (Kai Großjohann) wrote:
>
> I've confirmed that the following example works:
>
> (let ((file-coding-system-alist
>        (cons
> 	(cons (concat "\\`"
> 		      (regexp-quote (expand-file-name FILE))
> 		      "\\'")
> 	      'frumple)
> 	file-coding-system-alist))
>       (nnmail-file-coding-system nil))
>   (nnmail-find-file (expand-file-name FILE)))
>
> We can also set the value for file-coding-system-alist rigidly.
> However, I get confused.  Isn't there any difference in this and
> the next example?
>
> (let ((nnmail-file-coding-system 'frumple))
>   (nnmail-find-file (expand-file-name FILE)))

I would guess they are the same.

>> Another idea is to narrow the buffer so that point-min is after the
>> header.  But that might be more fragile.
>
> Hm, each is hard to be called good idea.  The hidden area might
> be exposed in the future like message-strip-forbidden-properties
> does.

Narrowing does not use text properties.  But maybe one of the (widen)
statements in message.el breaks things.

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