From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: David Maus <dmaus@ictsoc.de>, emacs-org <emacs-orgmode@gnu.org>
Subject: Re: empty lines in datetree capture templates
Date: Tue, 11 Jan 2011 12:37:34 -0800 [thread overview]
Message-ID: <20110111123734.3a9fd168@bhishma.homelinux.net> (raw)
In-Reply-To: <8E3EE8DE-E8C0-4A2B-AC3E-D60287934E64@gmail.com>
Hi Carsten,
On Tue, 11 Jan 2011 20:58:01 +0100
Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
> On Jan 9, 2011, at 3:31 PM, David Maus wrote:
>
> > At Tue, 28 Dec 2010 00:50:00 -0800,
> > Suvayu Ali wrote:
> >> ("mm" "Meeting minutes w/ clock" entry (file+datetree
> >> "~/org/ meetings.org")
> >> "**** %^{prompt} %U%^{CATEGORY}p\n\n %?"
> >> :prepend t :clock-in :empty-lines 1 :immediate-finish)
>
>
> After clock-in and after :immediate-finish, t is missing - all these
> keys need a value!
> The way you write it, :clock-in has the value :empty lines, and from
> then on the property list is broken.
>
Thank you for catching this, don't know how I missed that.
> If you make the templates with customize, it is much harder to make
> mistakes in a complex variable like this.
>
Yes I agree and I tried that, but customise doesn't handle newlines very
well. I would prefer the newlines show up as \n rather than actual
newlines in my custom-set-variables. I don't mind editing it later to
fix it either. But when I customise some other variable and save,
customize saves it again with newlines instead of keeping my edited
value with \n.
> Best wishes
>
Thanks
> - Carsten
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2011-01-11 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 8:50 empty lines in datetree capture templates Suvayu Ali
2011-01-09 14:31 ` David Maus
2011-01-09 18:05 ` Suvayu Ali
2011-01-11 19:58 ` Carsten Dominik
2011-01-11 20:37 ` Suvayu Ali [this message]
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=20110111123734.3a9fd168@bhishma.homelinux.net \
--to=fatkasuvayu+linux@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=dmaus@ictsoc.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).