On Thursday, January 21, 2016 at 5:42:13 PM UTC-6, Edward K. Ream wrote: > > 1. Leo will assume that the user isn't going to run the match-bracket > command on a bracket that is inside a string, comment or regex. If that > assumption is false *both* the forward and backward scanning code will > fail. > > 2. With the above assumption, it *is* possible (but not easy!) to scan > backwards reliably. The hard case is mb.ends_comment. >
Done at rev c03c7e2f. A test script verifies that matching brackets works in both directions for all curly brackets in both directions of the full jQuery sources.. This is an important step forward for Leo's javascript capabilities. Similar code should be used in the javascript importer. There is more testing to be done (adding to an existing unit test, etc.). I expect to close #127 <https://github.com/leo-editor/leo-editor/issues/127> soon. Note that the title of this thread should reference 127, not 129. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
