There're a lot of combinations to manage your email with emacs, but this works for me. I've a backup and I can manage my daily email.
The stack:
- emacs
- offlineimap
- mu
- mu4e
| {-# LANGUAGE OverloadedStrings #-} | |
| module Main where | |
| import Network.Wai (pathInfo, Request, requestMethod, Response, responseLBS, ResponseReceived) | |
| import Network.Wai.Handler.Warp (run) | |
| import Network.HTTP.Types (status200, status401) | |
| -- note: type Application = Request -> (Response -> IO ResponseReceived) -> IO ResponseReceived | |
| application :: Request -> (Response -> IO ResponseReceived) -> IO ResponseReceived |
| {-# LANGUAGE BangPatterns #-} | |
| {- | |
| Scenario / preconditions for the usefulness of this ring buffer: | |
| - mutable data structure | |
| - elements of the same size (here: ByteString, extending to values of class Storable should be trivial) | |
| - each element is denoted by a continuous Int id | |
| - main benefit, esp. for a large number of elements: |
| ! Atom One Light theme | |
| xterm*background: #f9f9f9 | |
| xterm*foreground: #383a42 | |
| xterm*cursorColor: #d0d0d0 | |
| xterm*color0: #000000 | |
| xterm*color1: #E45649 | |
| xterm*color2: #50A14F | |
| xterm*color3: #986801 | |
| xterm*color4: #4078F2 | |
| xterm*color5: #A626A4 |
| {-# LANGUAGE FlexibleInstances #-} | |
| -- | Monoids with holes. The 'HoleyMonoid' allows building monoidal values of which certain components are to be filled in later. For example: | |
| -- | |
| -- > > let holey = now "x = " | |
| -- > . later show | |
| -- > . now ", y = " | |
| -- > . later show | |
| -- > > run holey 3 5 | |
| -- > "x = 3, y = 5" | |
| -- |
| #install new versions of gcc and g++ | |
| sudo apt-get install gcc-4.8 g++-4.8 | |
| #remove existing alternatives | |
| sudo update-alternatives --remove-all gcc | |
| sudo update-alternatives --remove-all g++ | |
| #add new and old version to update-alternatives db | |
| sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.6 60 --slave /usr/bin/g++ g++ /usr/bin/g++-4.6 | |
| sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 40 --slave /usr/bin/g++ g++ /usr/bin/g++-4.8 |
| #!/usr/bin/env python2 | |
| # | |
| # dockbar.py | |
| # | |
| # Example program places a coloured bar across the top of the | |
| # current monitor | |
| # | |
| # demonstrates | |
| # | |
| # (a) creating the bar as an undecorated "dock" window |
| #include <X11/Xlib.h> | |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| int main() | |
| { | |
| Display *display; | |
| Window window; | |
| XEvent event; | |
| int s; |
| package main | |
| import( | |
| "log" | |
| "net/url" | |
| "net/http" | |
| "net/http/httputil" | |
| ) | |
| func main() { |
| #!/bin/sh | |
| # | |
| # Setup a work space called `work` with two windows | |
| # first window has 3 panes. | |
| # The first pane set at 65%, split horizontally, set to api root and running vim | |
| # pane 2 is split at 25% and running redis-server | |
| # pane 3 is set to api root and bash prompt. | |
| # note: `api` aliased to `cd ~/path/to/work` | |
| # | |
| session="work" |