Prereq:
apt-get install zsh
apt-get install git-coreGetting 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
| #!/bin/bash | |
| set -o errexit | |
| # Author: David Underhill | |
| # Script to permanently delete files/folders from your git repository. To use | |
| # it, cd to your repository's root and then run the script with a list of paths | |
| # you want to delete, e.g., git-delete-history path1 path2 | |
| if [ $# -eq 0 ]; then | |
| exit 0 |
git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
As configured in my dotfiles.
start new:
tmux
start new with session name:
As of version 3.3, python includes the very promising concurrent.futures module, with elegant context managers for running tasks concurrently. Thanks to the simple and consistent interface you can use both threads and processes with minimal effort.
For most CPU bound tasks - anything that is heavy number crunching - you want your program to use all the CPUs in your PC. The simplest way to get a CPU bound task to run in parallel is to use the ProcessPoolExecutor, which will create enough sub-processes to keep all your CPUs busy.
We use the context manager thusly:
with concurrent.futures.ProcessPoolExecutor() as executor:
This is a guide to implementing Getting Things Done (GTD) using [Simpletask][] by [Mark Janssen][].
Simpletask uses the [todo.txt][] syntax, but has sufficient differences and quirks of its own to be worth describing in detail---at least, that's the story I'm going with. I actually began this guide as an exploration of my own trusted system. Personal workflows are by definition eccentric; I have included only what seems to me to be broadly useful.
This implementation of GTD covers the "standard" classifications: next actions by context, projects, somedays, agendas by person and meeting, etc. In a departure from strict GTD, each entry in these lists is also tagged with an area of focus, interest or responsibility. I find that the ability to slice the system by this extra dimension is worth the additional complexity at the processing and organizing stages. Limitations, issues and workarounds are discussed at the end.
Before we begin, some words of wisdom
| # Latex Makefile using latexmk | |
| # Modified by Dogukan Cagatay <[email protected]> | |
| # Originally from : http://tex.stackexchange.com/a/40759 | |
| # | |
| # Change only the variable below to the name of the main tex file. | |
| PROJNAME=main | |
| # You want latexmk to *always* run, because make does not have all the info. | |
| # Also, include non-file targets in .PHONY so they are run regardless of any | |
| # file of the given name existing. |
| # Generate PDFs from the Markdown source files | |
| # | |
| # In order to use this makefile, you need some tools: | |
| # - GNU make | |
| # - Pandoc | |
| # - LuaLaTeX | |
| # - DejaVu Sans fonts | |
| # Directory containing source (Markdown) files | |
| source := src |
| """ | |
| A deep neural network with or w/o dropout in one file. | |
| License: Do What The Fuck You Want to Public License http://www.wtfpl.net/ | |
| """ | |
| import numpy, theano, sys, math | |
| from theano import tensor as T | |
| from theano import shared | |
| from theano.tensor.shared_randomstreams import RandomStreams |
