From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Grant Edwards <grant.b.edwards@gmail.com>
Cc: ecos-devel@sources.redhat.com
Subject: Re: eCos standard config for indent or astyle?
Date: Tue, 22 Mar 2011 16:56:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1103221844380.2145@sg-laptop> (raw)
In-Reply-To: <imad6q$1jg$1@dough.gmane.org>
On Tue, 22 Mar 2011, Grant Edwards wrote:
> Does anybody have a config file for either indent or astyle that will
> format source code according to eCos standards?
Hi,
They have 'Lindent'..., I thought, - Why we have not 'Eindent'? :-)
Well, I wrote *something* for myself
HG's repo https://bitbucket.org/tickling/geneindent/src
Install
sh genindent > ~/bin/Eindent
chmod +x ~/bin/Eindent
Usage (mostly in Vim on visual blocks)
:'<,'>!Eindent
Also I wrote vim.cdl (vim syntax file) to hack/check eCos config files:
HG's repo https://bitbucket.org/tickling/vim-syntax-cdl/src
HTH
Sergei
next prev parent reply other threads:[~2011-03-22 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 14:54 Grant Edwards
2011-03-22 16:56 ` Sergei Gavrikov [this message]
2011-03-22 19:00 ` Grant Edwards
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=alpine.DEB.2.00.1103221844380.2145@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@sources.redhat.com \
--cc=grant.b.edwards@gmail.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).