search string gets eval'd, causes error if there's a space or $ in it
Fix scheduled for eventual new version; can refer to commit 225 if details desired in the interim
Restrain over-zealous text search term expansion by EVAL
search string gets eval'd, causes error if there's a space or $ in it
OK - understand what happened - extra reparsing from EVAL caused unprotected search term to look like TCL and it all went south. V5.7 did not use "eval", which was added trying to simplify the command. Will repair.
search string gets eval'd, causes error if there's a space or $ in it
Ya know, I'd swear this was fixed once before. And its odd if it does really work for V5.7; maybe I'll look to see if anything appears changed between the two releases. In any event, standby...
OK - having now LOOKED at Ralph's actual changes, I'd agree that they are tilted toward the Mac platform a bit too much to consider retaining as mainline code. One question I STILL have is what was the point of ADDING the Left/Right arrow keys as ALTERNATE keyboard accelerators? Why not just CHANGE the accelerators directly (something the EXISTING Preferences allows you to do: see the 'Behavior' Tab)? Did you really need TWO accelerators EACH to jump to a Next (or Prev) difference region? While its...