From: Nikolaj Schumacher <me@nschum.de>
To: Rodrigo Canellas <rodrigo.canellas@tqtvd.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: no identation after 'namespace {'
Date: Tue, 07 Oct 2008 22:36:07 +0200 [thread overview]
Message-ID: <m23aj8m9c8.fsf@nschum.de> (raw)
In-Reply-To: <48EBB998.8070507@tqtvd.com> (Rodrigo Canellas's message of "Tue\, 07 Oct 2008 16\:33\:44 -0300")
Rodrigo Canellas <rodrigo.canellas@tqtvd.com> wrote:
> I would like that after a 'namespace {' C-j, the code would not be indented,
> even if I press C-i, or type, for instance, 'class a {'.
Customize `c-offsets-alist'. Set innamespace to 0.
You con also configure several coding styles with `c-add-style' if you
want to toggle the behavior.
regards,
Nikolaj Schumacher
prev parent reply other threads:[~2008-10-07 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 19:33 no identation after 'namespace {' Rodrigo Canellas
2008-10-07 20:36 ` Nikolaj Schumacher [this message]
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=m23aj8m9c8.fsf@nschum.de \
--to=me@nschum.de \
--cc=help-gnu-emacs@gnu.org \
--cc=rodrigo.canellas@tqtvd.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.
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).