Years ago, at my grandfather’s funeral, my dear neighbor Munzer gave an impassioned account of their relationship. His speech ended something like this:
Every time we had a bad day, Ed would say to me “Sure, but we have this beautiful sunset! And now, there will be no more sunsets.”
I paraphrase grotesquely. But it was a beautiful and sad notion. And he was right. Growing up, we had some unbelievable sunsets, and each one really was the signal for a fresh start; a new day.
There will always be sunsets.
I grew up on this mountain, and have biked it for decades. It doesn’t get any better than this.
Way back in 2009 I wrote up some instructions on how to use LilyPond with jEdit on Mac OS X. I never much attached myself to jEdit, but it was serviceable for LilyPond at least. Today however I use Sublime Text for just about all my coding, and it makes a perfectly fine replacement for the LilyPond app’s built-in editor, with a bit of configuration. Here’s how I have mine set up:
Install SubLilyPond into Sublime Text via Package Control
Add a build system to Sublime Text (Tools → Build System → New Build System…) based on these nice instructions. Specifically, I named my file lilypond.sublime-build and it had this code in it, which specifies the exact path to the Mac LilyPond binary in my Applications directory:
"cmd": ["/Applications/LilyPond.app/Contents/Resources/bin/lilypond '$file_base_name.ly'"],
Now .ly files will get syntax highlighting in Sublime Text, and the F7 or ⌘+B keystroke will build my PDF file. I then keep the working PDF loaded in Google Chrome (which has a built-in PDF viewer), and just hit refresh on that window every time I want to view the results of the build.
Was on my way out of the office today, and then this happened:
Deviled eggs with bacon fried in duck fat. Handmade mozzarella with berries. Cheese assortment. Comartin Cellars 2011 Tierra Alta Syrah.
Not too shabby for a hump day.