From: Oleh <firstname.lastname@example.org>
To: Dotan Cohen <email@example.com>
Subject: Re: Organizing org-mode files: Tree view
Date: Mon, 28 Apr 2014 18:16:26 +0200 [thread overview]
Message-ID: <CAA01p3oJNLThf0ECdx0W7b0mvd-zFcq9H3LtDJ38Pc6sHXWbjg@mail.gmail.com> (raw)
> If there is a better way to organize the files, then I would love to
> know how the more experienced users do it.
I'm using an extremely simplistic approach: just dump all the org
files into one directory. The name of each org file should be concise
but descriptive, e.g. Makefile.org describes Makefiles, and git.org
This simplicity completely alleviates organization effort: there's
nothing to organize, since there's only one directory to put the files in.
At the same time, it's very accessible by means of two `helm` wrappers:
- globally, "C-0" runs the command helm-org-wiki (the code is below)
- in org-mode, "g" runs the command wspecial-worf-goto (the code is at
It's like a two-stage personal Google: the first stage is to find an org-file,
the second stage is to search within an org-file.
For example, here's the sequence of key bindings when I want to look
up how git bisect works, assuming that I'm in some random buffer, like
C-0 gi RET g bis RET
Done. Note that "gi" was enough to match "git.org", since all my other
pages don't contain "gi". Same thing for "bis" being able to match
uniquely the heading "git bisect". I think that it's quite optimal
that I'm able to find the topic "git bisect" by using only 10 key
presses, which is the same as the amount of characters in "git
bisect". Compare this to `helm-google-suggest` (bound to "C-p g"):
C-p g git bi RET TAB RET
That's 12 key presses (10 in Emacs, 2 in Firefox).
New wiki pages can be created with "C-0" as well, just type in the
name of the new file and hit RET.
That's it, the code is below. It's very similar to `org-switchb`,
except that the files need not be opened to appear in the completion
list, and new files are created if there's no match.
(defgroup helm-org-wiki nil
"Simple jump-to-org-file package."
(defcustom helm-org-wiki-directory "~/org/wiki/"
"Directory where files for `helm-org-wiki' are stored."
(defun helm-org-wiki-files ()
"Return .org files in `helm-org-wiki-directory'."
(let ((default-directory helm-org-wiki-directory))
`((name . "Projects")
(candidates . helm-org-wiki-files)
(action . ,(lambda (x)
(format "%s.org" x)
`((name . "Create org-wiki")
(action . (lambda (x)
(defun helm-org-wiki ()
"Select an org-file to jump to."
next prev parent reply other threads:[~2014-04-28 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 19:39 Organizing org-mode files: Tree view Dotan Cohen
2014-04-27 1:56 ` David Masterson
2014-04-27 2:26 ` Charles Berry
2014-04-28 16:16 ` Oleh [this message]
2014-04-29 11:24 ` Dotan Cohen
2014-04-29 12:13 ` Bastien
2014-04-29 13:36 ` Oleh
2014-04-29 23:11 ` Grant Rettke
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).