#1720 Console: test area behaves differently from error parsing

open
None
5
2013-06-18
2013-06-14
jomabrueloe
No

I use a perl script to format the error output of my compiler in a way that can be easily parsed by the error list. This worked fine up to version 1.9 of the error list (which I still use today).
With the more recent versions (since the german localization, 2.0 ?) I get a very strange behaviour: I check the error output in the plugin options and get a display of all included errors and warnings. But in real life, the error list shows just nothing. I have tried to modify my perl script in several ways (output to std out, output to error out, output to both) without any change.

Discussion

1 2 3 > >> (Page 1 of 3)
  • Alan Ezust
    Alan Ezust
    2013-06-14

    This sounds like it is related to Console plugin?
    Let me confirm. Are you saying that from Console plugin options - error patterns, you can "test" the Perl regexp and it shows you the errors, as expected, but if you paste those same errors in a text file, and "cat" (or "type" from windows) it from the Console System shell, you do not see the same errors in ErrorList? Because I just tried those exact steps and it works for me.

    Please give me more details on how to reproduce your issue.

    Do you have the ErrorList Dockable already visible when you do this?

     
  • Alan Ezust
    Alan Ezust
    2013-06-14

    • status: open --> pending-works-for-me
     
  • jomabrueloe
    jomabrueloe
    2013-06-17

    Hi, thanks for your response.

    Yes, thats the way I do it, only I don't use a temporary file but direct piping via perl. I'm gonna try that way also and give you the result.
    Regarding your 2nd question: I use the error list docked an the bottom of jedit.

     
  • jomabrueloe
    jomabrueloe
    2013-06-17

    Hi,

    I just tried it: with the new version (and the latest console plugin), using the type command in the console results in a plain display with empty error list. Using the same with my old (working) configuration, the errros and warnings are shown as well in the console (colored text) as in the error list.
    I though it would be helpful for you to see, which other plugins are used. Therefore I attach two jpegs, one with the working and one with the not working configuration.

    Jo

     
  • jomabrueloe
    jomabrueloe
    2013-06-17

     
    Attachments
  • jomabrueloe
    jomabrueloe
    2013-06-17

     
    Attachments
  • Alan Ezust
    Alan Ezust
    2013-06-17

    Ok, this is the windows platform, and german localization.

    If you switch back to English locale, does the problem goes away?

    If so, please let us know. If not, I would suggest trying to see how else the settings differ between the working vs non-working configurations.
    Many error matchers in Console do you have enabled? Which ones are they? Is generic one of them? Can you make the "generic" error trigger, or is your problem specific to perl errors?
    I have a file called asdf.txt that looks like this:
    /etc/apt/sources.list:5: error! This is an arbitrary message.

    and whenever I cat it, I see errors in my errorlist. Do you?

    I will also go to windows and see if I can reproduce your issue by switching to german.

     
  • Alan Ezust
    Alan Ezust
    2013-06-17

    I tried typing the Error-Output.txt and it is not detected as a Perl error by the Perl error regexp, which for me is this:
    (.+) at ([^<>]+) line (\d+)(\.?|, (.+))
    Is that the same regexp you have?
    If so, I can reproduce your error but it seems to me there is something wrong with the regexp. Is this really the output of the perl command?

     
  • Alan Ezust
    Alan Ezust
    2013-06-17

    some perl error strings to test your regexp

     
    Attachments
1 2 3 > >> (Page 1 of 3)