```
To conclude, my issue is how to solve these problems at the same time.
> [@nobiot](#):
>
> `org-capture-templates` do what you want, but they do not have a useful `${}` (but it is not essential for your use case)
Sadly, it is:
> [@mnb100](#):
>
> Moreover, the additional `${}` syntax is very handy, at least for my use cases.
Mainly for `org-roam-node` properties such as `${title}` – if there is a nice alternative, I am open to suggestions.
> [@nobiot](#):
>
> `org-roam-node-*` functions work if you have an ID (Org-ID) no matter how you add them.
My fault for not being clear enough – but I meant for functions like `org-roam-node-find`, which I know would work if I have an ID like you have said – but sometimes do rely on `org-roam-capture-`. For example, entering a nonexistent node at the prompt of `org-roam-node-find` invokes `org-roam-capture-` – which is a behavior I would like to have (falling back to a capture, just not necessarily `org-roam-capture-`).
This specific functionality is easy to reimplement to work with `org-capture` – but I am not so sure about the other `org-roam-node-*` functions.
> [@nobiot](#):
>
> b. I am not sure if this is a material issue at the moment. If it becomes a material issue, then you can think of a solution then.
Fair enough, that is a good point.
---
### Author:  [@nobiot](https://org-roam.discourse.group/u/nobiot)
#### Post date: [February 24, 2023, 3:42pm UTC](https://org-roam.discourse.group/t/org-capture-template-expansion-properties-prompt-references/2993/8 "2023-02-24T15:42:58Z")
To be honest, I would have thought the following worked, but I trust that you have confirmed it does not.
> [@mnb100](#):
>
> ```auto
> ("d" "default" plain
> ":PROPERTIES:
> :FOO: bar
> :END:
> %?"
> :target (file "%<%Y%m%d%H%M%S>-${slug}.org")
> :unnarrowed t)
>
> ```
I’m away for the weekend without my computer so I cannot test the idea below; I’d create a custom function and add it to org-capture-after-finalize-hook. It’s a simple variation of the solution discussed in the thread you linked above.
The custom function should be something like this below. I am writing it on iPhone so am not checking the function name, parenthesis, or syntax. I hope something like this works
```elisp
(let ((var (read-string “Enter author: “)))
(org-add-property “AUTHOR” var)
;; I assume the point is already in the correct location
;; if not, move point, probably (plont-max) will work
;; if the capture buffer is narrow
(insert var)))
```
---
### Author:  [@mnb100](https://org-roam.discourse.group/u/mnb100)
#### Post date: [February 24, 2023, 4:35pm UTC](https://org-roam.discourse.group/t/org-capture-template-expansion-properties-prompt-references/2993/9 "2023-02-24T16:35:45Z")
I don’t fully understand how this approach would solve the second problem (referencing the prompt in the template):
> [@mnb100](#):
>
> ```auto
> ("d" "default" plain
> "This is a note about %\\1
> %?"
> :target (file+head "%<%Y%m%d%H%M%S>-${slug}.org"
> ":PROPERTIES:
> :FOO: %^{foo prompt}
> :END:
> ")
> :unnarrowed t)
>
> ```
But I guess I need to compromise and enter the same input for multiple prompts (discard the usage of prompt references altogether).
I thought there might be a solution which is less risky than what you have suggested [here](https://org-roam.discourse.group/t/how-to-prevent-org-roam-capture-from-adding-id-property/2669/6).
> [@nobiot](#):
>
> I’d create a custom function and add it to org-capture-after-finalize-hook.
> [@nobiot](#):
>
> `; if not, move point,`
I think finding the correct point would be rather difficult and unintuitive in the general case (as the references can occur at arbitrary places in the template).
---
### Author:  [@nobiot](https://org-roam.discourse.group/u/nobiot)
#### Post date: [February 24, 2023, 5:29pm UTC](https://org-roam.discourse.group/t/org-capture-template-expansion-properties-prompt-references/2993/10 "2023-02-24T17:29:35Z")
> [@mnb100](#):
>
> I thought there might be a solution which is less risky than what you have suggested [here](https://org-roam.discourse.group/t/how-to-prevent-org-roam-capture-from-adding-id-property/2669/6).
Maybe. I don’t have the same level of understanding of the “risk” as yours, so I can’t really comment.
> [@mnb100](#):
>
> I don’t fully understand how this approach would solve the second problem (referencing the prompt in the template):
This example does not. I would put the whole node-capture/node-find function in a let form (and create a custom command). Then, I believe, you can evaluate the let-bound-variable in the template and place it anywhere in the template (?) This way you only would need a prompt once.
---
### Author:  [@mnb100](https://org-roam.discourse.group/u/mnb100)
#### Post date: [February 24, 2023, 10:05pm UTC](https://org-roam.discourse.group/t/org-capture-template-expansion-properties-prompt-references/2993/11 "2023-02-24T22:05:15Z")
> [@nobiot](#):
>
> I don’t have the same level of understanding of the “risk” as yours, so I can’t really comment.
In this case, I cannot be sure that someday the code of `org-roam-capture.el` or its dependencies would depend on the ID property to be present at capture time, just as it is now.
I can advise functions to return the ID of the node instead ([like you have done](https://github.com/nobiot/md-roam/blob/9ccd8fee00ebea28dfdc1f6d6ffe3d312973ceb7/md-roam.el#L209)), but I cannot prevent all possible methods of retrieving this property (and advise them accordingly), because there are a lot of ways.
My (irrational?) fear of advices stems from the fact it’s always another place to look when a bug is found – as I change internal logic. That is why I try to the best of my ability to not use advices or private (double-dashed `--`) symbols.
I would like to hear your take about it, though – as I’ve seen a lot of people and package authors in particular advising functions. How can you ensure it won’t be a [cat-and-mouse game](https://en.wikipedia.org/wiki/Cat_and_mouse)?
> [@nobiot](#):
>
> This example does not. I would put the whole node-capture/node-find function in a let form (and create a custom command). Then, I believe, you can evaluate the let-bound-variable in the template and place it anywhere in the template (?) This way you only would need a prompt once.
Interesting. I need to think a little about how to implement it – as I don’t think it’s very intuitive (the capture template depend on the let-bound-variables which are created based on the template itself – a somewhat circular behavior).
Also, it would change the capture template to have implementation details (the calls for the evaluation of the let-bound-variables instead of the “normal” way of referencing prompts) – not a dealbreaker by any means, but still worth noting.
---
### Author:  [@nobiot](https://org-roam.discourse.group/u/nobiot)
#### Post date: [February 27, 2023, 8:48pm UTC](https://org-roam.discourse.group/t/org-capture-template-expansion-properties-prompt-references/2993/12 "2023-02-27T20:48:17Z")
I see there are a couple of different topics; let me unpick them.
#### Custom function with let-bound-variables for `org-roam-capture`
> [@mnb100](#):
>
> (the capture template depend on the let-bound-variables which are created based on the template itself – a somewhat circular behavior).
> [@mnb100](#):
>
> Also, it would change the capture template to have implementation details (the calls for the evaluation of the let-bound-variables instead of the “normal” way of referencing prompts)
I think the implementation below avoids the “circular behavior” and prompts for a property. It works on my end.
I tried to implement something different with a let-bound-variable, I failed. I needed to define the variable anyway with `defvar`, so perhaps my original idea was not possible syntactically.
```emacs-lisp
(add-to-list 'org-roam-capture-templates
'("s" "special" plain ""
:target
(file+head "./${id}.org" "
#+title: ${title}
#+author: %(read-string \"Author: \")
#+id: ${id}
")))
```
#### The code `org-roam-capture.el` may change someday
> [@mnb100](#):
>
> In this case, I cannot be sure that someday the code of `org-roam-capture.el` or its dependencies would depend on the ID property to be present at capture time, just as it is now.
In general, I would agree. For the case of `org-roam-capture`, however, I personally do not worry about this because `org-roam` is in maintenance since the end of 2021. See this [blog article](https://blog.jethro.dev/posts/org_roam_2021/) from Jethro, Org-roam’s author. The API and internals have been stable since then.
`org-roam-capture` also relies on `org-capture`, which is more actively developed but with backward compatibility carefully considered.
#### Use of advice in general and in `md-roam`
> [@mnb100](#):
>
> My (irrational?) fear of advices stems from the fact it’s always another place to look when a bug is found – as I change internal logic. That is why I try to the best of my ability to not use advices or private (double-dashed `--`) symbols.
>
> I would like to hear your take about it, though – as I’ve seen a lot of people and package authors in particular advising functions.
I don’t think it’s irrational. I would avoid advising for the same reason you mention: “as I change internal logic”.
In the particular case of `md-roam`, the concern for this risk might be exaggerated. If we follow this definition:
```auto
(R)isk = (P)robability × (M)agnitude
```
I consider P and M are very small, and thus R negligible (for me).
For P, Md-roam is advising functions from stable Org-roam, as noted in the previous point above, the probability of a major change is low.
For M, `md-roam` is my “personal config” shared via GitHub. It’s not distributed more widely; not available in MELPA and ELPA. Should advised functions change, I should not have to worry about much of the impact. In the end, I can just create notes in markdown without using `md-roam` until I have some time to fix the problem (which should be very infrequent anyway).
---
### Author:  [@nobiot](https://org-roam.discourse.group/u/nobiot)
#### Post date: [February 28, 2023, 7:36am UTC](https://org-roam.discourse.group/t/org-capture-template-expansion-properties-prompt-references/2993/13 "2023-02-28T07:36:30Z")
> [@nobiot](#):
>
> I think the implementation below avoids the “circular behavior” and prompts for a property. It works on my end.
>
> I tried to implement something different with a let-bound-variable, I failed. I needed to define the variable anyway with `defvar`, so perhaps my original idea was not possible syntactically.
>
> ```auto
> (add-to-list 'org-roam-capture-templates
> '("s" "special" plain ""
> :target
> (file+head "./${id}.org" "
> #+title: ${title}
> #+author: %(read-string \"Author: \")
> #+id: ${id}
>
> ")))
>
> ```
Please disregard this. I keep forgetting about your “template” requirement.
This below works on my end.
I am not really concerned with the “circular behavior” or that the “capture template to have implementation details (the calls for the evaluation of the let-bound-variables instead of the “normal” way of referencing prompts)”.
An inner scope can work with variables in the outer scope. In this case, it’s only me using this let-binding, and can guarantee that it works for me and I don’t need to worry about usage by others.
```emacs-lisp
(defvar var "")
(setq org-roam-capture-templates
'(("s" "special" plain ""
:target
(file+head "./${id}.org" "
#+title: ${title}
#+author: %(identity var)
#+id: ${id}
This is a template %(identity var)
"))))
(let ((var (read-string "Author: ")))
(org-roam-capture nil "s"))
```
---
### Author:  [@lyndhurst](https://org-roam.discourse.group/u/lyndhurst)
#### Post date: [April 24, 2024, 12:37pm UTC](https://org-roam.discourse.group/t/org-capture-template-expansion-properties-prompt-references/2993/14 "2024-04-24T12:37:22Z")
Hi, I am sorry if my question is dumb, but I am new to (doom) emacs, and I kind of struggle with elisp to be frank.
This snippet seems to do exactly what I am looking for, but if I copy it to my config, what I understand is a variable binding method `let` at the end of the code gets executed on startup prompting me for the variable’s value.
Can someone please show me how to modify the code so I can re-use it ?
Thanks for your time.
PS: I am also aware of the guidelines, and this reply is obviously an ask for help, and does not improve the conversation but I thought starting a new thread to reference this one was overkill and who knows it can help some other beginner like me in the future.
EDIT: Question moved to [this thread](https://org-roam.discourse.group/t/org-roam-templates-reuse-prompted-values-within-a-template/3443).
---
### Author:  [@nobiot](https://org-roam.discourse.group/u/nobiot)
#### Post date: [April 24, 2024, 12:47pm UTC](https://org-roam.discourse.group/t/org-capture-template-expansion-properties-prompt-references/2993/15 "2024-04-24T12:47:29Z")
It is not an overkill to create a new thread. I do not remember the context (I am assuming you are referring to the code snippet I gave above??).
It would be great to summarize the issue, what you wish to achieve, and reference the snippet.
> [@lyndhurst](#):
>
> This snippet seems to do exactly what I am looking for, but if I copy it to my config, what I understand is a variable binding method `let` at the end of the code gets executed on startup prompting me for the variable’s value.
I can’t be certain what “this snippet” exactly is even — I am sorry, but it appears to be too old a thread for my memory (I respond to many of the questions here, so I don’t remember them).