Following Broadcom’s buyout of VMWare, many home users of virtualization software such as VMWare’s ESXi were disappointed that the free personal use was discontinued.
News today however is more promising: from today you can download Fusion Pro for MacOS and Workstation Pro for Windows free for personal use. You need to sign up for an account at support.broadcom.com and then search for either product to download. More details here.
Sometimes muscle memory is hard to unlearn. I can’t get used to the Home and End keys on a Mac jumping to the top and end of a file instead of start and end of a line. Yes, I know Cmd-left and Cmd-right do the same thing on a Mac, but pressing Home and having it jump to the top of a file is too much for me to handle when in the middle of editing something in an IDE like Eclipse.
To remap the Home and End keys to behave the same as on Windows, make a dir here:
mkdir ~/Library/KeyBindings
and create a file called DefaultKeyBinding.dict (NOTE: this file must be named exactly as shown to work) containing this content:
Logoff and log back on again, and the Home and End keys should now work the same as on Windows. (source here)
If this still doesn’t work in Eclipse, it maybe because Line Start and Line End and explicitly mapped to Cmd-left and Cmd-right – these can be changed in Preferences under Keys:
Delete the existing mappings for Home and End and change to the Home and End keys:
I posted a while back about running mysql in a Docker container on an Apple Silicon MacBook. It’s been a while since I’ve run mysql locally, and it seems the mysqlsh client is now preferred over the previous mysql client.
With mysqlsh, after connecting, to issue a ‘use’ command to select a db, use ‘\use dbname’
Once a db is selected, to issue other mysql commands enter the sql mode with ‘\sql’ command.
I’ve seen this error before with MacOS’s zsh and I can never remember what the issue is:
> curl https://localhost:8080/example?email=test
zsh: no matches found: https://localhost:8080/example?email=test
You can get this error with multiple different commands for the same reason. The ‘?’ in the param to curl is interpreted as a substitution wildcard character. To avoid the issue, either escape the ? as \? or just wrap the whole url in double quotes.