Menu
▾
▴
#221 Search in Filesets is broken if regexp contains \n
(This bug was reported on the AlphaDev list by John Morris. I'm entering it in the bug tracker for easier reference)
Original message:
<< Searching inside a fileset seems to change how the Regexp search works. Simple searches (those not using any grep at all and some using just simple grep) seem to work fine. However, a somewhat more complex search fails completely. It does not find anything in the current window and does not find anything in any of the other files in the fileset.
For what it’s worth, I am using TeX filesets in Alpha 9.1 running on a 2014 MacBook Pro under Mojave (10.14.6). The “more complex” search that is giving me trouble right now has (?s)(monetary)(( +)| (\n) )(polic[^\s]+) in the Find field and \1-\5\4 in the Replace field. The response I get in the status bar is “Can’t find '(?s)(monetary)(( +)| (\n) )(polic[^\s]+)'; and there are no more files to search.” A partial work around to this problem is to press command-G after I get that error, which takes me through all instances of the search in that file. However, that does not cycle through the other files in the fileset. Finally, this problem does not seem to be restricted to filesets. Any selection In the Multiple Files panel seems to cause this problem.>>
Explanation: AlphaTcl relies on the scan commands (scancontext, scanmatch, etc.) defined by the TclX extension to perform its search in files on disk. Unfortunately these commands work on a line-by-line basis. AlphaTcl's workaround for this limitation is not robust enough and fails for the mentionned regexp which contains a linefeed symbol \n.
I'll try to fix this.
This is hopefully fixed now after a complete overhaul of the Supersearch package and the introduction of a new core command scanFile.
Changes committed to the repository (rev. 1810 (sourceforge.net)). The core must be rebuilt.