emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Re: the comment environment does not work for checkboxes
Date: Sat, 30 Jul 2022 14:15:13 +0800	[thread overview]
Message-ID: <87h72zt9ce.fsf@localhost> (raw)
In-Reply-To: <87bkt7kumc.fsf@mat.ucm.es>

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

>> Uwe Brauer <oub@mat.ucm.es> writes:
>
>> I am sorry, but I am not familiar with the feature you are referring to.
>
> I applied your patch and did a bit of testing: works flawlessly.

Thanks!

>> Either way, both src and comment blocks are supposed to contain
>> arbitrary non-parseable text, which should not contribute to the
>> statistics? calculations.
>
> With your patch, I can confirm this, before it did not since *** was not «escaped»

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.

>> AFAIK, you cannot. At least, not using an existing command. What you can
>> instead do is open C-c ' window, copy the unescaped text, exit the
>> window, remove the block, and yank the unescaped text.
>
> I see, (patches are welcome I presume 😉)

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.

Best,
Ihor


  reply	other threads:[~2022-07-30  6:15 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 [this message]
2022-07-30  6:23               ` Uwe Brauer
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=87h72zt9ce.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=oub@mat.ucm.es \
    /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).