From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 29767@debbugs.gnu.org
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 [thread overview]
Message-ID: <87y3lydwk6.fsf@imladris> (raw)
In-Reply-To: <b4mtvwmqknf.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 20 Dec 2017 09:59:32 +0900")
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
next prev parent reply other threads:[~2017-12-20 1:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 21:17 bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end) Jose A. Ortega Ruiz
2017-12-19 11:52 ` Michael Heerdegen
2017-12-19 16:16 ` Eli Zaretskii
2017-12-20 0:21 ` Katsumi Yamaoka
2017-12-20 0:39 ` Jose Antonio Ortega Ruiz
2017-12-20 0:59 ` Katsumi Yamaoka
2017-12-20 1:20 ` Jose A. Ortega Ruiz [this message]
2017-12-20 7:25 ` Katsumi Yamaoka
2017-12-20 17:04 ` Jose A. Ortega Ruiz
2017-12-20 17:16 ` Jose A. Ortega Ruiz
2018-01-03 16:31 ` Tomas Nordin
2018-01-04 19:52 ` Tomas Nordin
2017-12-25 14:38 ` Michael Heerdegen
2018-01-04 4:59 ` Stefan Monnier
2018-01-10 4:59 ` Katsumi Yamaoka
2018-01-11 3:32 ` Jose A. Ortega Ruiz
2018-01-11 13:41 ` Stefan Monnier
2018-01-12 3:54 ` Katsumi Yamaoka
2018-01-11 15:11 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3lydwk6.fsf@imladris \
--to=jao@gnu.org \
--cc=29767@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=yamaoka@jpl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).