Hook integration scripts v. 100 updates EagleFiler integration

An update to Hook’s integration scripts has been released (version 100) with major improvements to how Hook relates to EagleFiler.


For information about Hook’s new integration with EagleFiler, please see Using Hook with EagleFiler. In sum, Hook now defaults to using hook://file addresses (URLs). This has a major advantage in that whether you select a file in EagleFiler or open it with another app (like Preview or Skim), you will see the same links.

If you would prefer to stick with your previous integration scripts, please see Previous Scripts for Using Hook With EagleFiler – Hook.

When one gets into the habit of using “Link to New”, one can produce a lot of new files. Using “Link to New” with EagleFiler is particularly handy. It is not necessary to select EagleFiler in the “Link to New” menu to do this. Just choose your EagleFiler library folder (or an EagleFiler scanned folder) as the default destination for “Link to New” documents (on the Notes tab). This is mentioned in Using Hook with EagleFiler.

We intend to publish one or more “showcase” blog posts about using EagleFiler and Hook together.

Discourse website handling

You may have noticed that in the context of some discourse forum topic, Hook shows you all the links to the current topic (ignoring the final /number part of of the URL). We’ve generalized this support a bit in the latest release of the integration scripts. We will publish more information about this shortly.

formatting changes

There are also formatting improvements to

  • OmniFocus 3
  • Preview
  • TextEditor
  • Mail
  • BBEdit

We will gradually improve the formatting of the other integration scripts.

An in fact, on January 16, we added a blog post showcasing Using Hook with EagleFiler by C-Command Software – Hook.