As configured in my dotfiles.
start new:
tmux
start new with session name:
As configured in my dotfiles.
start new:
tmux
start new with session name:
| If: | |
| - you add and commit with the wrong email address in git, and | |
| - your remote has a hook set up to prevent you from pushing with the bad address | |
| Then you need to amend the author of your commit before push can succeed: | |
| 1. fix your email address in git config: | |
| $ git config user.name "Your Name" |
| # 適用於【鼠鬚管】0.9.13+ | |
| # 位置:~/Library/Rime/squirrel.custom.yaml | |
| # 用法:想要哪項生效,就刪去該行行首的#字符,但注意保留用於縮進的空格 | |
| patch: | |
| # us_keyboard_layout: true # 鍵盤選項:應用美式鍵盤佈局 | |
| # show_notifications_when: growl_is_running # 狀態通知,默認裝有Growl時顯示,也可設爲全開(always)全關(never) | |
| # style/horizontal: true # 候選窗横向顯示 | |
| # style/inline_preedit: false # 非內嵌編碼行 | |
| # style/font_face: "儷黑 Pro" # 我喜歡的字體名稱 |
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
| // | |
| // NSObject+setValuesForKeysWithJSONDictionary.h | |
| // SafeSetDemo | |
| // | |
| // Created by Tom Harrington on 12/29/11. | |
| // Copyright (c) 2011 Atomic Bird, LLC. All rights reserved. | |
| // | |
| #import <Foundation/Foundation.h> |
| A warning occurred (42 apples) | |
| An error occurred |
| $ FILE=/some/path/to/file.txt | |
| ################################### | |
| ### Remove matching suffix pattern | |
| ################################### | |
| $ echo ${FILE%.*} # remove ext | |
| /some/path/to/file | |
| $ FILE=/some/path/to/file.txt.jpg.gpg # note various file exts |
| { "path": "/content/geometrixx/my-first-jinja-page", | |
| "properties": [ | |
| { "name": "jcr:primaryType", | |
| "value": "cq:Page" }], | |
| "nodes": [ | |
| { "path": "jcr:content", | |
| "properties": [ | |
| { "name": "jcr:primaryType", | |
| "value": "cq:PageContent"}, |
This Gist is created in 2014, and it's highliy outdated now, according to one of mitmproxy's manjor contributor (check his comment below). Thanks for letting us know, @mhils!
Modern applications usually make use of back-end API servers to provide their services. With a non-transparent HTTPs proxy, which intercepts the communication between clients and servers (aka the man-in-the-middle scheme), you can easily manipulate both API requests and responses.