Meriel Luna Mittelbach

Seems like VeryLazy is typically triggered after UIEnter. https://github.com/folke/lazy.nvim/blob/aedcd79811d491b60d0a6577a9c1701063c2a609/lua/lazy/core/util.lua#L145

After UIEnter (VeryLazy) there's no way to avoid the problem. Lazy's docs say that VeryLazy should be used for things "not important for initial UI" (= can cause redraws on...

Happy I could help out :)

> Thats a neat use case! Like I said above, unconstructable (to the end user) variants makes sense, but making them entirely private defeats the pourpose. AN attribute could defintely...

I don't follow. `escaped` handles `\t\t\t` just fine. main parser gets `\t\t\t` as input, hits `\`, rejects it, `escaped` consumes `\`, runs second parser, which consumes `t`. Rinse and repeat....

- Parsers with neither a 0 or 1 variant basically never accept empty inputs (`tag`, `char`, etc.) - Parsers with only a 1 variant accept empty inputs (`take_*`, seems like...

`not_line_ending` has neither a 0 or 1 variant and errors on empty inputs. That's perfectly consistent with all the other ones.

This discussion is getting pretty tiresome, it has nothing to do with my actual issue (which is, at best a one line documentation change, and at worst a legitimate bug)...

Running into this with my own interpreter right now. Even going back to the initial commit (HTML spec dated 2004) the inconsistency exists. FBBI never implemented trefunge, and I don't...

> what is this gibberish unfortunately I don't have access to who the rest of the Funge-98 Standards committee was, and where to talk to them :p cheers! On Tue,...