From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nathan Weizenbaum <nex342@gmail.com>
Cc: 6203@debbugs.gnu.org
Subject: bug#6203: Frame-local variables break let-binding
Date: Mon, 17 May 2010 15:48:07 -0400 [thread overview]
Message-ID: <jwvbpcewbx5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <AANLkTik0FRwNZK_vAPUoUUJ64dxq8RRTmqhoygUC2cU9@mail.gmail.com> (Nathan Weizenbaum's message of "Mon, 17 May 2010 10:12:47 -0700")
> This all raises the issue, though: what's the accepted replacement for
> frame-local variables,
frame-parameters
> and why are they deprecated in the first place?
Because OT1H they're very little used, and OTOH they're a pain in the
rear to support and maintain because of all kinds of corner cases, and
it'll only get better with the addition of concurrency and/or
lexical scoping.
> My package has rather a few of them, and it's very useful to be able
> to use them like variables. I want to make them available for user
> customization, let-bind them, and use them without having to go
> through lots of manual frame-parameter rigamarole each time. I would
> rather not break any user customizations using these variables.
> So what should I do?
Use frame-parameters. Note that until Emacs-24 is released, that gives
you a fair bit of time to deal with it.
Stefan
next prev parent reply other threads:[~2010-05-17 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 22:18 bug#6203: Frame-local variables break let-binding Nathan Weizenbaum
2010-05-17 13:45 ` Stefan Monnier
2010-05-17 17:12 ` Nathan Weizenbaum
2010-05-17 19:48 ` Stefan Monnier [this message]
2010-05-17 20:10 ` Nathan Weizenbaum
2010-05-18 15:29 ` Stefan Monnier
2010-05-18 21:32 ` Nathan Weizenbaum
2010-05-18 22:42 ` Juri Linkov
2010-05-19 2:08 ` Stefan Monnier
[not found] ` <m3iq41trka.fsf@fleche.redhat.com>
[not found] ` <jwvhbjlkx0g.fsf-monnier+emacs@gnu.org>
2010-07-27 14:49 ` Tom Tromey
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=jwvbpcewbx5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=6203@debbugs.gnu.org \
--cc=nex342@gmail.com \
/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).