From: Carsten Dominik <carsten.dominik@gmail.com>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org, Tom <adatgyujto@gmail.com>
Subject: Re: Putting new to TODO/note to the beginning of the subtree
Date: Wed, 9 Nov 2011 18:38:38 +0100 [thread overview]
Message-ID: <BAA1BF65-7132-4BE6-885F-DF6F989CB646@gmail.com> (raw)
In-Reply-To: <CAMg28Osq_cX31HVNP70WrYMDbi7DsD3fTjZJXsCZxppgHFhiqg@mail.gmail.com>
On 9.11.2011, at 11:15, Tommy Kelly wrote:
> Actually it looks like you can have org-reverse-note-order be a wee
> bit selective using a regexp. Customize implies it's only on a per
> *file* basis but the doc is a bit unclear when it says:
>
> "Non-nil means store new notes at the beginning of a file or entry.
> When nil, new notes will be filed to the end of a file or entry.
> This can also be a list with cons cells of regular expressions that
> are matched against file names, and values."
>
> I'm wondering what, if anything, is the significance of that "and
> values". Seems to suggest you could select based on more than just
> file names.
No, please read this as
This can also be a list with cons cells of regular expressions (that
are matched against file names) and values.
So each cons cell has a regular expression in the car. The
cdr is the value that org-reverse-note-order should have in
files matched by that regular expression.
Anyway, you will be much better off by switching to org-capture
which has more capabilities and fine-grained per-template
control.
HTH
- Carsten
>
> Still, remember seems to be deprecated these days, so capture is
> probably a sensible move.
>
> Tommy
>
prev parent reply other threads:[~2011-11-09 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 9:33 Putting new to TODO/note to the beginning of the subtree Tom
2011-11-09 9:56 ` Tommy Kelly
2011-11-09 10:00 ` Tom
2011-11-09 10:05 ` Tommy Kelly
2011-11-09 10:11 ` Tom
2011-11-09 10:15 ` Tommy Kelly
2011-11-09 17:38 ` Carsten Dominik [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=BAA1BF65-7132-4BE6-885F-DF6F989CB646@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=adatgyujto@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tommy.kelly@verilab.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).