Version 9.7.2

• Bug fixes
  • When the "Search for" field was empty and a "Find" operation triggered, a popup "You cannot search for spaces" was wrongly presented. Now nothing happens at all.
  • Searching for characters that have a special meaning in a RegEx crashed the report (#40)
  • Search with RegEx and then trigger a replace can crash (#41)

Version 9.7.1

• Installation can now deal with OneDrive
• "Update" improved

Version 9.7.0

The API call as well as the user now allow to specify an additional (optional) argument that is used to populate the “Search for” field.

Version 9.6.4

Serious bug fix: when a function or a script was renamed implicitly via a "Replace" operation, Link/acre were given the old name rather than the new one, effectively loosing the change when the WS was destroyed one way or the other.

Version 9.6.3

• "Search QNL" corrected: "#" cannot be a hot key.
• Under some circumstances Fire did not find its release notes

Version 9.6.2

Version number corrected: both patch number and build id were wrong.

Version 9.6.1

If SALT's cmddir carried a symbolic name as in [HOME]/MyUCMDs then Fire did not find its documents.
The menu item `Reports > Search QNL" did not report its hot key: F7

Version 9.6.0

• The "Search ⎕NL" report now allows to start the search in either # or in ⎕SE.
• Bug fix: The last version was not able to find any of the HTML documents offered via the "Help" menu

Bug fix regarding exposed names in #

People who do not tick "Options > Object Syntax > Expose GUI Properties" could not use "Replace one-by-one"

Three bug fixes

• Bug fix in ListNamespaceTree_
• Bug fix in GUI.LetLinkDelete
• "Start looking here" offered #._tatin or ⎕SE._tatin etc even if "Ignore Tatin packages" was ticked