all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jeff Norden <norden.jeff@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, 64133@debbugs.gnu.org
Subject: bug#64133: CC Mode 5.35.2 (C/*l); incorrect indentation for an arrays of structs.
Date: Sat, 17 Jun 2023 12:36:30 -0500	[thread overview]
Message-ID: <CAPbFCnkW+HJNTEnwTtHG_VXZsUQufrJQoN==KY5ZgRpaqaUXZA@mail.gmail.com> (raw)
In-Reply-To: <83y1kioxzv.fsf@gnu.org>

On Sat, Jun 17, 2023 at 11:27 AM Eli Zaretskii <eliz@gnu.org> wrote:
> Thanks, I will let Alan chime in and decide whether this should be
> closed.
Actually, I now think that changing the style works because the gnu
style has
  (substatement-open . +)
in c-offsets-alist, while linux uses (substatement-open . 0).  With
either style, I initially get substatemnt syntax from "C-c C-s", which
changes to brace-list when I delete space and re-indent.

This issue *doesn't* occur if the opening brace is on its own line,
and it looks like most styles other than gnu do not indent
sub-statements.  So, I still think this bug can be closed, but maybe
the resolution could be "mostly harmless" :-).





  reply	other threads:[~2023-06-17 17:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17 15:03 bug#64133: CC Mode 5.35.2 (C/*l); incorrect indentation for an arrays of structs Jeff Norden
2023-06-17 15:14 ` Eli Zaretskii
     [not found]   ` <CAPbFCnniiTyPQBmayZpRwS46--JW6ipmmLAzMterB5cK9NEXCA@mail.gmail.com>
2023-06-17 16:27     ` Eli Zaretskii
2023-06-17 17:36       ` Jeff Norden [this message]
2023-06-18 13:13         ` Alan Mackenzie
2023-06-18 16:10           ` Jeff Norden
2023-06-18 17:23           ` Jeff Norden
2023-06-19 11:46             ` Alan Mackenzie
2023-06-19 14:30               ` Jeff Norden
2023-06-21 10:39               ` Alan Mackenzie
2023-06-21 18:43                 ` Jeff Norden
2023-06-27 20:19                   ` 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='CAPbFCnkW+HJNTEnwTtHG_VXZsUQufrJQoN==KY5ZgRpaqaUXZA@mail.gmail.com' \
    --to=norden.jeff@gmail.com \
    --cc=64133@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@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.