From: ERDI Gergo <cactus@cactus.rulez.org>
Subject: Re: cc-mode: Reverting to the 'dumber' indentation of nested function calls, as seen in Emacs20
Date: Tue, 11 Nov 2003 17:30:37 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0311111728380.6320-100000@panda.inf.elte.hu> (raw)
In-Reply-To: <3FB01A8B.6060304@yahoo.com>
On Mon, 10 Nov 2003, Kevin Rodgers wrote:
> ERDI Gergo wrote:
>
> > So, who's inserting all those '$'s and how do I get rid of it?
>
> Did you follow the instructions in the Interactive Customization section
> of the CC Mode manual?
Yes, but like I said, I still have no idea where the 'smart' indentation
comes from. C-c C-s in the second line tells me it's in arglist-intro, but
the value of arglist-intro only determines the '#' in the above example,
and not the '$' part.
next prev parent reply other threads:[~2003-11-11 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.112.1068494680.2005.help-gnu-emacs@gnu.org>
2003-11-10 23:08 ` cc-mode: Reverting to the 'dumber' indentation of nested function calls, as seen in Emacs20 Kevin Rodgers
2003-11-11 16:30 ` ERDI Gergo [this message]
2003-12-07 17:01 ` Kai Grossjohann
2003-11-10 19:00 ERDI Gergo
2003-11-13 19:33 ` ERDI Gergo
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=Pine.LNX.4.44.0311111728380.6320-100000@panda.inf.elte.hu \
--to=cactus@cactus.rulez.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.
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).