blitzkrieg

> The factor is index-based I think and will not work properly with custom numbers, I'll need to update the CLI code. I'll take a look soon. Could it be...

I have not personally tested the extension with remote workspaces (or at least, not with WSL ones). Can you take a screenshot of the scopes displayed for the cases you...

Closing this issue as I still unfortunately do not use remote workspaces or WSL and I don't have the time available to setup that test environment right now. Welcome to...

Yes, the extension needs to be updated to use the new setting value. Haven't gotten around to it yet, but the used setting (while deprecated, albeit) still works for the...

This problem should now be fixed in the [latest release](https://github.com/jamesonknutson/disable-copilot-comment-completions/blob/master/CHANGELOG.md#201), available on the VSCode marketplace now. > Updated the extension to use Copilot's new github.copilot.editor.enableAutoCompletions setting, instead of github.copilot.inlineSuggest.enable (which...

Sorry for taking so long to reply here. If this is still a relevant issue, can you replicate the problem and take a screenshot of the scopes at the caret...

To clarify, is your request basically to provide a setting that allows the user to specify which settings file to save its changes to? Eg `disable-copilot-comment-completions.saveFile` which would take any...

Added in the [latest release](https://github.com/jamesonknutson/disable-copilot-comment-completions/blob/master/CHANGELOG.md#201) (should be live on the VSCode marketplace now). > Added new setting (disable-copilot-comment-completions.configurationTarget) which can be used to specify the scope where this extension edits...