From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 29767@debbugs.gnu.org, jao@gnu.org
Subject: bug#29767: 26.0.90; Failing auto-fill in message-mode because of bad state (comment-skip-end)
Date: Tue, 19 Dec 2017 18:16:23 +0200 [thread overview]
Message-ID: <838tdypuaw.fsf@gnu.org> (raw)
In-Reply-To: <87shc7rl35.fsf@web.de> (message from Michael Heerdegen on Tue, 19 Dec 2017 12:52:30 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Tue, 19 Dec 2017 12:52:30 +0100
> Cc: 29767@debbugs.gnu.org
>
> "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
>
> > - sometimes, when composing a reply to an email in gnus (major mode is
> > message-mode there, auto-fill-mode is enabled), when a line is
> > auto-filled and broken in two, do-auto-fill incorrectly thinks that
> > it is inside a comment and adds a `> ' prefix to it.
>
> This has bugged me for a long time. I also don't have a recipe, the
> issue has a Heisenbug-like behavior. But it happens quite often - it
> > even happens right now, I didn't comment this line.
What does "C-h l" show immediately after this happens?
next prev parent reply other threads:[~2017-12-19 16: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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838tdypuaw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29767@debbugs.gnu.org \
--cc=jao@gnu.org \
--cc=michael_heerdegen@web.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.