start new:
tmux
start new with session name:
tmux new -s myname
# Credit http://stackoverflow.com/a/2514279 | |
for branch in `git branch -r | grep -v HEAD`;do echo -e `git show --format="%ci %cr" $branch | head -n 1` \\t$branch; done | sort -r |
# README: | |
# Copy this file to /usr/lib/systemd/system/ | |
# sudo systemctl daemon-reload | |
# systemctl enable ipython-notebook | |
# systemctl start ipython-notebook | |
# The WorkingDirectory and ipython-dir must exist | |
# If you don't want anything fancy, go to http://127.0.0.1:8888 to see your notebook | |
# wheneber you want it | |
[Unit] |
git archive --format=tar --prefix=git-1.4.0/ v1.4.0 | gzip >git-1.4.0.tar.gz # Create a compressed tarball for v1.4.0 release. | |
git archive --format=zip --prefix=git-1.4.0/ v1.4.0 > git-1.4.0-docs.zip # Create a compressed zipball for v1.4.0 release. |
package main | |
import ( | |
"fmt" | |
"os" | |
"path/filepath" | |
) | |
func main() ([]string, error) { | |
searchDir := "c:/path/to/dir" |
Bash is the JavaScript of systems programming. Although in some cases it's better to use a systems language like C or Go, Bash is an ideal systems language for smaller POSIX-oriented or command line tasks. Here's three quick reasons why:
This document is how I write Bash and how I'd like collaborators to write Bash with me in my open source projects. It's based on a lot of experience and time collecting best practices. Most of them come from these two articles, but here integrated, slightly modified, and focusing on the most bang for buck items. Plus some ne
See also, http://libraryofalexandria.io/cgo/
cgo
has a lot of trap.
but Not "C" pkg also directory in $GOROOT/src
. IDE's(vim) Goto command not works.
So, Here collect materials.
#!/usr/bin/env ruby | |
require 'rubydns' | |
INTERFACES = [ | |
[:udp, "0.0.0.0", 53], | |
[:tcp, "0.0.0.0", 53] | |
] | |
Name = Resolv::DNS::Name | |
IN = Resolv::DNS::Resource::IN |
/* | |
Watch out, os.IsExist(err) != !os.IsNotExist(err) | |
They are error checkers, so use them only when err != nil, and you want to handle | |
specific errors in a different way! | |
Their main purpose is to wrap around OS error messages for you, so you don't have to test | |
for Windows/Unix/Mobile/other OS error messages for "file exists/directory exists" and | |
"file does not exist/directory does not exist" |