Kazuya Takei attakei
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| -- packer.nvimを自動でインストール | |
| local install_path = vim.fn.stdpath "data" .. "/site/pack/packer/start/packer.nvim" | |
| local packer_bootstrap = nil | |
| if vim.fn.empty(vim.fn.glob(install_path)) > 0 then | |
| packer_bootstrap = vim.fn.system { | |
| "git", | |
| "clone", | |
| "--depth", | |
| "1", | |
| "https://github.com/wbthomason/packer.nvim", |
tk0miya
/ tk0miya-sponsors-2021.md
Last active
September 23, 2021 13:25
— forked from melpon/wandbox-sponsors.md
@tk0miya のスポンサー募集
(For English readers: please read https://github.com/sponsors/tk0miya instead)
@tkomiya は、日本在住の OSS 開発者です。
趣味として Sphinx や pycmark、 blockdiag などの OSS の開発やメンテナンスに携わっています。
ここ数年の活動の中心は Sphinx です。 Sphinx は Python や Linux カーネルをはじめとして、数多くの OSS のドキュメントに利用されているドキュメンテーションツールです。 Sphinx プロジェクトはごく少人数のメンテナによって活動しており、(明確な役割として定義はされていないものの) リードメンテナ、メインメンテナとして活動しています。
If you use Storybook with Next.js and have components using next/link you'll have to mock next/router the same you would for testing with Jest or others. Simply create a file with the mock router as shown below and import it in your Storybook config.
This is based on some information from an issue on Next.js:
udondan
/ include_vars_merged
Last active
June 15, 2023 17:57
Ansible action plugin "include_vars_merged". Same as "include_vars" but merges hashes instead of overriding
Current version of Ansible (1.7.1) does not merge hashes in the include_vars task even if told so via hash_behaviour = merge in your ansible.cfg. ansible/ansible#9116
This action plugin will merge hashes no matter how you have configured your hash_behaviour.
Save include_vars_merged.py to library/plugins/action/include_vars_merged.py
Save include_vars_merged to library/custom/include_vars_merged
tcnksm
/ docker_cheat.md
Last active
August 5, 2021 03:59
— forked from wsargent/docker_cheat.md
Docker 虎の巻
- Fork from Docker cheat sheet
- 実際にコマンドを試したい場合は、すぐにDockerを試したい人のための基礎コマンドを参照
Why Should I Care (For Developers)
"Dockerが面白いのはシンプルな環境に隔離性と再現性をもたらしてくれることだ．ランタイムの環境を一度作れば、パッケージにして別のマシンでも再利用することできる．さらに，すべてはホスト内の隔離された環境で行われる（VMのように）．最も素晴らしい点は，シンプルかつ高速であることだ．"
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.