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>, Robert Pluim <rpluim@gmail.com>
Cc: 31130@debbugs.gnu.org
Subject: bug#31130: 26; Regression: intra-glossary links broken in Emacs manual
Date: Thu, 12 Apr 2018 07:42:47 -0700 (PDT)	[thread overview]
Message-ID: <5a5ee055-9b18-4e1f-9f49-e95128fa0a80@default> (raw)
In-Reply-To: <<838t9s3cbf.fsf@gnu.org>>

> > > This regression was introduced in Emacs 24.5.  Prior to that, in
> > > Emacs 24 the links worked fine.
> >
> > This works fine for me in emacs-26 -Q, admittedly on GNU/Linux, not
> > Windows.
> 
> It shouldn't matter, because the Info files come from the source
> tarball in this case.
> 
> Anyway, I cannot reproduce this on Windows, either, neither with Emacs
> 26.1 which I built myself, not with the binary from the GNU site.
>
> Drew, are you sure you are reading the Info files that came with the
> Emacs binary whose details you included in the report?  ISTR that you
> reported in the past similar problems, and each time the reason turned
> out to be old Info files and/or old Emacs versions.
>
> Both Texinfo and
> Emacs changed a few years ago how offsets of index entries are
> calculated and used, and the change matters when the Info file has DOS
> CR-LF line endings, so now old Info files and new Emacs might be
> incompatible.

1. Trying again now, I can repro the problem only in Emacs 24.5,
   not in the more recent releases/builds.

2. I'm sure I tested those multiple builds, using `emacs -Q',
   going back to see whether it ever worked and, if so, in
   what release it became broken.  IIRC, found that prior to
   Emacs 24 those terms were not links; in Emacs 24.4 the
   links worked correctly; and starting with Emacs 24.5,
   through 27 (3rd snapshot) the links were broken.

3. I don't know how or why I saw different behavior then
   than now, when I retest.  I don't know what you mean,
   about somehow reading Info files that didn't come with
   the same binary.  How would that even happen?

4. But if it can happen then yes, perhaps that is the cause.
   I often have Emacs 20, 24.5, and something recent (e.g.
   27) open at the outset, using my setup.  And it's likely
   that I've already used Info in one or more of those,
   before I notice a problem and then retest using `emacs -Q'.

   In this case, I know that I discovered this problem first
   in a build using my setup.  I don't recall whether it was
   Emacs 24.5 or 26, but I'm pretty sure it was 26.  However,
   I may have already used Info with Emacs 24.5 at some point.

Sorry for any confusion.  I don't really understand what's
causing the mixup in behavior, but I'm sure that I tested
each of the releases 24.5, 25.3.1, and 26 using `emacs -Q'.
But I confirm that doing that again now I don't see the
problem except in 24.5.





       reply	other threads:[~2018-04-12 14:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<60e57152-0b45-4c8f-aef7-fc8f2b06c69b@default>
     [not found] ` <<874lkgrg14.fsf@gmail.com>
     [not found]   ` <<838t9s3cbf.fsf@gnu.org>
2018-04-12 14:42     ` Drew Adams [this message]
2018-04-12 15:22       ` bug#31130: 26; Regression: intra-glossary links broken in Emacs manual Eli Zaretskii
2018-04-12 16:16     ` Drew Adams
2018-04-12 17:03       ` Eli Zaretskii
     [not found] <<<60e57152-0b45-4c8f-aef7-fc8f2b06c69b@default>
     [not found] ` <<<874lkgrg14.fsf@gmail.com>
     [not found]   ` <<<838t9s3cbf.fsf@gnu.org>
     [not found]     ` <<5a5ee055-9b18-4e1f-9f49-e95128fa0a80@default>
     [not found]       ` <<83sh801mcl.fsf@gnu.org>
2018-04-12 15:53         ` Drew Adams
2018-04-12 16:43           ` Eli Zaretskii
2018-04-12 17:04           ` Drew Adams
     [not found]     ` <<94f9a38a-caa1-40d8-94c9-705f80f22f8c@default>
     [not found]       ` <<83h8og1hob.fsf@gnu.org>
2018-04-12 17:31         ` Drew Adams
2018-04-12 18:16           ` Eli Zaretskii
     [not found] <<<<60e57152-0b45-4c8f-aef7-fc8f2b06c69b@default>
     [not found] ` <<<<874lkgrg14.fsf@gmail.com>
     [not found]   ` <<<<838t9s3cbf.fsf@gnu.org>
     [not found]     ` <<<5a5ee055-9b18-4e1f-9f49-e95128fa0a80@default>
     [not found]       ` <<<83sh801mcl.fsf@gnu.org>
     [not found]         ` <<2e49187a-b623-46ad-8acc-1c8b0d787d99@default>
     [not found]           ` <<83muy81iln.fsf@gnu.org>
2018-04-12 17:27             ` Drew Adams
     [not found]     ` <<<94f9a38a-caa1-40d8-94c9-705f80f22f8c@default>
     [not found]       ` <<<83h8og1hob.fsf@gnu.org>
     [not found]         ` <<10583e1c-eefe-4561-beeb-ccaca9263be2@default>
     [not found]           ` <<83fu401eac.fsf@gnu.org>
2018-04-12 18:20             ` Drew Adams
2018-04-11 21:37 Drew Adams
2018-04-12  8:21 ` Robert Pluim
2018-04-12 11:15   ` 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

  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=5a5ee055-9b18-4e1f-9f49-e95128fa0a80@default \
    --to=drew.adams@oracle.com \
    --cc=31130@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rpluim@gmail.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).