QuickCursor + Google Chrome + TextMate

[Ben Woodruff]

Hi there,

Having major issues with QuickCursor on a new computer (rMBP). My setup:

OS X 10.8.2 (relatively fresh install)

TextMate 1.5.11

Google Chrome 22.0.1229.79

QC 2.7 (33)

I have QC set to open TextMate with Cmd+Opt+Shift+T.

If I open up a page in Chrome (I use Cerberus Helpdesk a lot, but any text area causes the same behavior, including the awesomebar), and activate QC+TM using the above mentioned shortcut, TM opens but opens a new document that does not contain the text from the text area used to activate QC. I've also tried it by doing a Cmd+a before activating QC+TM but it doesn't seem to make any difference. I'll also note that it doesn't matter if I use the keyboard shortcut or the menubar icon to activate QC. When this happens QC itself hangs. If I quit TM I'm prompted as to where to save the document (unexpected behavior).

A sample of QC while hung after such an attempt can be found here:

http://pastebin.com/Kamrxpk1

If I use QC to activate Writeroom (MAS verison) it properly creates a new file in the temp folder and copies the text from the text area in Chrome into the file. It still does not however fill back into Chrome when quitting Writeroom.

I have the same issue in Firefox 15.0.1. I have not tested elsewhere but would be happy to if you'd like.

Thank you.

Ben

[Ben Woodruff]

I read this thread: https://groups.google.com/forum/?fromgroups=#!topic/quickcursor/10zVw5jyD-s but since none of Chrome, TextMate, or Firefox are from the MAS I don't believe they are sandboxed and shouldn't necessarily have issues.

[Grey]

We're looking into this as a possible culprit: http://mjtsai.com/blog/2012/10/04/aesendmessage-bug-in-mac-os-x-10-8-2/

--
You received this message because you are subscribed to the Google Groups "QuickCursor" group.
To view this discussion on the web visit https://groups.google.com/d/msg/quickcursor/-/dNau5ORtRWcJ.
To post to this group, send email to quick...@googlegroups.com.
To unsubscribe from this group, send email to quickcursor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/quickcursor?hl=en.

[Ben Woodruff]

That adds up, as killing the appleeventsd process appears to fix the issue, if only temporarily. Thanks for the tip.