From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, 31130@debbugs.gnu.org
Subject: bug#31130: 26; Regression: intra-glossary links broken in Emacs manual
Date: Thu, 12 Apr 2018 10:27:30 -0700 (PDT) [thread overview]
Message-ID: <ef1416d2-c369-4358-a993-9cf31c69aaba@default> (raw)
In-Reply-To: <<83muy81iln.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.
>
> So you are saying that either (a) something in your setup causes this
> problem to happen, perhaps after some time the session is alive, or
> (b) something outside of Emacs causes the problem, and that something
> is not always happening, is that right?
Dunno what happened.
> > And I tested using emacs -Q also in Emacs 25.3.1,
> > 24.5, 24.4, 23.4, and even 22.3 and 20.
>
> Which means the (b) part above is more likely the culprit?
It suggests that, if (a) and (b) are the possibilities.
> Are you reasonably sure that your reproduction steps are the same in
> all of these attempts, whether successful or not? Or is that yet
> another potential reason for the problem to happen only sometimes?
Reasonably sure, yes. But I will try to pay more attention
to this.
I believe that I:
1. Discovered the problem with my setup, probably in E26.
(See my other msg about why my setup led to the problem,
which I just now figured out.)
2. Used emacs -Q in various releases, from 26 (and 27?)
back through to 20. I was both (a) checking it is still
a problem and (b) trying to find out whether it ever was
OK and if so where the regression was introduced.
I found that the problem was there starting with Emacs 24.5,
that it worked in 24.4, and that before 24.4 the text was
not linked.
> AFAIR, we ended up giving up on understanding the exact reasons back
> then as well, because you were unable to reliably reproduce the
> problem, except in an old version of Emacs or an old version of Info
> files. Exactly like now.
That's possible. I don't recall.
> Which Info files Emacs finds is determined by the code which computes
> Info-default-directory-list, and on code in info-initialize (and its
> subroutine Info-default-dirs). In a nutshell, that makes Emacs
> consider several alternative places until it finds one that "works".
> So the answer to your question depends on the directories you have or
> don't have on your system, out of those Emacs considers, something I
> cannot know. It also depends on whether you have INFOPATH defined in
> the environment, and if you do, what is its value.
INFOPATH is nil.
Each Emacs build is in a separate directory, and the dir contents
are what is extracted from a Windows snapshot. I don't modify
`Info-default-directory-list' or `info-initialize' when I use
emacs -Q. (When I use my setup, I don't modify `info-initialize',
but Cygwin does modify `Info-default-directory-list' to add
"c:/cygwin/usr/info".)
> > I don't see how different versions could show the same Info manual
> > version when each is started with emacs -Q.
>
> If you read the code in the functions I pointed to, you will see that
> it doesn't only consider directories under the directory where you
> unzipped the archive. It also looks in other places.
Yes, but I don't do anything (when I use emacs -Q) that affects
any of those places.
next parent reply other threads:[~2018-04-12 17:27 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>
[not found] ` <<2e49187a-b623-46ad-8acc-1c8b0d787d99@default>
[not found] ` <<83muy81iln.fsf@gnu.org>
2018-04-12 17:27 ` Drew Adams [this message]
[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 ` bug#31130: 26; Regression: intra-glossary links broken in Emacs manual Drew Adams
[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>
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=ef1416d2-c369-4358-a993-9cf31c69aaba@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).