keyboard shortcut needs to be configurable and have a better default about emacs_chrome

[aspiers]

Just checked again since upgrading to Chrome 6 with the unified menu, and Alt-E still brings up the Chrome menu rather than triggering the editor. Did this ever work?

[stsquad]

My mistake, the current keycode is Alt-Enter. The options page has been modified to reflect this. It is still my desire to make this completely configurable.

[aspiers]

Ahah, thanks!

[rnml]

I don't care what the default is, but I would like this to be configurable. As it is, it conflicts with a fairly important default keybinding in xmonad -- Alt+Enter swaps the currently in-focus window with master window. I can reconfigure xmonad to bind this behavior to some other key combination, leaving Alt+Enter for "Edit with Emacs", but I would rather not, as this bit of muscle memory is already burned in pretty hard.

[rubic]

I'm with @rnml. Even if Alt+Enter didn't interfere with xmonad, I would still want the keycode to be configurable. Love "Edit with Emacs", btw.

[stsquad]

If anyone can point to some good example code for capturing a keystore in the options box I'm all ears.

[spiderbit]

a related question, so your idea is when you click onto a textfield, that you then press alt+enter or something to start the emacs input.

I am a Vimium user, there are functions like:
Open a link in the current tab (LinkHints.activateMode)

Which I can press in my case "t" and then the number of all clickable including text-fields. when I select a textfield, it goes into it, after that I could press alt+enter to get to emacs buffer.

But shouldnt it be easy to have a "LinksHints.activateWithEmacsMode"

then you could customize the key over vimium to open the emacs buffer. Even much more easy without using keychords that are bad for your fingers but by jest pressing a a key like "e" for emacs or "y" or something like that.

So can you access a function from one extention through another extension? And which function in emacs-chrome would that be?

[spiderbit]

OK

1. the function would be "editTextArea"
   

   emacs_chrome/javascript/textareas.js

   Line 297 in 5e45626

   function editTextArea(event) {

2. you can't directly call functions from another extension
   So you would need to add a messagehandler I guess:
   https://developer.chrome.com/extensions/messaging#external

Would that make sense and would that at least partially fix this bug? Or go beyond that?
Should not be that hard to do, would that go into upstream?

[stsquad]

As long as it doesn't regress the current default behaviour I'll merge things to make it more configurable.

[spiderbit]

I give it maybe a try then at some point :D need to use your addon first... just installed it today... I might have already a bug, I think it does not load the input-method... but I should open a new bug for that...

I just have a few other things I want to address before that goes up my list :D

[stsquad]

I think all the keyboard triggers are now the domain of the browser itself. I've tested this on both Chrome and Firefox.