From: Alan Mackenzie <acm@muc.de>
To: Ergus <spacibba@aol.com>
Cc: help-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: C style alist question?
Date: Thu, 11 Apr 2019 08:28:06 +0000 [thread overview]
Message-ID: <20190411082806.GA4093@ACM> (raw)
In-Reply-To: <20190411011659.zplon3n3lrtqmb2i@Ergus>
Hello, Ergus.
On Thu, Apr 11, 2019 at 03:16:59 +0200, Ergus wrote:
> (I send to both mailing lists because it is related with a previous
> thread, but the right destination for this mail is the devels mailing
> list)
> Hi guys:
> The issue I was facing with indentations was related actually with the
> fact that once an offset is set (for example in the init file) it is
> ignored in some cases by c-set-style because it is not "from style"
> anymore.
The answer here is Read The Fantastic Manual. :-) In particular, the
CC Mode manual, page "Config Basics", explains how settings made in
different ways get resolved, and which one "wins".
> Does it makes sense (or is not too difficult) to provide an option (or a
> parameter in c-set-style) that allows the user to overwrite all the
> previous offsets with the values from the new style, in spite of if it
> is not "from style"? Maybe it already exist?
The thinking is that users, mostly, will be using the style system, or
possibly setting buffer local values in hooks (e.g. c-mode-common-hook).
And that anybody setting the global value of a style variable Really
Means It.
To supply the option you're suggesting would be quite difficult, yes,
since it would mean rethinking the entire way CC Mode handles the style
variables. To the five ways of setting style variables listed on that
manual page, could (should) be added the directory local settings. The
interaction between them all is quite involved.
I would ask you to read that manual page thoroughly, and see if it
provides you with a way to configure CC Mode adequate to your needs. If
not, then maybe we could come back to the question.
> Another question:
[ For another reply :-]
> Thanks in advance,
> Ergus.
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2019-04-11 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 3:26 C style alist question? Ergus
2019-04-06 4:10 ` Óscar Fuentes
2019-04-06 6:48 ` Eli Zaretskii
2019-04-11 1:16 ` Ergus
2019-04-11 8:28 ` Alan Mackenzie [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=20190411082806.GA4093@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=spacibba@aol.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).