[TxMt] Re: TextMate's Regexp has been running for 11hrs so far...

[Timothy Bates]

It would be good to alter ™1.X, adding a check-box to the find and replace dialog box saying “don’t worry about undo, or reformatting: just rip and dump”

WIth this checked, replace would spawn a chrome-like separate process that takes the selection or document, tosses it into a process that does the regex (leaving the UI thread clear, just with a transparent screen over the affected window saying “doing your regex, please make an espresso”), and with a button to kill the process if it is driving to Cupertino (#1 Infinite Loop).

This is the kind of light-weight change that would be great to have now, for just the reasons you outline.

tim

On 20 Apr 2011, at 4:07 AM, Mel Brands wrote:

> Stephen said:
> 
>> What's the search expression? Chances are that's what's causing the
>> problem. It's very easy to write a simple expression that (in any
>> engine) takes a very long time to evaluate. perldoc perlre has some
>> examples, IIRC.
> 
> Hi!
> 
> Search expression was something like:
> 
> \{\"[\d\s]+\",\"\",\"[\w\s]+\",\"[\w\s at -_\+]+\"\},
> 
> After an hour after I sent that email, I killed the process. I
> couldn't let it run anymore... was too frustrating.
> 
> I then wrote a quick ruby script and did it that way. It finished in
> seconds. TM has some serious issues with newlines... because it runs
> 100000x faster when the replacement statement has no "\n" characters
> and when the text you're running the regexp on is not one long line.
> Give it a try on your own test data.
> 
> Thank you for a message! I appreciate it for trying to help.
> 
> Melanie
> 
> _______________________________________________
> textmate mailing list
> textmate at lists.macromates.com
> http://lists.macromates.com/listinfo/textmate