I hereby claim:
- I am clarkema on github.
- I am clarkema (https://keybase.io/clarkema) on keybase.
- I have a public key whose fingerprint is B670 7070 A3AE 4165 6469 E397 8793 28D4 9C4E 924B
To claim this, I am signing this object:
| black = '#282828'; | |
| red = '#CC241D'; // red | |
| green = '#98971A'; // green | |
| yellow = '#D78821'; // yellow | |
| blue = '#458588'; // blue | |
| magenta = '#B16286'; // pink | |
| cyan = '#689D6A'; // cyan | |
| white = '#A89984'; // light gray | |
| lightBlack = '#928374'; // medium gray | |
| lightRed = '#FB4934'; // red |
| ### Keybase proof | |
| I hereby claim: | |
| * I am clarkema on github. | |
| * I am clarkema (https://keybase.io/clarkema) on keybase. | |
| * I have a public key ASBKRUkmlXxzB5FWOR4qRIFPOO3tz6DmsRp-p355s54uMAo | |
| To claim this, I am signing this object: |
| ;; Lisp | |
| (defun counter () | |
| (let ((i 0)) | |
| (lambda () (incf i)))) | |
| (setf indexer (counter)) | |
| (funcall indexer) => 1 | |
| (funcall indexer) => 2 |
| # resolve_path from here https://github.com/keen99/shell-functions/tree/master/resolve_path | |
| resolve_path() { | |
| #I'm bash only, please! | |
| # usage: resolve_path <a file or directory> | |
| # follows symlinks and relative paths, returns a full real path | |
| # | |
| local owd="$PWD" | |
| #echo "$FUNCNAME for $1" >&2 | |
| local opath="$1" | |
| local npath="" |
I hereby claim:
To claim this, I am signing this object:
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = [email protected]:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
| ; | |
| ; An example of prefix-based dispatch for Weblocks. | |
| ; | |
| ; This code allows you to have URLs like http://foo/details/callsign and | |
| ; http://foo/limited/callsign, and dispatch to different widgets based on | |
| ; pattern matching. In this case we dispatch to one widget for /details | |
| ; and another for /limited, in both cases passing callsign to the | |
| ; target widget. | |
| ; | |
| ; Error handling is left as an exercise for the reader ;) |