Userscripts.org

oh my god!
In the post window, "alt + B" can work smartly without openning the bookmark_menu!
And out of post windows "alt + B" would just open the bookmark_menu.
How do you achieve? I love you!

all the shortcut can work rightly now. thank you!

I made one change to my script at line 100: case 80:this.value=before+"<pre>\n"+selected+"\n</pre>"+after;break;

If you don't add new line's between the code and the pre tag's, the code displays weird.

ok .. i know you've been through all this.. but maybe u can set it to SHIFT + ALT... that shourtcut is rarley used..

sizzlemctwizzle wrote:
having problems with the current shortcuts?

• Optionally open the reply to topic box
• Optionally select text in the DOM body with mouse
• Click Quote under the gravatar
• Click to focus in the reply to topic box (if text cursor isn't there already)
• Select text in the reply to topic box
• Use "Hot keys" or click lettered links to the right to put the html tags around what is selected

sizzlemctwizzle wrote:
why would you use the hot keys outside of the reply box?

sizzlemctwizzle wrote:
I'm not accessing GM_getValue or GM_setValue with unsafeWindow.

sizzlemctwizzle wrote:
I have this update code in another script that uses unsafeWindow and it has never produced that error either.

sizzlemctwizzle wrote:
Well I might actually be able to add that shortcut if you want.

sizzlemctwizzle wrote:
This version includes some UI changes, the dynamic page lengthening feature, and added a @namespace

sizzlemctwizzle wrote:
catching some

Kewl CSS styling btw :) will load up a scums script and see if it works there too ;) *GRIN* Looks good for just yours... multiple pages were hiding the prev/next on prior install of your script with the static page lengthening... but appears to be well now. WOOT WOOT! :)

You da man!!! Even works with a scum's script enabled too... here's Joe's script test too:

the wiki

OMG! I think you can all play nicely together now. hehe nice job! Now if I could just get Joe to change his script like I suggested him to.

sizzlemctwizzle wrote:
so I didn't have to type all the words exactly for them to be replaced.

sizzlemctwizzle wrote:
Can't win 'em all ;)

bold bold strong underline italic underline ins strike del wussup gosubsubby http://example.com over thereexample dot org

sizzlemctwizzle wrote:
You're lazy like me lol

Error: document.evaluate("//a[@class='utility']/child::text()[.='Reply to topic']", document, null, 9, null).singleNodeValue is null
Source file: file:///~/.mozilla/firefox/{randomseed}.default/gm_scripts/userscripts_comments_fix/userscripts_comments_fix.user.js
Line: 241

sizzlemctwizzle wrote:
but still not the access violations

Error: Greasemonkey access violation: unsafeWindow cannot call GM_getValue.

No line number so it's out of GM's normal "scope"... which typically means it's the DOM or the browser.

...
pb.addEventListener("focus",    function(e){ fix(e); }, false);
...
epb.addEventListener("focus",    function(e){ fix(e); }, false);
...

If I comment out just your entire autoupdater code and leave Joe's untouched then I also don't get the Access Violation.

I would make a partial guess that your script is triggering his focus event listener where he set's GM_getValue and that trigger is where the Access Violation comes into play.

Any other ideas why it would be doing this?

sizzlemctwizzle wrote:
I installed Joe's script and I'm getting it too when I click "Reply to Topic".

Modified GM to actually tell me the source of the violation (This should be in GM but I can only guess advertising the source of a violation hasn't been addressed? Ticket #254 entered)

The actual violation is coming from multiple locations depending on context.

Click Quote anchor with no selection highlighting OR Reply to topic anchor

Error: Greasemonkey access violation: unsafeWindow cannot call GM_getValue.
Source: http://static.userscripts.org/javascripts/all.js?1240391508

Select text to quote, then click Quote anchor

Error: Greasemonkey access violation: unsafeWindow cannot call GM_getValue.
Source: javascript:$("post_body").focus();

Some of this may pertain to this post in that topic about Prototype... but your script is definitely triggering it as well.

@sizzlemctwizzle Is there any way you can retool your portion of your code?