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
Describe the bug
I use doom emacs and have configured org-roam ui as follows:
(use-package! websocket
:after org-roam)
(use-package! org-roam-ui
;; :after org-roam
:hook (after-init . org-roam-ui-mode)
:config
(setq org-roam-ui-sync-theme t
org-roam-ui-follow t
org-roam-ui-update-on-save t
org-roam-ui-open-on-start nil))
When I open a 2nd instance I receive the error that the address is already in use. A consequence of org-roam-ui being initialised a second time.
My attempts to remedy the problem failed so far. I'd like to only start org-roam-ui when it is not yet running. org-roam-ui-open-on-start is obviously to late. And my attempts with hook failed. Please suggest how that could be avoided and if necessary update the documentation in the README.
The text was updated successfully, but these errors were encountered:
Hello, did you ever find a fix for this? I've tried using other pulls of org-roam-ui with my doom config, and I still get the "address already in use" error. Seems like Issue #202 references this same issue, but I'm not able to implement their patches
@adieundie No, so far I had no look. It does not seem to be related to desktop. When I start my emacss with emacs --no-desktop the error persists. Trying to disable the desktop-save-mode in my config.org also did not affect the bug.
Describe the bug
I use doom emacs and have configured org-roam ui as follows:
When I open a 2nd instance I receive the error that the address is already in use. A consequence of org-roam-ui being initialised a second time.
My attempts to remedy the problem failed so far. I'd like to only start org-roam-ui when it is not yet running.
org-roam-ui-open-on-start
is obviously to late. And my attempts with hook failed. Please suggest how that could be avoided and if necessary update the documentation in the README.The text was updated successfully, but these errors were encountered: