Alex Bennée

Sure, I've uploaded a update to the git repo. ``` (setq edit-server-host "10.0.0.166") ``` To enable edit-server.el binding to a specific IP rather than localhost. I've defaulted to localhost only...

BTW, although the edit server can now bind to a non-local port the permissions in the manifest will stop Chrome from sending it's request beyond localhost. I'm happy to do...

Ahh I think we have a documentation or UI errror. That is because Command+e issues a foreground command which was added to bring Emacs to the foreground with the contents...

I've just realised the keyboard shortcut isn't enabled by default - it in the extension configuration tab under settings/configuration/interface and the check boxes for the enabling the various methods to...

Hmm interesting. I've just posted a test branch which cleaned this up a bit but as you point out the default active-extension seems to DTRT which is slightly confusing to...

It's likely the web-pages have changed the way they handle text areas. Have you got some specific URLs I can check? Does it still work on other sites? For example...

OK well that's unexpected (and works for me) and also probably a JavaScript issue. If your getting the colour fade then the text has been posted back so it's a...

Interesting. It seems you have discovered a different bug which is that the "edit focused textarea" feature got broken when I re-factored the code. However it doesn't explain the failure...

Essentially it's a few simple steps: git clone git://github.com/stsquad/emacs_chrome.git /path/to/somewhere disable the Edit with Emacs extension in chrome://settings/extensions in chrome://settings/extensions select Load Unpacked Repository and point it the cloned repo

Did you run that with the console open? I would hope at least a few of the errors went away.