From: Juanma Barranquero <lekktu@gmail.com>
To: rms@gnu.org
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 3615@debbugs.gnu.org
Subject: bug#3615: 23.0.94; (elisp)Local Variables: xrefs to nodes for buffer-local and frame-local vars
Date: Wed, 13 Jul 2011 12:57:54 +0200 [thread overview]
Message-ID: <CAAeL0SS09KL_RNaZ8YPO9=C8AsAfsUiETR3gJPTMxFrnd=_n7g@mail.gmail.com> (raw)
In-Reply-To: <E1QgtIH-0003cl-E7@fencepost.gnu.org>
> Why deprecate frame-local variables?
There's a long thread in emacs-devel, titled "frame-local variables
weirdness", started on 2006-12-05. After many exchanges, you said:
"When frame-local variables were first implemented, there was no other
way to put frame-specific data in the mode line. But now there is,
with :eval.
Since they are hardly used, and the original motive for them
no longer applies, we may as well delete the feature.
Would you like to do that?"
and Stefan answered:
"Sure. I currently just marked it obsolete in the 22 branch (with a note in
NEWS), see patch below. I'll change the pieces of code which make use of
that feature on the trunk. If anybody wants to help out: feel free."
and then you said:
"I will delete them from the Lisp manual."
Basically, they are a source of subtle, obscure bugs; they do not
provide (almost) anything that cannot be done with
(set-)?frame-parameter, and after ten years or so of its
implementation they had all of four uses in the sources, all of them
trivial and trivially changed.
Juanma
next prev parent reply other threads:[~2011-07-13 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 7:43 bug#3615: 23.0.94; (elisp)Local Variables: xrefs to nodes for buffer-local and frame-local vars Drew Adams
2011-07-12 14:15 ` Lars Magne Ingebrigtsen
2011-07-12 14:50 ` Drew Adams
2011-07-12 15:12 ` Lars Magne Ingebrigtsen
2011-07-12 16:08 ` Drew Adams
2011-07-12 17:23 ` Chong Yidong
2011-07-12 16:12 ` Drew Adams
2011-07-13 6:51 ` Richard Stallman
2011-07-13 10:57 ` Juanma Barranquero [this message]
2011-07-13 18:32 ` Richard Stallman
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='CAAeL0SS09KL_RNaZ8YPO9=C8AsAfsUiETR3gJPTMxFrnd=_n7g@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=3615@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@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.