Futago-za Ryuu

@kristianmandrup It's not included as far as I can tell, but @dmajda [said 3 years ago](https://github.com/pegjs/pegjs/issues/217#issuecomment-40918250) that he will look into it after releasing PEG.js v1, but from what I...

@kristianmandrup oh 😆, its on the roadmap. I haven't updated the ePEG.js repo for a while, and just recently decided to turn it into a complete rewrite of PEG.js instead...

@krisnye `[ ... ]` is used for character classes, see [https://github.com/pegjs/pegjs#characters](https://github.com/pegjs/pegjs#characters) What I'm doing in ePEG.js is adding ranges (also on the roadmap) to achieve what I think your describing:...

1. How about `^` instead of `#`? 2. Why wont `sequence / &{ error("expectation message here...", location()); }` cut it? I'm leaning towards adding this, but not 100% sure yet,...

@dmajda @Mingun I've updated the [CHANGELOG.md](https://github.com/pegjs/pegjs/blob/master/CHANGELOG.md) file, and before release I'm thinking of adding slightly more information for the major changes. For now, I'm doing other stuff (including an overhaul...

Thanks @dmajda > I don’t follow PEG.js development anymore Sorry, should have been more clear; was actually referring to any changes you guys have made that I've forgotten to add,...

@Mingun just pushed 4723176 with what you noted

@lindner @srenault @tilgovi @GreenImp @cr-roypeled Sorry for the late reply 🙇 I'm kind of overloaded with my work right now but have been (on my time off) working on a...

If I'm understanding correctly, you basically want to return the match of everything between the start and end of a rule's expression block, is that correct? `text()` already does this:...

Oh, sorry, I understand what you mean now 😆 As `match()` would require adding additional code to the generated parser that catches the result of every expression in the sequence,...