Re: info goto node with dot

2006-02-02 Thread Norbert Preining
Hi Karl! On Sa, 28 Jan 2006, Karl Berry wrote: What was the reason that node names cannot contain the sequence . or .\t etc ?? The only thing I can think of is that it is somehow related to the dir file, which contains entries like this, with a period followed by

Re: info goto node with dot

2006-01-29 Thread Karl Berry
GNU. Free.Document.License and boing, I cannot go the the node. Ah! Is it documented somewhere that node names *SHOULD NOT* contain .? Yes, in the Texinfo manual. If yes, we can also forget about this and close this bug, because info is not used according to the

Re: info goto node with dot

2006-01-29 Thread Norbert Preining
On Fre, 27 Jan 2006, Karl Berry wrote: I briefly grepped through the source, and I think (no promises) the relevant code might be the horribly ugly test in skip_node_characters in search.c, if you feel like messing with it for a few minutes ... Hmm it seems that you are right: At the end of

Re: info goto node with dot

2006-01-28 Thread Karl Berry
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

Re: info goto node with dot

2006-01-28 Thread Norbert Preining
Hi Karl! Good to hear from you, hope you are doing well in the new year! On Don, 26 Jan 2006, Karl Berry wrote: 146133 and 151850 Matching vs. Searching -- If you take a info file which is split into different files, and there

Re: info goto node with dot

2006-01-28 Thread Karl Berry
What was the reason that node names cannot contain the sequence . or .\t etc ?? The only thing I can think of is that it is somehow related to the dir file, which contains entries like this, with a period followed by whitespace: * Bash: (bash). The GNU

Re: info goto node with dot

2006-01-28 Thread Norbert Preining
So my suggestion is, try getting rid of that test, and see if things basically work (and matching vs. searching can be found). If it looks Ok, so you would suggest trying out: --- search.c.orig 2006-01-28 23:03:18.0 +0100 +++ search.c2006-01-28 23:05:00.0 +0100 @@

info goto node with dot

2006-01-26 Thread Karl Berry
Hi Norbert, Back on this from November ... 146133 and 151850 Matching vs. Searching -- If you take a info file which is split into different files, and there is a node containing a `.', jumping to this node does not work. I