Hi Simon,

I have a capture template that does almost exactly that, I just use a user entered subheading -- should be easy enough to tweak for your task.

When chosen as a capture option, it asks for a discussion context and looks up a 2nd level heading below "Discussion Items" matching that context. If it exists, it just adds to it. If not, it creates a new context at the end of the Discussion Items element. Note that you must create "Discussion Items" first, and it must be top-level.

...cj

Capture template:

  ("d" "Discussion Item" item
         (file+function
          "~/org/Todo.org"
          (lambda ()
            (let* ((ctxt (read-string "Discussion context: "))
                   (ctxt-pt
                     (condition-case msg
                         (org-find-olp (list "Discussion Items" ctxt) t)
                       (error nil))))
              (if ctxt-pt
                  (progn
                    (goto-char ctxt-pt)
                    (org-end-of-subtree)
                    (insert-string "\n"))
                (goto-char (org-find-olp (list "Discussion Items") t))
                (org-end-of-subtree)
                (insert-string (format "\n** %s\n" ctxt)))))))


On 8/13/12 12:26 PM, Simon Brown wrote:
Hi all,

Is it possible with org-capture to create a template that would create
the following:

* Log
** 2012 - Week 33
  - One liner of interest
  - Another one liner of interest

So that is a capture template that generates the 2nd level heading when
required and the text entered is converted to a list entry which is
added to the end of the list.

(format-time-string "%G - Week %W") is the correct date string, but
file+headline creates a top level heading and file+olp expects it to
already exist.

It seems that the text entered must also become a sub heading. Is that
correct?

I'm trying to achieve something very similar to this
http://metajack.im/2009/01/01/journaling-with-emacs-orgmode/

Any suggestions greatly appreciated. I haven't managed to strike gold in
the list archive.

Simon


Reply via email to