Vscode-project-manager: saving projects doesn't work, also edit projects does nothing.

[OneOfOne]

Like the title says, using the latest version as of 5 minutes ago on the store and vscode 0.10.10 on Linux 64bit.

[alefragnani]

Does it ask you for the project name, when you try to save the project?

If yes, you could try to find the projects.json file in your /Users/yourlogin folder, that is where I supposed it should be saved, in Linux.

I will try to get a Linux VM to test it. I remember having a Ubuntu available somewhere.

[OneOfOne]

It asks for the project name, doesn't show anything after I hit enter to save it.

I just ran find -iname projects.json on my $HOME and there was nothing.

[OneOfOne]

Taking a quick look at the code,

            let appdata = process.env.APPDATA || (process.platform == 'darwin' ? process.env.HOME + '/Library/Application Support' : '/var/local');
            var projectFile = path.join(appdata, "Code/User/projects.json");

projectFile is wrong, it should be vscodeConfigPath + "/projects.json", but i'm not sure if there's an actual api to return vscodeConfigPath.

// edit

on linux the path is ~/.config/Code/User/, so maybe just assume ~/.config on linux?

[gil-levy]

hi,

on linux i changed it to:
var appdata = process.env.HOME;
var projectFile = path.join(appdata, ".config/Code/User/projects.json");

and it works now.

[alefragnani]

Hi @OneOfOne ,

I tested in a Ubuntu VM and could reproduce your problem. Instead of /Users/YourLogin folder, as I supposed it should use, it tries to save in /usr/local (I didn't check the source prior my previous post). I don't use Linux, so I'm sorry for missing the right configs. I just used a _home folder template_ that I found in StackOverflow :disappointed: .

I tested @gil-levy approach and found more references that says it should be /home/YourUser/.config the right place. In fact, at least in my Ubuntu installation, it was here that Code itself put its temp files, so I suppose it is really the right place.

I pretend to update the extension until the weekend with this fix.

Thanks @gil-levy for pointing the right direction :+1:

[alioygur]

+1

I have same problem. I am on Ubuntu/Linux 64

[alefragnani]

The fix is already working, but I'm having problems while opening the projects. It seems to be a problem with child_process.exec, and as soon as I have a solution, I'll publish the update.
Stay tuned :smile:

[alioygur]

@alefragnani yes I have too :)

I think this about vscode it self

[alefragnani]

Good news... I just tested the latest Insider release, using the new Debian package and it worked perfectly. Even the openInNewWindow. :tada:

So, I will release this fix right after the new Code version is released.

Thanks for your patience

[alioygur]

Alefragnani can you explain the problem.

Thank you.
On Mar 31, 2016 5:03 AM, "Alessandro Fragnani" [email protected]
wrote:

Good news... I just tested the latest _Insider_ release, using the new
_Debian_ package and it worked perfectly. Even the openInNewWindow. [image:
:tada:]

So, I will release this fix right after the new _Code_ version is
released.

Thanks for your patience

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/alefragnani/vscode-project-manager/issues/16#issuecomment-203715613

[alefragnani]

Hi @alioygur ,

Would you like to know the _original problem_ reported in this issue, or the _opening projects_ problem, which is fixed in the Code Insider release? :smile:

[alioygur]

@alefragnani all of them :)

[alefragnani]

Hi @gil-levy ,

Which Linux distro are you using? Did you do anything else other than the soft link as described in https://code.visualstudio.com/Docs/editor/setup to work, because on an Ubuntu VM that I have, it has no effect. I can open Code from the shell, but not withing Code (the extension).

Thanks

[alefragnani]

Ok @alioygur :smile:

1. Original Problem: I used a _Stack Overflow_ answer to know where is the _home folder_ using Node.js. But the _supposed_ place where wrong, so I search a little bit and @gil-levy pointed me to the right direction. This is already fixed, but then, when testing the _switching_ between projects, I get problem 2

2.Opening Projects: The same problem that I had with Mac OS X, happened with Linux (_whata surprise_). I use child_process.exec to open Code with the folder defined for each project. But since Code uses a script to open itself in shell (that's why you had to follow this steps to open code via shell in Linux and Mac), it appears that child_process.exec has some issues with that. I mainly use Windows (also had a Mac) and this shell stuff is something that I'm not that fan.

Anyway, I will publish an update to fix the Original Problem, and also update the readme.md to be clear that there is a Know Issue for Linux users. And since the next Code release will have _Debian_ packages available to install, and this fixed the Opening Projects error, I will let this as a _requirement_ for the package.

I hope that doing so, every OS will be supported.

Hope this answered you :smile: