Skip to content
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.

Sign up for GitHub

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

Jump to bottom

autoSwitchInputMethod with vscode remote #8272

Open
RmZeta2718 opened this issue Mar 1, 2023 · 8 comments · May be fixed by #8675
Open

autoSwitchInputMethod with vscode remote #8272

RmZeta2718 opened this issue Mar 1, 2023 · 8 comments · May be fixed by #8675

Comments

@RmZeta2718
Copy link

Is your feature request related to a problem? Please describe.
Does vim.autoSwitchInputMethod work with vscode remote now? I'm using Windows and connect to a Linux machine using vscode remote. But these configurations are not supported on remote ("This setting cannot be applied in this window. It will be applied when you open a local window."):

  • vim.autoSwitchInputMethod.defaultIM
  • vim.autoSwitchInputMethod.obtainIMCmd
  • vim.autoSwitchInputMethod.switchIMCmd

image

Describe the solution you'd like
autoSwitchInputMethod works on remote.
@transtone
Copy link

It works fine in version 1.24.x, but not work in 1.25.x

@unship
Copy link

unship commented May 11, 2023

revert back to 1.24, this function works on remote again

@RmZeta2718
Copy link
Author

@listenerri Hi!
I have just noticed your contribution on #8328, I was facing the same racing problem, thanks a lot for fixing that.
Could you please take a look at this issue? It seems that something in 1.25.x broke this feature.

@listenerri
Copy link
Contributor

@listenerri Hi! I have just noticed your contribution on #8328, I was facing the same racing problem, thanks a lot for fixing that. Could you please take a look at this issue? It seems that something in 1.25.x broke this feature.

This issue may duplicate with: #8324

My solution has been commented at: #8324 (comment)

@RmZeta2718
Copy link
Author

@listenerri Hi! I have just noticed your contribution on #8328, I was facing the same racing problem, thanks a lot for fixing that. Could you please take a look at this issue? It seems that something in 1.25.x broke this feature.

This issue may duplicate with: #8324

My solution has been commented at: #8324 (comment)

Thanks for quick reply. The solution works!

But I think it's wired to configure a local path on remote settings, so I will leave this issue open for further improvements. Thanks again for your solution!

@bohrshaw
Copy link

Configuration settings like autoSwitchInputMethod.* shouldn't have a "machine“ scope as this extension is running on the local machine.
This commit may be reverted: 927ab38

@RmZeta2718
Copy link
Author

Configuration settings like autoSwitchInputMethod.* shouldn't have a "machine“ scope as this extension is running on the local machine. This commit may be reverted: 927ab38

@Quanuanc It seems that you made the commit. Could you please take a look?

@listenerri
Copy link
Contributor

Configuration settings like autoSwitchInputMethod.* shouldn't have a "machine“ scope as this extension is running on the local machine. This commit may be reverted: 927ab38

That commit is introduced by this PR

@bohrshaw bohrshaw linked a pull request Oct 18, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Revert "Set scope for vim.autoSwitchInputMethod to machine (#8051)" bohrshaw/Vim
5 participants
@transtone @bohrshaw @unship @listenerri @RmZeta2718