From: Christoph <cschol2112@googlemail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#193: Fix for bug#193.
Date: Fri, 09 Jul 2010 19:41:12 -0600 [thread overview]
Message-ID: <4C37CFB8.2020707@gmail.com> (raw)
In-Reply-To: <20100709185115.GA3036@muc.de>
Hi Alan,
On 7/9/2010 12:51 PM, Alan Mackenzie wrote:
> Hi, Deniz,
>
> On Sun, Jun 27, 2010 at 02:47:52PM +0200, Deniz Dogan wrote:
>> Did anyone ever agree on what needs to be done to fix the problem?
>
> Would you try this patch, please, and then tell me whether or not it
> works fully. Thanks!
M-q works fine for me with C as well as C++ style comments, both ways,
i.e. shorting long comments and extending short comments to fill the line.
The only "quirk" I found:
Using C-style comments, if the original comment looks like this:
/* This is a short comment
which is extended */
the resulting comment is:
/* This is a short comment which is extended */
Notice the two spaces after the last word 'extended', before the close
comment marker.
I would have expected either:
/* This is a short comment which is extended */
i.e. the whitespace of the original comment is preserved, or
/* This is a short comment which is extended */
i.e. the whitespace is zapped except one space before the close comment
marker.
This might be nitpicking but I thought I bring it up.
Christoph
next prev parent reply other threads:[~2010-07-10 1:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 21:49 Fill for // (C++) style comments in C (C99) Richard Hansen
2010-06-27 12:47 ` bug#193: Deniz Dogan
2010-07-05 20:06 ` bug#193: Alan Mackenzie
2011-03-05 20:43 ` bug#193: Glenn Morris
2010-07-06 19:29 ` bug#193: Alan Mackenzie
2010-07-06 19:29 ` bug#193: Alan Mackenzie
2010-07-09 18:51 ` bug#193: Fix for bug#193 Alan Mackenzie
2010-07-10 1:41 ` Christoph [this message]
2010-07-11 18:55 ` Alan Mackenzie
2010-07-14 1:08 ` Christoph
2010-08-06 18:59 ` Alan Mackenzie
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=4C37CFB8.2020707@gmail.com \
--to=cschol2112@googlemail.com \
--cc=bug-gnu-emacs@gnu.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 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.