Vadim Misbakh-Soloviov

> Did you hit the failure, then just not mention it at all Well, it is really my fault, that I forgot to mention that (altough, that is the reason...

also, I have dropped arches other than `~amd64` (just in case, although, as I said, I did tested that they compiles there fine). // Although, I'd like them to be...

@MatthewGentoo I've re-pushed, can you, please, re-review? Also @thesamesam @arthurzam @blueness @Flowdalic @leio @NeddySeagoon can you please correctly arch-test it on ARM64, please? (I have only tested that it compiles)...

(re-pushed again because of lost (during previous force-push) "Bug" header in grammar commits)

by the way, tree-sitter-markdown's upstream said to "try passing ALL_EXTENSIONS=1". So, I tried re-generating the things by calling `ALL_EXTENSIONS=1 tree-sitter generate --no-bindings` in `tree-sitter-inline` directory, and re-run the test, and...

> In future, you should take care to run the test suites (again before pushing) okay, I will, thanks ========= **\** > it's good to not let some stuff run...

Btw, @thesamesam, can you, please re-review, and approve the merge if all is okay? Github shows that you have requested changes, but says that it can't find corresponding things because...

By the way, I looked on one of my arm-boards (the one with ubuntu), and found that neovim is packaged with `markdown-inline` there. ``` /usr/lib/arm-linux-gnueabihf/nvim/parser/markdown_inline.so ``` So... Then there is...

ask your users to stop that :shrug: or password-protect the site

Yes, I can, but in my opinion, "first patch" is needed too: for now, user can only redefine values only by passing them to make, but setting their values, for...