diff options
Diffstat (limited to 'docs')
12 files changed, 62 insertions, 58 deletions
diff --git a/docs/custom.css b/docs/custom.css index a65d9b7..f492b95 100644 --- a/docs/custom.css +++ b/docs/custom.css @@ -1 +1,26 @@ -/* Place a custom css file in your own project to use this. */
\ No newline at end of file +/* Place a custom css file in your own project to use this. */ +.post-content h1, +.post-content h2, +.post-content h3, +.post-content h4, +.post-content h5, +.post-content h6 { + border-bottom: var(--primary) solid 1px; +} + +.post-content h1::before, +.post-content h2::before, +.post-content h3::before, +.post-content h4::before, +.post-content h5::before, +.post-content h6::before { + color: var(--secondary); + padding-right: 0.3rem; +} + +.post-content h1::before { content: '#'; } +.post-content h2::before { content: '##'; } +.post-content h3::before { content: '###'; } +.post-content h4::before { content: '####'; } +.post-content h5::before { content: '#####'; } +.post-content h6::before { content: '######'; } diff --git a/docs/favicon.svg b/docs/favicon.svg index f686284..2803e39 100644 --- a/docs/favicon.svg +++ b/docs/favicon.svg @@ -24,7 +24,7 @@ <use transform="rotate(252, 50, 50)" xlink:href="#favicon.l"/> <use transform="rotate(288, 50, 50)" xlink:href="#favicon.l"/> <use transform="rotate(324, 50, 50)" xlink:href="#favicon.l"/> - <rect x="33" y="35" width="5" height="20" rx="3" ry="3" fill="black"/> - <rect x="62" y="35" width="5" height="20" rx="3" ry="3" fill="black"/> + <rect x="30" y="35" width="5" height="20" rx="3" ry="3" fill="black"/> + <rect x="65" y="35" width="5" height="20" rx="3" ry="3" fill="black"/> <rect x="43" y="65" width="14" height="5" rx="3" ry="3" fill="black"/> </svg> diff --git a/docs/posts/2021-03-30/phperkaigi-2021/index.html b/docs/posts/2021-03-30/phperkaigi-2021/index.html index f7de49d..33273bd 100644 --- a/docs/posts/2021-03-30/phperkaigi-2021/index.html +++ b/docs/posts/2021-03-30/phperkaigi-2021/index.html @@ -32,6 +32,11 @@ <header class="post-header"> <h1 class="post-title">PHPerKaigi 2021</h1> <div class="post-meta">2021-03-30</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/conference">conference</a></li> + <li><a href="https://blog.nsfisis.dev/tags/php">php</a></li> + <li><a href="https://blog.nsfisis.dev/tags/phperkaigi">phperkaigi</a></li> + </ul> </header> <div class="post-content"><h1 id="phperkaigi-2021-参加レポ">PHPerKaigi 2021 参加レポ</h1> <p>2021/03/26 から 2021/03/28 にかけて開催された、<a href="https://phperkaigi.jp/2021/">PHPerKaigi 2021</a> に一般参加者として参加した。 @@ -505,13 +510,6 @@ Nginx などで相互に gRPC と gRPC-Web で変換</p> (ずっと常体で書いてしまったのでいきなり仏頂面から笑顔になったようで気持ち悪い)</p> <p>ではまた来年。</p> </div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/conference">conference</a></li> - <li><a href="https://blog.nsfisis.dev/tags/php">php</a></li> - <li><a href="https://blog.nsfisis.dev/tags/phperkaigi">phperkaigi</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/posts/2021-10-02/cpp-you-can-use-keywords-in-attributes/index.html b/docs/posts/2021-10-02/cpp-you-can-use-keywords-in-attributes/index.html index d3a9114..d04823b 100644 --- a/docs/posts/2021-10-02/cpp-you-can-use-keywords-in-attributes/index.html +++ b/docs/posts/2021-10-02/cpp-you-can-use-keywords-in-attributes/index.html @@ -32,6 +32,10 @@ <header class="post-header"> <h1 class="post-title">[C++] 属性構文の属性名にはキーワードが使える [[void]] [[for]]</h1> <div class="post-meta">2021-10-02</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/cpp">cpp</a></li> + <li><a href="https://blog.nsfisis.dev/tags/cpp17">cpp17</a></li> + </ul> </header> <div class="post-content"><p>この記事は Qiita から移植してきたものです。 元 URL: <a href="https://qiita.com/nsfisis/items/94090937bcf860cfa93b">https://qiita.com/nsfisis/items/94090937bcf860cfa93b</a></p> @@ -103,12 +107,6 @@ $ clang++ –std=c++17 hoge.cpp</p> <p>「<code>identifier</code> の構文上の要件を満たさないような代替トークン」はこれらが当てはまると思われる。</p> <p>調べた感想: 字句解析器か構文解析器が辛そう</p> </div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/cpp">cpp</a></li> - <li><a href="https://blog.nsfisis.dev/tags/cpp17">cpp17</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/posts/2021-10-02/python-unbound-local-error/index.html b/docs/posts/2021-10-02/python-unbound-local-error/index.html index 171005b..b7e0c19 100644 --- a/docs/posts/2021-10-02/python-unbound-local-error/index.html +++ b/docs/posts/2021-10-02/python-unbound-local-error/index.html @@ -32,6 +32,10 @@ <header class="post-header"> <h1 class="post-title">[Python] クロージャとUnboundLocalError: local variable 'x' referenced before assignment</h1> <div class="post-meta">2021-10-02</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/python">python</a></li> + <li><a href="https://blog.nsfisis.dev/tags/python3">python3</a></li> + </ul> </header> <div class="post-content"><p>この記事は Qiita から移植してきたものです。 元 URL: <a href="https://qiita.com/nsfisis/items/5d733703afcb35bbf399">https://qiita.com/nsfisis/items/5d733703afcb35bbf399</a></p> @@ -71,12 +75,6 @@ f() g() </code></pre></div><p><code>(*)</code> のように、<code>nonlocal</code> を追加する。これにより一つ外側のスコープ (<code>g</code> の一つ外側 = <code>f</code>) で定義されている <code>x</code> を探しに行くようになる。</p> </div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/python">python</a></li> - <li><a href="https://blog.nsfisis.dev/tags/python3">python3</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/posts/2021-10-02/ruby-detect-running-implementation/index.html b/docs/posts/2021-10-02/ruby-detect-running-implementation/index.html index 723cc6a..37360e3 100644 --- a/docs/posts/2021-10-02/ruby-detect-running-implementation/index.html +++ b/docs/posts/2021-10-02/ruby-detect-running-implementation/index.html @@ -32,6 +32,9 @@ <header class="post-header"> <h1 class="post-title">[Ruby] 自身を実行している処理系の種類を判定する</h1> <div class="post-meta">2021-10-02</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/ruby">ruby</a></li> + </ul> </header> <div class="post-content"><p>この記事は Qiita から移植してきたものです。 元 URL: <a href="https://qiita.com/nsfisis/items/74d7ffeeebc51b20d791">https://qiita.com/nsfisis/items/74d7ffeeebc51b20d791</a></p> @@ -100,11 +103,6 @@ jruby 1.2.0 (ruby 1.8.6 patchlevel 287) (2009-03-16 rev 9419) [i386-java] </span><span style="color:#75715e"> */</span> <span style="color:#75715e">#define MRUBY_RUBY_ENGINE "mruby" </span></code></pre></div></div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/ruby">ruby</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/posts/2021-10-02/ruby-then-keyword-and-case-in/index.html b/docs/posts/2021-10-02/ruby-then-keyword-and-case-in/index.html index 26564a8..d599d11 100644 --- a/docs/posts/2021-10-02/ruby-then-keyword-and-case-in/index.html +++ b/docs/posts/2021-10-02/ruby-then-keyword-and-case-in/index.html @@ -32,6 +32,10 @@ <header class="post-header"> <h1 class="post-title">[Ruby] then キーワードと case in</h1> <div class="post-meta">2021-10-02</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/ruby">ruby</a></li> + <li><a href="https://blog.nsfisis.dev/tags/ruby3">ruby3</a></li> + </ul> </header> <div class="post-content"><p>この記事は Qiita から移植してきたものです。 元 URL: <a href="https://qiita.com/nsfisis/items/787a8cf888a304497223">https://qiita.com/nsfisis/items/787a8cf888a304497223</a></p> @@ -169,12 +173,6 @@ C系の <code>if</code> 後に来る <code>(</code>/<code>)</code> や、Python <li>Ruby の構文を正確に知るには (現状) <code>parse.y</code> を直接読めばよい</li> </ul> </div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/ruby">ruby</a></li> - <li><a href="https://blog.nsfisis.dev/tags/ruby3">ruby3</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/posts/2021-10-02/rust-where-are-primitive-types-from/index.html b/docs/posts/2021-10-02/rust-where-are-primitive-types-from/index.html index 1946755..9e5df81 100644 --- a/docs/posts/2021-10-02/rust-where-are-primitive-types-from/index.html +++ b/docs/posts/2021-10-02/rust-where-are-primitive-types-from/index.html @@ -32,6 +32,9 @@ <header class="post-header"> <h1 class="post-title">Rust のプリミティブ型はどこからやって来るか</h1> <div class="post-meta">2021-10-02</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/rust">rust</a></li> + </ul> </header> <div class="post-content"><p>この記事は Qiita から移植してきたものです。 元 URL: <a href="https://qiita.com/nsfisis/items/9a429432258bbcd6c565">https://qiita.com/nsfisis/items/9a429432258bbcd6c565</a></p> @@ -157,11 +160,6 @@ rustc_resolve/src/lib.rs: table.insert(sym::i128, Int(IntTy::I128)); <h1 id="まとめ">まとめ</h1> <p>Rust のプリミティブ型は予約語ではない。名前解決の最終段階で特別扱いされ、他に同名の型が見つかっていなければ対応するプリミティブ型に解決される。</p> </div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/rust">rust</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/posts/2021-10-02/vim-difference-between-autocmd-bufwrite-and-bufwritepre/index.html b/docs/posts/2021-10-02/vim-difference-between-autocmd-bufwrite-and-bufwritepre/index.html index d2ff9e0..8f3233b 100644 --- a/docs/posts/2021-10-02/vim-difference-between-autocmd-bufwrite-and-bufwritepre/index.html +++ b/docs/posts/2021-10-02/vim-difference-between-autocmd-bufwrite-and-bufwritepre/index.html @@ -32,6 +32,9 @@ <header class="post-header"> <h1 class="post-title">[Vim] autocmd events の BufWrite/BufWritePre の違い</h1> <div class="post-meta">2021-10-02</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/vim">vim</a></li> + </ul> </header> <div class="post-content"><p>この記事は Qiita から移植してきたものです。 元 URL: <a href="https://qiita.com/nsfisis/items/79ab4db8564032de0b25">https://qiita.com/nsfisis/items/79ab4db8564032de0b25</a></p> @@ -107,11 +110,6 @@ FileEncoding Obsolete. It still works and is equivalent </ul> <p>ところでこの調査で知ったのだが、<code>BufRead</code> と <code>BufWrite</code> は上にある通り発火するタイミングが「後」と「前」で対称性がない。可能なら <code>Pre</code>/<code>Post</code> 付きのものを使った方が分かりやすいだろう。</p> </div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/vim">vim</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/posts/2021-10-02/vim-swap-order-of-selected-lines/index.html b/docs/posts/2021-10-02/vim-swap-order-of-selected-lines/index.html index 0ffdfda..dcd8e78 100644 --- a/docs/posts/2021-10-02/vim-swap-order-of-selected-lines/index.html +++ b/docs/posts/2021-10-02/vim-swap-order-of-selected-lines/index.html @@ -32,6 +32,9 @@ <header class="post-header"> <h1 class="post-title">Vimで選択した行の順番を入れ替える</h1> <div class="post-meta">2021-10-02</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/vim">vim</a></li> + </ul> </header> <div class="post-content"><p>この記事は Qiita から移植してきたものです。 元 URL: <a href="https://qiita.com/nsfisis/items/4fefb361d9a693803520">https://qiita.com/nsfisis/items/4fefb361d9a693803520</a></p> @@ -123,11 +126,6 @@ executing autocommands |autocmd-searchpat|. </span><span style="color:#960050;background-color:#1e0010"></span> \ <span style="color:#a6e22e">Reverse</span><span style="color:#960050;background-color:#1e0010"> </span><span style="color:#960050;background-color:#1e0010"></span> \ <span style="color:#a6e22e">keeppatterns</span> <<span style="color:#a6e22e">line1</span>>,<<span style="color:#a6e22e">line2</span>><span style="color:#a6e22e">g</span><span style="color:#e6db74">/^/</span><span style="color:#a6e22e">m</span><<span style="color:#a6e22e">line1</span>><span style="color:#ae81ff">-1</span><span style="color:#960050;background-color:#1e0010"> </span></code></pre></div></div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/vim">vim</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/posts/2022-04-09/phperkaigi-2022-tokens/index.html b/docs/posts/2022-04-09/phperkaigi-2022-tokens/index.html index 7245c01..62e6186 100644 --- a/docs/posts/2022-04-09/phperkaigi-2022-tokens/index.html +++ b/docs/posts/2022-04-09/phperkaigi-2022-tokens/index.html @@ -32,6 +32,11 @@ <header class="post-header"> <h1 class="post-title">PHPerKaigi 2022 トークン問題の解説</h1> <div class="post-meta">2022-04-09</div> + <ul class="post-tags"> + <li><a href="https://blog.nsfisis.dev/tags/conference">conference</a></li> + <li><a href="https://blog.nsfisis.dev/tags/php">php</a></li> + <li><a href="https://blog.nsfisis.dev/tags/phperkaigi">phperkaigi</a></li> + </ul> </header> <div class="post-content"><h1 id="更新履歴">更新履歴</h1> <ul> @@ -352,13 +357,6 @@ Quine とは、自分のソースコードをそっくりそのまま出力す 来年は 5問、より面白い問題を持っていきます。</p> <p>実はもう作りはじめているので、どうか来年もありますように……。</p> </div> - <footer class="post-footer"> - <ul class="post-tags"> - <li><a href="https://blog.nsfisis.dev/tags/conference">conference</a></li> - <li><a href="https://blog.nsfisis.dev/tags/php">php</a></li> - <li><a href="https://blog.nsfisis.dev/tags/phperkaigi">phperkaigi</a></li> - </ul> - </footer> </article></main> <footer class="footer"> <span>© 2022 <a href="https://blog.nsfisis.dev">REPL: Rest-Eat-Program Loop</a></span> diff --git a/docs/style.css b/docs/style.css index 99796c2..dd7407a 100644 --- a/docs/style.css +++ b/docs/style.css @@ -454,9 +454,6 @@ img { .post-content iframe { max-width: 100%; } -.post-footer { - margin-top: 56px; -} .post-tags li { display: inline-block; } |
