unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark Oteiza <mvoteiza@udel.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: On removing some obsolete code from subr and core
Date: Sun, 6 Nov 2016 23:24:15 -0500	[thread overview]
Message-ID: <20161107042415.GA27319@holos.localdomain> (raw)
In-Reply-To: <83ins0hshk.fsf@gnu.org>

On 07/11/16 at 05:35am, Eli Zaretskii wrote:
> > Date: Sun, 6 Nov 2016 19:32:35 -0500
> > From: Mark Oteiza <mvoteiza@udel.edu>
> > Cc: emacs-devel@gnu.org
> > 
> > On 05/11/16 at 10:34am, Eli Zaretskii wrote:
> > > For removed symbols, bringing back the ones that are still needed is
> > > easy.  But what do we do with the default-FOO variables, once the
> > > machinery for their generation is removed?
> > 
> > I am guessing this is referring to my erroneous comment on
> > buffer_defaults, as opposed to removing the DEFVAR_BUFFER_DEFAULTS
> > macro.
> 
> No, it referred to the DEFVAR_BUFFER_DEFAULTS macro and its users.

Ok, so we do nothing, then.  The default-FOO variables go away.  They
are the only users of DEFVAR_BUFFER_DEFAULTS, so that macro can also go.

> > > In any case, this needs a NEWS entry listing all the removed
> > > variables.
> > 
> > Do you really want me to list them all in NEWS? I was inclined to
> > use--under the section for removed things--the old entry from
> > NEWS.23:
> > 
> > ** All the default-FOO variables that hold the default value of the FOO
> > variable.
> 
> I think at least a few of them should be mentioned by name ("such as
> ..." etc.).

Ok.



  reply	other threads:[~2016-11-07  4:24 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
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 [this message]
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=20161107042415.GA27319@holos.localdomain \
    --to=mvoteiza@udel.edu \
    --cc=eliz@gnu.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).