start new:
tmux
start new with session name:
tmux new -s myname
on alfred_script(q) | |
tell application "iTerm" | |
activate | |
try | |
set _term to last terminal | |
on error | |
set _term to (make new terminal) | |
end try | |
#!/usr/bin/python2 | |
# Copyright (C) 2016 Sixten Bergman | |
# License WTFPL | |
# | |
# 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 |
library(Rmpi) | |
## load the packages we'll need | |
RLIBS="~/R/x86_64-redhat-linux-gnu-library/2.13" | |
.libPaths(c(RLIBS, .libPaths())) | |
### Direct RMPI way: | |
mpi.spawn.Rslaves(nslaves=15) | |
slavefn <- function() { print(paste("Hello from", foldNumber)) } | |
mpi.bcast.cmd(foldNumber <- mpi.comm.rank()) |
################################################################################ | |
# Copyright 2011 | |
# Andrew Redd | |
# 11/23/2011 | |
# | |
# Description of File: | |
# Makefile for knitr compiling | |
# | |
################################################################################ | |
all:pdf # default rule DO NOT EDIT |
from celery import chain | |
from django.core.management.base import BaseCommand | |
from . import tasks | |
class Command(BaseCommand): | |
def handle(self, *args, **kwargs): |
#!/bin/sh | |
# usage: mkramdisk 1024 ~/scratch | |
function mkramdisk() { | |
ramfs_size_mb=$1 | |
mount_point=$2 | |
ramfs_size_sectors=$((${ramfs_size_mb}*1024*1024/512)) | |
ramdisk_dev=`hdid -nomount ram://${ramfs_size_sectors}` | |
newfs_hfs -v 'ram disk' ${ramdisk_dev} |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j