This file contains configuration items for my org-mode use. It is intended to be used by a #+SETUPFILE: directive in a normal org-file.
The advantage of doing it this way, apart from the logical separation to make it easier to reuse, is that this configuration file is also just a normal orgmode file. That allows me to separate the configuration is different sections, publish the configuration in a variety of formats and generally describe the configuration in a clear way so I can remember what this was all about. This is not unlike literal programming.
The disadvantage is that it needs to be in every org-mode, which can sometimes be a nuisance (for example, it needs to be in every blog posting i write in orgmode if they are contained in separate files)
When moving to a new theme, use this subsection to test configuration of orgmode colors. This paragraph is the test for plain text and inline markings such as bold and italic code and underline and striked
- listmarker
- first
- listmarker
- last
- plain link
- http://hsdev.com
Source:
(defun function (par1 &optional par2)
"Documentation for the function"
(interactive)
;; Comment line
(setq var "string" 'quoted :property 0 -1 +1 0.01 ))[2018-03-24 za] Date display
Orgmode:
Level 7Level 8Level 9This section contains general settings.
Drawer definitions. We render drawers with a slightly smaller font, so it’s important to define them, otherwise orgmode does not know they are supposed to be rendered differently.
Standard category is things that fall withing GTD
Action tags make up the meat of task management. The reason we want these tags is that we want to produce a list of them, or filter with them. If that need does not exist for one of the tags below, remove them. The list requirement is valid in general for any tag btw.
Things I do to physical objects:
Administration like tags:
Status like tags. The first is to make items fall from the radar completely by making them inactive (see the custom agenda commands which use this tag). The fork tag is for projects I have started and need to finish before starting something new. The amount of forks is a good measure of how good I’m doing with organizing things. These tags are mutually exclusive.
Product tags allow me to create lists which are related to one particular product. A product is defined vaguely; it is something we produce, sell, buy or use. The product shortcuts should all be capitals.
Other:
- out : on the road, outside habitat, away from home etc.
- paid: this is a task for which I get paid
Specials, probably temporary in most cases
System tags, which define behaviour of orgmode itself. See also the exclude tag in the publishing and exporting section.
Define a tag which gives orgmode the signal to encrypt the contents of a certain headline
The ‘TODO’ keyword signals something that I myself have to do. It is is either still TO-DO or it has been DONE. If I change my mind, it’s CANCELLED. Other than the CANCELLED keyword, this is pretty much the default sequence. When cancelling I force myself to enter some reason for it.
Since buying stuff is abundant and warrants keeping track of, especially because I’m ordering lots of small things, I have defined a separate workflow for those type of activities. Initially I configure this as the same as doing a normal task, but I plan to introduce a couple of extra feature to this so it can be tracked when delivery will take place, add a tracking number to it in a smart way etc.
A second sequence of states is for tasks that have to be done by others, but still tracked. The initial state for these tasks is WAITING. I have defined a keybinding for (org-todo ‘nextset) which switches the sequences for the entry involved.
The ‘WAITING’ keyword signals a task that other people need to do and that I am waiting for them to complete them. Usually a property with the name ‘Responsible’ and the value of the person who needs to do the task is set. Tasks in the WAITING state are inactive for me, but I still want to produce a convenient list of those tasks so I can track progress on them. All this leads to the following state definitions:
When an item reaches a DONE state, i.e. anything after the vertical bar, we can log this automatically, either by inserting a timestamp, or by requiring to log a note. We use the timestamp.
Given a certain workflow with repeating tasks, tell the system to which state a repeating task must be reset if one of the instances has been completed. In our case just TODO
I often seem to write ‘paragraphs’ which contain reference information to be used a later time. These chapters contain steps to perform or a verbose howto on some systems management thing. They have in common thay I want to be able to look them up by type later on. So, I define some keywords, and give them fitting colors.
Keep track of some reading efforts with a simple sequence
Getting the defaults right for publishing and exporting took some time, save them as defaults and code deviations in the sections to be published.
Define a tag which hides stuff from exported documents
and use it
I have separated the latex (pdf exporting) from the rest because it is much more elaborate and took more time to get right.
The default style of our exported documents will be based on the LaTeX article style.
This option does not seem to work when not in the same file as exporting. I have added this in the customize interface directly now.
Latex default configuration to produce a memo-style document.
Our documents are mostly in dutch, so load that up by default, it’s easy to override this on a subtree or file basis.
Let the babel package handle our language settings automatically. This makes the TOC for example actually say “Inhoudsopgave” and the hyphenation rules be applied for the proper language.
Adjust the title of our documents
Make headers a bit more compact and more pleasing to look at
Make our headers use the HSD purple color
#+COMMENT This looks ok-ish on screen, but not on print
#+COMMENT This looks ok in print, but not so much on screen
Do the same for figure and table captions.
I still like the sans family of computer modern
Use the geometry package to set our left and top margins, the width as last parameter defines the body text rectangle
I want to have a ’page N of M‘-type footer, the lastpage package provides this functionality. One consequence of this is that the amount of TeX passes is minimally 2 to get all the references right.
Use the fancyhdr package to allow the customization of headers in an easy way.
Both header and footer have a horizontal rule along the width of the entire text, thus clearly separating them from the content.
Activate the fancy style, which is roughly a left, middle and right field for both header and footer.
Clear the header and footer first, so we are sure they are empty.
Set the height of the header. The value was deduced by LaTeX itself and suggested in the command line run. The logo, see below, is probably the most limiting element for this.
First, make the @ character a letter, so we can use the @title, @author and @date variables.
The header contains the title of the document on the left for odd pages and on the right for even pages.
The logo is just displayed on odd pages, on the right.
The footer contains page references N of M style and the author information. Here also, the position is alternating with odd and even pages.
Reset the @ character back to what it was
Some spacing corrections to make things look a little bit better. No paragraph indenting as our paragraphs tend to be short. We allow a ragged page bottom (no vertical filling), so the spacing is more relaxing to look at. This is especially an issue when using screenshots or other larger pictures which interrupt the text flow aggressively.
#+COMMENT LATEX_HEADER: \raggedright
For keyboard symbols:
For math:
For outline:
Autolinks which can be entered like keyword:parameter This is mostly here as an example, I don’t think I’ve ever used these in my org files