(C-x means ctrl+x, M-x means alt+x)
The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:
| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |
| node_modules/ |
| module.exports = function (grunt) { | |
| grunt.initConfig({ | |
| bower: { | |
| dev: { | |
| dest: '.tmp/public', | |
| js_dest: '.tmp/public/js/components', | |
| css_dest: '.tmp/public/styles/components', | |
| options: { | |
| packageSpecific: { | |
| bootstrap: { |
trying out gist-vim...
(copied from https://github.com/mattn/gist-vim)
set description
:Gist -s "nonsense random description"
list all my gists
Shall we caching the gist API result at a seperate server?
That means when create a new blog post, user must also update the server file providing blog posts list, it seems will only calling the gist API one time, when the blog updated.
On the other hand, if we do this all by client side, heavier gist API calling, but creating blog post just meaning create new gist, named you_name_it.md, it's more DRY.
Let's see how the second approach performed, shall we?
| $ diff .git-completion.sh /etc/bash_completion.d/git | |
| 292c292,296 | |
| < u="$(parse_git_dirty)" | |
| --- | |
| > if [ -n "${GIT_PS1_SHOWUNTRACKEDFILES-}" ]; then | |
| > if [ -n "$(git ls-files --others --exclude-standard)" ]; then | |
| > u="%" | |
| > fi | |
| > fi |
| # 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_themes: | |
| # git/ruby: bira, dpoggi | |
| # git only: takashiyoshida, duellj, candy |
| var github = (function(){ | |
| function render(target, repos){ | |
| var i = 0, fragment = '', t = $(target)[0]; | |
| for(i = 0; i < repos.length; i++) { | |
| fragment += '<li><a href="'+repos[i].url+'">'+repos[i].name+'</a><p>'+repos[i].description+'</p></li>'; | |
| } | |
| t.innerHTML = fragment; | |
| } | |
| return { |