Loads of solutions exist, but for changing the system default, alias is not the way to go.
$ update-alternatives --list python update-alternatives: error: no alternatives for python
| void LCD_write(uint8_t d) { | |
| // ILI9341 reads data pins when WR rises from LOW to HIGH (A1 pin on arduino) | |
| PORTC = PORTC & B11111101; // WR 0 | |
| // data pins of ILI9341 connected to two arduino ports | |
| PORTD = (PORTD & B00000011) | ((d) & B11111100); | |
| PORTB = (PORTB & B11111100) | ((d) & B00000011); | |
| PORTC = PORTC | B00000010; // WR 1 | |
| } |
| # npm using https for git | |
| git config --global url."https://github.com/".insteadOf [email protected]: | |
| git config --global url."https://".insteadOf git:// | |
| # npm using git for https | |
| git config --global url."[email protected]:".insteadOf https://github.com/ | |
| git config --global url."git://".insteadOf https:// |
If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.
Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.
The simplest way to add an alias for a specific git command is to use a standard bash alias.
# .bashrc| /** | |
| * Title: gpio.c | |
| * | |
| * Author: Andrew Montag | |
| * ajmontag@gmail.com | |
| * sites.google.com/site/andrewmontag | |
| * | |
| * Licence: Boost Software Licence - Verison 1.0 | |
| * http://www.boost.org/users/license.html | |
| * |