When I update Brew I minimize the terminal window so I can work on something else while it is running. Every so often I check to see if it finished. Then I read through the history to see if there is any work I need to perform by hand. For example sometimes Brew can’t link things and other times the package won’t even install. This has always worked well. Today I had a funny surprise though.
THANK YOU SILESKY
tell application "System Preferences" activate set the current pane to pane id "com.apple.preference.universalaccess" delay 1 # needs time to open universal access tell application "System Events" to tell process "System Preferences" to tell window "Accessibility" tell scroll area 2 to tell table 1 to tell row 6 #open display preferences select end tell click checkbox "Use grayscale" end tell end tell tell application "System Preferences" to quit # Sierra: System Preferences -> Accessibility -> Display -> Use grayscale
tell application "System Preferences" activate set the current pane to pane id "com.apple.preference.universalaccess" delay 1 # needs time to open universal access tell application "System Events" to tell process "System Preferences" to tell window "Accessibility" tell scroll area 2 to tell table 1 to tell row 6 #open display preferences select end tell click checkbox "Invert colors" end tell end tell tell application "System Preferences" to quit # Sierra: System Preferences -> Accessibility -> Display -> Invert colors
Run them from the command line. Maybe make your screen black and white at night or invert colors for screencasts or working in sunligh.
alias togglegrayscale='osascript /Users/gcr/util/sspadtogglegrayscale.scpt' alias invertcolors='osascript /Users/gcr/util/sspadtogglecolors.scpt'
If you want to lock and unlock your files from the command line using Finder instead of using
chmod there here are two aliases to do it:
alias flock=’chflags -R uchg’
alias funlock=’chflags -R nouchg’
My desk has 3 monitor on it—two external and one built into the Mac. They are used like this:
- Top left
- Top right
- Pulse SMS
I tried to keep it simple but it is still easy to forget which application that I’m working with. I wanted a way to highlight the window that had focus and I found it with HazeOver — Distraction Dimmer for Mac.
I can’t find the
git 2.10 binary so I run
Excellent, found it.
And then I check it’s version to verify I am looking at the right version
git version 2.21.0
Oops that isn’t what I wanted.
There must be another
git getting loaded earlier in the search path.
Here is how to find out where all copies of
type -a git
git is /usr/local/bin/git git is /usr/local/bin/git git is /usr/bin/git
Look for the right
git at version 2.10
git version 2.21.0 git version 2.14.3 (Apple Git-98)
I want the second one.
That is how to track down the location of a binary file on macOS that appears multiple times in the search path.
After using it for a few days I already love it.
- I have a document open, and I want copy a few parts from it, into an email. But I don’t want to have to command-tab between the document and the email. So I just comand-c… and then go to my email. I do that all the time.
- When I care about something that I am reading, a phrase, a word, and I want to remember it… maybe. So, the copy buffer is persistent, and I can go back anytime and look up what I may wanted to use.
Flycut: It’ll Remember It For You (but not Wholesale ).
If you are an Emacser you’ll instantly know and love this as a macOS Kill Ring.
Security concern: persisting sensitive information in your clipboard like this, it is easy to forget about it. Fortunately Flycut doesn’t copy values from password fields. Additionally it keeps it’s data local to your computer never sharing it between your other computers or devices. However, it is just like any other security concern so be careful what you keep in there.
Save a few mouse drags and clicks to open Finder by pressing Option(alt)-Command(⌘)-Space.
It is even faster than hitting Control-Space to start Spotlight.
Sometimes Bash needs its debugger but it can’t find it. It looks like this:
/usr/share/bashdb/bashdb-main.inc: No such file or directory -bash: warning: cannot start debugger
For example when you start
bashdb yourself with
bash --debugger or set
shopt -s extdebug. Another example is when your terminal turns it on.
Here is the fix that worked on my box:
brew install bashdb
bashhome=$(brew –prefix bash)
bdbhome=$(brew –prefix bashdb)
ln -s $bdbhome/share/bashdb $bashhome/share/bashdb
Be sure to install them.
macOS people maybe update now.