From: "William Xue" <william.xue@gmail.com>
To: "Alan Mackenzie" <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: redundant space after run 'c-indent-new-comment-line'
Date: Thu, 15 Feb 2007 09:51:07 +0800 [thread overview]
Message-ID: <op.tnrorhi9hkv0w5@williamnb> (raw)
In-Reply-To: <20070214234925.GA1024@muc.de>
On Thu, 15 Feb 2007 06:34:40 +0800, Alan Mackenzie <acm@muc.de> wrote:
> Hi, William!
>
> On Wed, Feb 14, 2007 at 03:24:54PM +0800, William Xue wrote:
>> First, 'M-;' make a c style comment in a new line in a .h file, it
>> prints
>> '/* */', and the cursor blinks at the 2nd space char.
>
> Yes. This is the place where you'll be wanting to start typing.
>
>> Then, 'M-J' to run 'c-indent-new-comment-line', and it gives
>> '/*
>> * */' and the cursor blinks at the last '*', but I think it should be
>> blinks at the 2nd space in the second line.
>
> More precisely, you get this (but not in gnu style - use C-. k&r first to
> see this):
>
> /*
> * */
> ^
> |
> point
>
> What you are saying, it I understand you correctly, is that you should
> see this:
>
> /*
> * */
> ^
> |
> point
Yes, that is what I want.
>
> I agree with you. It's a bug.
>
>> Please point out if I am wrong or have missed something.
>
> c-indent-new-comment-line is a rat's nest of special cases. Invoking it
> when there's no text inside the "/* */" needs special handling.
>
> I'll fix it.
Thank you!
>
>> Thanks!
>
> Thank you!
>
>> --
>> Sincerely yours,
>> William
>
--
Sincerely yours,
William
next prev parent reply other threads:[~2007-02-15 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 7:24 redundant space after run 'c-indent-new-comment-line' William Xue
2007-02-14 22:34 ` Alan Mackenzie
2007-02-15 1:51 ` William Xue [this message]
2007-02-15 15:18 ` Stefan Monnier
2007-02-15 19:34 ` Alan Mackenzie
2007-02-16 1:53 ` William Xue
2007-02-15 22:37 ` Alan Mackenzie
2007-02-16 2:37 ` William Xue
2007-02-16 7:16 ` Alan Mackenzie
2007-02-16 17:51 ` William Xue
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=op.tnrorhi9hkv0w5@williamnb \
--to=william.xue@gmail.com \
--cc=acm@muc.de \
--cc=emacs-devel@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 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).