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

The 'ext install' command is unavailable after compiling from the sources #1557

Closed
ghost opened this issue Dec 21, 2015 · 5 comments
Closed
Assignees
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code)
Milestone

Comments

@ghost
Copy link

ghost commented Dec 21, 2015

I compiled the VSCode as described here. After that I have created the code script with the following content:

(cd /some/path/vscode/src/scripts && ./code.sh)

and made it executable:

chmod +x /usr/local/bin/code

After that when I run the VSCode, hit Ctrl-Shift-p and type ext install I see the 'No extensions found' message, please see the attached file.
vscode bug

When I type the extension I see the only 'Extensions: Show Installed Extensions' message, please see the next attached file.
vscode bug1

Expected behaviour: show the 'Extensions: Install Extension' item in the list or suggest to install an extension.
Actual behaviour: empty list or the only one 'Extensions: Show Installed Extensions' item.


OS: Arch Linux, 64-bit

@bpasero bpasero added the *question Issue represents a question, should be posted to StackOverflow (VS Code) label Dec 22, 2015
@bpasero bpasero added this to the Backlog milestone Dec 22, 2015
@bpasero
Copy link
Member

bpasero commented Dec 22, 2015

The extension feature is only enabled in Microsoft VS Code builds. @egamma I think you documented distributions somewhere?

@bgse
Copy link
Contributor

bgse commented Dec 22, 2015

@bpasero Is this restriction set in stone, or is there a possibility that it might be reviewed at some point?

I'm asking since I can see having vscode readily available across the many different Linux distributions being a lot easier if it is left to the distributor to simply ship the OSS build from their repos, but still in such a case I'd prefer extensions coming from the official marketplace and not making distributing extensions overly complicated where we have to upload our extensions to many different places.

@egamma
Copy link
Member

egamma commented Dec 22, 2015

@bgse more background on this topic.

CC @chrisdias

@rezonant
Copy link

Could one simply configure their product.json to point to the official extension repositories? Is that allowed? In the analog of Chrome/Chromium, referenced in the split license issue by @chrisdias, Chromium is allowed to install Chrome Web Store extensions. Also, the actual README.md of the vscode repository includes a screenshot of the extension installer UI via F1, so if that's not allowed, I'd recommend the screenshot be changed to show a feature which is available when the repository is actually built.

@chrisdias
Copy link
Member

@rezonant yes, you can configure product.json to point to the official marketplace. look in the product.json that is installed with the visual studio code distro for the url.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code)
Projects
None yet
Development

No branches or pull requests

5 participants