SlickEdit Community

SlickEdit Product Discussion => SlickEdit® => Topic started by: jporkkahtc on January 08, 2019, 08:21:52 PM

Title: Truncated search result width - inconsistent behavior.
Post by: jporkkahtc on January 08, 2019, 08:21:52 PM
I'm getting very inconsistent results with this.
This led me to setting first to a large value: def_search_result_truncate_cols=800 (annoyingly, the UI limits it to 100 :-( ).
Then to small values (10, 20, 30)

Restarting slick and changing foreground/background searching doesn't seem to help.


OIC -- seems to be depend on whether the file is loaded in slick or not.
Files that are loaded do not get truncated.
Files that are not loaded do not get truncated.

The setting of def_search_result_truncate_cols, doesn't seem to make any difference to the results.


BTW,
    Maximum search result line length is 2000.
    Maximum search results output (KB)  = 10000.


Title: Re: Truncated search result width - inconsistent behavior.
Post by: Clark on January 08, 2019, 08:35:07 PM
Multi file searching is threaded by default. Erratic results probably means the files were processed in a different order.
Title: Re: Truncated search result width - inconsistent behavior.
Post by: jporkkahtc on January 08, 2019, 08:59:28 PM
I don't think that is the problem - file ordering isn't the issue.
Title: Re: Truncated search result width - inconsistent behavior.
Post by: Lee on January 08, 2019, 09:07:04 PM
There is a different code path where an open file buffer is processed by find in files and one that is not.  There definitely could be differences, though not intentionally.  Could you post an example or the differences in the results?   
Title: Re: Truncated search result width - inconsistent behavior.
Post by: jporkkahtc on January 09, 2019, 05:16:13 PM
I haven't got an isolated repro case - I tried a little, but failed.
It happens consistently for me on the real files that I cannot share :-(
It is definitely the difference between if the file is loaded or not.
I can do the search, and results have all truncated lines.
The I open those files that matched and repeat the search - no more truncation.
Close the buffers and repeat, and I get truncation again.

I have not been able to get truncated results on loaded buffers even when I try to.
Setting def_search_result_truncate_cols to small values seems to have no effect.
Title: Re: Truncated search result width - inconsistent behavior.
Post by: Lee on January 09, 2019, 07:44:43 PM
Thanks for the info, I started reading through code and I think I may have found the inconsistency you are seeing.  I should be able to hotfix for at least one case with an open buffer.  I will have to go through the threaded code to see if the same issue is there, that one may not be hotfixable at least right away.