> Uwe Brauer <oub@mat.ucm.es> writes:

> Thanks!


> To clarify, when you have

> * Heading

> #+begin_comment
> * Lorem ipsum
> #+end_comment


> it is not seen by Org as comment block.
> Instead, what Org "sees" is

> <begin heading 1>
> * Heading

> <begin paragraph>

> #+begin_comment
> <end paragraph>
> <end heading 1>
> <begin heading 2>
> * Lorem ipsum

> <begin paragraph>
> #+end_comment

> <end paragraph>
> <end heading 2>

> Headline markup has the top priority all the times.
I am confused

I have 
*** DONE Books
    :PROPERTIES:
    :Nr:       1
    :Comp1:    [X]
    :Comp2:    [X]
    :END:


Now with our patch I mark the headings and its properties and then insert a comment block, so I obtain 

#+begin_src 

,*** DONE Books
    :PROPERTIES:
    :Nr:       1
    :Comp1:    [X]
    :Comp2:    [X]
    :END:
#+end_src

Which is what I was looking for!


> Yup. Probably, we can make org-insert-structure-template more smart and
> remove the block when user selects the same block as the existing one.
> It should be controlled by defcustom though (t nil 'ask). Wrapping a
> comment block inside comment block can be a valid use case.


That would be nice.....

Uwe 
> Best,
> Ihor


-- 
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.