help-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[help-texinfo] Re: Gentoo Linux some `Info' manuals missing index


From: Harry Putnam
Subject: [help-texinfo] Re: Gentoo Linux some `Info' manuals missing index
Date: Sun, 01 Nov 2009 08:58:55 -0600
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux)

address@hidden (Karl Berry) writes:

> Hi Harry,
>
>     GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, 
>
> I don't have 23.1.50, but with 23.1.1, starting up with
>   emacs-23.1 --no-site --no-init
> doing
>   C-h i m cvs <RET>
>   i update RET
> does find index entries for update.  With the cvs.info* files you sent me.

Well that narrows it down quite a lot then.

> So, could it be something in your site and/or personal Elisp files?  On
> the other hand, if the above fails for you with 23.1.50, I am left with
> suggesting writing the Emacs developers.  Perhaps it's a change they
> introduced since 23.1.

It could be something local, sure.  But I've done nothing to the
files, so they are on the fs `as installed'.  And since its only that
one info file, it seems unlikely to be a general problem with
emacs-23.1.50.

Possibly something with the way gentoo installed cvs?

I'm going to post on emacs-dev before going the bug route... they'll
probably insist on it anyway... but I'd first like to hear if others
using latest emacs-23 have the same problem.

What, if anything, do you think it means that a newly generated set
of info files for cvs from the source texi, do not display this
problem?

Is it normal for a package of new sources to have info files generated
nearly 5 yrs ago?... I know in some pkgs the info file generation is
part of the build... but seems not to be the case with cvs as
evidenced by the fact that if I hand generate the info files from the
tarball texi file the problem goes away.

Do you think it would still be considered a bug for emacs if newly
generated info files from cvs work?

Anyway, sorry to have been a big pita for apparently no good reason.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]