public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] vim syntaxy goodness for ebuilds, eclasses, GLEPs
Date: Fri, 20 Aug 2004 20:51:06 +0100	[thread overview]
Message-ID: <20040820205106.64598921@snowdrop.home> (raw)

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

If anyone brave would like to play around with improved syntax
highlighting for ebuilds, eclasses and GLEP documents (and at some point
in the future when I figure them out, Gentoo style ChangeLogs)...

http://dev.gentoo.org/~ciaranm/overlay/app-vim/gentoo-syntax/

Chances are you'll have to re-emerge vim-core, etc-update and accept the
changes to /etc/vim/vimrc before these will actually work. (For those
who care, using set filetype= in a global configuration file is a bad
idea, since it can't be overridden from plugins... Using setfiletype is
the correct way to do things.)

The ebuild/eclass syntax file should be fairly clean, the GLEP one is a
mess and rather incomplete since vim doesn't particularly like that kind
of syntax... Patches encouraged.

-- 
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-08-20 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 19:51 Ciaran McCreesh [this message]
2004-08-26 18:53 ` [gentoo-dev] vim syntaxy goodness for ebuilds, eclasses, GLEPs Ciaran McCreesh
2004-08-26 22:19   ` purslow
2004-08-26 22:36     ` Ciaran McCreesh
2004-08-27  1:22       ` purslow
2004-08-27  1:30         ` Jon Portnoy
2004-09-02  0:03   ` [gentoo-dev] vim syntaxy goodness for ebuilds, eclasses, GLEPs, ChangeLogs Ciaran McCreesh

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=20040820205106.64598921@snowdrop.home \
    --to=ciaranm@gentoo.org \
    --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