Skip to content

Instantly share code, notes, and snippets.

@cutedogspark
cutedogspark / .zshrc
Created September 25, 2017 03:14 — forked from yorkxin/.zshrc
My ZSH Settings
# Path to your oh-my-zsh configuration.
ZSH=$HOME/.oh-my-zsh
# Set name of the theme to load.
# Look in ~/.oh-my-zsh/themes/
# Optionally, if you set this to "random", it'll load a random theme each
# time that oh-my-zsh is loaded.
#ZSH_THEME="yaci"
ZSH_THEME="yaci-agnoster"
@cutedogspark
cutedogspark / aria2.bat
Created September 23, 2017 14:33 — forked from aa65535/aria2.bat
Aria2的配置文件 & 启动脚本
:: 启动后需要保留窗口, 关闭窗口则结束进程
aria2c --conf-path=aria2.conf -D
@cutedogspark
cutedogspark / aria2.bat
Created September 23, 2017 14:33 — forked from aa65535/aria2.bat
Aria2的配置文件 & 启动脚本
:: 启动后需要保留窗口, 关闭窗口则结束进程
aria2c --conf-path=aria2.conf -D
@cutedogspark
cutedogspark / main.go
Created September 20, 2017 07:45
Sample golang tools
package main
import (
"fmt"
"log"
"net/http"
_ "net/http/pprof"
"regexp"
)
@cutedogspark
cutedogspark / better-nodejs-require-paths.md
Created September 10, 2017 03:42 — forked from branneman/better-nodejs-require-paths.md
Better local require() paths for Node.js

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

var Article = require('../../../models/article');

Those suck for maintenance and they're ugly.

Possible solutions