Tim Radvan

All good points @nathan. You're right we dropped support for capture groups because they added complexity, but also because we added value transforms which solve the same problem. I can't...

The following works fine for me: ```js moo.states({ main: { // throws the error instead of tokenizing it myError: moo.error }, }); ``` I don't think it would make sense...

Nathan added support for including states in other states, and support for `$all`, in #93. It still needs documentation and some tests :slightly_smiling_face:

@moranje If you're interested in trying out the latest `master` and seeing how it works for you, that would be really useful feedback! :blush:

Hmm. Can you get the information you need by calling `lexer.save()`? I think I'd recommend doing that instead if you can. Moo is probably more stable than the version number...

I'm afraid not! But you can manually call `lexer.setState` after you see that keyword 🙂 Sent with GitHawk

Hey, thanks for suggesting this! :) On consideration, I don't think semantic-release solves any problems that we have right now; sorry if I gave the wrong impression. I _do_ think...

The documentation needs to be updated to document `moo.fallback` (see #112). As for the rest, I think Nathan's just demonstrating that since a moo lexer object is an Iterator, you...

Have you tried swapping the order of the rules? Earlier rules take precedence.

I'm afraid I don't exactly understand what you're trying to do. Moo doesn't choose the regexp with the longest match -- indeed, because it combines all the regexps into a...