To run this, you can try:
curl -ksO https://gist.githubusercontent.com/nicerobot/2697848/raw/uninstall-node.sh
chmod +x ./uninstall-node.sh
./uninstall-node.sh
rm uninstall-node.sh
To run this, you can try:
curl -ksO https://gist.githubusercontent.com/nicerobot/2697848/raw/uninstall-node.sh
chmod +x ./uninstall-node.sh
./uninstall-node.sh
rm uninstall-node.sh
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| <?php | |
| function the_date_range($args) { | |
| global $post; | |
| $default = array( | |
| 'start_field' => 'start_date', | |
| 'end_field' => null, | |
| 'base_format' => 'Ymd', | |
| 'post_id' => $post->ID, | |
| 'separator' => '<span class="date-separator">–</span>', | |
| 'month_format' => 'F', |
| /** | |
| * Retrieves all the rows in the active spreadsheet that contain data and logs the | |
| * values for each row. | |
| * For more information on using the Spreadsheet API, see | |
| * https://developers.google.com/apps-script/service_spreadsheet | |
| */ | |
| function readRows() { | |
| var sheet = SpreadsheetApp.getActiveSheet(); | |
| var rows = sheet.getDataRange(); | |
| var numRows = rows.getNumRows(); |
| <?php | |
| // Based on https://mixpanel.com/docs/api-documentation/exporting-raw-data-you-inserted-into-mixpanel | |
| class MixpanelExport { | |
| private $api_url = 'https://data.mixpanel.com/api/2.0/export'; | |
| private $api_key; | |
| private $api_secret; | |
| public $debug; |
| #!/bin/bash | |
| f=$(pwd) | |
| sips --resampleWidth 1024 "${f}/${1}" --out "${f}/iTunesArtwork@2x.png" | |
| sips --resampleWidth 57 "${f}/${1}" --out "${f}/app-icon.png" | |
| sips --resampleWidth 114 "${f}/${1}" --out "${f}/app-icon@2x.png" | |
| sips --resampleWidth 29 "${f}/${1}" --out "${f}/app-icon-29.png" | |
| sips --resampleWidth 58 "${f}/${1}" --out "${f}/app-icon-29@2x.png" |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParentAs a freelancer, I build a lot of web sites. That's a lot of code changes to track. Thankfully, a Git-enabled workflow with proper branching makes short work of project tracking. I can easily see development features in branches as well as a snapshot of the sites' production code. A nice addition to that workflow is that ability to use Git to push updates to any of the various sites I work on while committing changes.
| Brewed Bash Ver: | |
| #!/usr/local/bin/bash | |
| source ~/.bash_profile | |
| /usr/local/bin/python2.7 ~/Apps/SickRage/SickBeard.py -d & | |
| Normal Mac Users: | |
| #!/bin/bash | |
| source ~/.bash_profile |
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
| Commit type | Emoji |
|---|---|
| Initial commit | 🎉 :tada: |
| Version tag | 🔖 :bookmark: |
| New feature | ✨ :sparkles: |
| Bugfix | 🐛 :bug: |