I do so appreciate developers who are willing to make these sorts of app tweaks to help their users. I decided to reach out to SnippetLab’s developer, Renfei Song, and we got into a discussion about my desire to use SnippetsLab with Hookmark.Īfter a bit of back and forth and me explaining the principles in a little detail, a new beta release of the app was forthcoming with a new menu item that I could then use to get the specific deep link I was looking for. Unfortunately, I couldn’t quite get one easy access to one thing. I looked at a few options with the SnippetsLab application, and I could get pretty far in getting it to work with Hookmark. More so, what I really wanted was to “hook” this into my existing automation documentation workflow utilising Hookmark and Obsidian. I wanted to find a way that enabled me to easily generate a way to track the relationship between a snippet and where it was used. The challenge then you end up with multiple locations where the code is used, and multiple places to maintain the code if there are any changes. In these cases, SnippetsLab is my go to utility.Īs far as possible, I like to use a cenralised library approach for my code, but as noted above, not all code snippets belong in a library. Code that isn’t practical to include in a single library. Sometimes I write (or find) code that I may want to use in several standalone places. SnippetsLab is a Mac code management utility that allows you to keep common snippets of code easily accessible. In this post I am going to explain a bit more about this. A small update to the user interface has enabled me to construct a basic integration with Hookmark (the app formerly known as Hook). My efforts to link together my documentation and automation took a little jump forward recently with a new beta of the code library utility called SnippetsLab. Automation Documentation: Hooking SnippetsLab
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |