From: Manuel Koell <man.koell@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: capture append entries, not prepend
Date: Sat, 25 Jul 2015 20:02:48 +0200 [thread overview]
Message-ID: <CAAAbm0qRVJEJN0PEAiYx-=GjbfGcpL+r+UHuj3Sh=0fzL3Z0bg@mail.gmail.com> (raw)
In-Reply-To: <87io98mgef.fsf@pierrot.dokosmarshall.org>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
Thank you, Nick. I didn't know this is a feature. It is usual for me to go
from top to bottom. So the only way to accomplish this order would be to
use file+headline or file+olp?
2015-07-25 17:00 GMT+02:00 Nick Dokos <ndokos@gmail.com>:
> Manuel Koell <man.koell@gmail.com> writes:
>
> > I've a capture template like this:
> >
> > '(org-capture-templates
> > (quote
> > (("j" "Journal" plain
> > (file+datetree "~/org/journal.org")
> > "**** %?" :unnarrowed t)...
> >
> > Current behaviour:
> >
> > * 2015
> > ** 2015-07 July
> > *** 2015-07-24 Friday
> > **** 3rd entry bla bla bla
> > **** 2nd entry foo bar
> > **** 1st entry test
> >
> > Expected behaviour:
> >
> > * 2015
> > ** 2015-07 July
> > *** 2015-07-24 Friday
> > **** 1st entry test
> > **** 2nd entry foo bar
> > **** 3rd entry bla bla bla
> >
> > I didn't set the 'prepend' key and also tried to set
> 'org-reverse-notes-order' to always.
> >
>
> I don't think you can do what you want: datetrees are always in the
> first form. They don't obey :prepend or reverse notes order.
>
> Not that it cannot be done, but the design has to be changed: "it's not
> a bug, it's a feature".
>
> --
> Nick
>
>
>
[-- Attachment #2: Type: text/html, Size: 2049 bytes --]
prev parent reply other threads:[~2015-07-25 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 9:01 capture append entries, not prepend Manuel Koell
2015-07-25 15:00 ` Nick Dokos
2015-07-25 18:02 ` Manuel Koell [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='CAAAbm0qRVJEJN0PEAiYx-=GjbfGcpL+r+UHuj3Sh=0fzL3Z0bg@mail.gmail.com' \
--to=man.koell@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/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).