As configured in my dotfiles.
start new:
tmux
start new with session name:
| function! GetColorFromHighlightGroup(group, color, env) | |
| return synIDattr(synIDtrans(hlID(a:group)), a:color, a:env) | |
| endfunction | |
| function! GetBackgroundColors(group) | |
| return | |
| \ ' ctermbg=' . GetColorFromHighlightGroup(a:group, 'bg', 'cterm') . | |
| \ ' guibg=' . GetColorFromHighlightGroup(a:group, 'bg', 'gui') | |
| endfunction |
As configured in my dotfiles.
start new:
tmux
start new with session name:
| #!/bin/sh | |
| prog_name=${0##*/} | |
| version=1.0 | |
| version_text="Boilerplate for new scripts v$version" | |
| options="h o: q v V" | |
| help_text="Usage: $prog_name [-o <text>] [-hqvV] [<file>]... | |
| Boilerplate for new scripts |
It's not immediately obvious how to pull down the code for a PR and test it locally. But it's pretty easy. (This assumes you have a remote for the main repo named upstream.)
Getting the PR code
Make note of the PR number. For example, Rod's latest is PR #37: Psiphon-Labs/psiphon-tunnel-core#37
Fetch the PR's pseudo-branch (or bookmark or rev pointer whatever the word is), and give it a local branch name. Here we'll name it pr37:
$ git fetch upstream pull/37/head:pr37