For my good (and yours), here's a list of things that I think I should know how to do in emacs, but somehow don't:

• Use the version control package so that I'm not constantly popping between bash (terminal) and emacs to talk to git, and I don't think that's necessary.
• Batch renaming with Dired. It should work, it should be simple, I've just not gotten there.
• File specific org-mode settings, for properties, tags, and TODO keywords. I understand that it's possible, but my brain/system doesn't have room for that yet.

I mentioned the other day that I was looking to build a fact file, but that I wanted to follow up on this in a bit more length. As you know and/or have probably guessed, I'm a writer, and I consume a lot of information in the pursuit of this practice. That's par for the course. The problem is figuring out a way to store collected information so that it's useful later. Here's a story:

I have a story that imagines a future where there are colonies and outposts throughout our solar system (among other things). I found myself a few days ago plotting out some details and I realized that I might be imagining a future with not only far flug outposts but also a substantially different system of orbital mechanics. I know about Hohmann transfers and enough about gravity assists, that getting between planets in the solar system is complex. My hope is that by knowing a bit about these things, I can avoid rank absurdity. In any case, I found myself looking up the length orbits of Jupiter and Saturn around the sun.

Now mostly this was just to get a sense of the distance, because unless I also posit free, lightweight, super-powerful propulsion systems, a trip between Jupiter and Saturn is going to take a number of years (say, 5-15; and even with posted amazing-drive, we're probably still talking several years,) and no matter how fast/what kind of propulsion system you use, there are going to be a very limited "windows" for transport. If you miss the buss from Jupiter to Saturn, it could be 10 or 20 years before you could get off world. Not to mention the huge impact this would have on the course of cultural development on these colonies.

But having said that, this detail about the orbital lengths (though burned into my memory at this point), isn't the kind of thing that I track very well, and what about the next time I have a question like this? Or what about a news story that I come across, or the abstract of a scientific paper that catches my interest? This detail about orbits of the outer planets was really just the straw that broke the camels back.

It was clear that I needed a system for storing information, facts, notes for later retrieval. I wasn't sure what that system would look like, or what I would need from it, but I was sure that something was better than the "read and hope" method I've been using.

I did some brainstorming and came up with some basic requirements. I needed something pretty unstructured so that "records," which were just links and a few words would be just as complete as records that had lengthy notes. I needed built in meta-data functionality to store categories, tags, and citation information (links, date, identifiers). Easy capture and editing is a must, and while I was, and am, willing to consider functionality outside of emacs, but emacs is preferred, and it would take a lot for me to want something that couldn't be stored in plain text files.

When other people (individuals) come to me with similar problems I almost always recommend private instances of Wordpress where people can post notes. This often is just the right thing. Conceptually it works like a notebook or journal in the physical world, but it has good meta-data support (categories, tags, dates), you can use it from anywhere (the web, the API), and it's a mature system. This works great for a lot of people, but I'm not incredibly happy with the web-interface, and I'd need to rely on search more than I think I'd like.

I put out a call on identi.ca for help on this problem. There were suggestions of PlannerMode and various systems based on org-mode (which is what I'm inclined to use at this point.) I then had this "moment" issue about not wanting my "fact file" to be built on some sort of to-do list. Todo lists are great, I love todo-lists (perhaps too much?) Having my information management software be built around "tasks" and "projects" provides too much of the wrong kind of structure.

I was frustrated, as you might imagine. After all I just wanted some sort of index-able note-card system, that I could use to store some basic information without fuss. I've settled down a bit and I'm using a format using a skeleton/org-remember template to store my fact file in an org-mode text file (data.org). The entries look something like this:

* The title                    :a:list:of:tags:
  :PROPERTIES:
  :date: <2009-03-14 Sat>
  :cite-key: a-u/uid
  :link: http://tychoish.com
  :END:

And then finally some notes text

And the input is just an prompt-tab interface. I can also add more details to the properties, section. If that makes sense at a later date. So the creation of these records is pretty quick. I'll get come code up when I have something a bit more clear. In the mean time, I'd like to continue to have a bit of a discussion about this information management problem. It's a domain that is clearly very suited to technological enhancement, but at the same time there aren't a lot of solutions on the ground. I suppose that's where I come in, but feedback is most appreciated on interface questions, on alternate use cases and applications. I look forward to hearing from you...

I promised that I'd post some of the stuff from my .emacs file that makes my org-mode system work. Here we are.

There are some basic settings that I use on all major modes that I use in emacs. Basically, I want to attach the spell checker (the minor modes, flyspell-mode and auto-fill-mode). These lines do this:

(add-hook 'org-mode-hook 'turn-on-auto-fill)
(add-hook 'org-mode-hook 'flyspell-mode)

I also, attached ".org" as the file extension to org-mode. This setting is good for this kind of thing:

(setq auto-mode-alist
(cons '("\\.org" . org-mode)auto-mode-alist))

The following are a list of basic org-mode related settings that I've found helpful. In some sequence, I keep org-mode files in the ~/org/ directory, with codex.org being my general catch-all file. I like my agenda views to include todos, even if they're not date-specific (this is a great boon) I've included the diary in the agenda views for grins, though I'm not yet smart enough to really make the most of that one.

The odd-levels-only, and hide-leading-stars are aesthetic settings only, and can be changed/converted from at any point, but I like them

The org-todo-keywords setting allows you to specify alternate todo-statuses. I've found that this sorting is a useful and allows me to visually sort out things I need to write, versus chores and other more clerical tasks. The pipe seperates finished statuses from open statuses. I debated for a long time about weather "differed" should be "done" or "not done," but decided that with "pending," I was safe to use "differed" tasks for "not my problem any more" items.

(setq org-directory "~/org/")
(setq org-default-notes-file (concat org-directory "/codex.org"))
(setq org-agenda-include-all-todo t)
(setq org-agenda-include-diary t)
(setq org-hide-leading-stars t)
(setq org-odd-levels-only t)
(setq org-todo-keywords
      '((sequence "TODO"
                  "WRITE"
                  "REVIEW"
                  "PENDING" "|"
                  "DIFFERED"
                  "DELEGATED"
                  "DONE")))

The next bit, is something that I got from Jack. It creates an org-mode file with time-stamp headlines which you can use to create a journal file to record daily activities.

The first block sets up which file the journal should be in, and the second sets up entry. My main complaint with this is that I'm not very habitual about using it.

(defvar org-journal-file "~/org/journal.org"
   "Path to OrgMode journal file.")
(defvar org-journal-date-format "%Y-%m-%d"
   "Date format string for journal headings.")

(defun org-journal-entry ()
  "Create a new diary entry for today or append to an existing one."
  (interactive)
  (switch-to-buffer (find-file org-journal-file))
  (widen)
  (let ((today (format-time-string org-journal-date-format)))
    (beginning-of-buffer)
    (unless (org-goto-local-search-headings today nil t)
      ((lambda ()
         (org-insert-heading)
         (insert today)
         (insert "\n\n  \n"))))
    (beginning-of-buffer)
    (org-show-entry)
    (org-narrow-to-subtree)
    (end-of-buffer)
    (backward-char 2)
    (unless (= (current-column) 2)
      (insert "\n\n  "))))

The integration between remember-mode functionality and org-mode is one of those things that just makes org-mode amazing and awe inspiring. The sad part is that it takes some setup to make it work right and therefore doesn't work straight out of the hook.

I'd explain the template syntax better if I understood it a bit better. I should look into that.

(require 'remember)
(setq remember-annotation-functions '(org-remember-annotation))
(setq remember-handler-functions '(org-remember-handler))
(add-hook 'remember-mode-hook 'org-remember-apply-template)

(setq org-remember-templates
      '(("todo" ?t "* TODO %?\n  %i\n  %a" "~/org/codex.org" "Tasks")
        ("notes" ?n "* %?\n  %i\n  %a" "~/org/codex.org" "Inbox and Notes")
        ("blog" ?b "* %U %?\n\n  %i\n  %a" "~/org/blog.org")
        ("technology" ?s "* %U %?\n\n  %i\n  %a" "~/org/technology.org")
        ("fiction" ?f "* %U %?\n\n  %i\n  %a" "~/org/fiction.org"))

Finally, key bindings that make org-mode functionality accessible whenever I need it in emacs. I should do things to have raise emacsclient windows from other applications, but I'll deal with that later. There aren't that many, and I put org-mode stuff under control-c (C-c).

(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cr" 'org-remember)
(global-set-key "\C-cj" 'org-journal-entry)

And that's it. If you use org-mode, what's the killer snippet that I've forgotten? If you don't use org-mode but are curious, what should I talk about next. If you're still not clear what org-mode is, ask, as I should work on getting better at explaining.

Thanks for reading. Cheers!

The last time I talked about org-mode, I covered a number of my "beginner mistakes,", this time I think it'd be a bit more productive to explain how I'm actually using org-mode. For those of you playing at home this is one of those systems I talked about.

I'm going to try and avoid including bits of code/lisp in this post, as I don't want to confuse "what I'm doing," with "how I'm doing it." We'll get to that point in time, and there's plenty to talk about.

At the moment the features of org-mode that I use the most are:

• org-agenda-mode
• checkboxes
• org-remember-mode
• and org-mode outlines

I also store org-mode files in a git repository that lives in my home folder of all machines that I use with any regularity. I'm running emacs-23 (ubuntu package: emacs-snapshot), generally in server-mode, with two frames open, one has "the thing I'm writing" and the other has the org-mode-agenda and some org-mode file in the other window. [1]

It takes me a while to adapt to new things with the computer. While I pick things up pretty quickly, I'm aware that it takes a while for me to adapt to new ways of working with the computer. I like to settle into a system before I start changing the key bindings or writing scripts (which I always think will be more successful than they are). This seems reasonable, and is generally something that I'd recommend to other people looking to learn "cool new stuff." Go slow.

In light of this realization this post will be a review of some of my more recent adventures with org-mode. For the uninitiated, org-mode is really a subsystem of the emacs text editor. [1] It's really powerful, and has a lot of disparate features that combine to do something really kind of magical. On one level, org-mode is just an outlining program: it provides some shortcuts and interfaces that make writing structured text really productive and pleasurable (e.g. easy navigation, block folding). On another level, org-mode is a fully featured calendaring and task/project management tool. The brilliance, is that it isn't just and outliner or a task manager, but it provides accessory tools (like a great calendar, and even a table/spreadsheet functionality) that integrate the environment.

I found about this two months ago, and I've slowly started to ease into using it. This past week, however, I think I crossed some sort of boundary, because I started using org-mode for most of my note-taking and project planning/organization work. And now that I'm here, I think a small series of blog posts is in order.

I'll start, I think with "mistakes I made," as I couldn't hope to explain everything the system does, and explaining how I'm working right now isn't nearly as interesting.

My first approach was to keep an org-mode file in all of my project directories, so that the .org file would be close to the files where the actual work was going on.

Wrong.

Turns out, keeping all your org-mode files together seems to work a lot better. Org's calendar/project planning features work by generating "agenda views" of todo items and time-specified events. While the system could pull from a half dozen different project directories. Keeping things centralized means that you can add new files willy-nilly, it makes it easy to keep things synchronized between machines.

My second approach was to keep one org-mode file and divide projects using the hierarchical nature of the file to keep things straight.

Wrong.

Turns out, that while we can represent all of our projects hierarchically [2] beyond a certain level it doesn't make a lot of sense to implement "categories" or project headings in this way. Org-mode provides a tagging infrastructure and the aforementioned agenda tool to tie together files, so while you can go overboard in creating new org files, you're probably not incredibly likely to for a while. Use outline hierarchies to represent information, use files and tags to categorize and sort your headlines.

When I discovered the agenda capabilities, I made todo items out everything and started giving all of my tasks dates so that they'd be sorted into the agenda view.

Wrong.

Turns out, you can get agenda to generate a list of undated todo items before the agenda view, and that--at least for the way I work--setting soft deadlines and scheduling tasks just confuses the point rather than facilitating action. Org-mode also has a system for task priorities--which I haven't felt the need for--but I think the larger lesson here is don't attach arbitrary information to items in your org-mode files. Let the agenda mode do it's work, and you do yours, and it'll work out.

I started my ~/org/ directory [3] by creating .org files for all of the major projects in my life. Fiction writing, day-job, the blog, academic work, so that I'd be able to collect similar kinds of notes and todo-lists together in files.

Wrong.

Turns out, that while some of the setting up big sphere-based org-mode files is unavoidable, the truth is that given the power of the agenda filter, putting a lot of information that is only casually connected in the same file doesn't make much sense when tagging can provide needed meta-data. There's a happy medium between "dividing things too much to the point where there's too much 'system' to manage," and "not dividing enough so that you have to build informal systems in the outline which complicates the organization." In my experience "too much division" is much harder to reach, and "not dividing enough," is quite easy.

I'll be blogging more about org-mode in the coming days and weeks. Stay tuned :)

Onward and Upward!

[1]

There's this joke about emacs, that "it's a good operating system, but it lacks a good text editor." I think the truth is that, emacs is an ok (but not exceptional) text editor, but it opens so many other possibilities for interacting with text in amazingly productive ways, that it's managed to garner the loyalty of people like me.

[2]	I'm not positive of this, but emacs itself might owe it's existence to this kind of work, as it's built around an lisp interpreter, which is a language used by AI researchers in the 60s because it could reflect the way we think. Or so the theory goes.

[3]

Really, it's not a directory, as much as it is a git repository. And this is I think this is a point where text-file geeks will say oh! dude! that's cool, because really org-mode provides interfaces to parse together text files, which you can: take everywhere, version and sore easily, save forever, and hell branch if you need to. A calendar. Dude!