Explore >> Select a destination
|
You are here 
|
techtldr.com | ||
| | | | |
gc-taylor.com
|
|
| | | | | [AI summary] A blog post detailing steps to build FoundationDB on macOS without the official Docker container, including dependency installation and build commands. | |
| | | | |
www.stevestreeting.com
|
|
| | | | | ||
| | | | |
emmanuelbernard.com
|
|
| | | | | tl;dr; using powerline and having it fail after a homebrew update? Read on. If you have tuned a bit your terminal in macOS, you might be using Powerline. It prettities your command line enough to warrant some trouble installing it. And it does it to vim status lines too. Now if you also use homebrew, every so often you see something like this when starting a new terminal window -bash: /usr/local/bin/powerline-daemon: /usr/local/opt/python/bin/python3.6: bad interpreter: No such file or directory I always fiddle with things until I get it fixed again. So here it is reported for posterity. The Python interpreter has been updated behind your back and the installed modules end up referencing the old interpreter. For powerline, here are the steps pip uninstall -y... | |
| | | | |
www.integralist.co.uk
|
|
| | | Introduction I'm an engineer with a new laptop, which requires setting up with various development tools and configuration. This post is my attempt to capture and document my process for getting a new dev environment set-up. I used to try and automate a lot of this with bash scripts, but realised over time that things go out of date quite quickly (e.g. OS configurations can change substantially, as well as my preferred ways of working). | ||
