-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quarto VS Code extension inadvertently disables GitHub Copilot autocomplete for all other languages #621
Comments
Sorry, I just want to make sure I understand. You're claiming that this setting disabled copilot for you in all languages? I have the extension installed and can't repro (I use copilot on a daily basis): Screen.Recording.2024-12-11.at.12.57.03.PM.mov |
Yes, in my case it did. Here's an example with a Remix project I just created: CleanShot.2024-12-11.at.12.21.46.mp4Details on my VS Code:
Happy to provide further details on my setup as required! |
That appears to be exactly what I'm running:
|
Did you possibly have other values set on the Edited to add: It looks like other people might have faced a similar issue: https://stackoverflow.com/a/78777839 |
Thanks for following up. It turns out that yes, I do have something very much like this on my VS Code user settings. I have no recollection of adding it (and I wish these files were stored in version control but, alas, they're not... :( ), but the following lines are present in my
|
I'll say that "When Adding |
I was just thinking exactly this myself, as I pondered it some more... setting a value specific to one language doesn't seem like it should require opting-in for all other languages! (I just tested, and changing the value to |
Quarto is wonderful. However, the VS Code extension sets the following configuration rule by default:
When
github.copilot.enable
has a value set for any particular language, though, it implicitly disables Copilot for all non-listed languages. This is unexpected and difficult to debug.The solution is to add a wildcard setting:
However, I'm not sure how to have this interact smoothly with any settings a user might already have for this configuration rule. (In my case, nothing was set before installing Quarto.)
The text was updated successfully, but these errors were encountered: