unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Stale links in Info tree?
Date: Wed, 2 Mar 2011 18:56:14 -0800 (PST)	[thread overview]
Message-ID: <fbbdec19-ae37-48b1-a1a2-d44d18c6f033@o21g2000prn.googlegroups.com> (raw)
In-Reply-To: 051eb29d-3f26-4467-a3c9-da4f024377c2@glegroupsg2000goo.googlegroups.com

On Mar 1, 10:23 pm, rmcd <rmcd1...@gmail.com> wrote:
> I have a number of non-existent entries in my info tree (C-h i). The stale entries refer to "emacs22" (e.g., "Autotype (emacs22)" ). I can't figure out where they are or even where the tree is originating. I've been using emacs 23.1 (Ubuntu 10.04) and just upgraded to 23.2 (via a ppa). The incorrect links existed in both versions.
>
> C-x C-f points me to /usr/share/info. The dir file there is not what is displayed in emacs. So I'm puzzled. I don't know how to find the file emacs is loading and I don't know how to refresh it to get rid of the non-existent links.  Most topics seem linked correctly. It is just the "emacs22" entries that point to non-existent files.
>
> Thanks for any help.

Something similar:

On debian, when upgrading (packages having nothing to do with emacs)
I sometimes get something to the effect (dont remember error messages
exactly)
Python2.5 info pages not present


  reply	other threads:[~2011-03-03  2:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 17:23 Stale links in Info tree? rmcd
2011-03-03  2:56 ` rusi [this message]
2011-03-03 11:07   ` 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=fbbdec19-ae37-48b1-a1a2-d44d18c6f033@o21g2000prn.googlegroups.com \
    --to=rustompmody@gmail.com \
    --cc=help-gnu-emacs@gnu.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.
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).