More posts about: emacs, kaizen, org Tags: description, exploration // 21 Comments »
Let me think about how I organize my Org Mode files, and how I might improve that. =)
You can put different things in different files, of course. I use a few large Org files instead of lots of small ones because I prefer searching within files rather than searching within directories. Separate files make sense when I want to define
org-custom-agenda-commands that summarize a subset of my tasks. No sense in going through all my files if I only want the cooking-related ones.
What would help me make better use of lots of files? I can practise on my book notes, which I’ve split up into one file per book. It’s easy enough to open files based on their titles (which I put in my filenames). But I don’t have that overall sense of it yet. Maybe
#+INDEX: entries, if I can get them to generate multiple hyperlinks and I have a shortcut to quickly grep across multiple files (maybe with a few lines of context)? Maybe a manual outline, an index like the one I’ve been building for my blog posts? I can work with that as a starter, I think.
Okay. So, coming at it from several directions here:
- A manual map based on an outline with lots of links, with some links between topics as well – similar to my blog outline or to my evil plans document
- Quick way to grep?
helm-do-grepworks, but my long filenames are hard to read.
- Links between notes and to blog posts
- TODOs, agenda views
Within each file, outlines work really well. You can create any number of headings by using
*, and you can use
TAB to collapse or expand headings. You can promote or demote subtrees, move them around, or even sort them.
I generally have a few high-level headings, like this:
* Projects ** One heading per current project *** TODO Project task * Reference Information I need to keep track of * Other notes * Tasks ** TODO Lots of miscellaneous tasks go here ** TODO Lots of miscellaneous tasks go here ** TODO Lots of miscellaneous tasks go here
Every so often, I do some clean-up on my Org files, refiling or archiving headings as needed. This makes it easier to review my current list of projects. I keep this list separate from the grab-bag of miscellaneous tasks and notes that might not yet be related to particular projects.
org-refile with the
C-u argument (so,
C-u C-c C-w) to quickly jump to headings by typing in part of them. To make it easy to jump to the main headings in any of my agenda files, I set my
org-refile-targets like this:
(setq org-refile-targets '((org-agenda-files . (:maxlevel . 6))))
How can I get better at organizing things with outlines? My writing workflow is a natural place to practise. I’ve accumulated lots of small ideas in my writing file, so if I work on fleshing those out even when I don’t have a lot of energy–breaking things down into points, and organizing several notes into larger chunks–that should help me become more used to outlines.
In addition to organizing notes in outlines, you can also use tags. Tags go on the ends of headings, like this:
** Heading title :tag:another-tag:
You can filter headings by tags using
M-x org-match-sparse-tree (
C-c \) or
M-x org-tags-view (
C-c a m).
Tags are interesting as a way to search for or filter out combinations. I used tags a lot more before, when I was using them for GTD contexts. I don’t use them as much now, although I’ve started tagging recipes by main ingredient and cooking method. (Hmm, maybe I should try visualizing things as a table…) I also use tags to post entries under WordPress blog categories.
How can I get better at using tags? I can look for things that don’t lend themselves well to outlines, but have several dimensions that I may want to browse or search by. That’s probably going to be recipe management for now. If I figure out a neat way to add tags to my datetree journal notes and then visualize them, that might be cool too.
Org Mode links allow me to refer not only to web pages, files, headings, and text searches, but to things like documentation or even executable code. When I find myself jumping between places a lot, I tend to build links so that I don’t have to remember what to jump to. My evil plans Org Mode file uses links to create and visualize structure, so that’s pretty cool, too. But there’s still a lot more that I could probably do with this.
How can I use links more effectively? I can link to more types of things, such as Lisp code. I can go back over my book notes and fill in the citation graph out of curiosity. Come to think of it, I could do that with my writing as well. My writing ideas rarely fit in neat outlines. I often feel like I’m combining multiple threads, and links could help me see those connections.
In addition to explicit links, I can also define “radio targets” that turn any instance of that text into a hyperlink back to that location. Only seems to work within a single file, though, and I’ve never actually used this feature for something yet.
You can set various properties for your Org Mode subtrees and then display those properties in columns or filter your subtrees by those properties. I’ve used
Effort to keep track of effort estimates and I have some agenda commands that use that. I also use a custom
Quantified property to make it easier to clock into tasks using my Quantified Awesome system.
I could track energy level as either tags or properties. Properties allow for easier sorting, I think. Can I define a custom sort order, or do I have to stick with numeric codes? Yeah, I can sort by a custom function, so I can come up with my own thing. Okay. That suggests a way I can learn to use properties more effectively.
There are even more ways to organize Org Mode notes in Emacs (agenda views, exports, etc.), but the ones above look like good things to focus on. So much to try and learn!