I will try to hack the hell out of everything I can to make that env variable available by default ... please release a gjs that doesn't bother developers with tool-chain/deployment related tasks like any linter would be: it's not your responsibility to tell people how to write **valid syntax**
Thank You!!! On Sat, Apr 9, 2016 at 8:18 PM, <philip.chime...@gmail.com> wrote: > > > On Sat, Apr 9, 2016 at 12:08 PM <philip.chime...@gmail.com> wrote: > >> Hi Andrea, >> >> On Sat, Apr 9, 2016 at 11:31 AM Andrea Giammarchi < >> andrea.giammar...@gmail.com> wrote: >> >>> Since I've received zero answers on this one, I've assumed there was no >>> way to do that. >>> >> >> I'm sure there is a way, but I just had no time to investigate this week. >> Sorry. >> >> I believe the "internal linter" is a SpiderMonkey thing, not GJS, so it >> would be more a question of whether GJS would accept a patch to disable it. >> > > ...aaaand I found the answer in scarcely more time than it took me to > reply to your email :-) > > GJS_DISABLE_EXTRA_WARNINGS=1 gjs myprogram.js > > https://git.gnome.org/browse/gjs/tree/gjs/jsapi-util.cpp#n88 > > It is indeed a SpiderMonkey feature that GJS turns on by default. Still, > it would be nice to disable it per file or something. > > Regards, > Philip >
_______________________________________________ javascript-list mailing list javascript-list@gnome.org https://mail.gnome.org/mailman/listinfo/javascript-list
