On Wed, 7 May 2008, Eric Belanger wrote:
On Wed, 7 May 2008, Aaron Griffin wrote:
On Wed, May 7, 2008 at 11:32 AM, Aaron Griffin <[EMAIL PROTECTED]>
wrote:
On Mon, May 5, 2008 at 9:22 PM, Eric Belanger
<[EMAIL PROTECTED]> wrote:
> From what I understood from the man page (and have experienced) we
can't
> create a new enscript file. I guess they are hardcoded in the code or
set at
> build time. Anyway, we can modified the bash.st file. Here's my quick
hack
> to have colored keywords. Compare:
Really? I assumed enscript.st did the matching. I am attempting to
copy your bash changes into a new PKGBUILD.st file, and fiddle with
it.
We will see.
Hah, look what I did: http://dev.archlinux.org/~aaron/PKGBUILD.st
I totally guessed at the "extends" part and then just deleted. This is
all from your original enscript file.
And it's also live, so hooray.
Congrats for figuring it out.
BTW, the only hash sums that will be colored are md5sums and sha1sums. I
haven't bothered adding the other ones to the list as no one uses them yet
AFAIK. It might be a good idea to add them too.
You need to add a pipe after makedepends and noextract otherwise they
don't get colored, i.e. :
/**
* Name: PKGBUILD
* Description: PKGBUILD syntax for Archlinux
*/
state PKGBUILD extends bash
{
/* PKGBUILD Keywords */
/\b(pkg(name|ver|rel|desc)|arch|license|depends|makedepends|
|url|groups|options|install|md5sums|sha1sums|startdir|noextract|
|backup|optdepends|conflicts|provides|replaces)\b/
{
builtin_face (true);
language_print ($0);
builtin_face (false);
}
}
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
