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

[2.3.2] Projects aren't listed #16

Closed
IanVS opened this issue Dec 12, 2017 · 5 comments
Closed

[2.3.2] Projects aren't listed #16

IanVS opened this issue Dec 12, 2017 · 5 comments

Comments

@IanVS
Copy link

IanVS commented Dec 12, 2017

Hi,

With the new release, it seems that my projects are not being listed as they were with 2.3.0.

2.3.2:
image

2.3.0:
image

I'm happy to provide any other information that might help in debugging, but I'm not sure what would be useful. Thanks!

@mdeboer
Copy link
Member

mdeboer commented Dec 12, 2017

Hi @IanVS, have you tried removing the workflow and reinstalling it? Please try using the release from the releases page: https://github.com/Cloudstek/alfred-atom/releases/tag/v2.3.2

If that doesn't work then please check for error messages or warnings in the debug log. You can open the debug log by opening Alfred, clicking on the workflow and clicking on the bug/spider icon in the top right corner. Leave this panel open and try to list your projects again. If anything goes wrong, you should see an error message.

But before you do, please try reinstalling first.

@mdeboer
Copy link
Member

mdeboer commented Jan 20, 2018

I'll close this due to inactivity.

@mdeboer mdeboer closed this as completed Jan 20, 2018
@ashton
Copy link

ashton commented Apr 25, 2018

Hello, I fresh installed it, and I'm having the same problem, here is a screenshot of debug log:

image

To reproduce it, I've just installed the workflow and typed "atom " with a space on alfred

I have node installed:

image

@ashton
Copy link

ashton commented Apr 25, 2018

The problem is that my nodejs binary is not in the default location, because it is installed by asdf, changing the default path on workflow object worked for me :)

@mdeboer
Copy link
Member

mdeboer commented Apr 26, 2018

Ah yes that is correct. By default it assumes NodeJS was installed with Homebrew and is located at /usr/local/bin/node. However if you have installed NodeJS at a different path you can override this path with the nodePath (case sensitive) environment variable (add it when missing).

screen shot 2018-04-26 at 14 48 02

In future versions I will default to node in the current $PATH to avoid most issues like these.

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

3 participants