It seems that the generation of the info files, especially with the jump indications at the end of the first file, are improperly created. WOuldn't this explain the problem?
Yes, it might explain it, except that those jump indications are correct, as far as I can tell. That's why I said it is necessary to have more files. My guess is a parsing problem in standalone info. Otherwise I'd expect all the nodes to be unfindable, not just the one with the period in the name. see at the end of the first file there is a binary blob giving information on where one has to jump to in the other files. True??? Yes. The binary blob is nothing very magical - it's character counts to find the nodes, kind of like all the subfiles are concatenated together, ignoring the preamble junk. The first table tells the count at which each subfile starts. Something related: The most puzzling, even for me, error/bug/strangeness is that info jumps to the man page of "top" when you enter info ./notexistingfile instead of going to the top node or giving an error message ;-) Unrelated. Isn't it wonderful behavior? Explanation: - info tries to find the top node to search for notexistingfile; - then that search fails; - there is no info page for top; - so it falls back to searching for the man page for top. Yes, this is a silly bug. I've never mustered enough interest to fix it. Shame on me. Thanks, Karl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]