- Connect an iOS defice with a cable
- In QuickTime Player: Option-Cmd-N (New Movie Recording) -> Select your device from the recording menu:
$white: #ffffff; | |
$black: #000000; | |
$red50: #ffebee; | |
$red100: #ffcdd2; | |
$red200: #ef9a9a; | |
$red300: #e57373; | |
$red400: #ef5350; | |
$red500: #f44336; | |
$red600: #e53935; | |
$red700: #d32f2f; |
# wp-cli | |
complete -c wp -l cache --description 'Manage the object cache.' | |
complete -c wp -l cap --description 'Manage user capabilities.' | |
complete -c wp -l cli --description 'Get information about WP-CLI itself.' | |
complete -c wp -l comment --description 'Manage comments.' | |
complete -c wp -l core --description 'Download, install, update and otherwise manage WordPress proper.' | |
complete -c wp -l cron --description 'Manage WP-Cron events and schedules.' | |
complete -c wp -l db --description 'Perform basic database operations.' | |
complete -c wp -l eval --description 'Execute arbitrary PHP code.' | |
complete -c wp -l eval-file --description 'Load and execute a PHP file.' |
<?php | |
// Please see https://github.com/Lewiscowles1986/WordPressSVGPlugin from now on |
// Reference: http://www.blackdogfoundry.com/blog/moving-repository-from-bitbucket-to-github/ | |
// See also: http://www.paulund.co.uk/change-url-of-git-repository | |
$ cd $HOME/Code/repo-directory | |
$ git remote rename origin bitbucket | |
$ git remote add origin https://github.com/mandiwise/awesome-new-repo.git | |
$ git push origin master | |
$ git remote rm bitbucket |
# The blog post that started it all: https://neocities.org/blog/the-fcc-is-now-rate-limited | |
# | |
# Current known FCC address ranges: | |
# https://news.ycombinator.com/item?id=7716915 | |
# | |
# Confirm/locate FCC IP ranges with this: http://whois.arin.net/rest/net/NET-165-135-0-0-1/pft | |
# | |
# In your nginx.conf: | |
location / { |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
$(document).ready(function() { | |
$("#pics iframe").each(function(index) { | |
var ratio = $(this).height() / $(this).width(); | |
var origHeight = $(this).height(); | |
var origWidth = $(this).width(); | |
var self = this; | |
// bind to window with closure that references the | |
// iframe since the iframe doesn't get resize events | |
// until (you know) we resize it. | |
$(window).resize(function() { |
- Install Package Control. For SublimeText 2, paste the following in Terminal:
import urllib2,os; pf='Package Control.sublime-package'; ipp = sublime.installed_packages_path(); os.makedirs( ipp ) if not os.path.exists(ipp) else None; urllib2.install_opener( urllib2.build_opener( urllib2.ProxyHandler( ))); open( os.path.join( ipp, pf), 'wb' ).write( urllib2.urlopen( 'http://sublime.wbond.net/' +pf.replace( ' ','%20' )).read()); print( 'Please restart Sublime Text to finish installation')
From here on out, use Package Control to install everything. ⌘
+Shift
+P
, then type Install
to get a list of installable packages you can 'livesearch through. After installing plugins, they should be running.