Unbreakable unls have already changed my workflow

10 views

Skip to first unread message

Edward K. Ream

unread,

Jul 5, 2023, 8:24:52 AM7/5/23

to leo-editor

I am using unbreakable (gnx-based) unls (clickable links) as a lightweight alternative to clones.

As you probably know, I use clones extensively while developing code. I create an organizer node for each issue/PR. This organizer node contains clones of all nodes related to my work.

Once I finish work on an issue, I move the organizer node so it is a child of another node. But now a slight problem arises.

Several times recently, I have wanted to find the organizer node for the big PR. Oops: the PR's organizer node is now harder to fetch. Yes, I could clone that node as usual. But I don't want to leave the clone lying around! So I delete the clone, only to fetch (re-clone) it later.

The solution: create an unbreakable link to the PR's node in my top-level "To do" node!