| ; https://z0ltan.wordpress.com/2018/08/04/simple-expression-evaluator-comparison-between-haskell-rust-and-common-lisp/ | |
| ; this version: 2018, Rainer Joswig, joswig@lisp.de | |
| ; we create a bunch of structures for the expression types | |
| ; each structure defines a constructor of the same name | |
| ; each expression knows the corresponding Lisp function | |
| (defstruct (val (:constructor val (e))) e) | |
| (defstruct (bop :conc-name) e1 e2 op) |
Using xclip to copy terminal content to the clip board:
Say you want to pipe shell output to your clipboard on Linux. How would you do it? First, choose the clipboard destination, either the Mouse clip or the system clipboard.
For the mouse clipboard, pipe straight to xclip:
echo 123 | xclip
For the system clip board, pipe to xclip and select clip directly:
This document was based on my local [GNU Guile][1]-3.0.5 setup. I'm not sure if it works as is with an older version of GNU Guile.
Because of a [dependency in Fedora][2] I had to compile GNU Guile from source release. As such, in your local setup the paths will differ. This is only relevant when defining the GUILE shell variable, and referencing the tags file in the vimrc.
Note that when building GNU Guile from source be sure that you have the readline-devel (or distro equivalent package) installed. That way the
./configurestep will pick that up, and theice-9 readlinemodule will be usable.
| #!/bin/bash | |
| # source: http://www.haskell.org/pipermail/haskell-cafe/2011-March/090170.html | |
| sudo rm -rf /Library/Frameworks/GHC.framework | |
| sudo rm -rf /Library/Frameworks/HaskellPlatform.framework | |
| sudo rm -rf /Library/Haskell | |
| rm -rf ~/.cabal | |
| rm -rf ~/.ghc | |
| rm -rf ~/Library/Haskell |
| 0 = Success | |
| 1 = Operation not permitted | |
| 2 = No such file or directory | |
| 3 = No such process | |
| 4 = Interrupted system call | |
| 5 = Input/output error | |
| 6 = No such device or address | |
| 7 = Argument list too long | |
| 8 = Exec format error |
| /* | |
| * To compile objective-c on the command line: | |
| * | |
| * gcc -framework Foundation objc-gcc.m | |
| * | |
| * You may have to link with -lobjc or other libs, | |
| * as required. | |
| */ | |
| #import <Foundation/Foundation.h> |
When [Markdown][markdown] appeared more than 10 years ago, it aimed to make it easier to express ideas in an easy-to-write plain text format. It offers a simple syntax that takes the writer focus away from the formatting, thus giving her time to focus on the actual content.
The market abunds of editors to be used for help with markdown. After a few attempts, I settled to Sublime and its browser preview plugin, which work great for me and have a small memory footprint to accomplish that. To pass the results around to other people, less technical, a markdown file and a bunch of images is not the best approach, so converting it to a more robust format like PDF seems like a much better choice.
[Pandoc][pandoc] is the swiss-army knife of converting documents between various formats. While being able to deal with heavy-weight formats like docx and epub, we will need it for the more lightweight markdown. To be able to generate PDF files, we need LaTeX. On OSX, the s
Quick guide on how to setup git signing. Information is aggregated from following sources: