Chris Klimas

Huh! That is definitely an unintended consequence of how the UI options work. Another workaround is to [reset Twine's preferences](https://twinery.org/reference/en/troubleshooting/wont-start.html).

Seems like a reasonable idea, though the concept of next/previous is a little tricky in a spatial context. What determines the ordering of results? It's tempting to say "top to...

> > Seems like a reasonable idea, though the concept of next/previous is a little tricky in a spatial context. What determines the ordering of results? It's tempting to say...

> > I feel like that could be confusing--IDs are random. > > Less "random" and more assigned based on the order of Passage creation/addition. > > But I agree...

@david-donachie in a new issue, could you post a screen recording of Twine not finding a passage by name? That's worth fixing. The goto function uses fuzzy matching using [Fuse.js](https://www.fusejs.io)...

A couple possible workarounds: 1. [Disable editor extensions for Chapbook](http://twinery.org/reference/en/story-formats/extensions.html) 2. Add the following to [user.css](http://twinery.org/reference/en/customizing/advanced.html): ```css .story-edit-route .link-connectors { display: none; } ```

There's a minor hassle here in that implementing this means we'd have to update documentation in two places (the reference and --help output), but I think it makes sense to...

#540 is similar but not exactly the same request.

The next minor release of Twine will include an Electron version bump, FWIW. I would target latest available when that happens.

Does the inconsistency disappear if you copy and paste in your search term all at once? I was doing some work on the fuzzy finder for 2.6 and discovered that...