[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad sta
From: |
Jose A. Ortega Ruiz |
Subject: |
bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end) |
Date: |
Wed, 20 Dec 2017 02:20:41 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) |
On Wed, Dec 20 2017, Katsumi Yamaoka wrote:
> On Wed, 20 Dec 2017 01:39:35 +0100, Jose Antonio Ortega Ruiz wrote:
>> not for me. i am answering here with a long line, and the two quoted
>> lines above don't trigger the bug on my side. here you see the lines
>> that was auto-filled without any extra >.
>
>> i've also seen the bug triggered many times below cited lines with a
>> single >.
>
> Confirmed. This causes the bug for me (note that the cite prefix
> should be ">", not "> ").
>
>>The quick brown fox jumps over the lazy dog.
>>The quick brown fox jumps over the lazy dog.
> A l o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
> o o o o o o o o o o o o o o o o o n g line.
Let me try: i'm copying below the two lines quoted above with a single >
and no spaces:
>The quick brown fox jumps over the lazy dog.
>The quick brown fox jumps over the lazy dog.
and now here's a l o o o o o o o o o o o o o o o o o o o o o o o o o o o
o o o o o ng line... which i am afraid got auto-filled without
trigerring the bug... so i guess we must be doing something different,
but i don't see what.
as i mentioned in my original report, this bug is annoying in that i can
paste the exact content of a buffer where it's happening into a second
one in message mode, and the bug won't be triggered in the second
buffer, so it seems to very sensitive to context.
anyway, Katsumi, since you have a couple of cases where it's happening
for you, perhaps you could answer Eli's question and tell him what's the
output of C-h l when you manage to reproduce it?
thanks!
jao
--
A lot of people have my books on their bookshelves.
That's the problem, they need to read them. -- Don Knuth
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Jose A. Ortega Ruiz, 2017/12/18
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Michael Heerdegen, 2017/12/19
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Eli Zaretskii, 2017/12/19
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Katsumi Yamaoka, 2017/12/19
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Jose Antonio Ortega Ruiz, 2017/12/19
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Katsumi Yamaoka, 2017/12/19
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end),
Jose A. Ortega Ruiz <=
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Katsumi Yamaoka, 2017/12/20
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Jose A. Ortega Ruiz, 2017/12/20
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Jose A. Ortega Ruiz, 2017/12/20
- bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end), Michael Heerdegen, 2017/12/25