From: Alan Mackenzie <acm@muc.de>
To: William Xue <william.xue@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: redundant space after run 'c-indent-new-comment-line'
Date: 16 Feb 2007 08:16:46 +0100 [thread overview]
Message-ID: <20070216083132.GA1086@muc.de> (raw)
In-Reply-To: <op.tntlj5dkhkv0w5@williamnb>
On Fri, Feb 16, 2007 at 10:37:07AM +0800, William Xue wrote:
> On Fri, 16 Feb 2007 06:37:34 +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.
> >>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.
> >I think the essence of this bug is that point ends up further to the
> >right after the M-j that where it started. An M-j should NEVER do this -
> >normally, of course, point ends up at the far left, just after the
> >comment prefix.
> >I've committed a fix to ..../progmodes/cc-cmds.el. Could you update your
> >Emacs and try it out, please.
> It seems not to work, even start emacs with -Q.
> When did you commit the fix? I made a update about 12 hours ago and now
> there is nothing newer.
Revision 1.54 of .../progmodes/cc-cmds.el, about 8 hours ago, at ~22:30
GMT. I've just had a look at http://savannah.gnu.org, and it's
definitely there now.
> William
--
Alan.
next prev parent reply other threads:[~2007-02-16 7:16 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070216083132.GA1086@muc.de \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=william.xue@gmail.com \
/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.