You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if I open two instances of emacs, the use-package call fails because the address is already in use:
Cannot bind server socket: Address already in use
The example README.md could be modified to wrap the use-package call within a with-demoted-errors so that emacs starts up normally, but then org-hyperscheduler-open can be called only from the first instance of emacs.
Should there be an unique server per machine? One server per instance of emacs? Is this wrapper enough?
The text was updated successfully, but these errors were encountered:
One workaround for this could also be to use emacs in its own server-client mode. If you just want multiple emacs editor windows, then running multiple emacsclient windows that all connect to the single emacs server daemon works extremely well and has other benefits (clients open near instantly, all emacs windows share buffers/state, etc.) So for this problem, the emacs daemon would run the hyperscheduler server, and calls to org-hyperscheduler-open would just open the existing server rather than run a new server.
Currently if I open two instances of emacs, the
use-package
call fails because the address is already in use:The example README.md could be modified to wrap the
use-package
call within awith-demoted-errors
so that emacs starts up normally, but thenorg-hyperscheduler-open
can be called only from the first instance of emacs.Should there be an unique server per machine? One server per instance of emacs? Is this wrapper enough?
The text was updated successfully, but these errors were encountered: