>>> "IR" == Ihor Radchenko <yanta...@posteo.net> writes:
> Uwe Brauer <o...@mat.ucm.es> 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 why you need to use level 2 heading
>>> specifically?
>>
>> Sure. I use this template for extracting from emails sent by my students
>> their names and email addresses to have entries like this
>> --8<---------------cut here---------------start------------->8---
>> * Grupos :noexport:
>> ...
>> ** !!TODO!! G1 <2023-01-24 12:51> :Annu24: Paul New
>> ...
>> #+TBLNAME: sheets
>> #+BEGIN: columnview :maxlevel 2...
>> ...
>> That however only works if the entries have level **
>>
>> It my workflow now clearer?
> Yup.
> 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 (file+olp
"~/ALLES/HGs/tex/vorlesungen/HGAnnu/Hojas-Teoria/Soluciones-2024/grupos2024.org")
"** TODO %^{Grupo} %T %^g %(org-contacts-template-name)
:ID: %(org-id-new)
:Link: %a
:Email: %(org-contacts-template-email)
:Grp: %^{Gr1|Gr2|Gr3|Gr4|Gr6|Gr7|Gr8|Gr9|Gr10|Gr11|Gr12|Gr13}
:Usuario1: %:fromname
:Email1: %:fromaddress
:Usuario2: %(my-extract-cc)
:Email2: %(my-extract-cc)
:Usuario3: %(my-extract-cc)
:Email3: %(my-extract-cc)
:Usuario4: %(my-extract-cc)
:Email4: %(my-extract-cc)
:Status: [ ]
:Hoja:
:Ej:
:End:")))
Gives the error
Deprecated date/weektree capture templates changed to ‘file+olp+datetree’.
org-capture-set-target-location: Wrong type argument: markerp, nil
Updating buffer list...done
>>> What command/variable could org-mode force to have always an UUID in the
>>> ID property?
>>
>>> `org-id-method' I think.
>>
>> This variable sets the format, but as far as I can see, is not
>> reasonable for adding an ID.
> Do you mean that you want IDs to be always added any time your create a
> heading? If so, the common method is to add `org-insert-heading-hook'.
That hook is empty, nevertheless and ID with an annoying END is inserted
in the middle of the template
> However, this hook will not work for templates. You may add
> :ID: %(org-id-new)
> to your template to generate an ID.
I will try that.
Thanks
--
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military.
I support the EU and NATO membership of Ukraine.
smime.p7s
Description: S/MIME cryptographic signature
