Scott Olson

I would like this, too. I accept the points made in the old discussion regarding context, but often I am implementing a simple parser with only a _single_ I/O operation...

I'd like for an easy way, for developers and not packagers, to install any version of Rust from any channel (so I would include beta, too). This makes it easier...

Note that in general I support making the implementation of this repo as minimal as possible by moving generic functions into nixpkgs. I'm interpreting this issue as a desire for...

I will try implementing this soon. [This](https://github.com/git/git/blob/311531c9de557d25ac087c1637818bd2aad6eb3a/wt-status.c#L1035-L1087) is the relevant logic in `git` for what to print when `commit.verbose = true`.

+1, I just ran into this when using `vim.b.term_title` and came to check for a bug report.

FYI it seems like you can implement this with the following configuration: ```yaml plugins: inline types types: date: date item_fields: date: | import datetime return datetime.datetime(year or 1, month or...

Thanks for the quick PR! When I re-try my reproduction steps from https://github.com/nvim-telescope/telescope.nvim/issues/2768, I run into this error: ``` Error executing vim.schedule lua callback: ...ker/start/telescope.nvim/lua/telescope/builtin/__lsp.lua:147: attempt to index local 'location'...

I've done some investigation and I believe I know the cause of the issue as well. Note that in every case, the file being loaded has a "virtual" name like...

(Worth noting that this can also affect `lsp_type_definitions` and the others, as well as not being Deno-specific, if any other LSP uses handlers like this, but this is the case...

It is probably interesting to note that trouble.nvim appears to have the same kind of bug (not invoking client-specific LSP handlers, and thus failing to handle Deno in the same...