| <!doctype html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title>HTML5 Template</title> | |
| <link rel="stylesheet" href="style.css"> | |
| </head> | |
| <body> | |
| </body> |
| #!/usr/bin/env sh | |
| ## | |
| # This is script with usefull tips taken from: | |
| # https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
| # | |
| # install it: | |
| # curl -sL https://raw.github.com/gist/2108403/hack.sh | sh | |
| # |
| function doStuff(){ | |
| landscape = window.orientation? window.orientation=='landscape' : true; | |
| if(landscape && window.innerWidth<1900 && window.innerWidth > 768){ | |
| //code here | |
| } | |
| } | |
| window.onload=window.onresize=doStuff; | |
| if(window.onorientationchange){ | |
| window.onorientationchange=doStuff; |
| $ git checkout -b <new-branch> | |
| This will leave your current branch as is, create and checkout a new branch and keep all your changes. You can then make a commit with: | |
| $ git add <files> | |
| and commit to your new branch with: | |
| $ git commit | |
| The changes in the working directory and changes staged in index do not belong to any branch yet. This changes where those changes would end in. |
| gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/screen -dNOPAUSE -dQUIET -dBATCH -sOutputFile=output.pdf input.pdf | |
| #Leave out the '-dPDFSETTINGS=/screen' setting for better quality, but slightly larger pdfs. |
| //trim string | |
| function trim(str){ | |
| return String.prototype.trim ? str.trim() : String(str).replace(/^([\s]*)|([\s]*)$/g, ''); | |
| } |
| var parser = document.createElement('a'); | |
| parser.href = "http://example.com:3000/pathname/?search=test#hash"; | |
| parser.protocol; // => "http:" | |
| parser.hostname; // => "example.com" | |
| parser.port; // => "3000" | |
| parser.pathname; // => "/pathname/" | |
| parser.search; // => "?search=test" | |
| parser.hash; // => "#hash" | |
| parser.host; // => "example.com:3000" |
Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discussions around concrete examples, not handy-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| String: foobaz | |
| Regex: (?=.*foo)(?=.*baz) |