From: Drew Adams <drew.adams@oracle.com>
To: 19298@debbugs.gnu.org
Subject: bug#19298: 25.0.50; `set-frame-font': non-nil FRAMES argument
Date: Sun, 7 Dec 2014 12:24:09 -0800 (PST) [thread overview]
Message-ID: <31a16b3d-7470-4f8a-b422-a0e9ba3a923d@default> (raw)
The doc string says:
If FRAMES is non-nil, it should be a list of frames to act upon,
or t meaning all existing graphical frames.
Also, if FRAMES is non-nil, alter the user's Customization settings
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
as though the font-related attributes of the `default' face had been
"set in this session", so that the font is applied to future frames.
I don't understand why a list of frames should alter Customization
settings.
Parameter FRAMES was added for Emacs 24, and it probably hasn't gotten
much use yet. For code to change the font for a given list of frames
and NOT ALSO screw with the user's customization settings, the code must
select each frame in turn and call `set-frame-font' with a nil FRAMES
arg. That's silly, no? I am coming up against this right now.
Hard to believe that there is no simple way to change the font of a
frame and NOT ALSO change custom settings without selecting that frame.
Why does that design make sense?
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2014-10-20 on LEG570
Bzr revision: 118168 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'
next reply other threads:[~2014-12-07 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 20:24 Drew Adams [this message]
2016-04-30 16:24 ` bug#19298: 25.0.50; `set-frame-font': non-nil FRAMES argument Lars Ingebrigtsen
2016-04-30 16:30 ` Eli Zaretskii
2021-07-13 21:50 ` Drew Adams
2021-07-13 19:49 ` 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=31a16b3d-7470-4f8a-b422-a0e9ba3a923d@default \
--to=drew.adams@oracle.com \
--cc=19298@debbugs.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.