A slightly different way of using Hook

The key function of Hook (at least in my workflows), is to quickly provide a URL for any document (and sometimes even, given the excellent scriptability, to sub-components of a document or database).

The key weakness, at this stage, is in helping us find these URLs when we need them.

The current approach (link-collection menus available only from central working documents) inevitably fails us whenever a project has more than one central working document, either:

  1. at a given moment (2 or 3 main documents in a given project), or
  2. over time (different central documents at different stages of the same project.

In the medium or long term for Hook, project-level link collections for the Hook GUI seem likely to imply a root and branch rethink of the DB structure, and possibly even of the central marketing metaphor, but in the meanwhile, I find that when I do use Hook it is in a simpler but still very useful mode, in which all projects:

  1. Have their own project folder,
  2. have a TaskPaper (or other .txt) summary file at the top level of that folder, which (inter alia)
  3. Contains all the Hook > Copy as Markdown Link URLs that the project accumulates and needs.

A meta level of this, in my own case, is that I also have an ~/activeProjects.taskpaper file, which:

  1. Opens automatically at login,
  2. is always just one (Keyboard Maestro) shortcut away,
  3. contains (inter alia) names of, and Hook-pasted Markdown links to, the current handful of active project folders.

In short:

  • Hook > Copy as Markdown Link is proving very useful.
  • Hook > Copy as Link well … to be honest … in this form … not so much …

To put it all a different way, the key cognitive links are not, in fact, document -> document, they are really project ⇄ document.


A footnote on shortcuts and cognitive load:

At the moment, I find in practice that having to open the Hook window adds operational and cognitive overheads without real reward.

All that I really need is a keyboard shortcut for a Hook-supported Copy as Markdown Link

Perhaps an addition would be valuable here:

so that we can easily harvest the real value of Hook (Copy as link) without repeatedly incurring the cognitive costs of having yet again to summon, use and dispense with the Hook window.


In the meanwhile, a simple Keyboard Maestro macro:

Thanks for explaining how you use Hook, @RobTrew, making a feature request, and even sharing a macro for it.

In fact, it is on the internal product road map to make some of the Hook window commands accessible without invoking Hook. (at least I have requested it internally :wink: ).

Excellent points – and thanks for the KeyboardMaestro macro! This is something I’ve posted about before: that what is most useful is being able to link a current item to an ongoing, persistent project. One idea that your suggestion prompts in me is to have, for each of a handful of active projects, a text file as a link repository to which one could append the Markdown link (perhaps with date-stamp).

For me, that would ideally be appended to a specific “sheet” in a project “group” in Ulysses, except that Ulysses is so tricky with pasting standard Markdown formatting.) Worth exploring further. In KeyboardMaestro, I’d then have all the macros assigned to the same keyboard shortcut, which then calls the “palette” menu, so that I can just pick the destination from the list.

A further detail:

A ‘current context’ (displayed in the menu bar) is something which I have for some time used textbar to display in my macos menubar.

It has hitherto been the text of the first line (in the working TaskPaper file of the day) that contains a @now tag, but I’m experimenting with:

  1. Displaying instead the name of the project I’m working on and
  2. using the taskpaper file in the project of that folder as:
  • the automatic-append destination of any new Hook links which I create with a KM keystroke,
  • the source of the KM-launched menu of Hook links when I am working on any file contained by that folder.

I find that setting a default project for the current working session (as a KM variable, for example, or by setting a tag in a TaskPaper file), reduces the slightly cumbersome two-step business of

  • copy as link (in one location) and then
  • link to copied address in another location,

down to a single hotkey which:

  • copies a Hook link in Markdown format,
  • automatically saving it in in the TaskPaper file for the active project.

All links in that file appear in a menu offered by a link-menu hotkey.

1 Like