bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end)

[Jose A. Ortega Ruiz]

On Wed, Dec 20 2017, Katsumi Yamaoka wrote:

> Hi Jose,
>
> On Wed, 20 Dec 2017 02:20:41 +0100, Jose A. Ortega Ruiz wrote:
>> so i guess we must be doing something different,
>
> Well, does evaluating this snippet in the message-mode buffer
> fix your problem?
>
> (setq paragraph-separate (default-value 'paragraph-separate))
> ...[1]

okay, i will absolutely try the next time the bug is triggered by some
mail... so far, this one is working fine :)

> As for me, I found the cause is that message-mode modifies its
> value in a message-mode buffer locally so as to have the value
> of `message-cite-prefix-regexp' (containing ">", etc.).  It makes
> the paragraph commands, `M-{', `M-}', etc. work conveniently in
> the message-mode.  However, it also seems to affect the auto-fill
> command undesirably.  A patch is below.

in my case, the value of message-cite-prefix-regexp does not coincide
with that of paragraph-separate (the latter is much longer, and includes
also things like header and multipart separators) ... but then, i'm
checking these variables in *this* buffer, in which the problem is not
happening...).

> But if [1] does not fix your problem, try evaluating the next
> one before composing a message-mode buffer:
>
> (fset 'message-setup-fill-variables 'ignore)
> ...[2]
>
> If it does the trick, a cause should be something done in the
> `message-setup-fill-variables' function.

yes, that was also the function that i was suspecting, although i got
> the impression ...

ah! here we have the problem happening.  i've set paragraph-separate to
> the suggested value, but that isn't fixing the problem either, as you
> can see...

jao
-- 
If all else fails read the instructions. - Donald Knuth