From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: On removing some obsolete code from subr and core
Date: Sat, 05 Nov 2016 13:50:48 -0400 [thread overview]
Message-ID: <jwvy40xu8ix.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83fun6jpeq.fsf@gnu.org
> easy. But what do we do with the default-FOO variables, once the
> machinery for their generation is removed?
BTW, the default-FOO vars were only deprecated in Emacs-23, not
Emacs-22, so maybe they can wait a little longer. Actually I think most
of them can be safely dropped (e.g. because they've never been used),
but some have been used fairly commonly and should stick around a bit
longer. Most obvious ones: default-major-mode and default-tab-width.
> Why do we need to remove buffer_defaults? Once it is not exposed to
> Lisp as variables, what's the harm?
AFAIK buffer_defaults is indeed still very much needed for
(default-value major-mode), (setq-default major-mode ...) and same for
all other variables which have their own field in the struct buffer.
OTOH, once all the DEFVAR_BUFFER_DEFAULTS are removed, we can remove the
hack in store_symval_forwarding.
Stefan
next prev parent reply other threads:[~2016-11-05 17:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 16:59 On removing some obsolete code from subr and core Mark Oteiza
2016-11-05 8:24 ` John Wiegley
2016-11-05 8:34 ` Eli Zaretskii
2016-11-05 13:50 ` Mark Oteiza
2016-11-05 17:59 ` Eli Zaretskii
2016-11-06 16:58 ` Mark Oteiza
2016-11-05 17:50 ` Stefan Monnier [this message]
2016-11-06 17:05 ` Mark Oteiza
2016-11-06 22:32 ` Stefan Monnier
2016-11-07 0:32 ` Mark Oteiza
2016-11-07 3:35 ` Eli Zaretskii
2016-11-07 4:24 ` Mark Oteiza
2016-11-07 15:11 ` Eli Zaretskii
2016-11-07 20:08 ` Mark Oteiza
2016-11-07 20:13 ` Eli Zaretskii
2016-11-07 20:25 ` Mark Oteiza
2016-11-08 6:51 ` Noam Postavsky
2016-11-07 20:31 ` Stefan Monnier
2016-11-07 21:32 ` Johan Bockgård
2016-11-08 13:00 ` Stefan Monnier
2016-11-08 19:49 ` John Wiegley
2016-11-05 15:51 ` Clément Pit--Claudel
2016-11-05 15:52 ` Clément Pit--Claudel
2016-11-05 16:42 ` Dmitry Gutov
2016-11-05 17:23 ` Clément Pit--Claudel
2016-11-05 17:31 ` Dmitry Gutov
2016-11-05 18:03 ` Clément Pit--Claudel
2016-11-05 15:57 ` Clément Pit--Claudel
2016-11-05 17:56 ` Stefan Monnier
2016-11-05 19:14 ` Clément Pit--Claudel
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=jwvy40xu8ix.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).