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.

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

Does plugin work with ssh-remote? #172

Open
psmoot opened this issue Oct 23, 2019 · 6 comments
Open

Does plugin work with ssh-remote? #172

psmoot opened this issue Oct 23, 2019 · 6 comments

Comments

@psmoot
Copy link

psmoot commented Oct 23, 2019

What the title says.

When I create a ssh-remote session, I only seem to have git as a SCM provider and can't find a way to tell code I'm using Perforce. Am I missing something obvious, something subtle, or is this know to not work?

If I open code on my Linux system, it figures out I'm using Perforce just fine.

@paisuhas
Copy link

It does work with Remote-SSH; you need to install the extension on the remote machine (the extension marketplace should provide you with an option for the extension to be installed on the remote once you're connected).

@BaankeyBihari
Copy link

While saving file I am getting following type of error
ERROR: "Path '/home/user/extension-output-%234' is not under client's root '/path/to/perforce/workspace'.\n"

@bryand7
Copy link

bryand7 commented Mar 12, 2020

paisuhas: "install extension on remote machine"
The remote machine is a linux server.
I am running vscode on my windows computer.
Remote - SSH works perfectly - all my source code on linux shows up fine in vscode in windows.
How exactly am I supposed to install the Perforce extension on the Linux server?
I have installed vscode and the extension on the linux server under my login, but that does nothing for Perforce.
I can run Perforce command line and visual (p4v) from linux fine.
EXACTLY how do you configure Perforce inside vscode on Windows to connect to the perforce server on Linux?
My sources are ONLY on the linux machine, not on my windows computer.
Thank you!

@mjcrouch
Copy link

mjcrouch commented Mar 21, 2020

@bryand7 You have to install the extension while you are using remote - SSH. You do not need to manually install vscode on the remote linux server - that will just give you another installation of vscode that is totally unrelated to your remote SSH installation

If you already have the extension installed locally on your windows computer, when you open your remote workspace, click on the extensions view. You will see there is a button for each locally installed extension, with the option to install on the remote server.

p.s. my fork is being actively maintained

@bryand7
Copy link

bryand7 commented Mar 23, 2020

I had installed Perforce on vscode before I configured Remote SSH and Perforce did not work - that was what my question was about.
Based on your recommendation, I uninstalled Perforce, and then installed the new mjcrouch fork while connected to the Remote SSH and restarted vscode and Perforce works perfectly now!
My only request would be to add documentation telling people to uninstall/reinstall Perforce AFTER getting Remote SSH installed and fully configured.
Thank You!!!!
https://marketplace.visualstudio.com/items?itemName=mjcrouch.perforce

@mjcrouch
Copy link

mjcrouch commented Mar 24, 2020

The important point is that each remote server you connect to has its own set of extensions installed, starting with no extensions at-all, even if you have installed them locally* - so whatever extensions you have installed locally, you have to install again while you are connected to the remote server - I've done this with lots of extensions without having to uninstall them first :) I did previously add a small section to the readme in my fork though it could probably be more decscriptive

Regardless, glad it is working for you :)

(*there are some certain exceptions to this like themes etc that are only applied locally)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants