From: Bo I. <bos...@ho...> - 2013-10-25 14:59:47
|
Hi Alan, >> But how shall I fill the "Line Number"? >> > That is what the "Extra lines regexp" is for. You can put (backreferences) there too, as the "generic" > pattern shows you. Line Number is $3 or $4 depending on how many groups were in the first line regexp. Actually, I think you are wrong there, Alan. You can indeed have groupings in the “Extra lines regexp”, but the only purpose of those groupings seem to be to format how the captured “extra lines” are displayed in the error list, not to be used for back-referencing. To continue with Viktor’s example, I updated the patterns to this: Error Regexp: ^Error in file "([^"]*?)": *(.*?) *$ Extra lines regexp: ^Line: *(\d+) Filename: $1 Line number: $3 Error message: $2 Pasting his example into the Test Area and clicking ”Test/Commit” just gives me a ”No Matches” message. However, simply removing the “$3” back-reference from “Line number” gives the expected match (presumably because Console only recognizes the two groupings from the “Error regexp” and not the third one from “Extra lines regexp”). Except that we (of course) have not actually _captured_ the line number, it is just shown as text on the captured “extra line”. The fact that the extra line shows only the line number (not the leading “Line:” or trailing “Column…”) is why I assumed that the groupings are for formatting. When I worked on this problem about a year ago, I came to the same conclusion and just assumed that this is how the extra lines regexp is intended to work. Are you saying that it is a bug? /Bosse Från: Alan Ezust [mailto:ala...@gm...] Skickat: den 24 oktober 2013 23:41 Till: Bo Iseborn Kopia: czinege viktor; jedit-users Ämne: Re: [ jEdit-users ] Error Pattern in Consol Plugin Från: czinege viktor [mailto:czi...@fr... <mailto:czi...@fr...> ] Skickat: den 24 oktober 2013 15:56 Till: jedit-users Ämne: [ jEdit-users ] Error Pattern in Consol Plugin Hi, I would like to use Consol Plugin to compile code (it is company specific language). My problem is, how to get the line number. The printout of the compiler is the following: Error in file "D:\xxxxx\xxxx\xxyyzz.scr": Variable "retvaal" undeclared Line: 147 Column: 4 retvaal := _SimFunc_I_1134_S_1130_S_1131 (blablabla); ^ The fields of the parameters: Error Regexp: Error in file "(.*)":(.*) But how shall I fill the "Line Number"? That is what the "Extra lines regexp" is for. You can put (backreferences) there too, as the "generic" pattern shows you. Line Number is $3 or $4 depending on how many groups were in the first line regexp. And one more question. Why there isn't edit mode specific error patterns. I mean a preferred one for every edit mode and not a fix list. Console is not an editor window and it doesn't edit files of any particular mode so we can't do highlighting there. Mapping an edit mode to a preferred error pattern might be a nice idea, but is it the current edit mode that of the current split pane's current buffer, or some default edit mode set on the project (which would probably be more useful), or what? Because it might happen that there are very similar errorlogs of different languages and wrong language's error pattern matches first? thanks. br Viktor ---------------------------------------------------------------------------- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991 <http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk> &iu=/4140/ostg.clktrk -- ----------------------------------------------- jEdit Users' List jEd...@li... <mailto:jEd...@li...> https://lists.sourceforge.net/lists/listinfo/jedit-users ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991 <http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk> &iu=/4140/ostg.clktrk -- ----------------------------------------------- jEdit Users' List jEd...@li... <mailto:jEd...@li...> https://lists.sourceforge.net/lists/listinfo/jedit-users |