From c90daec5f4a91cf1041a5a61411d860ea4329ece Mon Sep 17 00:00:00 2001 From: Tom Willemsen Date: Thu, 21 Jun 2012 21:24:54 +0200 Subject: Initial commit --- site/articles/emacs.org | 127 ++++++++++++++++++++++++++ site/code_vault.org | 49 ++++++++++ site/favicon.png | Bin 0 -> 974 bytes site/header.org | 7 ++ site/ideas/orgtpl.org | 7 ++ site/index.org | 45 ++++++++++ site/projects/bint.org | 18 ++++ site/projects/clever-mode.org | 31 +++++++ site/projects/dispass.el.org | 1 + site/projects/dlmenu.inc | 4 + site/projects/eye-on-manga.org | 38 ++++++++ site/projects/git-auto-commit-mode.org | 90 +++++++++++++++++++ site/projects/org-blog.org | 83 +++++++++++++++++ site/projects/org.org | 85 ++++++++++++++++++ site/projects/ryuslash.org | 75 ++++++++++++++++ site/stylesheet.css | 157 +++++++++++++++++++++++++++++++++ site/windowmanagers.org | 10 +++ 17 files changed, 827 insertions(+) create mode 100644 site/articles/emacs.org create mode 100644 site/code_vault.org create mode 100644 site/favicon.png create mode 100644 site/header.org create mode 100644 site/ideas/orgtpl.org create mode 100644 site/index.org create mode 100644 site/projects/bint.org create mode 100644 site/projects/clever-mode.org create mode 100644 site/projects/dispass.el.org create mode 100644 site/projects/dlmenu.inc create mode 100644 site/projects/eye-on-manga.org create mode 100644 site/projects/git-auto-commit-mode.org create mode 100644 site/projects/org-blog.org create mode 100644 site/projects/org.org create mode 100644 site/projects/ryuslash.org create mode 100644 site/stylesheet.css create mode 100644 site/windowmanagers.org (limited to 'site') diff --git a/site/articles/emacs.org b/site/articles/emacs.org new file mode 100644 index 0000000..f76a51a --- /dev/null +++ b/site/articles/emacs.org @@ -0,0 +1,127 @@ +#+TITLE: Emacs +#+STYLE: +#+LINK_UP: ../index.html +#+LINK_HOME: ../index.html +#+OPTIONS: H:5 + +* General Emacs Tips + + Tips might be the wrong word here, but the way I use Emacs has + resulted into looking at some things that others might not think of + or see. + +** Emacs Init File + + Your Emacs init file can be any of the following: + + - ~$HOME/.emacs~ + - ~$HOME/.emacs.el~ + - ~$HOME/.emacs.d/init.el~ + + I personally use ~$HOME/.emacs.d/init.el~ because that way I can + keep *everything* Emacs related in a single directory + (~$HOME/.emacs.d~). + +** Displaying time + + I've seriously minimized the use of my window manager's task + bar. It only shows which tags there are, some important daemons' + status (running or not) and whether or not I have mail. This makes + it difficult to tell time when I need it. That why it's useful to + see what time it is in Emacs, since that is on 99.99% of the time + I'm behind my computer, and it's very easy: + + #+BEGIN_SRC emacs-lisp + (display-time-mode t) + #+END_SRC + + That is all. When you have that in your [[Emacs Init File]], you will + always have the time in your modeline. + +** Automatically compile startup files + + I know that for 99% of the things you might have in your having a + compiled init files won't make much of a difference, but still I + like having my init files compiled. This gets messy when you share + your init files across multiple PCs and the source files become + newer than the compiled ones. + + To fix this I've put only a very little bit of code in my actual + [[Emacs Init File]]: + + #+BEGIN_SRC emacs-lisp + (require 'bytecomp) + + (defvar startup-files + (directory-files "~/.emacs.d/startup/" t "^[^.].*\\.el$") + "A list of the files that should be loaded during startup.") + + (while startup-files + (let ((filename (car startup-files)) + (byte-compile-warnings nil)) + (if (not (eq (byte-recompile-file filename nil 0) nil)) + (load (substring filename 0 -3)))) + (setq startup-files (cdr startup-files))) + #+END_SRC + + It gets all the files in the ~$HOME/.emacs.d/startup/~ directory + that end with ~.el~. It loops through all these files and compiles + them, and then loads them. I use ~byte-recompile-file~ instead of + ~byte-recompile-directory~ because the directory one didn't work + quite right. It doesn't recompile anything if the source file is + still up to date, so it only slows down when you have a lot of new + files in the ~startup~ directory. It also disables warnings so + that you're not bothered by them during startup. + +* Emacs as... + + There are *many* things Emacs[fn:emacs] is useful for, not just + coding and writing, but certainly very much for these uses as well. + +** ... An IDE... + + Emacs features many modes for a lot of different languages. + +# *** ... For PHP + +# Coming soon... + +# *** ... For Python + +# Coming soon... + +# **** ... With django + +# Coming soon... + +# *** ... For C + +# Coming soon... + +# *** ... For Java on Android + +# Coming soon... + +# *** ... For Go + +# Coming soon... + +# *** ... For Guile (Scheme) + +# Coming soon... + +# ** ... A web authoring tool + +# Coming soon... + +# ** ... An organizational tool + +# Coming soon... + +# ** ... A social network interface + +# Coming soon... + +# ** ... A notifier + +# Coming soon... diff --git a/site/code_vault.org b/site/code_vault.org new file mode 100644 index 0000000..394bee1 --- /dev/null +++ b/site/code_vault.org @@ -0,0 +1,49 @@ +#+TITLE: Code Vault + +Here we have some code snippets that I no longer (intend to) use, but +might still need (to look at) at some point in time. + +* Jabber urgency and libnotify + + This piece of code sends a message through ~libnotify~ and sets a + window urgency hint when a new message is received. + + #+BEGIN_SRC emacs-lisp +(defvar jabber-activity-jids-count 0) + +(defun jabber-urgency-hint () + (let ((count (length jabber-activity-jids))) + (unless (= jabber-activity-jids-count count) + (if (zerop count) + (x-urgency-hint (selected-frame) nil) + (x-urgency-hint (selected-frame) t)) + (setq jabber-activity-jids-count count)))) + +(defun libnotify-jabber-notify (from buf text proposed-alert) + "(jabber.el hook) Notify of new Jabber chat messages via libnotify" + (when (or jabber-message-alert-same-buffer + (not (memq (selected-window) (get-buffer-window-list buf)))) + (if (jabber-muc-sender-p from) + (notify-send (format "(PM) %s" + (jabber-jid-displayname + (jabber-jid-user from))) + (format "%s: %s" (jabber-jid-resource from) text))) + (notify-send (format "%s: " (jabber-jid-displayname from)) + (format "%.20s" text)))) + +(add-hook 'jabber-activity-update-hook 'jabber-urgency-hint) +(add-hook 'jabber-alert-message-hooks 'libnotify-jabber-notify) + #+END_SRC + +* Show symbol instead of ~lambda~ + + #+BEGIN_SRC emacs-lisp +(defun oni:pretty-lambdas () + "Show a lambda sign where the world `lambda' is found." + (font-lock-add-keywords + nil `(("(?\\(\\\\)[ :]" + (0 (progn + (compose-region (match-beginning 1) + (match-end 1) + ?λ))))))) + #+END_SRC diff --git a/site/favicon.png b/site/favicon.png new file mode 100644 index 0000000..4a82e51 Binary files /dev/null and b/site/favicon.png differ diff --git a/site/header.org b/site/header.org new file mode 100644 index 0000000..46d7f1b --- /dev/null +++ b/site/header.org @@ -0,0 +1,7 @@ +#+BEGIN_HTML +
+#+END_HTML + +#+BEGIN_HTML +
+#+END_HTML diff --git a/site/ideas/orgtpl.org b/site/ideas/orgtpl.org new file mode 100644 index 0000000..816a793 --- /dev/null +++ b/site/ideas/orgtpl.org @@ -0,0 +1,7 @@ +#+TITLE: Orgtpl + +* What + + Since we already create both HTML *and* XML templates in django, why + shouldn't we be able to do the same with org. Create a template that + creates an org file that can easily be viewed in emacs. diff --git a/site/index.org b/site/index.org new file mode 100644 index 0000000..a28ae76 --- /dev/null +++ b/site/index.org @@ -0,0 +1,45 @@ +#+TITLE: oni org +#+STYLE: +#+OPTIONS: toc:nil num:nil author:nil email:nil creator:nil +#+LANGUAGE: en +#+LINK_HOME: http://ryuslash.org +#+LINK_UP: http://ryuslash.org +#+STARTUP: showall + +@
+[[http://ryuslash.org/][Front page]] || [[file:blog/index.org][Blog]] +@
+ +* About + + I'm a programming, free software and GNU/Linux enthusiast. I'm also + a programmer professionally, so that works out well. + + I was born in the Netherlands, live in Belgium and work for a dutch + company. I have been using GNU/Linux since 2008, having settled on + [[http://www.archlinux.org][Archlinux]] after trying [[http://www.ubuntu.com][Ubuntu]], [[http://fedoraproject.org][Fedora]] and [[http://zenwalk.org][Zenwalk]]. I have been using + [[http://www.gnu.org][GNU Emacs]] since not long after switching over to GNU/Linux. + + I can be contacted through email (tom at ryuslash dot org) or any + other place you can find me, really. + +** Other places to find me + + - [[https://diasp.org/u/ryuslash][Diasp*]] + - [[http://gitorious.org/%7Eryuslash][Gitorious]] + - [[http://identi.ca/ryuslash][identi.ca]] + - [[http://www.emacswiki.org][EmacsWiki]] + +* Configuration files + + I'm working on putting all of my configuration files (dotfiles) in + ~org-mode~, with ~org-babel~'s literate programming support. [[http://org.ryuslash.org/dotfiles/][Here]] is + what I have so far. + +* Projects + + - [[file:projects/git-auto-commit-mode.org][git-auto-commit-mode]] + - [[file:projects/ryuslash.org][ryuslash.org]] + - [[file:projects/eye-on-manga.org][eye-on-manga]] + - [[file:projects/org-blog.org][org-blog]] + - [[file:projects/org.org][org]] diff --git a/site/projects/bint.org b/site/projects/bint.org new file mode 100644 index 0000000..e8c28af --- /dev/null +++ b/site/projects/bint.org @@ -0,0 +1,18 @@ +* About +** bint -- Bad Image Naming Tool + marijn_a: + dit is wat ik wil dat het doet + + * ik selecteer een map met plaatjes erin. + * programma scant alle mappen in die map voor plaatjes + * nadat ie klar is, laat ie filepath zien en het 1ste plaatje + * vraagt om de naam van het plaatje + * ik type een naam in en druk enter + * volgende plaatje in beeld + * ik typ naam en enter + * etc + + zie het als een image renamer + dus eerst heet het plaatje 35y6795634.jpg + dan type je in de balk: THE ALIENS INVADED!! + en dan renamed ie naar THE ALIENS INVADED!!.jpg diff --git a/site/projects/clever-mode.org b/site/projects/clever-mode.org new file mode 100644 index 0000000..f773ac2 --- /dev/null +++ b/site/projects/clever-mode.org @@ -0,0 +1,31 @@ +#+TITLE: clever-mode +#+STYLE: +#+LINK_UP: ../index.html +#+LINK_HOME: ../index.html + +#+INCLUDE: "../header.org" :lines "1-4" + +* About + + ~clever-mode~ is a GNU Emacs[fn:emacs:http://gnu.org/software/emacs/] + major mode for editing Smarty[fn:smarty:http://www.smarty.net] templates. + +** Why + + The only modes for editing Smarty[fn:smarty] templates are either + outdated or need MuMaMo, and I seriously dislike MuMaMo. + + Also, I have some Emacs[fn:emacs] projects now, but no major mode + yet, and I want to learn. + +** Features + + ~clever-mode~ is based on HTML mode, although Smarty[fn:smarty] is + not limited to HTML, that is what it is used for most (at least by me). + +* Usage + + Since it only has some syntax highlighting at the moment usage only + consists of getting it, installing it and enabling it. + +#+INCLUDE: "../header.org" :lines "5-8" diff --git a/site/projects/dispass.el.org b/site/projects/dispass.el.org new file mode 100644 index 0000000..b64a4ed --- /dev/null +++ b/site/projects/dispass.el.org @@ -0,0 +1 @@ +#+TITLE: Dispass.el diff --git a/site/projects/dlmenu.inc b/site/projects/dlmenu.inc new file mode 100644 index 0000000..618d3ad --- /dev/null +++ b/site/projects/dlmenu.inc @@ -0,0 +1,4 @@ +# -*- mode: org -*- +@
+[[src][Browse Source]] || [[tar_gz][Download tar.gz]] || [[zip][Download zip]] +@
diff --git a/site/projects/eye-on-manga.org b/site/projects/eye-on-manga.org new file mode 100644 index 0000000..e7c52de --- /dev/null +++ b/site/projects/eye-on-manga.org @@ -0,0 +1,38 @@ +#+TITLE: eye-on-manga +#+STYLE: +#+LINK_UP: ../index.html +#+LINK_HOME: ../index.html +#+LINK: src https://github.com/ryuslash/eye-on-manga +#+LINK: tar_gz https://github.com/ryuslash/eye-on-manga/tarball/master +#+LINK: zip https://github.com/ryuslash/eye-on-manga/zipball/master + +#+INCLUDE: "../header.org" :lines "1-4" +#+INCLUDE: "dlmenu.inc" + +* About + + ~eye-on-manga~ is a manga collection management application for the + Nokia N900. + +** Why + + I was always either standing in the shop, or at the + F.A.C.T.S. event, looking at and for manga, and I'd completely + forget which ones I needed to get and which ones I'd already read. + +** How + + ~eye-on-manga~ is a simple application for the N900, it keeps a + list of manga in a SQLite database and makes it possible to edit + this data through a UI. You can tell it how many volumes a manga + should have and then it makes it easy to select which ones you've + aquired and which ones you've read. + +** Features + + - Create a list of manga. + - Keep track of which volumes have been acquired and read. + - Edit wrongfully entered entries. + - Easily mark a volume as acquired or read. + +#+INCLUDE: "../header.org" :lines "5-8" diff --git a/site/projects/git-auto-commit-mode.org b/site/projects/git-auto-commit-mode.org new file mode 100644 index 0000000..3542217 --- /dev/null +++ b/site/projects/git-auto-commit-mode.org @@ -0,0 +1,90 @@ +#+TITLE: git-auto-commit-mode +#+STYLE: +#+LINK_UP: ../index.html +#+LINK_HOME: ../index.html +#+LINK: src https://github.com/ryuslash/git-auto-commit-mode +#+LINK: tar_gz https://github.com/ryuslash/git-auto-commit-mode/tarball/master +#+LINK: zip https://github.com/ryuslash/git-auto-commit-mode/zipball/master + +#+INCLUDE: "../header.org" :lines "1-4" +#+INCLUDE: "dlmenu.inc" + +* About + + ~git-auto-commit-mode~ is a minor mode for GNU Emacs[fn:: + http://gnu.org/software/emacs/] that, when enabled, adds and commits + a file after every save. + +** Why + + I thought of it when I was editing my configuration files. Most of + my changes in my configuration files are fairly simple and I would + like them immediately committed, I don't want to have to sift + through all the changes at a later point to figure out what I want + to commit when. + +** How + + ~git-auto-commit-mode~ blindly calls + + #+BEGIN_SRC bash + git add FILE + git commit -m "RELATIVE-FILE-PATH" + #+END_SRC + + setting up the git repository correctly is the responsibility of + the user. + +** Features + + ~git-auto-commit-mode~ only really has one feature: + + - Automatically commit file to current git repository after saving. + +* Usage + + To be able to use it you need to put it somewhere in your + ~load-path~ and load it, for example: + + #+NAME: .emacs.d + #+BEGIN_SRC emacs-lisp + (add-to-list 'load-path "~/path/to/git-auto-commit-mode.el") + (autoload 'git-auto-commit-mode "git-auto-commit-mode") + #+END_SRC + + There are a few ways this could be used: + +** As file-local variable + + This is the way I use it and I wanted to use it. Any file that you + would like to have automatically committed upon saving gets this + prop-line: + + #+BEGIN_SRC emacs-lisp + ;; -*- eval: (git-auto-commit-mode 1) -*- + #+END_SRC + + Or, if you're in anything older than emacs 24: + + #+BEGIN_SRC emacs-lisp + ;; -*- mode: git-auto-commit -*- + #+END_SRC + +** As a directory-local variable + + Put the following in a ~.dir-locals.el~ file in any directory where + you want to enable ~git-auto-commit-mode~ for *all* files: + + #+BEGIN_SRC emacs-lisp + ((nil . ((git-auto-commit-mode . t)))) + #+END_SRC + +** As a hook + + I doubt this will ever really be useful, but it is possible: + + #+BEGIN_SRC emacs-lisp + (add-hook 'some-hook 'git-auto-commit-mode) + #+END_SRC + +#+INCLUDE: "../header.org" :lines "5-8" diff --git a/site/projects/org-blog.org b/site/projects/org-blog.org new file mode 100644 index 0000000..251e877 --- /dev/null +++ b/site/projects/org-blog.org @@ -0,0 +1,83 @@ +#+TITLE: git-auto-commit-mode +#+LINK_UP: ../index.html +#+LINK_HOME: ../index.html +#+LINK: src https://github.com/ryuslash/org-blog +#+LINK: tar_gz https://github.com/ryuslash/org-blog/tarball/master +#+LINK: zip https://github.com/ryuslash/org-blog/zipball/master + +#+INCLUDE: "../header.org" :lines "1-4" +#+INCLUDE: "dlmenu.inc" + +* About + + ~org-blog~ is a blog exporter for ~org-mode~ written by David + O'Toole in 2006. ~org-mode~ has since then changed a bit and it + seemed that it no longer worked. It also seems to be the only + viable/acceptable pure-org solution for me, so I'm trying to revive + it. + +** Why + + As stated, it seemed to be out-of-date and packages like [[http://renard.github.com/o-blog/][o-blog]] and + [[http://www.emacswiki.org/emacs/Blorg][blorg]] didn't work for me, and many others require some external + tool to work. + +* Setup + + Since I've adapted it to work as a normal publishing function for + org, setting it up is a lot like any other publishing project as + well: + + #+BEGIN_SRC emacs-lisp + (setq org-publish-project-alist + '(("myblog" + :base-directory "~/location/to/org/files/" + :publishing-directory "/place/to/export/to/" + :base-extension "org" + :publishing-function org-publish-org-to-blog + :blog-title "some title" + :blog-description "some description" + :blog-export-rss t + :index-title "oni blog" + :recursive nil + :table-of-contents nil))) + #+END_SRC + + Most of these options are very normal project settings and can be + read about in the documentation for the variable + ~org-publish-project-alist~. The ~blog-title~, ~blog-description~, + ~blog-export-rss~ and ~index-title~, however, are used by + ~org-blog~. + + - ~blog-title~ + + This setting is used when exporting RSS. It sets the ~title~ in + the XML output. + + - ~blog-description~ + + This setting is also used when exporting RSS. It sets the + ~description~ in the XML output. + + - ~blog-export-rss~ + + Whether or not you would like an RSS feed to be exported. + + - ~index-title~ + + This is used as the title of the blog's index page. + + Apart from these there are also 2 other settings that need your + attention: + + #+BEGIN_SRC emacs-lisp + (setq org-blog-directory "~/path/to/blog/org/files/") + (setq org-blog-unfinished-directory "~/path/to/drafts/") + #+END_SRC + + These don't have any relevance to the exporting and publishing + functions, but they're used by the ~org-blog-new-post~ and + ~org-blog-finish-post~ functions, which help with creating new + posts. + +#+INCLUDE: "../header.org" :lines "5-8" diff --git a/site/projects/org.org b/site/projects/org.org new file mode 100644 index 0000000..c8b3adc --- /dev/null +++ b/site/projects/org.org @@ -0,0 +1,85 @@ +#+TITLE: org +#+STYLE: +#+LINK_UP: ../index.html +#+LINK_HOME: ../index.html +#+OPTIONS: H:5 + +* About + + No I don't mean that I have anything to do with [[http://orgmode.org][org-mode]], but trying + to find a nice and effective structure to my org files is an ongoing + project for me. + +* Organizational + +** inbox.org + + The ~inbox.org~ file is used as, surprise surprise, an + inbox. Whenever ~org-capture~ is used to create a new task, + appointment or note, it is placed in this file, from here it should + be distributed to one of the other org files. + + - appointments + + New appointments that should be placed in one of the other files + are first placed here. + + - notes + + New notes that should be placed in one of the other files are + first placed here. + + - tasks + + New tasks that should be placed in one of the other files are + first placed here. + +** personal.org + + The ~personal.org~ file is used for private tasks, appointments and + notes. Not specifically actually private, just not belonging to any + of the other org files. + + - appointments + + Appointments of a personal nature, not specifically about any of + the other org files. + + - birthdays + + Birthdays of friends and family are noted here. + + - bookmarks + + Some very interesting links that I should keep an eye on. + + - notes + + Notes about personal things should be placed here. + + - rss + + I have a single RSS feed that I load with org, this is a feed + from [[http://www.myepisodes.com][MyEpisodes]] which tells me when new episodes of shows I + watch air. + + - tasks + + Tasks of a personal nature, not belonging to any of the other + files/categories. + +** contacts.org + + Just keeps my contacts. + +** projects + + Org files about projects I work on. + +*** any org files + + + +** work + + Org files about work-related things. diff --git a/site/projects/ryuslash.org b/site/projects/ryuslash.org new file mode 100644 index 0000000..ccc6475 --- /dev/null +++ b/site/projects/ryuslash.org @@ -0,0 +1,75 @@ +#+TITLE: ryuslash.org +#+STYLE: +#+LINK_UP: ../index.html +#+LINK_HOME: ../index.html +#+LINK: python http://www.python.org +#+LINK: django http://djangoproject.com +#+LINK: feedparser http://code.google.com/p/feedparser/ +#+LINK: south http://south.aeracode.org/ +#+LINK: markdown http://packages.python.org/Markdown/ +#+LINK: src https://github.com/ryuslash/ryuslash.org +#+LINK: tar_gz https://github.com/ryuslash/ryuslash.org/tarball/master +#+LINK: zip https://github.com/ryuslash/ryuslash.org/zipball/master + +#+INCLUDE: "../header.org" :lines "1-4" +#+INCLUDE: "dlmenu.inc" + +* About + :PROPERTIES: + :hosted_at: github + :END: + + ~ryuslash.org~ is the project of the front page of [[http://ryuslash.org][my website]]. I + have noticed, though, that apart from the /design/ and the initial + data[fn:: The configured feeds], there is nothing really specific to + my about this project. + + Right now all it really does is show a bunch of feeds on a page. + +** Why + + I've been trying out different kinds of ways to manage/run a + website/blog for a long time now, and I can't seem to keep using + just one thing. This annoys me. + + With ~ryuslash.org~ I'm trying it in a different way, gather + everything I do elsewhere and present it in a single place. I + *must* be generating content /somewhere/, and if that's true, and + friends or other interested people might want to know about this, + then it's nice to have it all in one place. + +** How + + ~ryuslash.org~ uses the [[python][Python]] web framework [[django][django]] and the [[python][Python]] + module [[feedparser][feedparser]]. It uses a management command ~loadfeeds~ to go + through all the configured feeds and check them for new items. + +** Features + + - Define multiple RSS feeds to load news items from. + - Define relative paths for the xml and profile linked to a feed. + - Group feeds in categories. + - Add comments to any post that comes in. + - Generate feeds: One for all posts, one for all comments. + +** Requirements + + ~ryuslash.org~ uses the following modules and applications: + + - [[python][Python]] 2.6.x or 2.7.x + - [[django][Django]] 1.3 + - [[south][South]] 0.7.4 + - [[feedparser][Feedparser]] 5.1.1 + - [[markdown][Markdown]] 2.1.1 + +* Installation + + Must write... + +* Configuration + + The feeds that are loaded are defined in the database, through the + ~Feed~ model. Now when you want to run your own instance, it might + be preferable *not* to load my feeds, so you should remove (part of) + or change ~aggregator/fixtures/initial_data.json~, otherwise your + feeds will be overwritten by my feeds every time you migrate. diff --git a/site/stylesheet.css b/site/stylesheet.css new file mode 100644 index 0000000..b23ad2d --- /dev/null +++ b/site/stylesheet.css @@ -0,0 +1,157 @@ +* { + padding: 0; + margin: 0; + border: 0; +} + +a { + color: orange; + text-decoration: none; +} + +a:hover { + text-decoration: underline; +} + +body { + background-color: #262a2b; + color: #ffffff; + font-family: "DejaVu Sans", sans-serif; + padding-left: 10px; +} + +code { + padding: 1px 3px; + border-radius: 5px; + margin: 0 2px; +} + +code, pre { + font-family: "DejaVu Sans Mono", mono; + background-color: #181818; + color: #eeeeec; +} + +h1 { + border-bottom: 2px solid #839496; +} + +h1, h2, h3, h4, h5, h6 { + margin: 20px 0; +} + +h1.title { + border-bottom: none; +} + +h2 { + border-bottom: 2px dotted #839496; +} + +h3 { + border-bottom: 2px dashed #839496; +} + +h4 { + border-bottom: 1px solid #839496; +} + +h5 { + border-bottom: 1px dotted #839496; +} + +h6 { + border-bottom: 1px dashed #839496; +} + +ul { + margin: 20px; +} + +ul ul { + margin: 5px 20px; +} + +p { + margin: 20px 0; +} + +pre { + margin: 20px 0 20px 40px; + border-radius: 10px; + padding: 5px; +} + +#content { + width: 750px; + margin: 0 auto; +} + +.dlmenu { + text-align: center; +} + +.title { + text-align: center; +} + +#postamble { + margin-top: 40px; +} + +#org-div-home-and-up a { + text-decoration: none; + margin: 10px; +} + +/* Org font-locking */ +.src { + background-color: #002b36; + color: #839496; +} + +.org-keyword { + color: #859900; +} + +.org-string { + color: #2aa198; +} + +.org-function-name { + color: #268bd2; +} + +.org-doc { + color: #586e75; + font-style: italic; +} + +.org-constant { + color: #2aa198; + font-style: normal; +} + +.org-type { + color: #b58900; +} + +.org-regexp-grouping-backslash { + color: #b58900; +} + +.org-regexp-grouping-construct { + color: #cb4b16; +} + +.org-builtin { + color: #859900; +} + +.org-negation-char { + color: #dc322f; +} + +.org-variable-name { + color: #268bd2; +} diff --git a/site/windowmanagers.org b/site/windowmanagers.org new file mode 100644 index 0000000..de3f9bb --- /dev/null +++ b/site/windowmanagers.org @@ -0,0 +1,10 @@ +| herbstluftwm | c | manual | IPC (anything) | +| awesomewm | c | automatic | lua | +| wmx | ? | N/A | N/A | +| wm2 | ? | ? | N/A | +| dwm | c | automatic | c | +| spectrwm | c | automatic | text | +| kde | ? | N/A | graphical | +| gnome | ? | N/A | graphical | +| openbox | ? | N/A | xml | +| adwm | c | automatic | c? | -- cgit v1.2.3-54-g00ecf