Seongmin Lee

Closing this due to v3 release. Now rest.nvim don’t provide any default `` mapping, instead it comes with user commands like `:Rest run` Also, all code is rewrite to be...

Closing this due to v3 release. Now you can omit the `GET` method. rest.nvim will use `GET` http method when not specifed

Closing due to v3 release. Now rest.nvim can only read from `.env` files. It won’t update the file content.

Since `v3` release, rest.nvim provides some User autocmd events to modify the request/response content. You can turn off default `encode_url` option from config and make your own encoder hook. See...

This might be issue with url encoding feature. You can disable auto url encoding from `request.hooks.encode_url` option. Closing this issue. Feel free to reopen this if it still happens

Closing this due to v3 release of both rest.nvim and tree-sitter-http. Now http parser supports form data, and rest.nvim supports `form-urlencoded` `multipart-form-data` will be supported later with RFC standard.

I’m having same issue from aarch64 server (not android) I’ve installed `lua-language-server` before with `mason.nvim` but after uninstall it, I can’t reinstall it from current `mason.nvim` version. `uname -a` ```...

If first example is valid, it means one of these: - we see `\` and `a` as two separate nodes. so `*` at 3rd column is invalid bold opener because...

Spec also says that repeated `*` is not a valid open/close modifier. So if first example is valid, second example should not be valid unless we treat `\a` and `\*`...

> \a is an escaped "a" character, i.e. a "verbatim" "a". This is not whitespace or punctuation So you are saying that parser should distinguish `\a` and `\*` as different...