AutoHotkey Community

[savage]

Yes, I've finally cracked the mysteries of the VIM syntax file, and here are the results. It uses regex for nearly all of the matching, so let me know if I goofed somewhere because I based it off of my coding style. The only problem that I can foresee is that it won't match most function calls if you don't put in the first comma like I do.

On the other hand, the regex matching removes the need to parse the syntax files, so this ought to be alright until major syntax changes occur. Just drop this (make sure it's called ahk.vim) file in your $VIM/syntax directory and follow the instructions at the top to make it turn on automagically.a

[Chris]

Thanks for providing this. I will include it in the next release in the following path:

\Extras\Editors\Vim\ahk.vim

I've altered the "usage" section inside the file as follows:
"Usage:
"1) Copy this file into your $VIM/syntax directory.
"2) Add this line to filetype.vim:
"au BufNewFile,BufRead *.ahk setf ahk

If you would like your name or any contact details added to the file header, I'd be happy to do so.

Thanks!

[Atomhrt]

Sweet!! Thanks savage!
_________________
I am he of whom he speaks!

[savage]

Yeah chris, go ahead and add my email - kallen19918 at earthlink dot net, though I can't check it now because sprint's authentication server for employee accounts has been down for a week now .
_________________
<enormous animated gif>

[twwilliams]

A couple of things to add to make your file more standard (to prevent stepping on itself if it's loaded multiple times) put this at the beginning:

[savage]

Thanks for the pointers. I've never done a syntax file for vim before and it's still a little mysterious to me. I completely forgot about the c style comments, and probably a number of other things as well. I added really basic highlighting for functions, but it needs work before I post it. I also realized that not all operator combinations are highlighted. I've been busy with other projects lately, so it might be awhile before I get around to it again.
_________________
<enormous animated gif>

[Chris]

I can apply the changes above to the distributed file if they've been tested and no one objects.

[savage]

The new version above has those changes incorporated.

Let me know if anything isn't highlighting right. It's pretty hard to make this work. For instance I discovered that "{enter}" highlighted correctly but "{enter} blahblah {enter}" highlighted the whole thing. That's fixed, btw.
_________________
<enormous animated gif>

[Chris]

Thanks for all the improvements! I'll include the new file with the next update.

[TL]

The current ahk.vim file specifies the highlighting of variables using "greedy" wildcarding ("%.*%") which results in all characters between two variables on the same line being highlighted.
Example: a := %b% + %c%
This can be corrected by using "lazy" wildcarding ("%.\{-}%") which will highlight only the variables:
Example: a := %b% + %c%

The change is implemented by replacing the two "sy match ahkVariable ..." lines in the $VIM/syntax/ahk.vim file with:

[urlwolf]

Savage: this is great. This is the best parsing I've seen for any editor. I had a different vim syntax file, and this one is much better.

I found a problem though.

[img]http://academicproductivity.com/temporary/clipboard12_31_2007_ 01_52_51.jpg[/img]

second instance of Menu is not highlighted.

Thanks

PS: sorry, I don't know why the img doesn't show.

[urlwolf]

by the way, have you seen this other vim syntax file?
Now that I'm starting to understand how vim colors things, it may be more flexible... or not.
http://vim.cybermirror.org/runtime/syntax/autohotkey.vim