When I used scriptish, I could alter script @includes at the next tab to the user includes (and excludes). I use one script that has
// @include * in its body. And I can’t do anything to prevent it running on ALL sites I visit, except editing the file to manually replace its directive with my own particular @includes each time a new update releases, because the only way to override script includes greasemonkey encourages you to is adding '*' from script includes to user excludes, and taking into account that excludes take precedence over includes, this leads to excluding ALL websites, including those where I’d want this script to be working. That’s bothersome. I want to override it once and for all. I’ve contacted the developer of the script, but I couldn’t convince him to change the rules, because he thinks that since his script runs on many variations of a bunch of site engines, it’s hopeless to try to set particular includes globally, because it’d cause problems on domain yet unknown to the author, where the script should be working fine. But it causes _me_ problems _right now_, because this script breaks other sites to which it is not related to and shouldn’t run there. And, while I had complains, I could just override script includes in scriptish, all I have now is to damn manual editing? Continuing using scriptish is not an option, because I actually use Palemoon, and scriptish support has been removed in v25. -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/d/optout.
