From: eythanweg@gmail.com (Eythan Weg)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9646@debbugs.gnu.org
Subject: bug#9646: 24.0.90; Daemon does not heed desired font
Date: Sun, 02 Oct 2011 15:31:07 -0400 [thread overview]
Message-ID: <87d3efp4w4.fsf@gmail.com> (raw)
In-Reply-To: <837h4od29w.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Oct 2011 20:56:11 +0300")
Eli Zaretskii <eliz@gnu.org>
Sat, 01 Oct 2011 20:56:11 +0300
> From: Eythan Weg <eythanweg@gmail.com>
> Date: Sat, 01 Oct 2011 09:09:37 -0400
>
> I start emacs --daemon with the .emacs content just this:
>
> (setq initial-frame-alist '((font . "DejaVu Sans")))
>
> Now visit a file with hebrew text. The hebrew chars are shown using
> freefont. Do the same without --daemon and the font is chosen
> correctly.
The daemon does not display its initial frame, so you are customizing
a frame that is never shown.
Why do you request this font only for the initial frame? If you do
the same with default-frame-alist, does it do what you want, both in
daemon mode and normal invocation?
My original response was sent mistakenly only to Eli. Here is a revised
version.
To replicate what I see follow this recipe:
Create the file test.el containing:
(add-to-list 'default-frame-alist '(font . "DejaVu Sans Mono-14"))
(set-fontset-font t 'hebrew '("DejaVu Sans" . "unicode-bmp"))
Now run:
emacs -Q -l test.el file.txt
where file.txt contains some Hebrew characters.
The Hebrew text appears in DejaVu Sans.
Now run:
emacs --daemon -Q -l test.el
emacsclient -c file.txt.
The Hebrew text does not appear in DejaVu Sans, and moreover if file.txt
contains niqud it is incorrectly composed in that font. In my
case emacs chooses to use FreeMono.
next prev parent reply other threads:[~2011-10-02 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 13:09 bug#9646: 24.0.90; Daemon does not heed desired font Eythan Weg
2011-10-01 17:56 ` Eli Zaretskii
2011-10-02 19:31 ` Eythan Weg [this message]
2020-08-17 22:34 ` Stefan Kangas
2021-08-25 12:41 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d3efp4w4.fsf@gmail.com \
--to=eythanweg@gmail.com \
--cc=9646@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.