On Sat, Oct 17, 2026 at 08:09:05PM +0800, aidan wrote: > > There isn't a corresponding feature in Emacs Info as far as I know > > Yes, I think this is where stand-alone Info has an advantage over > Emacs Info. Its performance is also much better. > > > I've attempted a fix, although I would not be surprised if there are more > > bugs and/or inconsistencies in this feature. > > I also found other ways to reproduce it. > > 1. run info > 2. press `M-x tree-search`, enter `Index, Index` as the search term, > and press Enter, the cursor jumps to `(texinfo)Tips` > 3. press `M-x search-next`, the echo area shows "No more matches" > 4. press `M-x search-previous`, the cursor gets stuck in the echo area > and cannot move > > 1. run info > 2. press `M-x tree-search`, enter `sphinx` as the search term, and > press Enter, the cursor jumps to `(libgccjit)Submitting patches` > 3. press `M-x search-next`, the echo area shows "Going back to last > match from Top", the cursor gets stuck in the echo area and cannot > move
Thanks for the reports, there must be something strange going on with starting the tree search from the dir node. For the first report, the previous bug you reported (where the search string did not appear anywhere in any of the referenced manuals), the freeze also happened in the code to search backward - in my fix, I stopped this code from running in the first place. I didn't replicate the second failure because I don't have a libgccjit manual installed. Because the tree search goes across all the manuals referenced by dir, if one of the manuals has a strange structure that causes problems, the tree search will hit it. With a debugger, I found Info was stuck in the "mtools" manual. When I removed the line for "mtools" from the dir node, I found with your first test case, "M-x search-previous" went back to the dir node and printed the message "No more matches", which was a more successful outcome. (Of course, on your system it could be some other manual where the problem occurs.) Just running "info mtools", I had problems with the tree search feature. I notice that some of the nodes in this manual have duplicated menus (see end of email). I will investigate this manual further and try to make the tree search more resilient to malformed menus, if this is what the problem is. File: mtools.info, Node: Configuration, Next: Commands, Prev: Common features, Up: Top 3 How to configure mtools for your environment ********************************************** * Menu: * configuration file location:: * default values:: * global variables:: * per drive variables:: * parsing order:: * old style configuration:: 3.1 Description =============== This sections explains the syntax of the configurations files for mtools. The configuration files are called '/etc/mtools.conf' and '~/.mtoolsrc'. If the environmental variable 'MTOOLSRC' is set, its contents is used as the filename for a third configuration file. These configuration files describe the following items: * Global configuration flags and variables * Per drive flags and variables * Menu: * configuration file location:: Where mtools looks for its configuration files * general syntax:: The layout of the configuration files * default values:: Why you don't need a configuration file in most cases * global variables:: Variables that are independent of the drive * per drive variables:: Variables that are specific to a given drive * parsing order:: Location of configuration files and parsing order * old style configuration:: Backwards compatibility
