This is yet another good reason to manage all of your hotkeys/shortcuts in KM instead of Mac SP.
In the KM Select or Show a Menu Item action (KM Wiki), you can easily allow different menu item names:
The Select Menu action allow you to specify multiple options separated by a vertical bar (eg Show|Hide) to allow for toggling or varying menus. They will also ignore the difference between three dots (...) and an ellipsis (…) so you do not have to worry which one the menu uses.
Alternatively, you can start the name with an ^ and use a regular expression to match the menu.
I'm seeing a lot of that. You might be interested to know that even Shane Stanley is waiting until at least the .1 version of High Sierra is released, and he, by his own statement, is known for being an early adopter of macOS upgrades.
There are a lot of High Sierra complaints on the AppleScript Users List.
Another reviewer recommending to wait to .1 or .2 update.
I think the vast majority of people who decide to upgrade on day one will be essentially fine. But if it’s at all possible for you, you should wait for version 10.13.1 or 10.13.2 to update to High Sierra.
Aside from the fact that you’ll keep getting security (and Safari) updates in Sierra, I make this recommendation for three reasons:
The number of user-facing improvements is small. The Photos app gets the biggest overhaul, and it’s a good one, but otherwise you’re not missing very much.
Some things just aren’t done. APFS won’t work on Fusion Drives. External graphics support is usable but not finished. iMessage on iCloud isn’t here yet. The new Metal-powered windowserver is still intermittently buggy.
Even with fully finished, bug-free features, Apple has been clear that these are foundational updates. Meaning: cool, user-visible stuff will be built on top of them in future releases, but that stuff isn’t here yet.
10.13 has instant-solved two serious and very annoying issues for me. Both issues had been persisting across all 10.12, from .01 to the last revision. One of them probably since 10.11.
So, for me, 10.13 was like Christmas.
Of course, your milage may vary. If you don’t suffer any problems with 10.12, then this might be a reason to not update to 10.13.
But don’t forget the security issues that are being fixed in 10.13 but not in previous systems.
I'm glad the upgrade has worked well for you Tom. Would you mind sharing the issues that it solved for you?[quote="Tom, post:14, topic:7194"]
But don't forget the security issues that are being fixed in 10.13 but not in previous systems.
[/quote]
One was a lag in the Finder that occurred (apparently) randomly, accompanied by something that appeared like a memory leak to me. Finder windows took 20s or so to become frontmost when clicked, and Finder was consuming a two-figure amount of memory at those occasions. I think it was related to the iCloud sync, because most of the time it was OK after killing cloudd. (But I might as well be wrong, since some months ago I said Dropbox was the culprit. Anyway, it is gone now.)
The second one was a continuous auto-destruction of the pbs preferences (the pbs.plist file). This is the file where all your shortcuts for the Services are stored. (System Preferences > Keyboard > Shortcuts > Services).
Each time I changed a shortcut everything has been reset to the defaults. You imagine the annoyance!?
I worked around it by tracking any changes to that file by Hazel, so I could restore it. Furthermore some shell commands like /System/Library/CoreServices/pbs -flush en seemed to be useful, before touching any shortcut.
I was referring to the last "supplemental" update that covered a key chain vulnerability present not only in HS but also in Sierra and Capitan. It was first only released to HS (not to previous systems), but it seems in the meantime it has been released also to the legacy systems.
Not sure though if it really has been released to all systems.
I haven't seen that in El Capitan, but then I have very limited use of iCloud, and I was using TotalFinder, but now have switched to Path Finder (which I really like).
I was referring to iCloud Documents sync, which wasn't available with El Capitan. (Only since Sierra.)
But as said: It depends on how well your current system is working for you. Sierra was not working well for me (not even at 10.12.6), High Sierra was a God-sent.
LOL, in the very moment I was thinking about if I should tell you that for me High Sierra is still way better than Sierra (and El Capitan)
From the issues in the Twitter post I have experienced one (the movie file not launching due to “verifying”, but this also with DMG files in one or two occasions; indeed annoying)
I just contributed that, because I know you love to collect facts (and prejudices) “against” HighSierra
To be clear, I'm not for, or against, any macOS version in general. My evaluation is primarily based on whether or not there is a compelling reason to upgrade, and whether or not the new version breaks any of my essential workflows.
That's why I keep asking you guys who have upgraded what your experience/evaluation is so far.
So, I'd love to hear/see why you think "High Sierra is still way better than Sierra (and El Capitan)".
I have switched to Path Finder, which I like much better than Finder.
It is not as scriptable as Finder, but so far I've been able to start a script with PF, and then switch to Finder if needed. Works seamlessly.
I used to use PF in the past, but some years ago i went back to use the more native stuff. But you are right, in Sierra times, when the Finder really used to stall for 20s or more I often used ForkLift as a Finder replacement. (Which is similar to PF.)
I myself reverted back to El Capitan from High Sierra. The main reason here was Karabiner not working well with High Sierra where a lot of functions were lost and Apples Server app lost the function of WebDAV due to apfs.
Another Problem with High Sierras Keyboard driver is that Keyboard Maestro doesn’t detect the Apple keyboard keys via “USB Device Key Trigger”, which is pretty annoying. I know however that i can use Hotkey triggers, but in certain apps they didn’t trigger unless i added them again → went into the app and if they work never go out.
In El Capitan all those things work well and without any issues.
