o.k., to follow up on few of the questions/points made here —
a lot of this is moot at this point because, as i have said, i now installed from an apt-get package and it was working o.k. (more on that i a moment). the best thing i can tell you at this point is to try following the original instructions i link to above in this thread from the Atom github site on installing on an install of ubuntu linux 14.04 LTS yourself, and try and follow through with the final grunt file part of the install and see what happens for you. this should not be an impossible or hard task - you can install ubuntu on a usb thumb drive and run it from there.
@DavidLGoldberg - i’m not quite sure what you mean by your mention of nvm. also, i don’t know who i should file an issue with over the fact that, as @leedohm found and pointed out in the thread above, nvm doesn’t give root full acccess to node, which is why i had some of the initial install errors. do i file that here with Atom editor issues? with nvm? both?
@DavidLGoldberg - i will try, when i can, the install apm tools within Atom and see how that goes, thank you for the suggestion.
@abe - i don’t know how it came up in this thread, originally with @leedohm, or where anyone got the idea, it wasn’t from me, but i never put the Atom install in the linux
/tmpdirectory nor did i create a
/tmpdirectory and put anything into it. i downloaded the Atom
*.tar.gzfor linux and it went into my ubuntu linux
/home/faddah/Downloadsdirectory, and from the command line, after extracting it, i started the install from there, all the way through up to the problem with the script/grunt file. as everything seemed to be installed to the
/usr/local/bindirectory, i didn’t think that would be a problem. should i have moved the Atom install directory elsewhere, and to where, before i started the install from the command line? if yes, the instructions need to be re-written to explicitly state this.
@abe - i did not run the
--debug --stack --verboseas the instructions don’t say to and no one in this thread said to try it before this, and, as i say above, i’ve all ready installed Atom now with an apt-get package. is this something you want me to try? will it screw up my current Atom install if i try that?
@abe - i don’t have
locate, i have
sudo find / -name "atom.sh" 2> /dev/nullreturns —
sudo ls /tmp/atom-build/Atom returns —
ls: cannot access /tmp/atom-build/Atom: No such file or directory
…but this is to be expected, because, as i say above, i never put the Atom install in a
/tmp directory nor did i ever say i did. and
sudo find / -name "atom-build" 2> /dev/null returns nothing.
- finally, my install of Atom got bork’d. the ubuntu update manager told me there was an update for Atom, from 0.139.0 to 0.140.0, through the PPA i put in for the Atom package, so i went for it. ever since then, every time i bring up atom, i can’t get the settings window or any file, and the dev tools immediately shows a loooooooooong stack trace at start up with things about conflicts with the package manager and the Atom start window. so i don’t know what to do at this point. maybe re-install and lose all the packages i’ve put in so far.
sigh. that’s where it stands. this is why i say the linux installs and updates need to be looked at and made far simpler/cleaner.
— faddah wolf
portland, oregon, u.s.a.