81–90 of 182 posts
Earlier quoted context omitted.
Because if you ever run into a problem where your computer doesn't turn on, the startup sound is your first indicator of whether the screen is faulty, or the board is faulty.
It's a Mac. "whether the screen is faulty, or the board is faulty" have the same fix.
It'd be awesome if this could help with two anti-user innovations in recent macOS: 1) Disable Apple Music, which has the annoying habit of opening every time I touch my headphones, and is not removable from my own computer. 2) Force macOS to remember that I gave Chrome location permissions instead of reseting Chrome after every update.
https://git.eeqj.de/sneak/osx/src/branch/master/custompkg/ro...
Sorry, soon as I saw the line that disables the startup chime I knew everything here was wrong.
Can you elaborate? I despise the startup chime and disable it on all of my Macs. Why should they announce a startup when none of my other devices do? Why would I want to wake a sleeping baby or annoy other library patrons? This is one of the most obnoxious decisions Apple ever forced on its users (and, yes, I was happy when the illuminated logo on the laptop lid was finally put to rest).
It'd be awesome if this could help with two anti-user innovations in recent macOS: 1) Disable Apple Music, which has the annoying habit of opening every time I touch my headphones, and is not removable from my own computer. 2) Force macOS to remember that I gave Chrome location permissions instead of reseting Chrome after every update.
Safari does this too.. Apple is on some horse about requiring user intervention for every single location request even from sites you’ve already allowed in the past. It’s annoying.
I love that this document takes inscrutable OS X settings and translates them into familiar human-readable settings. I have no idea what "NSGlobalDomain NSNavPanelExpandedStateForSaveMode" is, but I understand what "Expand save panel by default" means. However, like other people, I'm not sure that I agree with this particular set of changes. Is there a project somewhere that packages these options into a GUI? I know…
It’s probably not exhaustive, but quite convenient.
As most of the comments here on HN are taking issue with the weirdly editorialised HN title, rather than with the content, it would be great if a moderator could change the title to something more accurate like "Mathias Bynens' macOS defaults"
I can change the title. I just set it to that because that is what Mathias calls it.
I love that this document takes inscrutable OS X settings and translates them into familiar human-readable settings. I have no idea what "NSGlobalDomain NSNavPanelExpandedStateForSaveMode" is, but I understand what "Expand save panel by default" means. However, like other people, I'm not sure that I agree with this particular set of changes. Is there a project somewhere that packages these options into a GUI? I know…
Onyx has a bunch of these: https://www.titanium-software.fr/en/onyx.html It’s probably not exhaustive, but quite convenient.
This gives me the impression that command line configuration interface for MacOS is really good, at least compared to FreeBSD, Windows or Linux.
While it's true that there are many command line options available, I use a similar script to configure my Macs and it can be quite painful compared to Linux. First of all, this is a script, not a configuration file, so the changes only take effect when it is run, not when a user starts a session (though I suppose that could be done). There are any number of ways the settings can be changed and preserved without your…
I don’t think there is anything wrong with re-setting a bunch of properties in plist files every time a session is opened.
You’re right, the CLI is a difficult to use if you don’t know it beforehand. And even knowing it does not tell you about the various properties you can change with default. At least the script here points to some useful options.