From: Uwe Brauer <oub@mat.ucm.es>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Uwe Brauer <oub@mat.ucm.es>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Re: the comment environment does not work for checkboxes
Date: Sat, 30 Jul 2022 08:23:58 +0200 [thread overview]
Message-ID: <875yjfktj5.fsf@mat.ucm.es> (raw)
In-Reply-To: 87h72zt9ce.fsf@localhost
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
> 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.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-07-30 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 5:30 the comment environment does not work for checkboxes Uwe Brauer
2022-07-29 7:56 ` Dr. Arne Babenhauserheide
2022-07-29 14:39 ` Uwe Brauer
2022-07-30 5:27 ` [PATCH] " Ihor Radchenko
2022-07-30 5:40 ` Uwe Brauer
2022-07-30 5:55 ` Ihor Radchenko
2022-07-30 6:00 ` Uwe Brauer
2022-07-30 6:15 ` Ihor Radchenko
2022-07-30 6:23 ` Uwe Brauer [this message]
2022-07-30 12:09 ` Ihor Radchenko
2022-08-04 12:08 ` Uwe Brauer
2022-08-04 14:26 ` Ihor Radchenko
2022-08-07 9:41 ` Ihor Radchenko
2022-07-30 5:21 ` [SOLVED: src not comment] (was: the comment environment does not work for checkboxes) Uwe Brauer
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=875yjfktj5.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).