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: 31130-done@debbugs.gnu.org, rpluim@gmail.com
Subject: bug#31130: 26; Regression: intra-glossary links broken in Emacs manual
Date: Thu, 12 Apr 2018 08:53:49 -0700 (PDT)	[thread overview]
Message-ID: <2e49187a-b623-46ad-8acc-1c8b0d787d99@default> (raw)
In-Reply-To: <<83sh801mcl.fsf@gnu.org>>

> > 1. Trying again now, I can repro the problem only in Emacs 24.5,
> >    not in the more recent releases/builds.
> 
> That could be, but I guess it means you reported the bug from a binary
> other than the one where the problem happened?

No.  I reported it from the Emacs 26 RC1, and the problem
happened in that version.  And I tested it with `emacs -Q'
in that version.  I likely reported it (M-x report-emacs-bug)
using my setup, but with the same binary that I tested using
emacs -Q.  And I tested using emacs -Q also in Emacs 25.3.1,
24.5, 24.4, 23.4, and even 22.3 and 20.

> > 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.
> 
> We've been through that before.

Have we?  Please tell me how what I saw is possible, in
that case.

> May I suggest that next time this happens you keep notes
> about the exact steps you took while reproducing the problem?
>
> >    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?
> 
> It depends on how your system is configured wrt multiple Emacs
> versions installed on it, and in particular how you invoke Info.  If
> you just type "C-h i" or "C-h r", the Info manual you get depends on
> whether you keep the share/info directories of different versions
> separate or not.

They are all separate.  Each Emacs version/release is in
a separate directory/folder, and all of it is there, in
the original subdirs (bin, etc, include,lib, libexec,
share, ssl).  All I do is extract the zip file
obtained from GNU Emacs (e.g. P. Lord's snapshots).  I
make no changes to the directories or their files.

(Even with my own setup I make no such changes - no
changes to the distributed files and their directories.
But with my own setup I do make changes to some Info
functions etc.)

So I repeat the question, how could it happen that I
would read an Info file that didn't come with the
current binary, when using emacs -Q?

Unless there is some kind of cache file that Emacs
uses for Info that is outside that directory, I don't
see how different versions could show the same Info
manual version when each is started with emacs -Q.

> Also, "C-h i" and "C-h r" go to different places by
> default.  This is why I always use "C-u C-h i", and then specify the
> Info file that corresponds to the Emacs version I'm running.

I used `C-h r' to simplify the repro recipe.  If invoked
from emacs -Q, how can that go elsewhere than the Emacs
manual for that binary?

> > 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.
> 
> Then I guess we can close this bug.





       reply	other threads:[~2018-04-12 15:53 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>
     [not found]     ` <<5a5ee055-9b18-4e1f-9f49-e95128fa0a80@default>
     [not found]       ` <<83sh801mcl.fsf@gnu.org>
2018-04-12 15:53         ` Drew Adams [this message]
2018-04-12 16:43           ` bug#31130: 26; Regression: intra-glossary links broken in Emacs manual 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
     [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
2018-04-12 15:22       ` Eli Zaretskii
2018-04-12 16:16     ` Drew Adams
2018-04-12 17:03       ` Eli Zaretskii
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=2e49187a-b623-46ad-8acc-1c8b0d787d99@default \
    --to=drew.adams@oracle.com \
    --cc=31130-done@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).