all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xu Chunyang <xuchunyang56@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 38844@debbugs.gnu.org
Subject: bug#38844: 28.0.50; Incorrect result by help-fns--mention-first-release
Date: Wed, 1 Jan 2020 20:58:42 +0800	[thread overview]
Message-ID: <CABCqdBmj0y9sjX4jcOzWbAesCUxtU4wWCUiSHp-5UaMAPNnZqQ@mail.gmail.com> (raw)
In-Reply-To: <CABCqdB=b01Z0L8daK32Szic4i5QERxAtMf_fpHNg5oyrnNvhkA@mail.gmail.com>

I just noticed 27.1 in "Probably introduced at or before Emacs version
27.1." is clickable and linked to relevant NEWS entry. It makes more
sense to me now.

On Wed, Jan 1, 2020 at 7:38 PM Xu Chunyang <xuchunyang56@gmail.com> wrote:
>
> Another case is the function file-size-human-readable, C-h f says it
> probably is added in 27.1, but I checked it's available in 24.5,
> though NEWS.27 does mention the function
>
> > ** The function 'file-size-human-readable' accepts more optional arguments.
>
> On Wed, Jan 1, 2020 at 6:22 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > On January 1, 2020 11:36:28 AM GMT+02:00, Xu Chunyang <xuchunyang56@gmail.com> wrote:
> > > C-h f exec-path mentions "Probably introduced at or before Emacs
> > > version 22.1.", however, according to NEWS.27 the function exec-path
> > > is introduced in Emacs 27.1. I checked that Emacs 24.5 doesn't provide
> > > the function exec-path.
> >
> > That's because 'exec-path' the variable was introduced a long time ago.  The heuristics we use to search the NEWS files for symbols cannot distinguish between diffetent kinds that have the same names





  reply	other threads:[~2020-01-01 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01  9:36 bug#38844: 28.0.50; Incorrect result by help-fns--mention-first-release Xu Chunyang
2020-01-01 10:22 ` Eli Zaretskii
2020-01-01 11:38   ` Xu Chunyang
2020-01-01 12:58     ` Xu Chunyang [this message]
2020-01-01 16:32     ` Eli Zaretskii
2021-08-30  2:02 ` 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=CABCqdBmj0y9sjX4jcOzWbAesCUxtU4wWCUiSHp-5UaMAPNnZqQ@mail.gmail.com \
    --to=xuchunyang56@gmail.com \
    --cc=38844@debbugs.gnu.org \
    --cc=eliz@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.