Problem: if word-wrapping is active in the console output window, when I place a filter for error lines in my C compilation script then those are highlighted correctly according to my filter, but error navigation doesn't work if the error lines are splitted into two or more parts.
Cause: this happens because word-wrapping split the lines into two or more parts in the console output window.
Solution: disable the word-wrapping so that each error line is not splitted.
I think this is a bug, it would be great to allow clickable lines (and thus error navigation) even with word-wrapping enabled in the console output window.
Best regards and thank you for this great tool.
Last edit: Pidgeon 2017-10-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Interesting, interesting... It looks like there is no official way to retrieve a full unwrapped line from a RichEdit control with WordWrap turned on. However, in practice it looks like when a retrieved line ends with '\r' it is a full line (or the trailing part of a word-wrapped line), and when it does not include '\r' at the very end it is an incomplete part of a word-wrapped line. But this is not documented anywhere! So I may rely on it without any confidence that it is true for all the versions of RichEdit >= 2.0 on any version of Windows.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Very interesting indeed, happy to have contributed with the discovery of the bug. Hopefully there could be a way to fix this, it would be nice to allow the error navigation even with word-wrapping turned on ;).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fixed in v0.6 alpha dev: NppExec20171025_src-3.zip
I'm expecting the official "v0.6 alpha 1" to be released in November. And this version is expected to be more stable than the "v0.5.3". But it will be named "alpha" anyway because the "v0.6" core has been rewritten completely - and this is the main reason of "alpha" in its name.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I'm running:
Problem: if word-wrapping is active in the console output window, when I place a filter for error lines in my C compilation script then those are highlighted correctly according to my filter, but error navigation doesn't work if the error lines are splitted into two or more parts.
Cause: this happens because word-wrapping split the lines into two or more parts in the console output window.
Solution: disable the word-wrapping so that each error line is not splitted.
I think this is a bug, it would be great to allow clickable lines (and thus error navigation) even with word-wrapping enabled in the console output window.
Best regards and thank you for this great tool.
Last edit: Pidgeon 2017-10-24
I can reproduce it in v0.6 alpha dev with, for example, the following:
I'll see what can be done with it.
Interesting, interesting... It looks like there is no official way to retrieve a full unwrapped line from a RichEdit control with WordWrap turned on. However, in practice it looks like when a retrieved line ends with '\r' it is a full line (or the trailing part of a word-wrapped line), and when it does not include '\r' at the very end it is an incomplete part of a word-wrapped line. But this is not documented anywhere! So I may rely on it without any confidence that it is true for all the versions of RichEdit >= 2.0 on any version of Windows.
Very interesting indeed, happy to have contributed with the discovery of the bug. Hopefully there could be a way to fix this, it would be nice to allow the error navigation even with word-wrapping turned on ;).
Fixed in v0.6 alpha dev: NppExec20171025_src-3.zip
I'm expecting the official "v0.6 alpha 1" to be released in November. And this version is expected to be more stable than the "v0.5.3". But it will be named "alpha" anyway because the "v0.6" core has been rewritten completely - and this is the main reason of "alpha" in its name.
Great, thanks for the hard work!