Zach Birenbaum

I've wanted to solve this for a while since I also use pairs completion, but autopairs really doesn't like to play nice. There might be a way to selectively disable...

Believe it or not I am actually way ahead of you on this. I've been looking into different options for a while now (Including the repo that you linked) that...

I'm gonna pin this so that people won't miss it and can provide input on potential sources or my plans to write a more generalized LSP sever

@marcelarie I have a functioning prototype LSP that implements the completion handlers properly but it gets rate limited really fast, as I found out upon completing it that open ai...

I have noticed this too, but I think it's an upstream issue. I'll see if I can trace down the cause and make an issue post in neovim.

I have considered it, but the goal here is ultimately to replace all copilot.vim functionality, and it seems bloated to have a whole plugin as a requirement for just a...

So I'm gonna close this because Microsoft keeps doing stuff to break copilot when they update and I don't want to have to keep rolling it back manually. The last...

Hi @sbulav, thank you for the input, just a couple of comments: > * Async startup of copilot(is it possible?) I'm not certain of what you mean by this. The...

@sbulav Specifying on which filetypes to start the plugin Checks have been written in to make sure copilot doesn't start in buffers like `help` or `packer`. ft_disable has been added...

> Hi @zbirenbaum Thanks for your in-depth explanation! I had significant input lag with `vim.schedule` on one of the previous `copilot.lua` versions, but with the latest version, the lag is...