Thanks for the suggestion. I just tried it, and it behaves exactly the same. Really, though, I should have written the rule your way in the first place; the regexp is a bit of a sledgehammer in this case.
For matching pages, I'm always seeing the script appear in the Greasemonkey menu with a checkmark, even when the script does not execute. I would think that means that the matching rule is working properly. But I'll try anything you suggest at this point. Next? :) - Neil On May 6, 2012, at 8:38 PM, LWChris@LyricWiki wrote: > Am 07.05.2012 02:23, schrieb neilw: >> // @include /^https://.*\.rallydev\.com/.*/changesets$/ > > As this pattern can also be modelled with usual placeholders, it might be > worth to test if this behaviour also occurs if you don't use regular > expressions. Please try this rule: > >> // @include https://*.rallydev.com/*/chagesets > > RegExp is a rather new feature and the placeholders worked flawlessly for me > so far. > > Chris > > -- > You received this message because you are subscribed to the Google Groups > "greasemonkey-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/greasemonkey-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.
