|## This is where you want the entire toolchain to live|
|## You should run this script from within the destination directory, or|
|## redefine the BASE variable to fit your lifestyle.|
|echo [getESP32.sh]: Checking for system prerequisites|
|[[ $(which pacman) ]] && sudo pacman -S --needed gcc git make ncurses flex bison gperf python2-pyserial wget 2>/dev/null|
|[[ $(which apt-get) ]] && sudo apt-get install git make libncurses-dev flex bison gperf python python-serial wget 2>/dev/null|
Nuclear Power is a major new feature introduced to Factorio in version 0.15. It requires higher level technology compared to either Solar Power or Steam Boiler Power, but it offers very high power output in exchange. It's a great solution for middle- to end-game power generation and it works well in combination with other power generation techniques.
This guide is written for people who want to know exactly how nuclear power works, but don't necessarily want all the solutions. It focuses on what you should do and what you should know to get Nuclear up and running, but doesn't tell you what to do or exactly how to solve the problems.
Technology Required: Nuclear Power You can mine uranium ore sooner, but you'll need the Nuclear Power technology to do anything useful with it.
Switch To Vim For Good
NOTE: This guide has moved to https://github.com/bpierre/switch-to-vim-for-good
This guide is coming from an email I used to send to newcomers to Vim. It is not intended to be a complete guide, it is about how I switched myself.
My decision to switch to Vim has been made a long time ago. Coming from TextMate 1, I wanted to learn an editor that is Open Source (so I don’t lose my time learning a tool that can be killed), cross platform (so I can use it everywhere), and powerful enough (so I won’t regret TextMate). For these reasons, Vim has always been the editor I wanted to learn, but it took me several years before I did it in a way that works for me. I tried to switch progressively, using the Janus Vim distribution for a few months, then got back to using TextMate 2 for a time, waiting for the next attempt… here is what finally worked for me.
Original gist with comments: https://gist.github.com/bpierre/0a0025d348b6001394e0
- http://stackoverflow.com/questions/804115 (
- https://www.atlassian.com/git/tutorials/merging-vs-rebasing (
- https://www.atlassian.com/git/tutorials/undoing-changes/ (
- http://stackoverflow.com/questions/2221658 (HEAD^ vs HEAD~) (See
- http://stackoverflow.com/questions/292357 (
- http://stackoverflow.com/questions/39651 (
- http://stackoverflow.com/questions/8358035 (
A good commit message looks like this:
Header line: explaining the commit in one line Body of commit message is a few lines of text, explaining things in more detail, possibly giving some background about the issue being fixed, etc etc. The body of the commit message can be several paragraphs, and please do proper word-wrap and keep columns shorter than about
|Windows Registry Editor Version 5.00|
Via brew or other method
Set up DNS resolver order
In order to work on every connection and on any TLD,
dnsmasq needs to be the first DNS resolver receving the query.
dnsmasq is a local process, all DNS queries need to go to
/etc/resolv.conf is automaticaly created, depending on a variety of things (network settings, etc), so it cannot be edited.