Join me as we look at the source code for the popular Haskell project Pandoc. We'll take it apart, see how it works, and build a program from the components we find. In this, part 1, we'll look at how Pandoc uses the Parsec library to parse email addresses. Links from the video (in order): - http://www.vocabulink.com/ (my site that uses the Pandoc library) - http://jekor.com/ (my personal site that uses the Pandoc command-line program) - http://whatismarkdown.com/ (Markdown) - http://en.wikipedia.org/wiki/Ctags (TAGS) - http://www.cs.nott.ac.uk/~pszgmh/monparsing.pdf (Monadic Parser Combinators) - https://github.com/chrisdone/hasktags (hasktags) - https://github.com/akheron/jansson/blob/master/src/load.c (example C parser for JSON) - https://github.com/douglascrockford/JSON-js/blob/master/json_parse.js (example JavaScript parser for JSON) - http://www.ietf.org/rfc.html (IETF RFCs) - http://hackage.haskell.org/package/parsec (Parsec parsing library) My Bash $PS1 is defined as: PS1="\[\033[ 01;37m\]\$(exit=\$?; if [[ \$exit == 0 ]]; then echo \"\[\033[01;32m\]✓\"; else echo \"\[\033[01;31m\]✗ \$exit\"; fi) \[\033[01;32m\]\u\[\033[01;34m\] \W \$\[\033[00m\] " To customize yours, see "Return value visualization" at https://wiki.archlinux.org/index.php/Color_Bash_Prompt If you use Windows and want to see the exit codes, see http://stackoverflow.com/questions/334879/how-do-i-get-the-application-exit-code-from-a-windows-command-line All Code Deconstructed videos:    • Code Deconstructed