From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: 2929@emacsbugs.donarmstrong.com, Tassilo Horn <tassilo@member.fsf.org>
Subject: bug#2929: 23.0.92; Broken auto-filling in message-mode
Date: Fri, 10 Apr 2009 13:45:40 -0400 [thread overview]
Message-ID: <jwvk55s4d7j.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <q6prflps5w.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 09 Apr 2009 15:02:03 -0400")
> I'm not sure newcomment.el can be blamed much for this.
It can.
> The buffer has:
> comment-start = "> "
> comment-end = "*/"
> The comment-end string never appears in the example buffer, but the
> comment-start one does. So it looks to newcomment like the whole
> buffer is one big comment.
Yes, if we consider a C file with the following content:
/* blablabla
blablabla
blablabla long line to cut here
it's better for auto-fill-mdoe to do:
/* blablabla
blablabla
blablabla long line to cut
here
then
/* blablabla
blablabla
blablabla long line to cut /*
/* here
since the comment is obviously not using a "one comment per line"
style anyway. That's why I said:
>> "*/\n> " should not be added to lines which don't start with "> ".
-- Stefan
next prev parent reply other threads:[~2009-04-10 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 10:06 bug#2929: 23.0.92; Broken auto-filling in message-mode Tassilo Horn
2009-04-08 13:37 ` Stefan Monnier
2009-04-08 15:21 ` Tassilo Horn
2009-04-09 19:02 ` Glenn Morris
2009-04-10 17:45 ` Stefan Monnier [this message]
2021-12-04 21:18 ` bug#2929: filling of multi-line comments Lars Ingebrigtsen
2021-12-04 21:37 ` Tassilo Horn
2021-12-04 21:48 ` Lars Ingebrigtsen
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=jwvk55s4d7j.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=2929@emacsbugs.donarmstrong.com \
--cc=rgm@gnu.org \
--cc=tassilo@member.fsf.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).