Posted by: Clark
« on: December 23, 2022, 04:26:01 PM »Added hot fix for this. You can work around this by specifying a literal list of extensions.
Posted by: Clark
« on: December 23, 2022, 03:55:54 PM »Reproduced. Not a new bug.
Posted by: rowbearto
« on: December 23, 2022, 03:52:52 AM »I added *.vpwhistu to "Default Excludes" in Tools->Options->Editing->Search, made <Default Excludes> equal to:
Now when I do "Find in Files" the searched text (which is present in the .vpwhistu file) is no longer shown in the search results (it was in the search results when *.vpwhist* was not in <Default Excludes>).
However when I then go to "Replace in Files", and keep using my <Default Excludes>, it does now find the term in the .vpwhistu file and is asking to replace it, even though *.vpwhist* is in <Default Excludes> and it doesn't show in "Find in Files" results - it still asks to replace it.
I'm using 27.0.1 on Linux x64.
Code: [Select]
<Binary Files>;*.vpwhist*Now when I do "Find in Files" the searched text (which is present in the .vpwhistu file) is no longer shown in the search results (it was in the search results when *.vpwhist* was not in <Default Excludes>).
However when I then go to "Replace in Files", and keep using my <Default Excludes>, it does now find the term in the .vpwhistu file and is asking to replace it, even though *.vpwhist* is in <Default Excludes> and it doesn't show in "Find in Files" results - it still asks to replace it.
I'm using 27.0.1 on Linux x64.