emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Re: [BUG] nested blocks aren't protected on export
Date: Mon, 28 Jun 2010 19:04:49 +0200	[thread overview]
Message-ID: <87wrtjgkb2.wl%n.goaziou@gmail.com> (raw)
In-Reply-To: <87pqzb9nu2.fsf@gmail.com>

>>>>> Eric Schulte writes:
> I would disagree here.  There *is* a case where a protected comment
> should be retained in the export.  For example, if I'm writing a
> document in which I want to discuss Org-mode markup.  It should be
> possible for me to include verbatim Org-mode code in my document,
> through the use of e.g.

>   #+begin_src org
>     ,* example org

>     ,# this is a comment
>     ,this is not a comment
>   #+end_src

> however without the protection check, the comment would be removed.  If
> there is a problem with comments being marked as protected when they
> shouldn't be, then that should be fixed where the protection is being
> applied, but I believe that the protection check in this patch is
> required.

Ok, I get your point. I wasn't thinking recursively.

Regards,

--
Nicolas

      reply	other threads:[~2010-06-28 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26  2:18 [BUG] nested blocks aren't protected on export Eric Schulte
2010-06-28  2:42 ` Eric Schulte
2010-06-28  6:37   ` Carsten Dominik
2010-06-28 15:04     ` Eric Schulte
2010-06-28 16:21       ` Carsten Dominik
2010-06-28 18:40         ` Eric Schulte
2010-06-28 19:59         ` Eric Schulte
2010-06-29  4:32           ` Carsten Dominik
2010-06-29  5:09             ` Eric Schulte
2010-06-28 15:07     ` Nicolas Goaziou
2010-06-28 15:30       ` Eric Schulte
2010-06-28 17:04         ` Nicolas Goaziou [this message]

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=87wrtjgkb2.wl%n.goaziou@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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).