Getting zsh to work in ubuntu is weird, since sh does not understand the source command. So, you do this to install zsh
wget https://github.com/robbyrussell/oh-my-zsh/raw/master/tools/install.sh -O - | zsh
and then you change your shell to zsh
chsh -s `which zsh`
and then restart
| var express = require('express'); | |
| var sys = require('sys'); | |
| var oauth = require('oauth'); | |
| var app = express.createServer(); | |
| var _twitterConsumerKey = "YOURTWITTERCONSUMERKEY"; | |
| var _twitterConsumerSecret = "YOURTWITTERCONSUMERSECRET"; | |
| function consumer() { |
| #!/bin/sh | |
| # build_fat.sh | |
| # | |
| # Created by Robert Carlsen on 15.07.2009. Updated 24.9.2010 | |
| # build an arm / i386 lib of standard linux project | |
| # | |
| # initially configured for tesseract-ocr v2.0.4 | |
| # updated for tesseract prerelease v3 | |
| outdir=outdir |
| //This sample is how to use websocket of Tomcat. | |
| package wsapp; | |
| import java.io.IOException; | |
| import java.nio.ByteBuffer; | |
| import java.nio.CharBuffer; | |
| import java.util.ArrayList; | |
| import org.apache.catalina.websocket.MessageInbound; | |
| import org.apache.catalina.websocket.StreamInbound; | |
| import org.apache.catalina.websocket.WebSocketServlet; |
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
| #import <Foundation/Foundation.h> | |
| @interface DataModel : NSObject | |
| @property (nonatomic, copy) NSString *email; | |
| @property (nonatomic, copy) NSString *password; | |
| @property (nonatomic, copy) NSString *sessionId; | |
| @property (nonatomic, copy) NSString *deviceId; | |
| @property (nonatomic, copy) NSString *encryptionKey; | |
| @end |
| // | |
| // KSDIdlingWindow.h | |
| // | |
| // Created by Brian King on 4/13/10. | |
| // Copyright 2010 King Software Designs. All rights reserved. | |
| // | |
| // Based off: | |
| // http://stackoverflow.com/questions/273450/iphone-detecting-user-inactivity-idle-time-since-last-screen-touch | |
| // |
Post Upgrade to El Capitan, with Homebrew & Ruby
... and Xcode and Java, etc.
If you don't already have homebrew installed, do that first, so you don't have to deal with SIP issues. Install all Software Updates available in the Apple Menu, up to and including El Capitan.
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
This is where any fun you might have been having ends. Now it’s time to get serious and talk about rules.
Writing CSS is hard. Even if you know all the intricacies of position and float and overflow and z-index, it’s easy to end up with spaghetti code where you need inline styles, !important rules, unused cruft, and general confusion. This guide provides some architecture for writing CSS so it stays clean and ma