From: Bernard D. <bde...@or...> - 2019-11-05 11:24:13
|
More about this… After some investigation, it appears that the culprit is the \n in the regexp. There is nothing wrong with this regexp itself, it should work : what is wrong is the way AlphaTcl handles it. There is some legacy code (dating from AlphaX and maybe even earlier) which splits the regexp string into a first line and a tail and breaks everything. The code is very obscure there and it is clearly time to revise this package and proceed to a complete overhaul. My next goal... Sorry for the inconvenience, Bernard > Le 5 nov. 2019 à 11:23, Bernard Desgraupes <bde...@or...> a écrit : > > Hi John, > > thanks for reporting. Something is obviously going wrong there. I’ll have a look. > > Cheers, > > Bernard > >> Le 4 nov. 2019 à 03:44, John Morris <joh...@ed...> a écrit : >> >> Hi, >> I’m having a problem searching in file sets. I did not find any tickets discussing this problem. Before I spend a lot of time researching the problem, I would like to know if it is already on the developers’ radar. >> >> The problem is twofold. First, I seem to have to reselect the fileset to search each time I enter the Find dialog. It would be nice if the selection persisted from one instance of the search to the next. >> >> Second, and much more importantly, 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. >> >> Best, >> John >> >> >> >> _______________________________________________ >> AlphaCocoa-devel mailing list >> Alp...@li... >> https://lists.sourceforge.net/lists/listinfo/alphacocoa-devel > > > > _______________________________________________ > AlphaCocoa-devel mailing list > Alp...@li... > https://lists.sourceforge.net/lists/listinfo/alphacocoa-devel |