all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22986-done@debbugs.gnu.org
Subject: bug#22986: 24.5; (elisp) `Overlay Properties' has incorrect link `Text help-echo'
Date: Sun, 1 May 2016 08:07:52 -0800 (GMT-08:00)	[thread overview]
Message-ID: <b53ce7f6-abef-4f57-83a1-ab3d4984db0b@default> (raw)
In-Reply-To: <<831t5lolf4.fsf@gnu.org>>

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

> > > Under the `help-echo' entry there is this cross-reference: "For
> details
> > > see Text help-echo".  That link takes you to the `prepare-change-
> group'
> > > entry of node `Atomic Changes', which does not seem to have anything
> to
> > > do with `help-echo' or displaying a help string in the echo area.
> >
> > I'm unable to reproduce this bug.
> 
> Neither can I.  I suspect that Drew has an Info file with DOS EOLs,
> which would cause the cross-references to anchors place you at the
> wrong location.

No. This was reported for Emacs 24.5 (release), and there the problem
is exactly as reported.  See attached screenshot.

That erroneous xref has since been removed, so the problem no longer exists.

> Closing.

Correct.


[-- Attachment #2: throw-emacs-bug-22986.png --]
[-- Type: image/png, Size: 20571 bytes --]

       reply	other threads:[~2016-05-01 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<44599d24-39e3-4b7c-bf14-4337684f992f@default>
     [not found] ` <<877ffe66tz.fsf@gnus.org>
     [not found]   ` <<831t5lolf4.fsf@gnu.org>
2016-05-01 16:07     ` Drew Adams [this message]
2016-03-11 15:43 bug#22986: 24.5; (elisp) `Overlay Properties' has incorrect link `Text help-echo' Drew Adams
2016-04-30 22:59 ` Lars Ingebrigtsen
2016-05-01 15:19   ` Eli Zaretskii

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=b53ce7f6-abef-4f57-83a1-ab3d4984db0b@default \
    --to=drew.adams@oracle.com \
    --cc=22986-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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.