> Uwe Brauer writes:
> It is actually not the culprit. The problem is much simpler.
> You forgot :PROPERTIES: line in your capture template.
> So, what Org sees is
> * Heading
> :ID:
> ...
> :END:
😱 😨
I am very sorry. Thanks for you patience and help!!!
Regards
Uwe
Uwe Brauer writes:
"IR" == Ihor Radchenko writes:
>
>> Uwe Brauer writes:
>>> ("my" "Annu Grupos Ejercicios" entry (file+olp
>>> "~/ALLES/HGs/tex/vorlesungen/HGAnnu/Hojas-Teoria/Soluciones-2024/grupos2024.org"
>>> "Grupos")
>>> "** TODO %^{Grupo} %T %^g %(org-contacts-template-name)
>>>
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> ("my" "Annu Grupos Ejercicios" entry (file+olp
>> "~/ALLES/HGs/tex/vorlesungen/HGAnnu/Hojas-Teoria/Soluciones-2024/grupos2024.org"
>> "Grupos")
>> "** TODO %^{Grupo} %T %^g %(org-contacts-template-name)
>> :ID: %(org-id-new)
>> :Link:
Uwe Brauer writes:
> ("my" "Annu Grupos Ejercicios" entry (file+olp
> "~/ALLES/HGs/tex/vorlesungen/HGAnnu/Hojas-Teoria/Soluciones-2024/grupos2024.org"
> "Grupos")
> "** TODO %^{Grupo} %T %^g %(org-contacts-template-name)
> :ID: %(org-id-new)
> :Link: %a
>
> You can try M-x debug-on-entry org-id-new to trigger
> backtrace when `org-id-new' is called and see what is calling it.
> Then, M-x cancel-debug-on-entry to disable the debugger.
Here are some news:
--8<---cut here---start->8---
(setq org-capture-templat
Uwe Brauer writes:
>> You can try M-x debug-on-entry org-id-new to trigger
>> backtrace when `org-id-new' is called and see what is calling it.
>> Then, M-x cancel-debug-on-entry to disable the debugger.
>
> Here is the result
>
> Debugger entered--entering a function:
> * org-id-new()
> eva
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>>> I recommend changing your capture template to
>>> (file+olp "~/grupos2024.org" "Grupos")
>>
>> That gives an error, as gives file+headline
>> so this part
>>
>> (setq org-capture-templates
>> '(
>> ("m" "Mail options")
>> ("mk" "Annu
Uwe Brauer writes:
>> I tightened the template target location reader to produce less cryptic
>> error in similar cases.
>> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=0a58a53ed
> shall I the pull and reinstall?
You do not have to. My commit will just change the
org-capture-s
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> ("mk" "Annu Grupos Ejercicios" entry (file+olp
>> "~/ALLES/HGs/tex/vorlesungen/HGAnnu/Hojas-Teoria/Soluciones-2024/grupos2024.org")
>> ...
>> Gives the error
>> ...
>> org-capture-set-target-location: Wrong type argument: markerp, nil
Uwe Brauer writes:
> ("mk" "Annu Grupos Ejercicios" entry (file+olp
> "~/ALLES/HGs/tex/vorlesungen/HGAnnu/Hojas-Teoria/Soluciones-2024/grupos2024.org")
> ...
> Gives the error
> ...
> org-capture-set-target-location: Wrong type argument: markerp, nil
I tightened the template target loc
Uwe Brauer writes:
>> I recommend changing your capture template to
>> (file+olp "~/grupos2024.org" "Grupos")
>
> That gives an error, as gives file+headline
> so this part
>
> (setq org-capture-templates
> '(
> ("m" "Mail options")
> ("mk" "Annu Grupos Ejercicios" entry (f
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>>> It might be changed. Currently, we mimic the behavior of
>>> org-yank-subtree, so that we always insert captured entry under the
>>> correct level regardless of the capture target. For example, when you
>>> use OLP, the level will be ad
Uwe Brauer writes:
>> It might be changed. Currently, we mimic the behavior of
>> org-yank-subtree, so that we always insert captured entry under the
>> correct level regardless of the capture target. For example, when you
>> use OLP, the level will be adjusted.
>
>> May you please explain more w
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer via "General discussions about Org-mode."
> writes:
>>> Uwe Brauer writes:
>>
>> Thanks for you answer
>>> This is expected. As per `org-capture-templates' docstring, "entry"
>>> capture type inserts top-level entries into files:
>>
>>> entry
Uwe Brauer via "General discussions about Org-mode."
writes:
>> Uwe Brauer writes:
>
> Thanks for you answer
>> This is expected. As per `org-capture-templates' docstring, "entry"
>> capture type inserts top-level entries into files:
>
>>entry an Org node, with a headline.
> Thanks for you answer
> So that cannot be changed, do I understand correctly.
> Thanks for trying it out, I suspect it is then my setting, I just looked
> up the org-mode-hook
> And I can't find any suspicious. I will try to eyeball my org-add-ons
> files.
> What command/variable could o
> Uwe Brauer writes:
Thanks for you answer
> This is expected. As per `org-capture-templates' docstring, "entry"
> capture type inserts top-level entries into files:
>entry an Org node, with a headline. Will be filed
>as the child of the target
Uwe Brauer writes:
> I have the following setting
>
> (setq org-capture-templates
> ...
> "** TODO ...
>
> and I am facing two problems.
> When I call org-capture and select this template the corresponding buffer
> 1) the corresponding CAPTURE buffer looks like
> ...
> * TODO G13
Hi
I have the following setting
--8<---cut here---start->8---
(setq org-capture-templates
'(
("mk" "Grupos Ejercicios" entry (file "~/grupos2024.org")
"** TODO %^{Grupo} %T %^g %(org-contacts-template-name)
:Link: %a
19 matches
Mail list logo
