Re: [code] Multiline error patterns

From: Mitchell <m.att.foicica.com>
Date: Tue, 22 Apr 2014 13:49:06 -0400 (Eastern Daylight Time)

Hi Carlos,

On Tue, 22 Apr 2014, Carlos Pita wrote:

> Hi all,
>
> currently the python error pattern is defined as:
>
> --[[OCaml,Python]]'^%s*File "(.-)", line (%d+)'
>
> but python outputs errors like this:
>
> Traceback (most recent call last):
> File "/tmp/test.py", line 1, in <module>
> 1/0
> ZeroDivisionError: integer division or modulo by zero
>
> so the message itself is not matched and consequently not shown as a
> tooltip but only in the output buffer. A time ago I've written a
> pattern for vim for this very case and it was a PITA. Is the current
> textadept python pattern intended to keep things simple or due to a
> limitation in the pattern matching engine regarding multiline errors?

Both, actually. When you double-click an error message, Textadept only
parses the clicked line for an error message. While this makes things
simple, it's still a limitation. There is no logic to tell Textadept to
search surrounding lines (which may introduce false positives).

Cheers,
Mitchell

-- 
You are subscribed to code.att.foicica.com.
To change subscription settings, send an e-mail to code+help.att.foicica.com.
To unsubscribe, send an e-mail to code+unsubscribe.att.foicica.com.
Received on Tue 22 Apr 2014 - 13:49:06 EDT

This archive was generated by hypermail 2.2.0 : Wed 23 Apr 2014 - 06:34:31 EDT