| # -*- coding: utf-8 -*- | |
| Plugin.create :vanish do | |
| command(:vanish_message, | |
| name: "これきらい", | |
| condition: Plugin::Command[:CanReplyAll], | |
| visible: true, | |
| role: :timeline ) do |opt| | |
| opt.messages.each do |msg| | |
| Plugin.call(:destroyed, [msg]) |
| # RSpec matcher for alias_method. | |
| # https://gist.github.com/1950961 | |
| # Usage: | |
| # | |
| # describe User do | |
| # it { should alias_from(:username).to(:email) } | |
| # end | |
| RSpec::Matchers.define :alias_from do |alias_method| |
| " カーソル位置の復元(git commit のときだけは動かさない) | |
| augroup restore-cursor | |
| autocmd! | |
| autocmd BufReadPost * | |
| \ if line("'\"") > 1 && line("'\"") <= line("$") && &ft !=# 'gitcommit' | | |
| \ exe "normal! g`\"" | | |
| \ endif | |
| augroup END |
It is possible to compile Go programs for a different OS, even though go build says otherwise.
You'll need:
golang-crosscompile helper script https://github.com/davecheney/golang-crosscompile
| #!/usr/bin/sh | |
| # symlinker.sh | |
| # shell script to create symbolic link of "dotfiles" in which same directory with this script to your home directory. also handles directory whose name starts with dot. | |
| # NOTICE: this script processes only files whose name begin with . (dot) | |
| # | |
| # polamjag <[email protected]> | |
| # license: public domain | |
| echo -e "creating symbolic link of dotfiles..." |
| Version: | Build version go 1.1.1 |
|---|---|
| original: | http://golang.org/doc/code.html |
| ## | |
| ## This nginx.conf servers as the main config file for webflow reverse proxy | |
| ## | |
| ## RCS: | |
| ## https://gist.github.com/sansmischevia/5617402 | |
| ## | |
| ## Hardening tips: | |
| ## http://www.cyberciti.biz/tips/linux-unix-bsd-nginx-webserver-security.html | |
| ## |
| # A sample Gemfile | |
| source "https://rubygems.org" | |
| gem 'rubix' | |
| gem 'zabbixapi' | |
| gem 'zabby' | |
| gem 'zbxapi' |
(´へεへ`*) ＜ 10日目だよ〜
(´へεへ`*) ＜ 昨日は@penguin2716氏、明日は@teshi04氏だよ〜
(´へεへ`*) ＜ ………
#Introduction
Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.
Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.
