SlickEdit Community
Archived Read Only Forums => SlickEdit 2016 v21 Beta Discussion => Topic started by: jporkkahtc on August 03, 2016, 08:59:36 pm
-
Seems like the message list misses a lot of errors.
I just did a "mymake > log.txt" from a cmd window.
In Build I did "type log.txt".
Then using next-error and prev-error I can step through the many many errors.
I configured Project->Tools ->Execute to be "type log.txt".
#1: Doing a "type" this way is *far* slower that doing "type log.txt" directly in the build window.
#2: After it completed, there were just 3 messages in the Message list.
What happened to the rest of the errors?
I was hoping to use MessageList as a more structured way to walk through a ton of error messages - as it filters out all the rest of the crud in the log, and lets me sort in various ways.
-
Post your log.txt file. We will look into this. Thanks
-
Can you post your "log.txt" file?
Thanks
-
Can I send it to you privately?
-
For some reason, sending me a PM on the forum doesn't work. Haven't had time to figure out why.
I'll email you directly and you can just respond and attach the file.
-
Never mind :-(
I was using Project -> Tools -> Execute to run my "type log.txt" *and* BuildFirst was checked.
Looks like it was me confusing myself.
-
I found a case and created a simple repro where stepping thru the errors in build makes MessageList jump around even when sorted by index.
The problem happens when an error is in a header that is included from several source files.
The error messages are identical - while Message List shows all the errors, apparently when you step thru them in the build window it can't tell them apart so it jumps to the first match in the message list.
It would be useful if the message list could filter out these duplicates.
The txt file in the zip is the error log from building.
-
Reproduced. Thanks for the example
-
Sorry but this is a limitation