Justin M. Keyes
Justin M. Keyes
> and I think [the issue that caused it to get changed](https://github.com/neovim/nvim-lspconfig/pull/2885) should have instead been: > > 1. **Fixed locally** (e.g. by removing certain patterns, or calling `root_pattern()` multiple...
> If the decision is to implement something like this in neovim I can send a PR Yes! It looks like more code than I was expecting, so it can...
> we can use `nvim_open_term()` and copy/pipe data from stdin into the terminal channel. Thanks. Yes, that's an option... is there a benefit to supporting this for "normal" buffers though?...
It definitely makes sense to leverage Nvim's builtin PTY features instead of reinventing that in Lua. The code snippet in https://github.com/neovim/neovim/issues/30415#issuecomment-2368519968 works nicely and perhaps we should provide it by...
Considering this closed, though the "Expected behavior" lists 2 unresolved ideas.
> Is there a reason for the upper limit on `scrollback`? Or is it just a number that seemed "big enough" at the time? yeah, no reason. could be infinite,...
Thanks for looking at this! We are close to releasing 0.11 so please keep this rebase every week or so and we'll get to it. Updating/adding a test will add...
merge semantics are being discussed in https://github.com/neovim/neovim/issues/33577
VS has a menu with options to choose a target.
If this is specifically about `vim.uri_*`, I don't want to spend time on it. Those will be replaced by `vim.uri` module.