I have searched the group for answers to my question, but didn't find any 
relevant ones. So I have to 'bother' you with this problem.

The system (apt) has installed nodejs and npm in '/usr/share. '  Npm 
install -g elm has installed Elm like this:  
'usr/share/lib/node_modules/elm/Elm-Platform/0.17.1/.cabal-sandbox/bin/' 
->elm, elm-make, -package, -reactor, -repl (runnables). 
Under the 'usr/share/lib/node_modules/elm/binwrappers/' there are 
text-files with the same name as the runnables.
Under 'usr/share/lib/node_modules/elm/node_modules/'  are lots of files 
(yes, there are 2 'node_modules' directories in the same hierarchy).

The 'usr' and the 'lib' directories are owned by root, but the rest down 
the hierarchy are owned by me, the user.

 Issuing commands at the prompt:  npm --version -> 3.5.2,  node --version 
-> v4.2.6                                                             

But issuing elm-commands (elm-make --version) at the user-prompt only 
produces 'no such file or directory'

When I CD to 
usr/share/lib/node_modules/elm/Elm-Platform/0.17.1/.cabal-sandbox/bin 
$ and isssue  'elm-make' or elm-repl,' I still get 'no such file or 
directory.'  When I issue the 'ls' command, the 
elm, elm-make, -package, -reactor, -repl  are listed in green colour, as if 
they were directories.

I have asked the author in the book-forum, but of course there are many 
variations of this problem, and mine may be relevant only to Mint 18-users 
(and Ubuntu users).

Any ideas?

regards
audun

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to