From: Bruce Korb <bkorb@gnu.org>
To: 20778@debbugs.gnu.org
Subject: bug#20778: Flush left indentation in c-mode
Date: Tue, 09 Jun 2015 09:49:15 -0700 [thread overview]
Message-ID: <5577190B.4000003@gnu.org> (raw)
With the patched cc-mode, I ran into this situation again.
It seems to think that the flush-left alignment of the "if" statement is fine.
The rest of the code indents as you see here. Reloading cc-mode does no
good, it leaves the statement flush left. Closing and re-visiting the file
cleans up the confusion and re-indents correctly.
I do not know what you can do about it without better information from me,
but I don't know what to tell you either. :( Oh, the "c-file-style" is "linux".
> void ftl_ns_print(void)
> {
> #if MAX_EVENT_EVT_PRIORITY >= LOG_DEBUG
> int skip_ct = 0;
>
> for (int i = 0; i < s_ns_table.nst_count; i++) {
> struct ftl_ns_t * const ns_p = &s_ns_table.nst_ns_list[i];
>
> if (ns_p->active_ns_id == NS_ID_NULL) {
> skip_ct++;
> continue;
> }
>
> EMIT_PRINT_NS_EVENT(
> debug, "ns_id=%d, flags=%u, active_ns_id=%d, parent_ns_id=%d, next_snapshot_ns_id=%d, "
> "snapshot_sn=%u, size_byte=%lu, used_bytes=%lu, physical_used_bytes=%lu, max_lpn=%lu, "
> "creation_io_id=%lu, snapshot_sn_seq=%u\n",
> sint32, ns_p->ns_id,
> uint32, ns_p->flags,
> sint32, ns_p->active_ns_id,
> sint32, ns_p->parent_ns_id,
> sint32, ns_p->next_snapshot_ns_id,
> uint32, ns_p->snapshot_sn,
> uint64, ns_p->size_bytes,
> uint64, ns_p->used_bytes,
> uint64, ns_p->physical_used_bytes,
> uint64, ns_p->max_lpn,
> uint64, ns_p->creation_io_id,
> uint32, ns_p->snapshot_sn_seq
> );
> }
>
> if (skip_ct > 0)
> EMIT_SKIPPED_NS_EVENT(debug, "skipped %d empty name spaces", sint32, skip_ct);
> #endif
> }
next reply other threads:[~2015-06-09 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 16:49 Bruce Korb [this message]
[not found] ` <mailman.4701.1433868613.904.bug-gnu-emacs@gnu.org>
2015-06-10 11:00 ` bug#20778: Flush left indentation in c-mode Alan Mackenzie
2015-06-12 14:55 ` Bruce Korb
2015-06-26 21:24 ` Bruce Korb
2021-08-16 13:05 ` Lars Ingebrigtsen
2021-09-14 10:54 ` Lars Ingebrigtsen
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=5577190B.4000003@gnu.org \
--to=bkorb@gnu.org \
--cc=20778@debbugs.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.