unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 12149@debbugs.gnu.org
Subject: bug#12149: 24.1; `C-h f' is worse and worse at telling where a function was defined
Date: Thu, 28 Apr 2016 18:20:14 +0200	[thread overview]
Message-ID: <87a8kd903l.fsf@gnus.org> (raw)
In-Reply-To: <28819A29BB374779AEEA60B7FF63A25B@us.oracle.com> (Drew Adams's message of "Mon, 6 Aug 2012 10:49:15 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> In Emacs prior to Emacs 23, `C-h f' did not point to the wrong files
> as having defined these function.  At least it did not lie and steer
> you wrong.
>
> Emacs 23.4 did not point to the wrong file for `y-or-n-p', but it did
> point to the wrong file for `top-level'.
>
> Emacs 24.1 gets them both wrong.  It simply gives the original location
> (from emacs -Q) for each of them: `C source code' for `top-level' and
> `subr.el' for `y-or-n-p'.  This is not good.  Better to say "no idea"
> than to mislead the user this way.

(progn
  (defun yes-or-no-p (prompt) (y-or-n-p prompt))
  (describe-function  'yes-or-no-p))

=>

yes-or-no-p is a Lisp function.

(yes-or-no-p PROMPT)

Not documented.

So I seem to be unable to reproduce this bug.  Are you still seeing it?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2016-04-28 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 17:49 bug#12149: 24.1; `C-h f' is worse and worse at telling where a function was defined Drew Adams
2012-09-16 23:35 ` Drew Adams
2016-04-28 16:20 ` Lars Ingebrigtsen [this message]
2016-04-28 16:34   ` Drew Adams
2016-04-28 21:31     ` Nicolas Richard
2016-04-29 20:23       ` 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

  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=87a8kd903l.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=12149@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).