Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Font size and powerline separator are wrong when starting GUI frame from daemon #4816

Closed
apaleslimghost opened this issue Jan 26, 2016 · 13 comments
Labels
Question Running as daemon stale marked as a stale issue/pr (usually by a bot) Visual

Comments

@apaleslimghost
Copy link

screenshot 2016-01-26 10 40 36

Left is started from daemon, right is standalone. The issue still occurs on develop. I realise several similar issues (#299, #1894, #2652) have been raised, but I'd thought they were all resolved 😕

System Info

  • OS: darwin
  • Emacs: 24.5.1
  • Spacemacs: 0.105.9
  • Spacemacs branch: nil (rev. 5fab8e8)
  • Distribution: spacemacs
  • Editing style: vim
  • Completion: helm
  • Layers:
(emacs-lisp osx syntax-checking vinegar javascript version-control php shell-scripts html themes-megapack
            (auto-completion :variables auto-completion-enable-help-tooltip t auto-completion-enable-sort-by-usage t)
            quarterto react markdown
            (shell :variables shell-default-shell 'ansi-term shell-default-term-shell "/usr/local/bin/zsh"))

Edit: if it helps, here is my .spacemacs. My configuration layer is also in that repo.

@TheBB
Copy link
Contributor

TheBB commented Jan 26, 2016

I can't see this screenshot.

@apaleslimghost
Copy link
Author

Apologies, reuploaded

@StreakyCobra
Copy link
Contributor

Fastly error: unknown domain: butt.githubusercontent.com. Please check that this domain has been added to a service.

Refreshed the page again and it works now.

@TheBB
Copy link
Contributor

TheBB commented Jan 26, 2016

https://github.com/quarterto/.spacemacs.d/blob/master/.spacemacs#L225

You have to do this after the GUI frame is created, not before.

(spacemacs|do-after-display-system-init
  (setq powerline-default-separator 'slant))

@apaleslimghost
Copy link
Author

What about the font size?

@TheBB
Copy link
Contributor

TheBB commented Jan 26, 2016

I don't know…

@apaleslimghost
Copy link
Author

Quick update: I tried spacemacs/set-default-font in spacemacs|do-after-display-system-init and it had no effect.

@spijet
Copy link

spijet commented Jan 28, 2016

It seems that the only way for now is to start Spacemacs with emacsclient -c -a "". Just checked it, powerline separators get re-set to default ones after frame is created.

@shuokay
Copy link

shuokay commented Apr 12, 2016

I incidentally find a way to solve this problem when trying to find a way to use the solaried theme, I record here in case someone need.

  1. Disable the spacemacs themes-megapack by removing it from dotspacemacs-configuration-layers
  2. Add color-theme-solarized to dotspacemacs-additional-packages
  3. add the following lines to dotspacemacs/user-config ()
(set-terminal-parameter nil 'background-mode 'dark)  
(set-frame-parameter nil 'background-mode 'dark)   
(spacemacs/load-theme 'solarized)  

I think this problem is caused by the themes-megapack,
but I didn't confirm it.

@jcf
Copy link

jcf commented Oct 25, 2016

To fix the font size issue I added the following snippet to my dotspacemacs/user-init function:

(setq default-frame-alist '((font . "Source Code Pro-14")))

http://superuser.com/questions/721634/different-font-size-when-running-emacs-and-emacsclient

Update: To make sure I don't trample other frame configuration, like presence of scrollbars, I'm using the following function to set the font:

(defun jcf/set-frame-font (s)
  (add-to-list 'default-frame-alist `(font . ,s)))

HTH.

liweitianux added a commit to liweitianux/dotfiles that referenced this issue Feb 7, 2017

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
@panicbit
Copy link
Contributor

Still valid.

@JAremko JAremko added updated This issue has been updated since becoming stale and removed stale marked as a stale issue/pr (usually by a bot) updated This issue has been updated since becoming stale labels May 26, 2020
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Mar 14, 2022
@github-actions github-actions bot closed this as completed May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Running as daemon stale marked as a stale issue/pr (usually by a bot) Visual
Projects
None yet
Development

No branches or pull requests

8 participants