http://blog.gmane.org/gmane.editors.jedit.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.editors.jedit.devel/41020 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by synh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Artem Bryantsev (synh) Summary: Console: test area behaves differently from error parsing Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-19 02:25 Message: Probably it is related to handling of line's breaks '\n', '\r\n'. I'll research this during the weekend. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-18 16:50 Message: Nevermind, I see it is Console 4.4.4 (from your working configuration) from your screenshot. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-18 15:48 Message: What version of Console is the latest version that works for you? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-18 09:03 Message: So to summarize, the original test case is this: The error/warning patterns were these: ^(E.+) :: (.+) :: (.+)$ ^(W.+) :: (.+) :: (.+)$ For a "test area", I pasted some lines from 85-103 of Error-Output.txt which is attached. When I "test/commit" the regexes against the pasted text, it works fine. But if I "cat" the Error-Output.txt file from Console, none of these errors are picked up. Personally, I have not worked on this code recently, so I hope one of the other engineers (Dale or Artem) will take a look at this. Also, I am pretty sure this has nothing to do with the ErrorList plugin. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-18 06:00 Message: New info: - using the english localisation doesn't change the behavior - the error is dedicated to the parser line; using "W" in the "error" parsing line results in display of warnings but errors - the "extra line" parsing line does not work either ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:27 Message: And for some reason, I only see errors and no warnings. There might be 2 bugs here, one related to how errors are parsed and another related to warnings. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:12 Message: Sorry, it was not just a addition of the $ at the end. I changed your patterns to this: ^(E.+) :: (.+) :: (\d+)$ ^(W.+) :: (.+) :: (\d+)$ ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-19T09:25:09 http://permalink.gmane.org/gmane.editors.jedit.devel/41019 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Artem Bryantsev (synh) Summary: Console: test area behaves differently from error parsing Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-18 16:50 Message: Nevermind, I see it is Console 4.4.4 (from your working configuration) from your screenshot. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-18 15:48 Message: What version of Console is the latest version that works for you? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-18 09:03 Message: So to summarize, the original test case is this: The error/warning patterns were these: ^(E.+) :: (.+) :: (.+)$ ^(W.+) :: (.+) :: (.+)$ For a "test area", I pasted some lines from 85-103 of Error-Output.txt which is attached. When I "test/commit" the regexes against the pasted text, it works fine. But if I "cat" the Error-Output.txt file from Console, none of these errors are picked up. Personally, I have not worked on this code recently, so I hope one of the other engineers (Dale or Artem) will take a look at this. Also, I am pretty sure this has nothing to do with the ErrorList plugin. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-18 06:00 Message: New info: - using the english localisation doesn't change the behavior - the error is dedicated to the parser line; using "W" in the "error" parsing line results in display of warnings but errors - the "extra line" parsing line does not work either ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:27 Message: And for some reason, I only see errors and no warnings. There might be 2 bugs here, one related to how errors are parsed and another related to warnings. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:12 Message: Sorry, it was not just a addition of the $ at the end. I changed your patterns to this: ^(E.+) :: (.+) :: (\d+)$ ^(W.+) :: (.+) :: (\d+)$ ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T23:50:03 http://permalink.gmane.org/gmane.editors.jedit.devel/41018 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Artem Bryantsev (synh) Summary: Console: test area behaves differently from error parsing Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-18 15:48 Message: What version of Console is the latest version that works for you? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-18 09:03 Message: So to summarize, the original test case is this: The error/warning patterns were these: ^(E.+) :: (.+) :: (.+)$ ^(W.+) :: (.+) :: (.+)$ For a "test area", I pasted some lines from 85-103 of Error-Output.txt which is attached. When I "test/commit" the regexes against the pasted text, it works fine. But if I "cat" the Error-Output.txt file from Console, none of these errors are picked up. Personally, I have not worked on this code recently, so I hope one of the other engineers (Dale or Artem) will take a look at this. Also, I am pretty sure this has nothing to do with the ErrorList plugin. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-18 06:00 Message: New info: - using the english localisation doesn't change the behavior - the error is dedicated to the parser line; using "W" in the "error" parsing line results in display of warnings but errors - the "extra line" parsing line does not work either ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:27 Message: And for some reason, I only see errors and no warnings. There might be 2 bugs here, one related to how errors are parsed and another related to warnings. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:12 Message: Sorry, it was not just a addition of the $ at the end. I changed your patterns to this: ^(E.+) :: (.+) :: (\d+)$ ^(W.+) :: (.+) :: (\d+)$ ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T22:48:07 http://permalink.gmane.org/gmane.editors.jedit.devel/41017 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Settings changed) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Summary: Console: test area behaves differently from error parsing Initial Comment: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-18 09:03 Message: So to summarize, the original test case is this: The error/warning patterns were these: ^(E.+) :: (.+) :: (.+)$ ^(W.+) :: (.+) :: (.+)$ For a "test area", I pasted some lines from 85-103 of Error-Output.txt which is attached. When I "test/commit" the regexes against the pasted text, it works fine. But if I "cat" the Error-Output.txt file from Console, none of these errors are picked up. Personally, I have not worked on this code recently, so I hope one of the other engineers (Dale or Artem) will take a look at this. Also, I am pretty sure this has nothing to do with the ErrorList plugin. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-18 06:00 Message: New info: - using the english localisation doesn't change the behavior - the error is dedicated to the parser line; using "W" in the "error" parsing line results in display of warnings but errors - the "extra line" parsing line does not work either ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:27 Message: And for some reason, I only see errors and no warnings. There might be 2 bugs here, one related to how errors are parsed and another related to warnings. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:12 Message: Sorry, it was not just a addition of the $ at the end. I changed your patterns to this: ^(E.+) :: (.+) :: (\d+)$ ^(W.+) :: (.+) :: (\d+)$ ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T16:05:32 http://permalink.gmane.org/gmane.editors.jedit.devel/41016 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Console: test area behaves differently from error parsing Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-18 09:03 Message: So to summarize, the original test case is this: The error/warning patterns were these: ^(E.+) :: (.+) :: (.+)$ ^(W.+) :: (.+) :: (.+)$ For a "test area", I pasted some lines from 85-103 of Error-Output.txt which is attached. When I "test/commit" the regexes against the pasted text, it works fine. But if I "cat" the Error-Output.txt file from Console, none of these errors are picked up. Personally, I have not worked on this code recently, so I hope one of the other engineers (Dale or Artem) will take a look at this. Also, I am pretty sure this has nothing to do with the ErrorList plugin. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-18 06:00 Message: New info: - using the english localisation doesn't change the behavior - the error is dedicated to the parser line; using "W" in the "error" parsing line results in display of warnings but errors - the "extra line" parsing line does not work either ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:27 Message: And for some reason, I only see errors and no warnings. There might be 2 bugs here, one related to how errors are parsed and another related to warnings. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:12 Message: Sorry, it was not just a addition of the $ at the end. I changed your patterns to this: ^(E.+) :: (.+) :: (\d+)$ ^(W.+) :: (.+) :: (\d+)$ ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T16:03:13 http://permalink.gmane.org/gmane.editors.jedit.devel/41015 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by jomabrueloe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Console: test area behaves differently from error parsing Initial Comment: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-18 06:00 Message: New info: - using the english localisation doesn't change the behavior - the error is dedicated to the parser line; using "W" in the "error" parsing line results in display of warnings but errors - the "extra line" parsing line does not work either ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:27 Message: And for some reason, I only see errors and no warnings. There might be 2 bugs here, one related to how errors are parsed and another related to warnings. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:12 Message: Sorry, it was not just a addition of the $ at the end. I changed your patterns to this: ^(E.+) :: (.+) :: (\d+)$ ^(W.+) :: (.+) :: (\d+)$ ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T13:00:39 http://permalink.gmane.org/gmane.editors.jedit.devel/41014 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Console: test area behaves differently from error parsing Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-17 23:27 Message: And for some reason, I only see errors and no warnings. There might be 2 bugs here, one related to how errors are parsed and another related to warnings. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:12 Message: Sorry, it was not just a addition of the $ at the end. I changed your patterns to this: ^(E.+) :: (.+) :: (\d+)$ ^(W.+) :: (.+) :: (\d+)$ ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T06:27:05 http://permalink.gmane.org/gmane.editors.jedit.devel/41013 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-17 23:12 Message: Sorry, it was not just a addition of the $ at the end. I changed your patterns to this: ^(E.+) :: (.+) :: (\d+)$ ^(W.+) :: (.+) :: (\d+)$ ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T06:12:53 http://permalink.gmane.org/gmane.editors.jedit.devel/41012 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Settings changed) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Initial Comment: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T06:06:44 http://permalink.gmane.org/gmane.editors.jedit.devel/41011 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Settings changed) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Error list does not show errors Initial Comment: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T06:04:07 http://permalink.gmane.org/gmane.editors.jedit.devel/41010 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Resolution: Works For Me Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Error list does not show errors Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-17 23:02 Message: I have no idea/didn't check why your pattern worked before and doesn't now. Are you sure the regexps are the same? I can reproduce your current issue. It is really strange. I don't know why when testing the pattern, it shows things working but when I cat it, it is not detected. *HOWEVER*, there is a workaround: by simply adding a $ at the end of each of those regexps. The problem goes away. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T06:02:06 http://permalink.gmane.org/gmane.editors.jedit.devel/41009 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by jomabrueloe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Pending Resolution: Works For Me Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Error list does not show errors Initial Comment: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 22:28 Message: Hi, thanks for your efforts! I have to apologize, that I wasn't that clear: I use a Tasking C-Compiler for a microcontroller. But because the error output of this one is very hard to handle (2 lines per error ...) I use the perl script to transform it to an conveniant pattern. Than - I have to apologize again for not transmitting this already - I use an own error pattern to parse the errors and warnings. I attach the error pattern as a screen shot. Thanks again Jo ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-18T05:28:41 http://permalink.gmane.org/gmane.editors.jedit.devel/41008 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Pending Resolution: Works For Me Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Error list does not show errors Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-17 09:37 Message: I attached alan-perl-errors.txt which works for my perl error regexp. See if typing that from Console gives you perl errors. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-17T16:37:16 http://permalink.gmane.org/gmane.editors.jedit.devel/41007 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Pending Resolution: Works For Me Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Error list does not show errors Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-17 09:31 Message: 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 ([^&lt;&gt;]+) 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? ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-17T16:31:57 http://permalink.gmane.org/gmane.editors.jedit.devel/41006 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Pending Resolution: Works For Me Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Error list does not show errors Initial Comment: 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. ---------------------------------------------------------------------- Date: 2013-06-17 09:19 Message: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-17T16:19:42 http://permalink.gmane.org/gmane.editors.jedit.devel/41005 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by jomabrueloe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Pending Resolution: Works For Me Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Error list does not show errors Initial Comment: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-17 00:45 Message: 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 ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-17T07:45:05 http://permalink.gmane.org/gmane.editors.jedit.devel/41004 <pre>Plugin Bugs item #3614502, was opened at 2013-06-14 06:01 Message generated for change (Comment added) made by jomabrueloe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Pending Resolution: Works For Me Priority: 5 Private: No Submitted By: jomabrueloe (jomabrueloe) Assigned to: Nobody/Anonymous (nobody) Summary: Error list does not show errors Initial Comment: 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. ---------------------------------------------------------------------- Comment By: jomabrueloe (jomabrueloe) Date: 2013-06-16 22:54 Message: 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. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 07:57 Message: 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614502&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-17T05:54:49 http://permalink.gmane.org/gmane.editors.jedit.devel/41003 <pre>Plugin Bugs item #3614491, was opened at 2013-06-12 13:58 Message generated for change (Settings changed) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614491&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Priority: 5 Private: No Submitted By: tvojeho (tvojeho) Assigned to: Shlomy Reinstein (shlomy) Summary: Exception in DirtyGutter on buffer save Initial Comment: The WhiteSpace plugin needs updating to new version 5.2 with the canceled IOUtilities.closeQuietly method. Saving the buffer with plugin active throws an exception. Regards, tvojeho Using jEdit version: 5.2pre1 Daily build: 2013-06-12 Java runtime version: 1.7.0_21-b11 OS name: Windows 7 OS version: 6.1 OS arch: x86 Log: ... 22:44:21 [AWT-EventQueue-0] [debug] EditBus: ViewUpdate[what=VIEW_ACTIVATED,source=org.gjt.sp.jedit.View[active]] 22:44:21 [AWT-EventQueue-0] [debug] jEdit: checkBufferStatus for all buffers 22:44:21 [AWT-EventQueue-0] [debug] EditBus: DynamicMenuChanged[menu=recent-files,source=null] 22:44:21 [AWT-EventQueue-0] [debug] ActionHooksPlugin: using actionhooks.handler.ViewUpdateHandler&lt; at &gt;155ffe4 to fireAction... 22:44:21 [AWT-EventQueue-0] [debug] ViewUpdateHandler: Handling org.gjt.sp.jedit.msg.ViewUpdate 22:44:27 [AWT-EventQueue-0] [debug] EditBus: BufferUpdate[what=SAVING,view=org.gjt.sp.jedit.View[active],source=1770424.txt (%TMP%\)] 22:44:27 [AWT-EventQueue-0] [debug] ActionHooksPlugin: using actionhooks.handler.BufferUpdateHandler&lt; at &gt;4d63d0 to fireAction... 22:44:27 [AWT-EventQueue-0] [debug] BufferUpdateHandler: Handling org.gjt.sp.jedit.msg.BufferUpdate 22:44:27 [AWT-EventQueue-0] [debug] BufferUpdateHandler: getting view for BufferUpdate[what=SAVING,view=org.gjt.sp.jedit.View[active],source=1770424.txt (%TMP%\)] 22:44:27 [AWT-EventQueue-0] [error] Buffer: Exception while sending buffer event to lcm.providers.diff.DiffBufferHandler&lt; at &gt;13cf82b : 22:44:27 [AWT-EventQueue-0] [error] Buffer: java.lang.NoSuchMethodError: org.gjt.sp.util.IOUtilities.closeQuietly(Ljava/io/Reader;)V 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.LCMPlugin.readFile(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.addLine(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.handleContentChange(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.contentRemoved(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.buffer.JEditBuffer.fireContentRemoved(JEditBuffer.java:2482) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.buffer.JEditBuffer.remove(JEditBuffer.java:789) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.DocumentUtilities.removeTrailingWhiteSpace(DocumentUtilities.java:107) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.WhiteSpacePlugin.bufferSaving(WhiteSpacePlugin.java:154) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.WhiteSpacePlugin.handleMessage(WhiteSpacePlugin.java:96) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.dispatch(EditBus.java:246) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.sendImpl(EditBus.java:281) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.access$200(EditBus.java:87) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus$SendMessage.run(EditBus.java:461) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.send(EditBus.java:206) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.Buffer.save(Buffer.java:468) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.Buffer.save(Buffer.java:423) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.lang.reflect.Method.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Reflect.invokeMethod(Reflect.java:134) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Reflect.invokeObjectMethod(Reflect.java:80) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Name.invokeMethod(Name.java:855) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:75) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHBlock.evalBlock(BSHBlock.java:130) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHBlock.eval(BSHBlock.java:80) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invokeImpl(BshMethod.java:362) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:258) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:186) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShellFacade.runCachedBlock(BeanShellFacade.java:225) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:431) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:73) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:342) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.jEdit$4.invokeAction(jEdit.java:3423) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.jEdit$4.invokeAction(jEdit.java:3405) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditAction$Wrapper.actionPerformed(EditAction.java:212) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.DefaultButtonModel.setPressed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton.doClick(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.JComponent.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.processEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.processEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Window.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.access$200(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$3.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$3.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.AccessController.doPrivileged(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$4.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$4.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.AccessController.doPrivileged(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEvents(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEvents(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [debug] WhiteSpacePlugin: bufferSaving: 31 ms 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: java.io.IOException: Rename failed: D:\Temp\#1770424.txt#save# 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at org.gjt.sp.jedit.bufferio.BufferSaveRequest._run(BufferSaveRequest.java:157) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at org.gjt.sp.util.Task.run(Task.java:64) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.lang.Thread.run(Unknown Source) 22:44:27 [jEdit Worker #1] [error] ErrorListDialog$ErrorEntry: D:\Temp\1770424.txt: 22:44:27 [jEdit Worker #1] [error] ErrorListDialog$ErrorEntry: Cannot save: java.io.IOException: Rename failed: D:\Temp\#1770424.txt#save# 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Program Files\_Editory\jEdit\Nastaveni\jEdit Settings Linstopper\Backup\D\Temp,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Program Files\_Editory\jEdit\Nastaveni\jEdit Settings Linstopper\Backup\D\Temp\1770424.txt.bak1.bak,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp\#1770424.txt#save#,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp\1770424.txt,source=null] ---------------------------------------------------------------------- Comment By: tvojeho (tvojeho) Date: 2013-06-14 08:22 Message: I do wonder how this switch happened - I distinctly remember posting a bug for WhiteSpace plugin, not DirtyGutter, and do not remember assigning the task to shlomy, but here we are... Cheers, tvojeho ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 08:09 Message: Oops. This is not related to WhiteSpace plugin at all. This is in fact, DirtyGutter plugin. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 08:05 Message: It's actually a binary breakage that only requires rebuilding and releasing a new version, not any change to the source. I will handle it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614491&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-14T16:00:08 http://permalink.gmane.org/gmane.editors.jedit.devel/41002 <pre>Plugin Bugs item #3614491, was opened at 2013-06-12 13:58 Message generated for change (Settings changed) made by tvojeho You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614491&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Resolution: Invalid Priority: 5 Private: No Submitted By: tvojeho (tvojeho) Assigned to: Shlomy Reinstein (shlomy) Summary: Exception in DirtyGutter on buffer save Initial Comment: The WhiteSpace plugin needs updating to new version 5.2 with the canceled IOUtilities.closeQuietly method. Saving the buffer with plugin active throws an exception. Regards, tvojeho Using jEdit version: 5.2pre1 Daily build: 2013-06-12 Java runtime version: 1.7.0_21-b11 OS name: Windows 7 OS version: 6.1 OS arch: x86 Log: ... 22:44:21 [AWT-EventQueue-0] [debug] EditBus: ViewUpdate[what=VIEW_ACTIVATED,source=org.gjt.sp.jedit.View[active]] 22:44:21 [AWT-EventQueue-0] [debug] jEdit: checkBufferStatus for all buffers 22:44:21 [AWT-EventQueue-0] [debug] EditBus: DynamicMenuChanged[menu=recent-files,source=null] 22:44:21 [AWT-EventQueue-0] [debug] ActionHooksPlugin: using actionhooks.handler.ViewUpdateHandler&lt; at &gt;155ffe4 to fireAction... 22:44:21 [AWT-EventQueue-0] [debug] ViewUpdateHandler: Handling org.gjt.sp.jedit.msg.ViewUpdate 22:44:27 [AWT-EventQueue-0] [debug] EditBus: BufferUpdate[what=SAVING,view=org.gjt.sp.jedit.View[active],source=1770424.txt (%TMP%\)] 22:44:27 [AWT-EventQueue-0] [debug] ActionHooksPlugin: using actionhooks.handler.BufferUpdateHandler&lt; at &gt;4d63d0 to fireAction... 22:44:27 [AWT-EventQueue-0] [debug] BufferUpdateHandler: Handling org.gjt.sp.jedit.msg.BufferUpdate 22:44:27 [AWT-EventQueue-0] [debug] BufferUpdateHandler: getting view for BufferUpdate[what=SAVING,view=org.gjt.sp.jedit.View[active],source=1770424.txt (%TMP%\)] 22:44:27 [AWT-EventQueue-0] [error] Buffer: Exception while sending buffer event to lcm.providers.diff.DiffBufferHandler&lt; at &gt;13cf82b : 22:44:27 [AWT-EventQueue-0] [error] Buffer: java.lang.NoSuchMethodError: org.gjt.sp.util.IOUtilities.closeQuietly(Ljava/io/Reader;)V 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.LCMPlugin.readFile(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.addLine(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.handleContentChange(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.contentRemoved(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.buffer.JEditBuffer.fireContentRemoved(JEditBuffer.java:2482) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.buffer.JEditBuffer.remove(JEditBuffer.java:789) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.DocumentUtilities.removeTrailingWhiteSpace(DocumentUtilities.java:107) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.WhiteSpacePlugin.bufferSaving(WhiteSpacePlugin.java:154) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.WhiteSpacePlugin.handleMessage(WhiteSpacePlugin.java:96) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.dispatch(EditBus.java:246) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.sendImpl(EditBus.java:281) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.access$200(EditBus.java:87) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus$SendMessage.run(EditBus.java:461) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.send(EditBus.java:206) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.Buffer.save(Buffer.java:468) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.Buffer.save(Buffer.java:423) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.lang.reflect.Method.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Reflect.invokeMethod(Reflect.java:134) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Reflect.invokeObjectMethod(Reflect.java:80) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Name.invokeMethod(Name.java:855) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:75) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHBlock.evalBlock(BSHBlock.java:130) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHBlock.eval(BSHBlock.java:80) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invokeImpl(BshMethod.java:362) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:258) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:186) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShellFacade.runCachedBlock(BeanShellFacade.java:225) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:431) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:73) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:342) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.jEdit$4.invokeAction(jEdit.java:3423) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.jEdit$4.invokeAction(jEdit.java:3405) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditAction$Wrapper.actionPerformed(EditAction.java:212) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.DefaultButtonModel.setPressed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton.doClick(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.JComponent.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.processEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.processEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Window.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.access$200(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$3.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$3.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.AccessController.doPrivileged(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$4.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$4.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.AccessController.doPrivileged(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEvents(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEvents(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [debug] WhiteSpacePlugin: bufferSaving: 31 ms 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: java.io.IOException: Rename failed: D:\Temp\#1770424.txt#save# 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at org.gjt.sp.jedit.bufferio.BufferSaveRequest._run(BufferSaveRequest.java:157) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at org.gjt.sp.util.Task.run(Task.java:64) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.lang.Thread.run(Unknown Source) 22:44:27 [jEdit Worker #1] [error] ErrorListDialog$ErrorEntry: D:\Temp\1770424.txt: 22:44:27 [jEdit Worker #1] [error] ErrorListDialog$ErrorEntry: Cannot save: java.io.IOException: Rename failed: D:\Temp\#1770424.txt#save# 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Program Files\_Editory\jEdit\Nastaveni\jEdit Settings Linstopper\Backup\D\Temp,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Program Files\_Editory\jEdit\Nastaveni\jEdit Settings Linstopper\Backup\D\Temp\1770424.txt.bak1.bak,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp\#1770424.txt#save#,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp\1770424.txt,source=null] ---------------------------------------------------------------------- Comment By: tvojeho (tvojeho) Date: 2013-06-14 08:22 Message: I do wonder how this switch happened - I distinctly remember posting a bug for WhiteSpace plugin, not DirtyGutter, and do not remember assigning the task to shlomy, but here we are... Cheers, tvojeho ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 08:09 Message: Oops. This is not related to WhiteSpace plugin at all. This is in fact, DirtyGutter plugin. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 08:05 Message: It's actually a binary breakage that only requires rebuilding and releasing a new version, not any change to the source. I will handle it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614491&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-14T15:23:35 http://permalink.gmane.org/gmane.editors.jedit.devel/41001 <pre>Plugin Bugs item #3614491, was opened at 2013-06-12 13:58 Message generated for change (Comment added) made by tvojeho You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614491&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: tvojeho (tvojeho) Assigned to: Shlomy Reinstein (shlomy) Summary: Exception in DirtyGutter on buffer save Initial Comment: The WhiteSpace plugin needs updating to new version 5.2 with the canceled IOUtilities.closeQuietly method. Saving the buffer with plugin active throws an exception. Regards, tvojeho Using jEdit version: 5.2pre1 Daily build: 2013-06-12 Java runtime version: 1.7.0_21-b11 OS name: Windows 7 OS version: 6.1 OS arch: x86 Log: ... 22:44:21 [AWT-EventQueue-0] [debug] EditBus: ViewUpdate[what=VIEW_ACTIVATED,source=org.gjt.sp.jedit.View[active]] 22:44:21 [AWT-EventQueue-0] [debug] jEdit: checkBufferStatus for all buffers 22:44:21 [AWT-EventQueue-0] [debug] EditBus: DynamicMenuChanged[menu=recent-files,source=null] 22:44:21 [AWT-EventQueue-0] [debug] ActionHooksPlugin: using actionhooks.handler.ViewUpdateHandler&lt; at &gt;155ffe4 to fireAction... 22:44:21 [AWT-EventQueue-0] [debug] ViewUpdateHandler: Handling org.gjt.sp.jedit.msg.ViewUpdate 22:44:27 [AWT-EventQueue-0] [debug] EditBus: BufferUpdate[what=SAVING,view=org.gjt.sp.jedit.View[active],source=1770424.txt (%TMP%\)] 22:44:27 [AWT-EventQueue-0] [debug] ActionHooksPlugin: using actionhooks.handler.BufferUpdateHandler&lt; at &gt;4d63d0 to fireAction... 22:44:27 [AWT-EventQueue-0] [debug] BufferUpdateHandler: Handling org.gjt.sp.jedit.msg.BufferUpdate 22:44:27 [AWT-EventQueue-0] [debug] BufferUpdateHandler: getting view for BufferUpdate[what=SAVING,view=org.gjt.sp.jedit.View[active],source=1770424.txt (%TMP%\)] 22:44:27 [AWT-EventQueue-0] [error] Buffer: Exception while sending buffer event to lcm.providers.diff.DiffBufferHandler&lt; at &gt;13cf82b : 22:44:27 [AWT-EventQueue-0] [error] Buffer: java.lang.NoSuchMethodError: org.gjt.sp.util.IOUtilities.closeQuietly(Ljava/io/Reader;)V 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.LCMPlugin.readFile(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.addLine(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.handleContentChange(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at lcm.providers.diff.DiffBufferHandler.contentRemoved(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.buffer.JEditBuffer.fireContentRemoved(JEditBuffer.java:2482) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.buffer.JEditBuffer.remove(JEditBuffer.java:789) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.DocumentUtilities.removeTrailingWhiteSpace(DocumentUtilities.java:107) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.WhiteSpacePlugin.bufferSaving(WhiteSpacePlugin.java:154) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at whitespace.WhiteSpacePlugin.handleMessage(WhiteSpacePlugin.java:96) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.dispatch(EditBus.java:246) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.sendImpl(EditBus.java:281) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.access$200(EditBus.java:87) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus$SendMessage.run(EditBus.java:461) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditBus.send(EditBus.java:206) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.Buffer.save(Buffer.java:468) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.Buffer.save(Buffer.java:423) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.lang.reflect.Method.invoke(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Reflect.invokeMethod(Reflect.java:134) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Reflect.invokeObjectMethod(Reflect.java:80) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.Name.invokeMethod(Name.java:855) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:75) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHBlock.evalBlock(BSHBlock.java:130) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BSHBlock.eval(BSHBlock.java:80) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invokeImpl(BshMethod.java:362) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:258) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:186) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShellFacade.runCachedBlock(BeanShellFacade.java:225) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShell.runCachedBlock(BeanShell.java:431) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.BeanShellAction.invoke(BeanShellAction.java:73) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.gui.InputHandler.invokeAction(InputHandler.java:342) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.jEdit$4.invokeAction(jEdit.java:3423) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.jEdit$4.invokeAction(jEdit.java:3405) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at org.gjt.sp.jedit.EditAction$Wrapper.actionPerformed(EditAction.java:212) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.DefaultButtonModel.setPressed(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.AbstractButton.doClick(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at javax.swing.JComponent.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.processEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.processEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Container.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Window.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.Component.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.dispatchEventImpl(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.access$200(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$3.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$3.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.AccessController.doPrivileged(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$4.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue$4.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.AccessController.doPrivileged(Native Method) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventQueue.dispatchEvent(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEvents(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.pumpEvents(Unknown Source) 22:44:27 [AWT-EventQueue-0] [error] Buffer: at java.awt.EventDispatchThread.run(Unknown Source) 22:44:27 [AWT-EventQueue-0] [debug] WhiteSpacePlugin: bufferSaving: 31 ms 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: java.io.IOException: Rename failed: D:\Temp\#1770424.txt#save# 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at org.gjt.sp.jedit.bufferio.BufferSaveRequest._run(BufferSaveRequest.java:157) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at org.gjt.sp.util.Task.run(Task.java:64) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 22:44:27 [jEdit Worker #1] [error] BufferSaveRequest: at java.lang.Thread.run(Unknown Source) 22:44:27 [jEdit Worker #1] [error] ErrorListDialog$ErrorEntry: D:\Temp\1770424.txt: 22:44:27 [jEdit Worker #1] [error] ErrorListDialog$ErrorEntry: Cannot save: java.io.IOException: Rename failed: D:\Temp\#1770424.txt#save# 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Program Files\_Editory\jEdit\Nastaveni\jEdit Settings Linstopper\Backup\D\Temp,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Program Files\_Editory\jEdit\Nastaveni\jEdit Settings Linstopper\Backup\D\Temp\1770424.txt.bak1.bak,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp\#1770424.txt#save#,source=null] 22:44:27 [AWT-EventQueue-0] [debug] EditBus: VFSUpdate[path=D:\Temp\1770424.txt,source=null] ---------------------------------------------------------------------- Date: 2013-06-14 08:22 Message: I do wonder how this switch happened - I distinctly remember posting a bug for WhiteSpace plugin, not DirtyGutter, and do not remember assigning the task to shlomy, but here we are... Cheers, tvojeho ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 08:09 Message: Oops. This is not related to WhiteSpace plugin at all. This is in fact, DirtyGutter plugin. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2013-06-14 08:05 Message: It's actually a binary breakage that only requires rebuilding and releasing a new version, not any change to the source. I will handle it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3614491&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-14T15:22:24 http://permalink.gmane.org/gmane.editors.jedit.devel/41000 <pre>Plugin Bugs item #3291008, was opened at 2011-04-21 09:33 Message generated for change (Settings changed) made by ezust You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3291008&amp;group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Steve (snarum-micron) Summary: DirtyGutter + Save All reverts some files Initial Comment: Save All has recently started failing. Rather than saving all the dirty buffers, some buffers are saved correctly while others seem to have been reverted, saved part way through the revert, and are still marked dirty. The file on drive may have, for example, one of three edits done and the other two not done, while the open buffer shows none of the edits done, but all of the edit lines marked dirty using the DirtyGutter plugin. If I use the Redo function, the edits all reappear, one by one. There seems to be no correlation with file type, folder location, etc. as I have seen two files of the same type (.c) in the same directory where one has the problem and the other does not. I am using jEdit 4.5.pre1, daily builds from April 5, with Java 1.6.0_24 on WinXP64. I updated to the latest daily (April 13) and still see the same problem. ---------------------------------------------------------------------- Comment By: Steve (snarum-micron) Date: 2011-05-09 11:23 Message: Steps to reproduce: Select 'Simple' mode in the Dirty Gutter plugin options Restart jEdit &lt;=== Yes, I have found this step to be necessary, reload didn't seem to work the same. Open a bunch of buffers and edit several of them without saving. Issue the Save All command. Some of the time this works, other times it fails. Observe that one or more buffers is still "dirty" (I can spot it quickly because the Buffer Tabs plugin shows me dirty vs. clean on every buffer.) Of the buffers that are NOT marked dirty, observe that some are saved, but without some of the changes. In these buffers, issuing the Redo command will redo the edits that are missing. Of the buffers that ARE marked dirty, some will be in various states of editing, with some edits missing but others present. Again, Redo will bring the buffer up to where it was when you issued Save All. I will turn on macro record and post the result under separate cover. ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2011-05-09 08:31 Message: Can you capture a macro until you get the buggy behavior? Also, can you specify the steps to reproduce? Thanks. ---------------------------------------------------------------------- Comment By: Steve (snarum-micron) Date: 2011-05-09 07:41 Message: Yes, simple mode still has the bug with the May 5th daily. ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2011-05-07 07:25 Message: No need, thanks. If you can't reproduce the problem, it is probably fixed. ---------------------------------------------------------------------- Comment By: Steve (snarum-micron) Date: 2011-05-06 12:27 Message: Sorry, I've been offline for a week. I've been using the daily build of DirtyGutter plugin, using Diff mode, for several days and have not seen this problem. I'll switch back to simple mode (temporarily, as I find I like the Diff mode better now) and see if I can reproduce the problem. If not, do you want me to revert to the prior daily I was using so I can capture the macro? ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2011-04-29 11:35 Message: Steve, I just thought of something. Can you turn on the macro recorder,and try to reproduce this? Then you can submit the macro, it may give a clue of what happened. Alternatively, it would be useful to have a screencast showing the problem. ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2011-04-29 11:32 Message: Thanks Alan. I just tried to reproduce this, but couldn't. Instead, I got another strange behavior of "save all" which is not related to DirtyGutter - it happens even when DirtyGutter is not installed. I have two buffers open. I make a change to one of them and select 'Save all'. I get a dialog asking me to verify that I want to save all. I answer 'Yes'. Then, a new untitled buffer is created automatically, and the "save all" action that I started before tried to save it, and opens the "save file as" dialog because this buffer is untitled... Neither of this should happen as a result of 'save all'. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2011-04-29 10:08 Message: Ignore previous comment. It seems DirtyGutter has a few bugs fixed in git and has not been released yet. Try out the latest daily build here: http://www.tellurianring.com/projects/jedit-daily/index.php?dir=DirtyGutter%2F2011-04-04_23-56-14%2F See if you have the same problem. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2011-04-28 07:48 Message: perhaps diff mode should be the default in DirtyGutter for future versions until this is fixed? ---------------------------------------------------------------------- Comment By: Shlomy Reinstein (shlomy) Date: 2011-04-27 22:26 Message: This might be caused by DirtyGutter, if you use the "simple" mode (i.e. "Dirty line provider" in the option pane is set to 'simple'). DirtyGutter (in "simple" mode only) actually runs an undo/redo procedure every time the buffer is saved in order to build its own support for undo/redo - since the core does not expose the undo list to plugins. I will try to check &amp; fix this soon, but in the mean time you can switch to "Diff" mode - which does not perform any undo/redo, but instead compares the buffer to the file on disk. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2011-04-27 15:33 Message: Please describe some easy steps to reproduce with 2 test files, if possible. ---------------------------------------------------------------------- Comment By: Steve (snarum-micron) Date: 2011-04-27 12:50 Message: I am beginning to wonder if my statement was correct. I turned off the DirtyGutter plugin a couple days ago, and I don't believe I have seen this happen since. So, this may indeed be a plugin bug. I am using version 0.2 of DirtyGutter, April 5 daily build. ---------------------------------------------------------------------- Comment By: Steve (snarum-micron) Date: 2011-04-21 10:52 Message: Sorry for the confusion. This has nothing to do with the DirtyGutter plugin, I was simply noting that it seems to indicate that some lines were actually changed AFTER the save, which is a symptom, not a cause. The problem happens with or without the plugin turned on. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2011-04-21 10:39 Message: is this a bug with the dirty gutter plugin or jedit itself? Can you describe the problem without using dirtygutter? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&amp;atid=565475&amp;aid=3291008&amp;group_id=588 ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev </pre> SourceForge.net 2013-06-14T15:16:12 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.editors.jedit.devel