Using Python's built-in defaultdict we can easily define a tree data structure:
def tree(): return defaultdict(tree)
That's it!
%!TEX TS-program = xelatex | |
\documentclass[12pt]{scrartcl} | |
% The declaration of the document class: | |
% The second line here, i.e. | |
% \documentclass[12pt]{scrartcl} | |
% is a standard LaTeX document class declaration: | |
% we say what kind of document we are making in curly brackets, | |
% and specify any options in square brackets. |
<!-- | |
Copyright (c) 2012 Terrence Ryan | |
Permission is hereby granted, free of charge, to any person obtaining a copy of this | |
software and associated documentation files (the "Software"), to deal in the Software | |
without restriction, including without limitation the rights to use, copy, modify, | |
merge, publish, distribute, sublicense, and/or sell copies of the Software, and to | |
permit persons to whom the Software is furnished to do so, subject to the following | |
conditions: |
Using Python's built-in defaultdict we can easily define a tree data structure:
def tree(): return defaultdict(tree)
That's it!
Oops. They did it again.
It hit the market during the last few weeks. Last generation of Intel Atoms: CedarView (D2300, D2500, D2550, D2600, D2700) and Cedar Trail (N2600, N2700, N2800) SoCs integrate a PowerVR GPU from Imagination instead of the usual Intel GPU. If you remember the Poulsbo fiasco, it's the same. More or less.
An unsupported graphic card on Linux distributions, and which can't properly support a basic desktop environnment like Unity or Gnome 3.
To prevent this issue, Intel woke up MeeGo from the dead in last february [to add support for CedarView]
TodoMVC.module 'TodoApp', (App, TodoMVC, Backbone, Marionette, $, _) -> | |
log arguments | |
class App.TodoForm extends Marionette.ItemView | |
events: | |
'keypress #new-todo' : 'createOnEnter' | |
'click .mark-all-done' : 'toggleAllClicked' | |
triggers: | |
'click .todo-clear a' : 'clear:completed' |
#!/bin/bash | |
# Reverts HEAD back to ORIG_HEAD, for example after a 'git pull' accidentally | |
# creates a merge. This is identical to running 'git reset --hard ORIG_HEAD', | |
# except that unpull prints some helpful information along the way. | |
# Useage: | |
# $ git unpull | |
# HEAD: a0ac0fd Merge branch 'master' of /tmp/foo | |
# 2284c9d some remote commit | |
# ORIG_HEAD: 35431fd my local commit | |
# Really reset HEAD to ORIG_HEAD? (y/n) y |
#!/usr/bin/env python | |
""" pybcompgen | |
Pybcompgen calculates context sensitive tab-completion data which is | |
derived from environment bash system settings. It doesn't need to know | |
anything about whether you use /etc/completion or /etc/bash_completion.d, | |
all that matters is whether *bash* knows about the completion. The benefit | |
of doing this are obvious: you get access to all the completion features | |
that the system has installed without caring how the completion features | |
work. Note that this approach doesn't just work for things in the users |
" I don't remember exactly how to make it not spit out the actual command you are running. Meh. | |
nnoremap u :call system("say -v whisper 'balls'")<CR> |