If unicode-fonts-setup errors (such as if the eieio cache is
corrupted), emacsclient behaves confusingly by opening both a
graphical frame and a terminal frame.
You can reproduce this scenario by corrupting
~/.emacs.d/.cache/pcache/unicode-fonts (such that is no longer valid
Lisp syntax) and then starting Emacs with emacsclient -ca ''.
Also remove an unnecessary require, since unicode-fonts-setup is
autoloaded.
If
unicode-fonts-setup
errors (such as if the eieio cache is corrupted), emacsclient behaves confusingly by opening both a graphical frame and a terminal frame.You can reproduce this scenario by corrupting
~/.emacs.d/.cache/pcache/unicode-fonts
(such that is no longer valid Lisp syntax) and then starting Emacs withemacsclient -ca ''
.Also remove an unnecessary require, since
unicode-fonts-setup
is autoloaded.