From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: slewsys@gmail.com, emacs-devel@gnu.org
Subject: Re: master 2ec8f28: Introduce defcustom 'executable-prefix-env'
Date: Wed, 26 Jul 2017 21:55:20 +0300 [thread overview]
Message-ID: <837eyv58pz.fsf@gnu.org> (raw)
In-Reply-To: <jtwp6v5eme.fsf@fencepost.gnu.org> (message from Glenn Morris on Wed, 26 Jul 2017 12:47:53 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: emacs-devel@gnu.org, slewsys@gmail.com
> Date: Wed, 26 Jul 2017 12:47:53 -0400
>
> > But do you see anything wrong with doing that? I didn't, so I left it
> > as submitted by the author.
>
> It's not part of the documented meaning for :version ("This keyword
> specifies that the item was first introduced in Emacs version VERSION,
> or that its default value was changed in that version").
Yes, it's not the "usual" meaning, but it sounded close enough to me.
> There's a standard method for deprecating options, to mark them
> obsolete; so yes, I think using :version for that is wrong.
I don't think we should deprecate it in the normal sense of that word.
next prev parent reply other threads:[~2017-07-26 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170722073452.31002.6998@vcs0.savannah.gnu.org>
[not found] ` <20170722073453.C375420329@vcs0.savannah.gnu.org>
2017-07-24 15:58 ` master 2ec8f28: Introduce defcustom 'executable-prefix-env' Glenn Morris
2017-07-24 16:24 ` Eli Zaretskii
2017-07-26 16:47 ` Glenn Morris
2017-07-26 18:55 ` Eli Zaretskii [this message]
2017-07-24 16:38 ` Glenn Morris
2017-07-24 16:57 ` Eli Zaretskii
2017-07-24 18:57 ` Andrew L. Moore
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=837eyv58pz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=slewsys@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).