all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 21225@debbugs.gnu.org
Subject: bug#21225: 25.0.50; doc strings of `define-obsolete-*'
Date: Sun, 9 Aug 2015 10:28:50 -0700 (PDT)	[thread overview]
Message-ID: <7ec85eda-d5e0-4bda-8dba-4a75fe5f93e5@default> (raw)

Argument WHEN is not described at all for some of these macros.  For
others it is described incorrectly or only via an example.  It needs to
be described clearly.

The correct description is, in all cases, what is said in the Elisp
manual for `make-obsolete':

   If provided, WHEN should be a string indicating when the function
   was first made obsolete=81\for example, a date or a release number.

(with "function" replaced by "face" or "variable", as appropriate),
except that "version number" is preferable to "release number".

These macros are used by users and 3rd-party libraries too, not just by
core Emacs development, and in such contexts "release" is not
necessarily appropriate.  The most important remark, however, is that "a
date" should be offered as an example of a WHEN value, in addition to "a
version number".

The same change should be made for the Elisp manual, node `Variable
Aliases'.  It is better to say "for example, a date or a version number"
than just "(usually a version number string)".

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-07-03 on LEG570
Repository revision: 2b848fadd51e805b2f46da64c5958ea7f009048a
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --host=3Di686-pc-mingw32 --enable-checking=3Dyes,glyphs'





             reply	other threads:[~2015-08-09 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 17:28 Drew Adams [this message]
2015-08-09 17:35 ` bug#21225: 25.0.50; doc strings of `define-obsolete-*' Drew Adams
2015-08-11 12:50   ` Artur Malabarba
2015-08-11 16:07     ` Stefan Monnier
2016-04-30 21:52 ` Lars Ingebrigtsen

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=7ec85eda-d5e0-4bda-8dba-4a75fe5f93e5@default \
    --to=drew.adams@oracle.com \
    --cc=21225@debbugs.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.