unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "William M. (Mike) Miller" <william.m.miller@gmail.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: c-fill-paragraph closing comment delimiter, emacs 23.4.1
Date: Wed, 18 Jul 2012 09:42:07 -0400	[thread overview]
Message-ID: <CAH5rLZWorgatYDu4t_eJAypuhSX-x9cJnPMr26kHVCWVO1aK3Q@mail.gmail.com> (raw)
In-Reply-To: <5006B68D.6090301@easy-emacs.de>

On Wed, Jul 18, 2012 at 9:13 AM, Andreas Röhler
<andreas.roehler@easy-emacs.de> wrote:
> Am 17.07.2012 14:39, schrieb William M. (Mike) Miller:
>
>> The behavior of c-fill-paragraph with regard to the closing delimiter of
>> the
>> paragraph has changed in version 23.4.1 from that of version 21.2.1.  My
>> company has a coding standard that begins each C function with a
>> comment of the form
>>
>> /*
>> Description...
>> */
>>
>> In version 23.4.1, running c-fill-paragraph (M-q) with the point in such a
>> comment moves the closing delimiter onto the last line of the description,
>> e.g.,
>>
>> /*
>> Description... */
>>
>> Version 21.2.1 respected the placement of the closing delimiter on a line
>> by itself.
>>
>> Is there a setting I can use to force version 23.4.1 not to wrap the
>> closing
>> delimiter onto the last line of the comment text?
>>
>
> AFAIK it's developed here:
>
> cc-mode-help@lists.sourceforge.net

Thanks; I hadn't realized that there was a more-specific mailing list for
this.  I'll post there.

-- 
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com



  reply	other threads:[~2012-07-18 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 12:39 c-fill-paragraph closing comment delimiter, emacs 23.4.1 William M. (Mike) Miller
2012-07-18 13:13 ` Andreas Röhler
2012-07-18 13:42   ` William M. (Mike) Miller [this message]
2012-07-18 21:03 ` William M. (Mike) Miller
     [not found] ` <mailman.5109.1342645433.855.help-gnu-emacs@gnu.org>
2012-07-19  5:39   ` Jason Rumney

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=CAH5rLZWorgatYDu4t_eJAypuhSX-x9cJnPMr26kHVCWVO1aK3Q@mail.gmail.com \
    --to=william.m.miller@gmail.com \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=help-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.
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).