From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Suggestion
Date: Wed, 14 Feb 2007 10:40:10 +0000 [thread overview]
Message-ID: <equoov$f13$1@sea.gmane.org> (raw)
In-Reply-To: dcdcb9a80702080250s416b8208ie9a817467b696d20@mail.gmail.com
> On 2/8/07, Ciaran McCreesh <ciaranm@ciaranm.org> wrote:
>> On Thu, 8 Feb 2007 10:38:08 +0100 Jose San Leandro
>> <jose.sanleandro@ventura24.es> wrote:
>> | A friend of mine and myself are willing to develop some tools to help
>> | ebuild development.
>>
>> All the common cases should be handled by default functions, package
>> manager functions and eclasses. Thus, writing ebuilds should consist
>> merely of handling unique or uncommon special cases, and the best tool
>> for doing that is an ebuild-aware text editor.
>>
Christopher Covington wrote:
> Apropos ebuild-aware text editor, has anyone written an eclipse plugin
> yet? I find that setting up ebuild as an external tool is basically
> all I need but syntax highlighting and eclass reference would make
> things prettier.
>
Personally I find kwrite or kate to be excellent. I guess kate if you want
to set up tools etc. Have looked at the bash syntax highlighting xml for
katepart in (~|/usr/share)/apps/katepart/ and it's an excellent basis. Am
hacking it now to add ebuild functions, but if anyone knows a bit more
about this (specifically writing rules) and is willing to help, please mail
me.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-14 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 9:38 [gentoo-dev] Suggestion Jose San Leandro
2007-02-08 9:43 ` Ciaran McCreesh
2007-02-08 10:50 ` Christopher Covington
2007-02-08 13:26 ` Joshua Nichols
2007-02-14 10:40 ` Steve Long [this message]
2007-02-08 10:59 ` Jose San Leandro
2007-02-08 12:39 ` Chris Gianelloni
2007-02-08 14:42 ` Luis Francisco Araujo
2007-02-08 10:40 ` Alistair Bush
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 16:44 [gentoo-dev] suggestion Andy Molloy
2002-06-19 17:59 ` [gentoo-dev] suggestion Mark Gordon
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='equoov$f13$1@sea.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--cc=gentoo-dev@lists.gentoo.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