Closed sebhahn closed 7 years ago
I already identified the problem. It is coming from
;; theming-modifications
;; '((sanityinc-tomorrow-eighties
;; ;; Font locking
;; (font-lock-string-face :foreground "#99cc99")
;; (font-lock-type-face :foreground "#cc99cc")
;; (font-lock-function-name-face :foreground "#6699cc"))
;; (base16-tomorrow-dark
;; (default :background "#2d2d2d")))
which is just written above. As soon as I uncomment the custom theme modification the bug occurs.
@TheBB Do you have any info about this?
@sebhahn Can you show me exactly where you put that code in your dotfile?
Actually I can reproduce something similar, but it appears to work (that is, to not work) independently of the theming
layer. Instead I get a different font in the new frame if I set dotspacemacs-default-font
to something that is not equal to the system monospace font.
@sebhahn if you use the default Spacemacs font (Source Code Pro), do you still have the problem ?
yes, e.g. if I change the default font size, the font size will be different in the new frame
I have the same issue on OS X. The font in the other frame doesn't appear to be a monospace font.
I have the same issue on archlinux, with spacemacs on develop branch.
I can't reproduce this any more in 0.200
I'm using the following code in my .spacemacs file to set a custom font, which works without a problem. But once opening a new frame with
C-x 5 2
the font is different in the new frame! Is this a bug?