Ilia Choly
Ilia Choly
Might make sense to hide the `vim.b[bufnr].changedtick` inside a `util.buf_version(bufnr)` function: ``` lua function M.buf_version(bufnr) return vim.b[bufnr].changedtick end ``` This way it can be changed in the future without breaking...
If the LSP returns a diagnostic for an unloaded file, an unlisted buffer is created https://github.com/neovim/neovim/blob/8ba73f0e4cc6c82032a348a1d6c8d794ed150fd7/runtime/lua/vim/lsp/diagnostic.lua#L241 Since the client never attaches to these buffers, the current logic doesn't clear them...
@crwebb85 you have a failing test.
After some real-life experience with #3657, what I actually want to do is point it at a template directory. Having the template as a zip committed to the repo is...
> having a flag to enable it, to not break backward compatibility. @rwese Can you provide an example of something that this change would break?
@robpottify The objects are delimited by newlines, but `jq` allows a single object to span multiple lines: ``` json { "a": 123 } { "a": 321 } ``` **edit:** `jq`...
@robpottify JSON lines is a subset of JSON streams.
@ynqa tested and working perfectly!
@neur1n AFAIK it wasn't backported to 0.10.2
No, but it can happen if a download fails.