emacs_chrome icon indicating copy to clipboard operation
emacs_chrome copied to clipboard

Win7 not transfer text through edit-server

Open cmal opened this issue 9 years ago • 9 comments

I've been working with edit-server for years and it works well on my mac. but when I try to use it on Win7, edit-server not transfer text to emacs. The buffer has been created in emacs but there is nothing in. And the text i input into the buffer will not transfer to chrome, either. I've tried multiple versions of emacs: 24.5.1, 25.0.9, babun emacs 24.5.1, 24.5.2, and all have the same problem. Could you please help me with this? Thanks and thank you for your excellent work.

cmal avatar Jul 23 '16 09:07 cmal

Please run M-x edit-server-stop and C-u M-x edit-server-start to enable logging and paste your logs here when it fails.

stsquad avatar Jul 04 '17 15:07 stsquad

Thanks for working on this exciting project. I'm having the same experience as @cmal . Here are the contents from the *edit-server-log* buffer. I opened a non-empty textarea via the extension and the buffer was empty. I added some new text and did C-C C-C, and the buffer closed but the textarea did not change.

There was no "Edit" button next to the textarea, but I was able to use the context menu to invoke the extension. I see the same behavior whether the extension icon is purple or green (when I click on it).

Google Chrome: Version 65.0.3325.181 (Official Build) (64-bit) Emacs: 25.3.1 (x86_64-mingw32) of 2017-09-26 edit-server-20180120.752 via melpa

Sun Apr  8 15:08:15 2018 Created a new edit-server process
Sun Apr  8 15:08:25 2018  *edit-server*-352774: accept from 127.0.0.1
Sun Apr  8 15:08:25 2018  *edit-server*-352774: Got HTTP `POST' request of url `/undefined', processing in buffer ` *edit-server*-352774'...
Sun Apr  8 15:08:25 2018  *edit-server*-352774: Found x-file: undefined
Sun Apr  8 15:08:25 2018  *edit-server*-352774: Processed headers, length: 0, url: C:/Users/nifr/text-edit.html, file: undefined
Sun Apr  8 15:08:25 2018  *edit-server*-352774: using buffer C:/Users/nifr/text-edit.html for edit (existing-buffer is nil)
Sun Apr  8 15:08:25 2018  *edit-server*-352774: copying new data into buffer
Sun Apr  8 15:08:25 2018 Creating frame for w32/w32
Sun Apr  8 15:08:48 2018  *edit-server*-352774: sending edit-server response
Sun Apr  8 15:08:48 2018  *edit-server*-352774: Editing done, sent HTTP OK response.
Sun Apr  8 15:08:48 2018  *edit-server*-352774: sent response to browser
Sun Apr  8 15:08:48 2018  *edit-server*-352774: sending edit-server response
Sun Apr  8 15:08:48 2018  *edit-server*-352774: Editing done, sent HTTP OK response.

nfrisby avatar Apr 08 '18 22:04 nfrisby

Huh. The buttons show up and the tool works if I do the Chome -> Extensions -> Developer Mode and load the unpacked master branch e1f86b4ff0b8b872a121287bde4875a7c3c4f8e2 as a "local" extension.

nfrisby avatar Apr 08 '18 22:04 nfrisby

OK that is a bit weird. There is only one commit above the last release and I don't see how that affects things.

Looking at the log something odd is going on because the edit-server reports it got a 0 byte buffer which shouldn't be the case if there is already text in the text area.

stsquad avatar Apr 09 '18 08:04 stsquad

The absence of the "Edit" buttons (with the Chrome store version, not the local Dev version) makes me suspect the extension isn't even finding the textareas eg. Hence JavaScripts "undefined" showing up in the emacs logs?

On Mon, Apr 9, 2018, 01:05 Alex Bennée [email protected] wrote:

OK that is a bit weird. There is only one commit above the last release and I don't see how that affects things.

Looking at the log something odd is going on because the edit-server reports it got a 0 byte buffer which shouldn't be the case if there is already text in the text area.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/stsquad/emacs_chrome/issues/122#issuecomment-379668990, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDg0_uZS7rVRznPPUjHfMRRxs7su2D8ks5tmxZGgaJpZM4JTU-u .

nfrisby avatar Apr 09 '18 15:04 nfrisby

The edit button is looked up by the extension using:

chrome.extension.getURL("icons/gumdrop.png")

Which should calculate the proper path for the icon....

stsquad avatar Apr 09 '18 17:04 stsquad

I'm suggesting that the node for the button is not even being added to the DOM near the textarea.

On Mon, Apr 9, 2018, 10:46 Alex Bennée [email protected] wrote:

The edit button is looked up by the extension using:

chrome.extension.getURL("icons/gumdrop.png")

Which should calculate the proper path for the icon....

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/stsquad/emacs_chrome/issues/122#issuecomment-379835854, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDg0_XpDHqnzroHLwjdPASufaRWngWWks5tm56BgaJpZM4JTU-u .

nfrisby avatar Apr 09 '18 19:04 nfrisby

@nfrisby @cmal @stsquad did you ever manage to resolve this? I'm currently experiencing too, also on Windows 7

xeijin avatar Jun 14 '18 18:06 xeijin

Ironically I just right-clicked this GitHub comment text area and choosing "Edit with Emacs" and it now works, but doesn't seem to work anywhere else (e.g. Google.com searchbox, the text area from the w3schools html text area tutorial, etc)

Though it still doesn't show me any button to edit near the text box.

xeijin avatar Jun 14 '18 19:06 xeijin