From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] vim syntaxy goodness for ebuilds, eclasses, GLEPs
Date: Thu, 26 Aug 2004 19:53:37 +0100 [thread overview]
Message-ID: <20040826195337.5dd3b570@snowdrop.home> (raw)
In-Reply-To: <20040820205106.64598921@snowdrop.home>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
On Fri, 20 Aug 2004 20:51:06 +0100 I wrote:
| http://dev.gentoo.org/~ciaranm/overlay/app-vim/gentoo-syntax/
A much improved updated version is now in the main tree. I strongly
suggest that anyone using vim to edit portagey things gives it a go. As
well as giving you better syntax highlighting for ebuild keywords, it'll
pick up certain mistakes and make them really stand out:
http://dev.gentoo.org/~ciaranm/tmp/gentoo-syntax.png
Suggestions, patches, etc welcomed. Smartarse remarks about emacs or
nano will lead to a smiting.
The following still applies if you've got a not-so-recent vim-core:
| 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.)
--
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 --]
next prev parent reply other threads:[~2004-08-26 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 19:51 [gentoo-dev] vim syntaxy goodness for ebuilds, eclasses, GLEPs Ciaran McCreesh
2004-08-26 18:53 ` Ciaran McCreesh [this message]
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=20040826195337.5dd3b570@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