From b1275671a80d6ec2f1acb6f98b79daeb19729e5c Mon Sep 17 00:00:00 2001 From: William Carroll Date: Wed, 20 Mar 2019 18:38:02 +0000 Subject: Return (server-start) to Emacs initialization See the comment for an explanation about this revision. - we want to support to GUI - it's difficult to reuse GUI windows elegantly unless the server is started from the GUI itself - consider starting the emacs GUI when X initializes --- configs/shared/emacs/.emacs.d/wpc/packages/wpc-misc.el | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) (limited to 'configs/shared/emacs') diff --git a/configs/shared/emacs/.emacs.d/wpc/packages/wpc-misc.el b/configs/shared/emacs/.emacs.d/wpc/packages/wpc-misc.el index b3ff7dc7f475..cc7a8c86a1da 100644 --- a/configs/shared/emacs/.emacs.d/wpc/packages/wpc-misc.el +++ b/configs/shared/emacs/.emacs.d/wpc/packages/wpc-misc.el @@ -184,5 +184,22 @@ "Return the name of the current frame." (frame-parameter nil 'name)) +;; Having difficulty starting the server using systemd or calling +;; `emacs --daemon' in ~/.profile, ~/.xsessionrc, and similar files. + +;; systemd has issues syncing the socket-name, so it becomes messy. I also +;; experienced strange initialization where things like wpc-org and other +;; modules wouldn't get loaded. +;; +;; Even if I resolved the socket-name resolution issue, I couldn't find an +;; elegant way to reuse GUI frames. GUIs for me have the advantage of supporting +;; True Color, support additional keys for KBDs (i.e. super), and aren't limited +;; by the terminal for rendering certain things. +;; +;; For these reasons, it seems preferable to start the server from here. I'm +;; considering starting emacs in my ~/.xsessionrc so that the server will be +;; running after X initializes. +(server-start) + (provide 'wpc-misc) ;;; wpc-misc.el ends here -- cgit 1.4.1