unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22987@debbugs.gnu.org
Subject: bug#22987: 24.5; Incorrect index entry for (elisp) `‘help-e
Date: Fri, 11 Mar 2016 08:29:48 -0800 (PST)	[thread overview]
Message-ID: <7a63860f-3902-4dcf-a8ac-9b6af77f16d0@default> (raw)
In-Reply-To: <834mcdj8or.fsf@gnu.org>

> > You will see that index entry only if you have substring completion.
> 
> I cannot reproduce this in the recent pretest of Emacs 25.  I do see
> the entry without substring completion

The bug is filed for Emacs 24.5, the latest Emacs release.
If the bug has been fixed since then, great.

I cannot use any Emacs 25 pretest that I've found - at all.
It simply crashes almost immediately.  And no, I don't have
the time to dig into why.

> > The index entry "‘help-echo’ event" seems misguided.
> 
> I don't see such an index entry.  I see this instead:
> 
>   * help-echo event:                  Misc Events.         (line  55)

Which is clearly why you don't need substring completion - there
are no single curly quotes around the index entry, in your pretest.
There are such quotes around the entry in the release.

> So I'm not really sure what you see and why.

You're not sure what and why?  Try using the latest release, which
the bug pertains to:

In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=3D3D/c/usr --host=3D3Di686-pc-mingw32'

Here is what is in the index of the release:

* help-command:                          Help Functions.      (line  43)
* help-echo (overlay property):          Overlay Properties.  (line 114)
* help-echo (text property):             Special Properties.  (line  83)
* ‘help-echo’ event:                     Misc Events.         (line  55)
* help-echo, customization keyword:      Type Keywords.       (line  98)
* help-event-list:                       Help Functions.      (line  69)

(I can send a screenshot if this is not clear enough as is.)





  reply	other threads:[~2016-03-11 16:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 15:52 bug#22987: 24.5; Incorrect index entry for (elisp) `‘help-e Drew Adams
2016-03-11 16:11 ` Eli Zaretskii
2016-03-11 16:29   ` Drew Adams [this message]
2016-03-11 18:02     ` Eli Zaretskii
2016-03-11 18:25       ` Drew Adams
2016-03-11 18:36         ` Eli Zaretskii
2016-03-27  0:09     ` John Wiegley
2016-03-27  1:33       ` bug#22987: 24.5; Incorrect index entry for (elisp) `?help-e Drew Adams
2016-03-27  5:56         ` John Wiegley
2016-03-27 15:03           ` Eli Zaretskii
2016-03-28  3:50             ` Marcin Borkowski
2016-03-28  4:06               ` Drew Adams
2016-03-27 16:52           ` Drew Adams
2016-03-29  6:48             ` John Wiegley
2016-03-29 13:05               ` Drew Adams

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=7a63860f-3902-4dcf-a8ac-9b6af77f16d0@default \
    --to=drew.adams@oracle.com \
    --cc=22987@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 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).