From: Galen Boyer <galenboyer@hotpop.com>
Subject: Re: emacs info behaving strangely
Date: 8 Jan 2003 09:30:14 -0600 [thread overview]
Message-ID: <uy95vwtjh.fsf@standardandpoors.com> (raw)
In-Reply-To: mailman.62.1042038793.21513.help-gnu-emacs@gnu.org
On Wed, 8 Jan 2003, tiarnan.ocorrain@cmg.com wrote:
> Hello--
>
> something seems seriously wrong with the info facility in emacs
> on my machine: when I try to access (for example) the node for
> CVS, I get "No such anchor in tag table or node in tag table:
> Top". However, "info cvs" from the shell accesses the file. The
> directories that contain info files (including that from CVS)
> are in my Info-directory list.
I have the following entry in my dir file.
* CVS Manual: (cvs.info). CVS Manual.
I have the files cvs.info and then cvs.info-1/9
I found the "." directly after the second ")" seemed important.
Also, of course, the filename between the ()'s needs to match the
first one in the hierarchy, exactly.
--
Galen Boyer
next parent reply other threads:[~2003-01-08 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.62.1042038793.21513.help-gnu-emacs@gnu.org>
2003-01-08 15:30 ` Galen Boyer [this message]
2003-01-08 15:07 emacs info behaving strangely Tiarnan O Corrain
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=uy95vwtjh.fsf@standardandpoors.com \
--to=galenboyer@hotpop.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.
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).