search

chuckhendo / project-quick-open

A quick view of all projects inside your 'project home' in Atom
MIT License
13 stars 4 forks source link

error message #5

Closed maxheld83 closed 9 years ago

maxheld83 commented 10 years ago

I get this: 

Window load time: 1402ms /Applications/Atom.app/Contents/Resources/app/src/window-bootstrap.js:18
Uncaught TypeError: Cannot read property 'length' of undefined project-quick-open-view.coffee:36
mattholmes commented 10 years ago

if the problem you are having is what i think it is, then there isnt actualy anything wrong with the plugin but the path it is looking for your projects in cant be found, to make sure you can add the following line to project-quick-open-view.coffee console.log(err, files) after the line fs.readdir projectPath, (err, files) =>

if in the stack trace you get a message of "ENOENT" then it is a file not found error. to fix it just update your project root in settings

hope this helps

chuckhendo commented 10 years ago

@mattholmes is exactly right - this is probably due to the path not existing. v0.2.2 now defaults to the home folder if a project path isn't set, and if a wrong path is set, it will now display an error message. Can you take a look to see if it's working better now?

mattholmes commented 10 years ago

unfortunately i cant install/update the latest version

Error: Unable to download https://www.atom.io/api/packages/project-quick-open/versions/0.3.0/tarball: 404

i dont have time today play around with it but i will take a look at it properly tomorrow and get back to you

EDIT: i just realised that the latest version is 0.2.2 and atom is looking for version 0.3.0 wich is presumably why it wont update or install

chuckhendo commented 10 years ago

That's odd. I went ahead and published with a 0.3.0 tag - when you get a chance, could you try again?

mattholmes commented 10 years ago

it downloads properly wit the 0.3.0 tag, if i leave the project root empty (using default) for some reason it tries to use "C:\etc\passwd" as my project root.

Not sure why this is as even if i was running a linux system thats not a file i want atom to be accessing

chuckhendo commented 10 years ago

Yeah that's odd. I haven't tested it on Windows yet, but I'll take a look. The default is set to use "~" and I'm using the node-tilde-expansion package, so I wonder if it's an issue upstream with that.

chuckhendo commented 9 years ago

For what it's worth, I believe I've fixed this with 0.4.1. Let me know if you continue to have issues with it