start new:
tmux
start new with session name:
tmux new -s myname
/* | |
http://stackoverflow.com/questions/1371460/state-machines-tutorials/1371654#1371654 | |
State machines are very simple in C if you use function pointers. | |
Basically you need 2 arrays - one for state function pointers and one for state | |
transition rules. Every state function returns the code, you lookup state | |
transition table by state and return code to find the next state and then | |
just execute it. | |
*/ |
First, you have to enable profiling
> db.setProfilingLevel(1)
Now let it run for a while. It collects the slow queries ( > 100ms) into a capped collections, so queries go in and if it's full, old queries go out, so don't be surprised that it's a moving target...
/** | |
* More info? | |
* [email protected] | |
* http://aspyct.org | |
* | |
* Hope it helps :) | |
*/ | |
#include <stdio.h> | |
#include <stdlib.h> |
o.......Open files, directories and bookmarks....................|NERDTree-o|
go......Open selected file, but leave cursor in the NERDTree.....|NERDTree-go|
t.......Open selected node/bookmark in a new tab.................|NERDTree-t|
T.......Same as 't' but keep the focus on the current tab........|NERDTree-T|
i.......Open selected file in a split window.....................|NERDTree-i|
gi......Same as i, but leave the cursor on the NERDTree..........|NERDTree-gi|
s.......Open selected file in a new vsplit.......................|NERDTree-s|
gs......Same as s, but leave the cursor on the NERDTree..........|NERDTree-gs|
O.......Recursively open the selected directory..................|NERDTree-O|
expr -- (void)printf("[%s, %s]\n",(char *) object_getClassName(*(long*)($esp+4)), (char *) *(long *)($esp+8) ) |
// Just before switching jobs: | |
// Add one of these. | |
// Preferably into the same commit where you do a large merge. | |
// | |
// This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
// and then it quickly escalated into more and more evil suggestions. | |
// I've tried to capture interesting suggestions here. | |
// | |
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
#!/usr/bin/env bash | |
if [ -z "$1" ]; then | |
echo "usage: $(basename $0) <process>" | |
exit 1 | |
fi | |
IP=$(adb shell netcfg | grep wlan0 | awk '{print $3}' | cut -d '/' -f1) | |
if [ $? -ne 0 ]; then | |
echo "device plugged in?" | |
exit 1 |
Here I'm trying to understand what happens when I run
./hello
#include
Software that provides a programmer friendly interface between application programs and the hardware by providing a virtual environment to applications.
Software that handles resource requests from application programs and prevents applications from trampling each other.