-
Protected: Andrea’s Surprise Party
-
Installing Boost on macOS High Sierra (10.13.2)
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.
-
Protected: Bigelow Holiday Party 2017
-
Indulging my hobbies
-
How I installed IPython on macOS 10.13.1 High Sierra
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 [1]:
- Macintodffeb798:local me$ ipython
-
Connecting to remote MySQL servers so they appear as though they are local
Simple! Just create an SSH tunnel. Or a couple of them.
Create SSH tunnel to MySQL server running on port 3306 on 192.168.213.207 so that server appears to be running locally on port 3307:
ssh -L 3307:127.0.0.1:3306 root@192.168.213.207 -NnT
Create SSH tunnel to MySQL server running on port 3306 on machine2 so that server appears to be running locally on port 3308:
ssh -L 3308:127.0.0.1:3306 root@machine2 -NnT
Compare the fancyDatabaseName database on each machine using the
mysqldbcompare
tool (part of themysql-utilities
package):/usr/local/bin/mysqldbcompare --server1=root@127.0.0.1:3308 --server2=root@127.0.0.1:3307 fancyDatabaseName
Explanation of flags to ‘ssh‘:
-L [bind_address:]port:host:hostport
Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side. This works by allocating a socket to listen to port on the local side, optionally bound to the specified bind_address. Whenever a connection is made to this port, the connection is forwarded over the secure channel, and a connection is made to host port hostport from the remote machine. Port forwardings can also be specified in the configuration file. IPv6 addresses can be specified with an alternative syntax:
[bind_address/]port/host/hostport or by enclosing the address in square brackets. Only the superuser can forward privileged ports. By default, the local port is bound in accordance with the GatewayPorts setting. However, an explicit bind_address may be used to bind the connection to a specific address. The bind_address of ”localhost” indicates that the listening port be bound for local use only, while an empty address or ‘*’ indicates that the port should be available from all interfaces.-N will disable the ability to execute a remote command.
-n will prevent reading from stdin.
-T will disable the pseudo-terminal allocation.
-
Writing reliable Windows Batch files
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.
-
Chrome still opens last session instead of home page
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”
-
How to remove or uninstall software on Windows 10
1. Tap/click Start > Settings (gear icon) > Apps
2. Locate the app to uninstall and tap/click it.
3. Tap/click UninstallNote: 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.
-
Can’t type into Spotlight? On 10.12?
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.
Questions?