anyway to disable warning "Error (use-package): atomic-chrome :config: Cannot bind server socket: Address already in use" when opening new emacs?

[zeltak]

Hi again

first of all again thx so much for your work, i use it daily

this is a minor annoyance but when i launch emacs standalone (alongside my current running emacs deamon) for testing i always get the annoying pop up

Error (use-package): atomic-chrome :config: Cannot bind server socket: Address already in use

is there anyway to have a user option to disable that error?

best

Z

[alpha22jp]

Hi @zeltak

The cause of the error message is that the TCP port the websocket server uses is already opened by atomic-chrome.el running on another Emacs session. I think the only way to surpress it is to call atomic-chrome-start-server manually when you use atomic-chrome.

[tarsius]

Could you add a function that checks whether the port is already in use? This would allow replacing (atomic-chrome-start-server) in a users init file with something like (unless (atomic-chrome-port-used-p) (atomic-chrome-start-server)). Thanks!

[alpha22jp]

@tarsius Do you know how to check the port is already in use?

[tarsius]

No, I don't.

[xuchunyang]

@alpha22jp you can try lsof (I learn this via https://emacs-china.org/t/emacs/2523/7):

$ lsof -i :64292
COMMAND     PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
Emacs     67526  xcy   38u  IPv4 0x3e7b015e5d724521      0t0  TCP localhost:64292 (LISTEN)
Emacs     67526  xcy   43u  IPv4 0x3e7b015e50bb2901      0t0  TCP localhost:64292->localhost:58940 (ESTABLISHED)
Google    69929  xcy  217u  IPv4 0x3e7b015e50bb0521      0t0  TCP localhost:58940->localhost:64292 (ESTABLISHED)

and from Lisp

(defun atomic-chrome-server-running-p ()
  (zerop (call-process "lsof" nil nil nil "-i" ":64292")))

For use-package, I think it is reasonable to use :defer N to reduce emacs-init-time because of the workflow of atomic-chrome.

[tarsius]

Also see #22.

[dakrone]

Perhaps do the same thing server-running-p does?

(delete-process (make-network-process :name "atomic-client-test" :host "localhost" :noquery t :service "64293"))

It'll throw an error if there's nothing running on port 64293, otherwise it'll silently succeed.

[alpha22jp]

@zeltak @dakrone

I think #40 resolved this issue.

[iagogv3]

I got this issue (because I opened an emacs session when I already had another opened), so it seems #40 did not solve the issue. Which would be the current status?