![]() I’m glad I found this solution because I never would have known how to do what this somebody did. Nope, I Googled for Keyboard Maestro and Git and discovered someone else had solved it already. The good news for you is this isn’t going to be a 20-minute dissertation on everything I tried to do and how it failed and finally I figured it out. When I decided I really needed a way to do version control on my Keyboard Maestro macros, my first thought was to do it in Git. If you mess up your code (or any kind of document you put into Git) you can always revert back to a previous version by looking at those commit messages you carefully crafted. These commit messages are essential to figuring out which version you might want to roll back to.Īll of these committed versions of the same file live on your computer, but you can also push them to another machine on your network for safe keeping, or push them up to a repository on the web such as GitHub or Bit Bucket. This commit message tells future you something about that version of the file. ![]() When you commit, you also add a commit message. With Git, when you want to save a version of a file, you do what’s called a commit. Not that I would ever break my own code of course. It’s pretty nerdy, but I’ve really grown to enjoy the safety net that it creates when I program. In the Programming By Stealth podcast, Bart Busschots taught a 20-part mini-series within the series all about version control, and specifically the tool Git to do version control. ![]() Since Keyboard Maestro doesn’t have its own built-in version control, I went on a hunt for a way to do this. I’ve had to ask Mike to send the original to me again and now I have to try to get it back to the configuration that did work. For a while it got better, but then whatever I did completely broke the macro. When something got fiddly with the macro, I started poking at it changing things. If you like the chapter marks in the NosillaCast, you should thank Mike for them. Mike Price worked out a really nifty macro for me that streamlines the addition of chapter marks into my recording software, Hindenburg. But what if you’re working on a more complex macro with 20 or 30 separate steps and it’s almost working, but you tweak it in a couple of different places over the course of days or weeks and it breaks? How do you figure out what you changed? If you’ve got a simple little macro you’re working on with 3 steps and you try to add a 4th step and it falls over in a heap, it’s pretty easy to roll back the change by removing that 4th step. If you change something in one of your macros, there’s no way to get back to a known good version. ![]() Keyboard Maestro is essentially like a little programming language with a graphical user interface, but it’s missing an essential part of any document creation tool – there’s no way to save versions of what you create. I’ve talked quite a bit lately about learning to automate things on the Mac using the fabulous tool Keyboard Maestro. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |