all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: (emacs-version) in the Elisp reference
Date: Wed, 21 Jun 2017 19:09:11 +0900	[thread overview]
Message-ID: <5914D65D-D57A-4AAD-BD13-2B6BC4BB5F59@gmail.com> (raw)
In-Reply-To: <gn37au8e1c.fsf@fencepost.gnu.org>


> On Jun 21, 2017, at 7:55, Glenn Morris <rgm@gnu.org> wrote:
> 
> Jean-Christophe Helary wrote:
> 
>> (why hardcode values that do not correspond to the current manual?)
> 
> Becuase they are just illustrative examples, and nothing would be gained
> by changing them to always refer to the current version.

Sorry, back to the thread.

If we hardcode 1 value, why not hardcode the 2 other:

@defvar emacs-major-version
The major version number of Emacs, as an integer.  For Emacs version
26.1, the value is 26.
@end defvar

@defvar emacs-minor-version
The minor version number of Emacs, as an integer.  For Emacs version
26.1, the value is 1.
@end defvar

That's an even better illustration of the variables and it costs extremely little since we already hardcode the value of (emacs-version).

Jean-Christophe


  parent reply	other threads:[~2017-06-21 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-20 12:39 (emacs-version) in the Elisp reference Jean-Christophe Helary
2017-06-20 15:29 ` Eli Zaretskii
2017-06-20 19:56   ` Jean-Christophe Helary
2017-06-20 22:55     ` Glenn Morris
2017-06-20 23:25       ` Jean-Christophe Helary
2017-06-21  2:35         ` Eli Zaretskii
2017-06-21  3:39           ` Jean-Christophe Helary
2017-06-21 10:09       ` Jean-Christophe Helary [this message]
2017-06-22  1:56     ` 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=5914D65D-D57A-4AAD-BD13-2B6BC4BB5F59@gmail.com \
    --to=jean.christophe.helary@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.