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

Adding compatibility with VSCode portable mode #2378

Closed
Peariforme opened this issue Jul 13, 2023 · 2 comments
Closed

Adding compatibility with VSCode portable mode #2378

Peariforme opened this issue Jul 13, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@Peariforme
Copy link

Is your feature request related to a problem? Please describe.

In our company we are packaging a vscode with several mainframe extension for our Z/OS developpers. In order to not interfer with a potential already installed vscode on the developpers post we use the vscode portable mode (https://code.visualstudio.com/docs/editor/portable). It enables us to have severall version of our package on one post and have no interference for the settings and installed extensions between each vscode installation.

The problem is that zowe explorer is not compatible with the portable mode. All settings file are stored under %USER%/.zowe and so are common to all our installation.

In my understanding with the portable mode they should be under %vscodeinstallationfolder%/data/user-data/User/globalStorage/.zowe

Describe the solution you'd like

When using vscode in portable mode the .zowe folder should be in %vscodeinstallfolder%/data

@Peariforme Peariforme added the enhancement New feature or request label Jul 13, 2023
@github-actions
Copy link

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

@t1m0thyj
Copy link
Member

t1m0thyj commented Nov 7, 2023

Zowe Explorer uses %USER%/.zowe as the default location for settings because it is shared by multiple Zowe apps (for example, Zowe CLI and Zowe Explorer for IntelliJ look there as well).

If you want settings be stored elsewhere, you can control the location where ZE stores settings with the ZOWE_CLI_HOME environment variable (see Zowe docs).

@JTonda JTonda closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Closed
Development

No branches or pull requests

3 participants