61–70 of 182 posts
nitpik: I prefer to define the $PATH of every command used in a bash script to prevent some possible shenanigans. sudo="/usr/bin/sudo" launhctl="/bin/launchctl" scutil="/usr/sbin/scutil" nvram="/usr/sbin/nvram" defaults="/usr/bin/defaults" et cetera
Earlier quoted context omitted.
> I'm so used to caps == ESC now, it takes me a minute to realize what's wrong when I'm on a new system/keyboard. Isn't this a bad thing?
Compare how much time you spend using your own system vs others'.
I'm not sure I agree with much of these, which makes sense because this is definitely not 'sensible defaults' it is just someones preferred settings. I wouldn't copy this unless you know for sure this is how you want your system configured.
A before and after picture (video?) for each would be helpful in making a decision in each case.
Also, is there a revert-to-defaults script?
Earlier quoted context omitted.
> Wouldn't be better to call this "cheat sheet"? Why would you call a script that actually changes things and doesn't actually show you a cheat sheet a "cheat sheet?"
Because the lines that do something are nicely categorized with documentation included. Instead of running it all, you can take a look what’s possible and apply it individually.
That's true of any script. The fact that this one is well commented doesn't make it not a script.
A cheat sheet is something you hang on a wall and glance at every so often. A script is something you run to make changes to a system. You can't run a cheat sheet.
Earlier quoted context omitted.
Compare how much time you spend using your own system vs others'.
If you learn the default, it doesn't matter how much time you spend on any given system. I don't get why people make themselves less portable by becoming dependent on non-defaults.
I'm not sure I agree with much of these, which makes sense because this is definitely not 'sensible defaults' it is just someones preferred settings. I wouldn't copy this unless you know for sure this is how you want your system configured.
Presumably everyone thinks their own defaults are 'sensible', otherwise they wouldn't be using them. I think the most sensible defaults are those that come out of the box, rather than spending time tweaking things.
Earlier quoted context omitted.
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).
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.
Wouldn't be better to call this "cheat sheet"? macOS already has sensible defaults, that's how people who have no interest in dealing with computers can use their machines for years with no issues or servicing(unless a latte is spilled over the keyboard). Then, you can customise behaviour for some specific things to fit your workflow. The problem with diverging from defaults without putting much thought on it is that…
> Wouldn't be better to call this "cheat sheet"? Why would you call a script that actually changes things and doesn't actually show you a cheat sheet a "cheat sheet?"