emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Josef Wolf <jw@raven.inka.de>
To: emacs-orgmode@gnu.org
Subject: Problems with org-capture
Date: Tue, 6 May 2014 11:57:34 +0200	[thread overview]
Message-ID: <20140506095734.GA5437@raven.inka.de> (raw)

Hello everybody,

I am new to org-mode, and am currently working through
http://members.optusnet.com.au/~charles57/GTD/gtd_workflow.html and am stuck
a little bit the the caprure mode.

My first question is: org-capture seems to come with a pre-confuigured
template for a "Todo" stanza. I thought, I'd take a closer look at this
example to learn from it and as a starting point for my own
customizations. But DESCRIBE-VARIABLE shows that ORG-CAPTURE-TEMPLATES is set
to NIL. So, where does this pre-configured "Todo" entry come from?

The I created my own template like this:

 (setq org-capture-templates
  '(("t" "Todo" entry (file+headline "/m/s/rep/git/todo/newgtd.org" "Tasks")
     "* TODO %^{Brief Description} %^g%?\n   Created: %U\n   %i\n   %A\n\n"
     :kill-buffer :empty-lines 3)))

With this template, I have two problems:

- The most annoying problem is that it eats up the newlines behind the newly
  created entry. I always keep multiple empty lines between top-level
  headings. But even then, a newly created entry eats up all the newlines and
  even melts the succeeding heading onto the end of the newly created entry.
  I guess, this is not how it is meant to work. How would I define 

- The second problem is that when invoked with content fron an active region
  (the %i flag), then the %A flag won't ask me for a link description and the
  %i contents are used as description.

Any ideas what might be wrong here?

-- 
Josef Wolf
jw@raven.inka.de

             reply	other threads:[~2014-05-06 10:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06  9:57 Josef Wolf [this message]
2014-05-09  7:25 ` Problems with org-capture Josef Wolf
2014-05-21  3:07   ` Bastien
2014-05-23 12:39 ` Bastien

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140506095734.GA5437@raven.inka.de \
    --to=jw@raven.inka.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).