Use default Copilot commands when CopilotChat is active?

[prilosac]

I'd like to run certain default Copilot commands at times, like :Copilot status or :Copilot disable/enable, or :Copilot setup, but when I have CopilotChat active it seems to "take over" the use of :Copilot. Some commands (like :Copilot status) give a lua error like this

Error executing Lua callback: /home/prilo/.vim/plugged/copilot.lua/lua/copilot/config.lua:72: [Copilot] not initialized stack traceback: [C]: in function 'error' /home/prilo/.vim/plugged/copilot.lua/lua/copilot/config.lua:72: in function 'get' /home/prilo/.vim/plugged/copilot.lua/lua/copilot/client.lua:52: in function 'get_node_version' ...e/prilo/.vim/plugged/copilot.lua/lua/copilot/command.lua:75: in function 'flush_lines' ...e/prilo/.vim/plugged/copilot.lua/lua/copilot/command.lua:94: in function <...e/prilo/.vim/plugged/copilot.lua/lua/copilot/command.lua:56> /home/prilo/.vim/plugged/copilot.lua/plugin/copilot.lua:39: in function </home/prilo/.vim/plugged/copilot.lua/plugin/copilot.lua:8>

and others like :Copilot status say unknown params: setup. How can I send commands to the normal Copilot plugin while CopilotChat is also active? Thanks

[deathbeam]

This looks like copilot.lua bug to me, not sure. I had no issues when using copilot.vim

[prilosac]

Switching to copilot.vim fixed it, thanks!I honestly just used the install instructions in the README, and didn't realize that doing so caused copilot.lua to be defined after (and used instead of) copilot.vim in my config.

Surprising to me that the README recommends copilot.lua instead of the official copilot.vim released by GitHub when it immediately breaks default Copilot commands. Perhaps something is going on on my system that doesn't happen for others

[deathbeam]

I put copilot.vim as recommendation in MIGRATION.md but rest of maintainers use copilot.lua so they went with that in README. I agree that copilot.vim should be used, copilot.lua also wasnt getting many updates lately either.