Jump to content

Alfred VSCode Workspace Explorer


Recommended Posts

Alfred workfow to search, expore and open VSCode workspaces.

Requirements

  • Python 3
  • VSCode

Setup

Define path (workspaces_home) where VSCode workspaces are stored. The workflow also supports subdirectories in VSCode Workspace folder

Set workspaces_home e.g. to /Users/user/vscode-workspaces

 

Download on Git

Edited by Acidham
Link to comment

This seems useful, but I get the error 

ERROR: VSCode Workspace Explorer[Script Filter] Code 127: env: python3: No such file or directory

I realize that it is likely due to that Python 3 is not the deafult version in macOS (using version 10.14.6). I have Python 3 installed in some different environments using Anaconda, but I don't know how to get Python 3 as the default version used by macOS. Any tips how this can be fixed? 

Link to comment
  • 2 years later...

Hello,
 

after yesterday's update to Mac OS 12.3.1, the VSCode Workspace Explorer workflow is failing. 

 

Error message: 

Quote

 

Unable to run task!
Reason: Couldn't posix_spawn: error 2

The external script may not exist, or doesn't have execute (+x) permissions.

Related Workflow Info...
Name: 'VSCode Workspace Explorer'

Folder: ...

 

 

 

Alfred is up to date (4.6.4).
I checked the rights in the control panel and reassigned them.

 

I have uninstalled and reinstalled the workflow.

No improvement.

 

All my attempts to get the workflow working again have failed so far and I don't know what to do.
 

All best

Martin

 

Link to comment

@Giesskanne When making a request or a bug report pertaining to a specific workflow, please do not open a new thread. While it may seem like a new thread gives your problem visibility, in truth it fragments the discussion and makes it less likely the author and users of the workflow (the people who can help) will see it.

 

I’ve moved your post to the Workflow’s thread.

Link to comment

 

On 4/11/2022 at 3:11 PM, vitor said:

@Giesskanne When making a request or a bug report pertaining to a specific workflow, please do not open a new thread. While it may seem like a new thread gives your problem visibility, in truth it fragments the discussion and makes it less likely the author and users of the workflow (the people who can help) will see it.

 

I’ve moved your post to the Workflow’s thread.

Hi Vitor,
as a newbie I did not know this rule.
Rather, I had thought that I had to open a new thread for a new problem so that another thread would not become offtopic or lead to confusion.
Please excuse my mistake.
 

Edited by Giesskanne
Link to comment
On 4/11/2022 at 4:49 PM, Acidham said:

The error comes due to the OS changes from Apple around python. I updated the workflow on git. Let me know if it works. 

I have reinstalled Python as told in Python 2 and macOS Monterey.
Unfortunately without success.
 

But your update on git did it.
Now the workflow  is running fine again.

Thank you very much!

All best
Martin

Link to comment
10 minutes ago, Giesskanne said:

Hi Vitor,
as a newbie I did not know this rule.
Rather, I had thought that I had to open a new thread for a new problem so that another thread would not become offtopic or lead to confusion.
Please excuse my mistake.

 

 No harm done. Just please take it into consideration for future posts. I certainly understand you logic, but doing it this way (all posts relating to a Workflows in their own thread) ends up being more effective to everyone. Thank you for understanding.

 

10 minutes ago, Giesskanne said:

But your update on git did it.
Now the workflow  is running fine again.

 

That’s the correct approach. When there’s an official update, reinstalling Python 2 no longer applies to that specific Workflow.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...