As configured in my dotfiles.
start new:
tmux
start new with session name:
| #!/usr/bin/env python3 | |
| # -*- mode: python -*- | |
| # This program is free software. It comes without any warranty, to the extent | |
| # permitted by applicable law. You can redistribute it and/or modify it under | |
| # the terms of the Do What The Fuck You Want To Public License, Version 2, as | |
| # published by Sam Hocevar. See http://sam.zoy.org/wtfpl/COPYING for more | |
| # details. | |
| # Some useful resources: |
| #!/usr/bin/env python | |
| # -*- coding: utf-8 -*- | |
| import sys | |
| import math | |
| from PyQt4 import QtGui, QtCore | |
| def binomial(i, n): |
As configured in my dotfiles.
start new:
tmux
start new with session name:
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
This means, on your local machine, you haven't made any SSH keys. Not to worry. Here's how to fix:
*nix based command prompt (but not the default Windows Command Prompt!)cd ~/.ssh. This will take you to the root directory for Git (Likely C:\Users\[YOUR-USER-NAME]\.ssh\ on Windows).ssh folder, there should be these two files: id_rsa and id_rsa.pub. These are the files that tell your computer how to communicate with GitHub, BitBucket, or any other Git based service. Type ls to see a directory listing. If those two files don't show up, proceed to the next step. NOTE: Your SSH keys must be named id_rsa and id_rsa.pub in order for Git, GitHub, and BitBucket to recognize them by default.ssh-keygen -t rsa -C "your_email@example.com". ThPre-requisite: go to http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html download http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe and http://the.earth.li/~sgtatham/putty/latest/x86/puttygen.exe
Saved from Archive.org, Date: May 14, 2010 Author: Jesse Webb
Our development machines here at Point2 are not standardized; we have a mixture of Windows XP, 7, and Mac OSX/Unix computers. I find myself constantly switching back and forth between command prompt interfaces when pair programming. As a result, I catch myself using “ls” to list a directories contents regardless of what system I am on. I am currently using a Windows XP machine for my developer box and I wanted to setup an alias to the “ls” command to actually perform a “dir”. Here is how I accomplished it…
There is a command available in a Window’s shell that let’s you “alias” command to whatever you please: DOSKey. It allows you to create “macros” to execute one or more other commands with a custom nam
| Do | |
| Msgbox "This is a simple infinite loop" | |
| Loop |
| # Execute select in pgAdmin | |
| # write result to file | |
| """ | |
| select encode(my_bin_field,'base64') | |
| from my_schema.my_table | |
| where id=123; | |
| """ | |
| # Remove column name from generated file | |
| import base64 |