Now we just need a way to get those man pages into Kaleidoscope. So why not come up with a solution to this problem? Assuming the man pages are up-to-date, what if we could compare those man pages between releases? We already have an app that is pretty good at showing differences in text files. But we tried again.Ī diff showing the new raw option that was only introduced on macOS Monterey. We remembered faintly that we tried this in the past but failed. There’s a command called plutil (property list utility) for exactly that task. The next step was the most obvious candidate to begin with. So the search went on for something simple we could use within a shell script. You need to have the Xcode command-line tools. Since Python 2 is end-of-life, what could be more obvious than switching to Python 3? But we quickly realized that Python is no longer installed by default on macOS. In Python, it’s very simple to get the content of a plist entry. The information offered by the “ Learn More…” button led us to believe that we must be using Python 2 somewhere inside Kaleidoscope.Īnd sure enough, we found it buried in a script to extract the version number of a property list. That’s not the kind of message you want your customers to see less than 3 weeks after releasing a brand new major update. When testing Kaleidoscope 3 on the first release candidate of macOS Monterey, we noticed an alert that we hadn’t seen before: “Kaleidoscope” needs to be updated.
0 kommentar(er)
