-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Extension breaks when VS Code Insiders Edition is updated #194
Comments
Is this still happening? |
ianic
added a commit
to ianic/edamagit
that referenced
this issue
Jul 31, 2023
I'm using vscode insiders from macOS to develop on remote Linux machine. When I try to commit edamagit fails because it cannot find code cli. 'code-insiders' it is in PATH when running terminal from vscode: ```sh which code-insiders /home/ianic/.vscode-server-insiders/bin/9800cf6dd6bf4634889d60720ef46a400f3a7298/bin/remote-cli/code-insiders ``` The problem is that edamagit is looking into `../bin/code-insiders` instead of `../bin/remote-cli/code-insiders`. So it fails to find it and [fallback](https://github.com/kahole/edamagit/blob/e9462afbdad4ed0a84ec3b1d92c6a9eb4dd20aa2/src/commands/commitCommands.ts#L212) to using `code` from PATH. Which works if insiders version is not used. In insiders version there is no `code` cli in PATH but `code-insiders`. I think that [this](kahole#194) issue has the same root cause.
hedning
pushed a commit
to hedning/edamagit
that referenced
this issue
Jan 31, 2024
I'm using vscode insiders from macOS to develop on remote Linux machine. When I try to commit edamagit fails because it cannot find code cli. 'code-insiders' it is in PATH when running terminal from vscode: ```sh which code-insiders /home/ianic/.vscode-server-insiders/bin/9800cf6dd6bf4634889d60720ef46a400f3a7298/bin/remote-cli/code-insiders ``` The problem is that edamagit is looking into `../bin/code-insiders` instead of `../bin/remote-cli/code-insiders`. So it fails to find it and [fallback](https://github.com/kahole/edamagit/blob/e9462afbdad4ed0a84ec3b1d92c6a9eb4dd20aa2/src/commands/commitCommands.ts#L212) to using `code` from PATH. Which works if insiders version is not used. In insiders version there is no `code` cli in PATH but `code-insiders`. I think that [this](kahole#194) issue has the same root cause.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
When the VS Code Insiders Edition receives a new update (typically many times a week), and I reload the IDE, the extension cannot find the
code --wait
command anymore and thus errors when entering the commit message window. After updating, I can fix this manually by symlinking thecode-insiders
tocode
in myPATH
.I suppose there might be a hard-coded path somewhere that breaks? Using this in WSL Ubuntu 20.04 under Windows 11.
The text was updated successfully, but these errors were encountered: