On Mon, May 17, 2021 at 07:25:38PM +0100, Brian wrote: > On Mon 17 May 2021 at 11:01:33 -0400, Greg Wooledge wrote: > > [...] > > > Done! Now, let's try that with pinfo date. I ran pinfo date from my > > shell, which took me to one of the pages within the tree of coreutils > > texinfo documentation corresponding to the date program. This particular > > page is titled "21.1 ‘date’: Print or set system date and time". > > > > I pressed /, typed %F, pressed Enter, and I got: > > > > "Search string not found..." > > > > That's because pinfo doesn't search beyond the current page, and the > > current page is just a menu of links to other pages. > > As a longtime user of pinfo I appreciate your exposing it to a wider > audience. > > Regarding seaching: does the s key do anything to cause you to modify > your observation?
Huh... that's interesting. OK, these key bindings are *really* not ideal, and I think I found some kind of bug. According to the man page, there's no default key binding for "search again" (KEY_SEARCH_AGAIN_1), but in Debian's /etc/pinforc, it's bound to 'f'. OK, armed with that knowledge, I did "pinfo date", then "s" and "%F" to search for the same word as before. Then I pressed "f" which advanced me to the next instance. Then "f" a second time, and it says: Tag table is corrupt, trying to fix... (press a key to continue) Pressing space takes me back to the main page of coreutils.info. I'm just gonna go ahead and report the bug. And thanks for the tip.
