From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: question about frame local variable
Date: Tue, 28 Oct 2003 17:03:36 +0900 (JST) [thread overview]
Message-ID: <200310280803.RAA05883@etlken.m17n.org> (raw)
In-Reply-To: <E1ADjMF-0005OQ-HM@fencepost.gnu.org> (message from Richard Stallman on Sun, 26 Oct 2003 06:46:55 -0500)
In article <E1ADjMF-0005OQ-HM@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:
> It seems that we need the attached patch to make a code like
> this (allow scalable fonts only for a specific frame) work
> well.
> (defun make-frame-allowing-scalable-fonts ()
> (make-variable-frame-local 'scalable-fonts-allowed)
> (let ((frame (make-frame '((name . "SCALABLE")))))
> (modify-frame-parameters frame '((scalable-fonts-allowed . t)))
> frame))
> The patch accesses the value of `scalable-fonts-allowed' not
> directly by Vscalable_fonts_allowed but via:
> is there a bug in handling frame-local bindings for variables
> forwarded to C vars? if so, can we fix that bug?
I don't know how "frame-local bindings for variables" should
be treated in C code. So I can't tell if there's a bug or
not.
Ideally, I think selecte-frame should change the value of
Vscalable_fonts_allowed when that has frame local binding.
Then, C code can simply refer to this variable to get the
current value.
But, apparently, Fselect_frame and do_switch_frame called
from it does nothing about such variables. Only via
find_symbol_value, C code gets the current value.
On the other hand, set_buffer_internal_1 surely pays
attention to buffer local variables so that C variables get
the current value.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-10-28 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 0:49 question about frame local variable Kenichi Handa
2003-10-26 11:46 ` Richard Stallman
2003-10-28 8:03 ` Kenichi Handa [this message]
2003-10-30 1:35 ` Kenichi Handa
2003-10-30 9:33 ` Gerd Moellmann
2003-10-30 10:46 ` Kenichi Handa
2003-10-30 16:27 ` Stefan Monnier
2003-10-30 19:33 ` Gerd Moellmann
2003-11-10 1:05 ` Kenichi Handa
2003-11-10 10:35 ` Gerd Moellmann
2003-11-11 8:38 ` Kenichi Handa
2003-11-12 20:02 ` Richard Stallman
2003-11-13 0:42 ` Kenichi Handa
2003-11-13 4:14 ` Richard Stallman
2003-11-13 4:32 ` Kenichi Handa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200310280803.RAA05883@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).