TerminalFi / LSP-copilot

GitHub Copilot support for Sublime Text LSP plugin provided through Copilot.vim.
623 stars 25 forks source link

How to trigger manually? #134

Closed rlabbe closed 4 months ago

rlabbe commented 4 months ago

The documentation for "auto_ask_completions" states: "Auto ask the server for completions. Otherwise, you have to trigger it manually."

Okay, but how do you trigger it manually? I'm sure I'll be slapping my forehead at the answer, but it is not obvious to me. Is there a key bound to it, or do I have to define it? If so, how? There is something in the FAQ for binding a key to accepting, but it is not clear if I need to do this, what the command is, and since I am not a sublime expert, what to put into "context".

To clarify, it works fine when auto_ask_completions == true, I just don't know how to manually trigger it if I set it to false.

jfcherng commented 4 months ago

https://github.com/TerminalFi/LSP-copilot/blob/519139949c05381829442b2631779065e22cd970/Default.sublime-keymap#L82-L92

rlabbe commented 4 months ago

Worked, thanks!

ardabro commented 3 months ago

https://github.com/TerminalFi/LSP-copilot/blob/519139949c05381829442b2631779065e22cd970/Default.sublime-keymap#L82-L92

Why there is no option in ST4 for these package keybindings? I had to extract them manually from the package file and paste into my User/Default (Linux).sublime-keymap Is it a standard procedure or did I miss something?

jfcherng commented 3 months ago

Is it a standard procedure or did I miss something?

That's how it works now but we can make it better for sure by making it into a side-by-side edit just like how ST's builtin keybinding editing works.

ardabro commented 3 months ago

That's how it works now but we can make it better for sure by making it into a side-by-side edit just like how ST's builtin keybinding editing works.

Sure. I think at least a sentence about it in the readme would be a great help for those not familiar with ST-package configuration nuances.