From: Leo <sdl.web@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 11165@debbugs.gnu.org
Subject: bug#11165: 24.0.95; c-indent-new-comment-line bug or feature?
Date: Thu, 17 May 2012 15:19:56 +0800 [thread overview]
Message-ID: <m1txzfnujn.fsf@gmail.com> (raw)
In-Reply-To: <20120515165038.GB20152@acm.acm> (Alan Mackenzie's message of "Tue, 15 May 2012 16:50:39 +0000")
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
On 2012-05-16 00:50 +0800, Alan Mackenzie wrote:
> I don't think this is a bug. When you've read that manual page, would
> you please check exactly what you've done, and whether your buffer
> indents as we both would like.
I have read the manual before and I just read it again. Here is a
detailed recipe to reproduce:
1. Emacs -q
2. Make a new buffer named BUG and enable c-mode in it
3. C-c C-o and customise syntactic 'c' to 4 in BUG buffer
4. Now typing in the BUG buffer slash star /*, then press M-j
5. type TAB to indent
In step 4 the buffer looks like:
[-- Attachment #2: bug1.png --]
[-- Type: image/png, Size: 8322 bytes --]
[-- Attachment #3: Type: text/plain, Size: 34 bytes --]
In step 5 the buffer looks like:
[-- Attachment #4: bug2.png --]
[-- Type: image/png, Size: 8301 bytes --]
[-- Attachment #5: Type: text/plain, Size: 73 bytes --]
The bug is M-j (c-indent-new-comment-line) indents to the wrong column.
next prev parent reply other threads:[~2012-05-17 7:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 18:30 bug#11165: 24.0.95; c-indent-new-comment-line bug or feature? Leo
2012-04-17 10:53 ` Alan Mackenzie
2012-04-17 13:57 ` Leo
2012-05-15 16:50 ` Alan Mackenzie
2012-05-17 7:19 ` Leo [this message]
2012-05-17 10:12 ` Alan Mackenzie
2019-10-25 20:34 ` Alan Mackenzie
2019-10-26 13:08 ` Leo Liu
[not found] ` <20191025203405.GA24064@ACM>
2019-10-26 17:08 ` Glenn Morris
2019-10-27 11:32 ` Alan Mackenzie
2019-11-06 16:43 ` Glenn Morris
[not found] ` <dpv9rxez0a.fsf@fencepost.gnu.org>
2019-11-06 20:33 ` 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=m1txzfnujn.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=11165@debbugs.gnu.org \
--cc=acm@muc.de \
/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.