From: Bastien <email@example.com>
To: Robert Goldman <firstname.lastname@example.org>
Cc: Org Mode <email@example.com>
Subject: Re: Fix for bug in org-capture
Date: Tue, 16 Apr 2013 09:29:23 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <516C7BE3.email@example.com> (Robert Goldman's message of "Mon, 15 Apr 2013 17:14:59 -0500")
Robert Goldman <firstname.lastname@example.org> writes:
> I tried to make two submenus to my org-capture templates: a prefix key
> "t" (for TODO) and a prefix key "T" (for today's TODO).
> When I tried to use them, the "T" key did not appear and was not accepted.
> Looking more deeply, it appears that it was filtered out by a mistakenly
> case-folding (or at least potentially case-folding) search in org-capture.
I cannot reproduce this.
I have these two captures templates:
("Ir" "Information read" entry (file+headline "~/org/garden.org" "Infos")
"* TODO %?%a :Read:\n :PROPERTIES:\n :CAPTURED: %U\n :END:\n\n%i" :prepend t)
("IR" "Information read (!)" entry (file+headline "~/org/garden.org" "Infos")
"* TODO %?%a :Read:\n :PROPERTIES:\n :CAPTURED: %U\n :END:\n\n%i" :prepend t :immediate-finish t)
They are both recognized well.
Maybe you can try with this minimal example and tell if you can
still reproduce the problem? Also let us know what version of Org
you are using.
> I am attaching a diff which has the two line fix for this bug.
I'll apply it if we can reproduce and narrow down the problem.
next prev parent reply other threads:[~2013-04-16 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 22:14 Fix for bug in org-capture Robert Goldman
2013-04-16 7:29 ` Bastien [this message]
2013-04-16 16:06 ` Robert Goldman
2013-04-16 16:27 ` Bastien
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).