Closed the-nipper closed 5 years ago
Is this still an issue, because I'm using Emacs / atomic-chrome on Linux and it works for me.
Emacs 26.1 atomic-chrome.el v2.0.0 GhostText: 17.12.11.910 Firefox: 64
Also using Emacs / atomic-chrome on Linux with no problems:
Browser: Firefox 64.0 on Ubuntu 18.04 Editor: Emacs 25.2.2
@bfred-it this issue can probably be closed as stale.
Please anybody post their emacs config 'cause it's not working (as per OP's report) with my setup: Emacs-26.1 + FireFox Quantum 64.0 :-(
@sphakka my entire setup is
atomic-chrome
Emacs packageM-x atomic-chrome-start-server
in the Emacs instance where I want the GhostText buffers to appear.The issue is the port number: apparently no other value than 4001 works (nmap confirms) -- possibly an atomic-chrome's bug. @ntc2, could you please try a different port?
@sphakka could you give more detail on the setup you want me to try? Looking at that bug you link to I see
(setq atomic-chrome-server-ghost-text-port 4441)
Is that the only setting you want me to try? Or should I also change some port setting in the GhostText browser plugin?
@ntc2, the port number must also be changed in GhostText: it's the only option available at the bottom of the addon's preferences page.
@sphakka Changing the port works for me in Firefox. Steps:
M-: (setq atomic-chrome-server-ghost-text-port 4567)
.M-x atomic-chrome-start-server
.I can still edit text areas in Emacs using GhostText with this setup.
Software versions:
No issue anymore with Firefox 65.0.1, Ghosttext 17.12.11.910
Thank you all.
All right for me too -- I had the start
statement in the wrong position ^-^
Setup
System: Linux kernel 4.4.0 64bit Browser: Chromium 63. / Firefox 57.0.4 / Waterfox 55. Editor: Emacs 24.5.1
Description
Imported GhostText in all three browsers, and setup Emacs with atomic-chrome package.
Port 4001 is set. tcpdump shoes traffic on :4001 when Chromium is used, but no activity when Firefox/Waterfox is used