From: Ergus <spacibba@aol.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: C style alist question?
Date: Thu, 11 Apr 2019 17:00:47 +0200 [thread overview]
Message-ID: <20190411150047.s6cs3ajq5h2cvxdj@Ergus> (raw)
In-Reply-To: <83v9zk4o6l.fsf@gnu.org>
On Thu, Apr 11, 2019 at 05:22:10PM +0300, Eli Zaretskii wrote:
>> Date: Thu, 11 Apr 2019 03:16:59 +0200
>> From: Ergus <spacibba@aol.com>
>> Cc: help-gnu-emacs@gnu.org
>>
>> But other common policies around are:
>>
>> 1) add only tabs (and ignore the small mismatch in some cases)
>>
>> int function(int var1,
>> ------->double b,
>> ------->double c)
>> {
>> ------->for (int i = 0; i < 10; ++i)
>> ------->------->myprintf ("%d\n",
>> ------->------->------->i);
>> }
>
>AFAIU, this is the 'linux' style in CC Mode.
No, the linux style is the first example I inserted in my mail. With
some spaces to align. Like this (or at least this is what I get)
int function(int var1,
------->.....double b,
------->.....double c)
{
------->for (int i = 0; i < 10; ++i)
------->------->myprintf ("%d\n",
------->------->------->..i);
}
The indent-tabs-mode inserts "as many tabs as possible" and then aligns
with spaces.
>
>> 2) Use tabs (but only for indentation) and spaces to align
>>
>> int function(int var1,
>> .............double b)
>> {
>> ------->for (int i = 0; i < 10; ++i)
>> ------->------->myprintf ("%d\n",
>> ------->------->..........i);
>> }
>
>And this is the 'bsd' style.
>
bsd style defines 4 spaces after tabulator align for continuation lines,
not alineation with spaces.
>Can you use these built-in styles to get what you want? Or did I
>misunderstand what you are looking for?
According with Alan's mail the policy is not included and it needs a
workaround he sent in his email as an answer to a mail from 2008.
prev parent reply other threads:[~2019-04-11 15:00 UTC|newest]
Thread overview: 7+ 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
2019-04-11 14:22 ` Eli Zaretskii
2019-04-11 15:00 ` Ergus [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190411150047.s6cs3ajq5h2cvxdj@Ergus \
--to=spacibba@aol.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.