Permalink
Browse files

new table marker syntax; no need for metadata

This means there's no need to separate the toc marker from its
configuration, i.e. alignment. This never should've been necessary.

This has the nice side-effect of naturally invalidating the cache when
the toc marker is moved around or its alignment is changed.
  • Loading branch information...
blaenk committed Aug 28, 2015
1 parent 21d6d63 commit dc6ff87f3f330f75047d9a89fa892293e9cc2dd8
Showing with 477 additions and 704 deletions.
  1. +0 −4 input/drafts/notes/bitcoin.markdown
  2. +1 −5 input/drafts/notes/diecast.markdown
  3. +0 −4 input/drafts/notes/distributed-systems.markdown
  4. +0 −4 input/drafts/notes/julia.markdown
  5. +0 −4 input/drafts/notes/rabbitmq.markdown
  6. +118 −237 input/notes/algorithms.markdown
  7. +1 −4 input/notes/angular.markdown
  8. +9 −12 input/notes/clojure-web-development.markdown
  9. +67 −70 input/notes/clojure.markdown
  10. +1 −4 input/notes/cpp.markdown
  11. +1 −4 input/notes/erlang.markdown
  12. +1 −5 input/notes/game-development.markdown
  13. +32 −35 input/notes/gdb.markdown
  14. +1 −4 input/notes/go.markdown
  15. +15 −18 input/notes/haskell.markdown
  16. +25 −28 input/notes/java.markdown
  17. +41 −46 input/notes/machine-learning.markdown
  18. +1 −4 input/notes/play.markdown
  19. +6 −9 input/notes/react.markdown
  20. +1 −4 input/notes/redis.markdown
  21. +44 −47 input/notes/rust.markdown
  22. +1 −4 input/notes/scala.markdown
  23. +2 −5 input/notes/statistics.markdown
  24. +16 −19 input/notes/swift.markdown
  25. +0 −1 input/pages/about.markdown
  26. +0 −1 input/pages/binary.markdown
  27. +0 −1 input/pages/lately.markdown
  28. +0 −1 input/pages/work.markdown
  29. +0 −2 input/posts/a-simpler-vim-statusline.markdown
  30. +1 −5 input/posts/dots.markdown
  31. +1 −5 input/posts/live-editing-with-hakyll.markdown
  32. +1 −5 input/posts/naive-convolution-in-haskell.markdown
  33. +1 −1 input/posts/terminal-customization.markdown
  34. +1 −1 input/posts/the-switch-to-hakyll.markdown
  35. +4 −0 input/scss/_article.scss
  36. +84 −101 src/markdown.rs
@@ -3,9 +3,5 @@ title = "Bitcoin"
published = "October 24, 2014"
excerpt = "The first decentralized cryptocurrency"
comments = false
[toc]
show = true
align = "left"
---
@@ -3,13 +3,9 @@ title = "Diecast"
published = "November 7, 2014"
excerpt = "Static Site Generator written in Rust"
comments = false
[toc]
show = true
align = "right"
---
* toc
<toc align="right"/>
A `Generator` generates a site, maintaining a notion of input and output directories and bindings used to compile trees in the input directory to the output directory.
@@ -3,10 +3,6 @@ title = "Distributed Systems"
published = "September 15, 2014"
excerpt = "Solving problems with multiple computers"
comments = false
[toc]
show = true
align = "left"
---
I'm using [Distributed Systems for Fun and Profit] for an introduction to the field of distributed systems.
@@ -3,10 +3,6 @@ title = "Julia"
published = "July 23, 2014"
excerpt = "A high-performance dynamic language for numerical computing"
comments = false
[toc]
show = true
align = "left"
---
# Types
@@ -3,10 +3,6 @@ title = "RabbitMQ"
published = "July 27, 2014"
excerpt = "Open source AMQP-compliant message broker"
comments = false
[toc]
show = true
align = "false"
---
For every TCP connection there could be multiple channels through which AMQP commands may be sent, each channel with its own unique ID. There are three parts to successful routing of an AMQP message: exchanges, queues, and bindings. Exchanges are where produces publish messages, bindings are how messages get routed from an exchange to a given queue, and queues are where messages end up.
Oops, something went wrong.

0 comments on commit dc6ff87

Please sign in to comment.