Thanks to osxdaily.com for this tip.
First, do this (one-time operation):
$ sudo ln -s /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport /usr/local/bin/airport
Then, anytime you want to query the nearby Wi-Fi networks, make sure Wi-Fi is enabled, and do this:
$ airport -s
This will create output that looks like this (B/SSIDs changed to protect the innocent 🙂 ):
SSID BSSID RSSI CHANNEL HT CC SECURITY (auth/unicast/group)
XXXX 1a:2b:3c:4d:5e:6f -66 149 Y US WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -68 6 Y -- WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -43 6 Y US WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -65 6 Y -- WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -84 1 Y US WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -70 1 Y US WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -58 1 Y US WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -86 11 Y -- WPA(PSK/AES/AES) WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -85 11,-1 Y US WPA2(PSK/AES/AES)
XXXX 1a:2b:3c:4d:5e:6f -58 11 Y US WPA2(PSK/AES/AES)
macOS (tested on 10.11.6):
sudo lsof -i :80
…where ’80’ is the port you’re curious about (substitute any value)
Thanks to Databasically.
Windows (tested on 10 Pro version 1709):
…this will produce a list of ports in use and the PIDs using them)
Thanks to @RickVanover.
netstat -npl | grep 8013
…this will find the name of the process running on port 8013. Thanks to Vivek Gite at nixCraft.
Assuming you have Homebrew installed already:
- Launch Terminal
- “brew install boost” (without the quotes). Notice errors. Try updating brew by doing a ‘brew update’. Failures. Notice by looking at /Users/<userid>/Library/Logs/Homebrew/boost/01.bootstrap.sh that “brew” is at version 0.95 on my machine. Research brew and see it’s on version 1.4.0. Reinstall Brew as though it’s never been installed (even though it is). Notice install says success despite printing a couple of errors during the install. Use “sudo rm /usr/local/share/man/man1/brew.1” and “sudo rm /usr/local/share/doc/homebrew” and re-install brew: /usr/bin/ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)” to fix.
- Retry “brew install boost”. Success! And brew has installed the latest Boost (1.66.0); under the old version of brew it was trying to install version Boost 1.59.0.
So I installed IPython today. It was a bit of an adventure, so thought I’d document it here, in case it helps anyone else (including my future self, heh):
- Installed Python 3.6 (the default, 2.7, included with macOS, isn’t new enough). This puts the “python3” executable on your machine, which you can invoke similarly to “python” (which will invoke the default OS-supplied Python, probably 2.7).
- Got ‘pip‘. Note this was a convoluted process that involved copying some text from the pip website, pasting it into a text file, then executing that text file from python3 like so: ‘python3 get-pip.py’ (without the quotes). This yielded the ‘pip3.6’ executable, located here: /usr/local/bin/pip3.6
- Used the ‘pip3.6’ executable to download ‘ipython’: /usr/local/bin/pip3.6 install ipython
- Noticed that IPython looked like it installed correctly, but ‘ipython’ didn’t run from the command line immediately after that, and the installation path wasn’t noted anywhere in the installation output. Turns out, IPython added its installation location to my PATH via my .bash_profile file, but didn’t tell me. I reloaded my .bash_profile like this, and all was good: source ~/.bash_profile
- Now I’ve got IPython! Invoke like this from the command line like this: ‘ipython’. Output looks like this:
- Macintodffeb798:local me$ ipython
Python 3.6.3 (v3.6.3:2c5fed86e0, Oct 3 2017, 00:32:08)
Type ‘copyright’, ‘credits’ or ‘license’ for more information
IPython 6.2.1 — An enhanced Interactive Python. Type ‘?’ for help.In :
This is probably a good argument to just ditch Windows Batch (.bat) files entirely for Windows Powershell scripts, but if you find yourself in a position where this is not feasible, see this Stack Overflow post about how to check the exit codes of programs run within Windows Batch files.
This is still a problem exhibited in Chrome 55 on the Mac (I know, I know, not the very latest available at this moment, but still, pretty new):
“I was prompted (the little up arrow on the wrench icon) to update yesterday (Sept 28 2012), so I did. Now when I open Chrome after shutting it down, it opens my last session. This is not what I want to happen. I have always set Chrome to open my home page on start. I have confirmed my setting is still set to open my home page. I did change the setting to something else and change it back, it didn’t help. Version 22.0.1229.79 m on Windows 7 Ultimate 64 bit”
1. Tap/click Start > Settings (gear icon) > Apps
2. Locate the app to uninstall and tap/click it.
3. Tap/click Uninstall
Note: Note: these instructions were written using Windows 10 Pro Version 1703 OS Build 15063.0. To see what version of Windows 10 you are using, select Start > Settings (gear icon) > About.
This afternoon I found myself without the ability to type into Spotlight on my new iMac running macOS 10.12.3. All other apps received keyboard input just fine. At the time I was using Spotlight to do some basic calculations involving adding two sums of money up. A bit of Googling lead me to this page, one answer for which was to restart the Spotlight process using the Terminal command “killall Spotlight”. That did the trick for me, Spotlight once again accepted keyboard input.
Going to keep an eye on this site by Matthew Brett, as much of the content seems right up my alley as a Mac developer.
A good post on this topic by Brian Dickens over at HostileFork: http://blog.hostilefork.com/trashes-fseventsd-and-spotlight-v100/
If you’re reading this, you have probably found some USB stick or external drive with files named .Trashes, .fseventsd, .Spotlight-V100 (and possibly even the more rarely reported ._.Trashes) on it. You might also be annoyed to see files in various directories called .DS_Store. Right?