Adapt as in modify the compile or run command in /usr/share/geany/filetypes.*? I might be able to write a wrapper script to run the respective tool and reformat its output - however, I don't know what the "standard interpreter error/warning syntax" looks like... Also, If this is gonna be built into Geany soon, it's probably not worth the trouble!?

I've written a simple wrapper script to reformat JSLint's (http://jslint.com) output - see below. That seems to work fine so far. Looking forward to it! --------------- import sys import subprocess import re # settings -- TODO: read from cofniguration file cmd = "rhino" lint = "/usr/share/jslint/jslint.js" pattern = r"Lint at line (\d+) character (\d+): (.*)" def main(args): filename = args[1] command = [cmd, lint, filename] output = subprocess.Popen(command, stdout=subprocess.PIPE).communicate()[0] print "\n".join(reformat(output, pattern, filename)) def reformat(text, pattern, filename): results = [] regex = re.compile(pattern) for line in text.split("\n"): matches = regex.search(line) if matches: line = int(matches.groups()[0]) char = int(matches.groups()[1]) msg = matches.groups()[2] results.append("%s:%d: [char %d] %s" % (filename, line, char, msg)) return results if __name__ == "__main__": sys.exit(main(sys.argv))

Hi, On Fri, 26 Sep 2008 13:02:28 +0000 (UTC) AC <gmane.0vd(a)gishpuppy.com> wrote: There are plans for a new release but nothing finalized by now. There are still a couple of things inside queue that needs to be done. So building from svn might be a good idea at this time ;) Regards, Frank -- Frank Lanitz <frank(a)frank.uvena.de>

On Sun, 28 Sep 2008 09:32:40 +0000 (UTC), AC <gmane.0vd(a)gishpuppy.com> wrote: The regular expression you used from the manual is to match a different format that you have. Try this one: error_regex=^(.+?):([0-9]+):[0-9]+ Maybe it could be done better, I'm not good in writing regexps, but it works :). Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

On Sun, 28 Sep 2008 13:40:03 +0000 (UTC), AC <gmane.0vd(a)gishpuppy.com> wrote: Usually people are just happy if something works :). I'm not sure about the greedy operator but your error message contained not only filename:line but filename:line:column and because of the :column, especially because of the second colon, the regular expression of the documentation failed and the addition was necessary. Without this addition, it parsed "test.py:7" as the filename and "24" as the line number. With the addition, it detects there have to be two colons and it takes the filename as first reference, the line number as the second and then looks for a second colon followed by digits. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc

On Sun, 28 Sep 2008 09:32:40 +0000 (UTC) AC <gmane.0vd(a)gishpuppy.com> wrote: Thanks for pointing this out, I've now updated the docs (but the web docs might not be up to date until tomorrow): *Example:* ``error_regex=(.+):([0-9]+):[0-9]+`` This will parse a message such as: ``test.py:7:24: E202 whitespace before ']'`` I'd thought GNU regex did support non-greedy matching, but evidently my initial tests weren't good enough to show they didn't. For reference, I have glibc-2.4-11 (Fedora Core 5). Regards, Nick