- Download the perforce visual tool suite from here: http://www.perforce.com/perforce/downloads/index.html
- Copy only the p4merge.app file into your /Applications/ directory
Most configuration really isn't about the app -- it's about where the app runs, what keys it needs to communicate with third party API's, the db password and username, etc... They're just deployment details -- and there are lots of tools to help manage environment variables -- not the least handy being a simple .env file with all your settings. Simply source the appropriate env before you launch the app in the given env (you could make it part of a launch script, for instance).
env files look like this:
SOMEVAR="somevalue"
ANOTHERVAR="anothervalue"
To source it:
$ source dev.env # or staging.env, or production.env, depending on where you're deploying to
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
- By Edmond Lau
- Highly Recommended 👍
- http://www.theeffectiveengineer.com/
| #!/bin/bash | |
| # this forces Arena into full screen mode on startup, set back to 3 to reset | |
| # note that if you go into the Arena "Graphics" preference panel, it will reset all of these | |
| # and you will need to run these commands again | |
| defaults write com.wizards.mtga "Screenmanager Fullscreen mode" -integer 0 | |
| defaults write com.wizards.mtga "Screenmanager Resolution Use Native" -integer 0 | |
| # you can also replace the long complicated integer bit with any other scaled 16:9 | |
| # resolution your system supports. |
| # SOURCES | |
| # https://starship.rs/config | |
| # https://starship.rs/presets/nerd-font.html#configuration | |
| # DEBUG via: | |
| # starship explain | |
| # STARSHIP_LOG=trace | |
| "$schema" = 'https://starship.rs/config-schema.json' |
For some reason, it is surprisingly hard to create a bootable Windows USB using macOS. These are my steps for doing so, which have worked for me in macOS Monterey (12.6.1) for Windows 10 and 11. After following these steps, you should have a bootable Windows USB drive.
You can download Windows 10 or Windows 11 directly from Microsoft.
After plugging the drive to your machine, identify the name of the USB device using diskutil list, which should return an output like the one below. In my case, the correct disk name is disk2.