emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gustavo Barros <gtvbrs@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Force creation of org id in template
Date: Mon, 26 Oct 2020 19:40:08 -0300	[thread overview]
Message-ID: <87sga0lign.fsf@gmail.com> (raw)
In-Reply-To: <87lffswu33.fsf@web.de> (Michael Heerdegen's message of "Mon, 26 Oct 2020 22:33:36 +0100")

On Mon, 26 Oct 2020 at 22:33, Michael Heerdegen <michael_heerdegen@web.de> wrote:

> I'm not sure.  I see that creating an id involves slightly more than
> adding the property - see the `org-id-add-location' call in
> `org-id-get'.  Calling the higher level `org-id-get' or the like in a
> %() spec in a template fails however, since when it's called a temp
> buffer not associated with a file is current.
> And then I'm also not sure if the above is always secure when something
> else in the template spec wants to add a (different) property.  Do you
> know?

Not really.  `org-id' usually "just works" for me, so I never had to dig
anything deeper there.  But, as far as I recall, this is meant to add
the new ID on the IDs file.  Considering your capture template is likely
to be on your agenda files, this is probably not going to be of
concern (meaning here these files will eventually be scanned and the ID
found).  But, if it is, you could then go with `%(org-id-get nil t)`,
right?  It does seem to be more appropriate either way, I agree.

I have stored here in my init file a message from the list describing
the procedure Org uses to try to find an ID, you might find it useful:

Regarding the second issue, of course, you should end up with a single
properties drawer, and the template should ensure that.


  reply	other threads:[~2020-10-26 22:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 18:26 Michael Heerdegen
2020-10-26 19:24 ` gusbrs.2016
2020-10-26 21:33   ` Michael Heerdegen
2020-10-26 22:40     ` Gustavo Barros [this message]
2020-10-26 23:30       ` Gustavo Barros
2020-10-27  6:12         ` Colin Baxter

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:

  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=87sga0lign.fsf@gmail.com \
    --to=gtvbrs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael_heerdegen@web.de \
    --subject='Re: Force creation of org id in template' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).