From: Glenn Morris <rgm@gnu.org>
To: Nikolaj Schumacher <me@nschum.de>
Cc: 812@emacsbugs.donarmstrong.com
Subject: bug#812: frame-local-variable documentation
Date: Sat, 30 Aug 2008 18:56:55 -0400 [thread overview]
Message-ID: <i9fxomdsco.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m24p54suk6.fsf@nschum.de> (Nikolaj Schumacher's message of "Thu, 28 Aug 2008 23:23:21 +0200")
Nikolaj Schumacher wrote:
> As far as I can tell frame-local variables have been (or are about to
> be) removed and currently don't work.
They haven't been removed and will still be in 23.1, except:
"Variables cannot be both buffer-local and frame-local any more."
However, something seems broken. This works as it should:
emacs -Q
(setq foo 'bar)
(make-variable-frame-local 'foo)
; [1]
(set-frame-parameter nil 'foo t)
foo ; -> t [2]
(make-frame)
foo ; -> bar in new frame, still t in old frame [3]
If you add an extra evaluation of `foo' at point [1] (after making it
frame local, but before adding a frame parameter), then at point [2]
you get 'bar rather than t. After you make a new frame, it starts
working (at [3]).
> `modify-frame-parameters' still contains this paragraph:
>
>> The value of frame parameter FOO can also be accessed
>> as a frame-local binding for the variable FOO, if you have
>> enabled such bindings for that variable with
>> `make-variable-frame-local'.
>
> That should be removed, I think.
I mentioned it's obsolete.
> `make-variable-frame-local' has this note:
>
>> This function is obsolete since 22.2;
>> use a frame-parameter instead.
I tweaked it.
next prev parent reply other threads:[~2008-08-30 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 21:23 bug#812: frame-local-variable documentation Nikolaj Schumacher
2008-08-30 22:56 ` Glenn Morris [this message]
2010-06-24 19:12 ` bug#1159: frame-local-variable problem Glenn Morris
2010-06-24 19:30 ` Chong Yidong
2010-06-24 20:00 ` Glenn Morris
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=i9fxomdsco.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=812@emacsbugs.donarmstrong.com \
--cc=me@nschum.de \
/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.