start new:
tmux
start new with session name:
tmux new -s myname
#!/bin/sh | |
colors=($(xrdb -query | sed -n 's/.*color\([0-9]\)/\1/p' | sort -nu | cut -f2)) | |
echo -e "\e[1;37m | |
Black Red Green Yellow Blue Magenta Cyan White | |
───────────────────────────────────────────────────────────────────────────────────────\e[0m" | |
for i in {0..7}; do echo -en "\e[$((30+$i))m █ ${colors[i]} \e[0m"; done | |
echo | |
for i in {8..15}; do echo -en "\e[1;$((22+$i))m █ ${colors[i]} \e[0m"; done |
OS=`echo \`uname\` | tr '[:upper:]' '[:lower:]'` | |
AURL="https://gist.githubusercontent.com/hightemp/5071909/raw/" | |
ANAME=".bash_aliases" | |
TMPAPATH="/tmp/$ANAME" | |
HOMEAPATH="~/$ANAME" | |
[ "$OS" = "windowsnt" ] && OS_WIN="yes" | |
[ "$OS" = "darwin" ] && OS_MAC="yes" | |
[ "$OS" = "linux" ] && OS_LIN="yes" |
#!flask/bin/python | |
from flask import Flask, jsonify, abort, request, make_response, url_for | |
from flask_httpauth import HTTPBasicAuth | |
app = Flask(__name__, static_url_path = "") | |
auth = HTTPBasicAuth() | |
@auth.get_password | |
def get_password(username): | |
if username == 'miguel': |
My typical setup for a development box in VirtualBox uses two NICs. The first uses NAT to allow the box to communicate with the outside world through my host computer’s network connection. (NAT is the default, so shouldn't require any setup.) The second is a "host-only" connection that allows my host and guest to interact.
To create a host-only connection in VirtualBox, start by opening the preferences in VirtualBox. Go to the "Network" tab, and addd a Host-only Network. Modify the host-only network, and disable DHCP. Make a note of the IP address. (Feel free to set the IP address as well, if you like.)
Next, assign this host-only adapter to the virtual machine. Select the VM and press "Settings". Go to the "Network" tab, and select "Adpater 2". Enable the adapter, set it to a "Host-only Adapter", and select the adpater you created above.
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
Install Package Control for easy package management.
Ctrl+`
/* http://l3net.wordpress.com/2012/12/09/a-simple-telnet-client/ */ | |
#include <stdio.h> | |
#include <stdlib.h> | |
#include <unistd.h> | |
#include <string.h> | |
#include <arpa/inet.h> | |
#include <termios.h> | |
#include <fcntl.h> | |