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 18:16:06 +0100 [thread overview]
Message-ID: <87zi6dcobt.fsf@imladris> (raw)
In-Reply-To: <b4m4lol274e.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 20 Dec 2017 16:25:37 +0900")
I think i've found a reliable way to reproduce the problem.
If i write my in-line response by opening a line in the middle of the
citacion text with a plain RET or C-o, things work as expected.
But, i i go to the middle of cited text and press M-j (i.e.,
indent-new-comment-line, which is an alias for comment-indent-new-line),
the bug is always triggered (or at least, it's been triggered for me all
the times i've tried).
Possibly telling: any line written above the point where i pressed M-j
is auto-filled correctly, and any line written below that point gets the
wrong behaviour.
Of course, the first thing comment-indent-new-line does is calling
comment-normalize-vars, so it seems Katsumi is on the right track.
BTW, after i trigger the bug in this way, setting paragraph-separate to
its previous value doesn't seem to have any effect: th problem's still
there.
Cheers,
jao
--
A man is like a fraction whose numerator is what he is and whose
denominator is what he thinks of himself. The larger the denominator,
the smaller the fraction. -Leo Tolstoy (1828-1910)
next prev parent reply other threads:[~2017-12-20 17:16 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
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 [this message]
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=87zi6dcobt.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).