Thank you both for the years of developing the Sigil application.
What am I missing?
- The ability to rename files in BookBrowser via plugins.
Explanation: I KNOW this requires checking all linkages to every other file, but since Rename in the GUI does this all the time, the plug would do it too.
- Ability to enable/disable adding Sigil version to metadata in the OPF file.
Explanation: I would not like to offend the creators and developers of Sigil with this proposal, I simply express my subjective opinion. I am proud to use Sigil, but like having clean metadata. Theoretically, the output plugin could help, though invoking a plugin and simply hitting "Save" makes a difference.
- Templates for the table of contents/index.
Explanation: I mean the possibility to "build" a different layout, because the current one has a hardcoded <div> structure, even if I adapt it to my needs, another TOC refresh will restore the default layout again.
This is where a plugin could help, if there was a function that would give the TOC/index "ingredients" to styleaccording to the current table of contents settings, including "sigil_not_in_toc", "sigil_index_marker" etc. Sure, you could write a plugin to do the table of contents in a different form, but the plugin would do 99% of what Sigil is already doing, adding only the final layout of the TOC.xhtml file.
----------
As for Saved Searches:
In my opinion, the existing solution is not perfect. The fact that it forces you to pre-set all the options and then load saved searches is the weakest point. It also means that - although I like this option - I rarely use it. It may seem strange, but I have quite a few different searches where the key information is whether they are normal or regex searches.
If I save them in Saved Searches in a folder, I always have to remember that these are normal, and these are regex ...
I would like to be able to have any searches in the folder so that it could be performed sequentially, e.g.
- regex
- regex
- normal
- case sensitive
- regex, enabled "DotAll"
- normal
- regex
etc.
I see different solutions, always taking into account backward compatibility.
Sample solution:
We ignore backward compatibility

Just kidding.
For backward compatibility, we ignore the existing sigil_searches.ini file and from version 1.5 only save sigil_searches_new.ini
The file structure may be the same:
Code:
[search_entries]
1\Name=XXX
1\Find=YYY
1\Replace=ZZZ
but we add
If someone insists and downgrades Sigil:
* will have its old file
* if he wants to use newly created searches he can make a copy of the new ini file and name it sigil_searches.ini and IMHO should work with previous versions of Sigil.