Closed peter-b closed 8 years ago
I'll see what I can come up with. It is documented that it needs to be accessible so I guess silently failing would be sufficient.
@peter-b I separated these commits so you could decide on the behavior you want to pull. The warning is nice but could be annoying if you didn't want to use the linter.. Although I wonder why you would have the linter package installed and yet not want to use it on livecode files...
Currently, if there's no
livecode-server
in the$PATH
and the user hasn't configured package, opening a.livecodescript
file triggers a scary uncaught exception error.The exception should be caught and an informational warning should be shown, directing users to the settings.
Probably another one for @montegoulding?