I was looking for descendant selectors in javascript files and used
[size=200]".*>.*" [/size]
as the regex search term.
The results page appears but is frozen and then a few seconds later Sublime Text closes.
Build 3083 on 64-bit Xubuntu 15.04
I was looking for descendant selectors in javascript files and used
[size=200]".*>.*" [/size]
as the regex search term.
The results page appears but is frozen and then a few seconds later Sublime Text closes.
Build 3083 on 64-bit Xubuntu 15.04
[quote=“NickTulett”]I was looking for descendant selectors in javascript files and used
[size=200]".*>.*" [/size]
as the regex search term.
The results page appears but is frozen and then a few seconds later Sublime Text closes.
Build 3083 on 64-bit Xubuntu 15.04[/quote]
Of course, the editor shouldn’t crash. But why not just search for “>”?
Similar issues:
github.com/SublimeTextIssues/Core/issues/767
github.com/SublimeTextIssues/Core/issues/442
github.com/SublimeTextIssues/Core/issues/461
github.com/SublimeTextIssues/Core/issues/602
Because the quotes are part of the regex.
I’m looking for this sort of thing in the source
[size=150]$(".something > .something-inner")[/size]
[quote=“NickTulett”]Because the quotes are part of the regex.
I’m looking for this sort of thing in the source
[size=150]$(".something > .something-inner")[/size][/quote]
Oh, of course. My habit is to use quotes to delimit strings, so I misread the problem. Sorry about that.
As written, though, that regular expression will match all of “abc”>" as well as the final “>”. If that’s what you want, fine, but it looks too broad to me. But my judgment is clearly a bit fuzzy today. My inclination would be to restrict the search to not succeed when there’s a quotation mark inside: “^”}>^"}" would find far fewer matches, and still include what I think you’re looking for.