From: Eric Schulte <schulte.eric@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel should not work in the subtree marked as not exported
Date: Fri, 14 Mar 2014 13:59:57 -0600 [thread overview]
Message-ID: <8738ik8rod.fsf@gmail.com> (raw)
In-Reply-To: 874n31dvf8.fsf@med.uni-goettingen.de
> Sorry for being unclear here. I wanted to propose different
> behaviour for TAGs (lets say :noexport:) and the COMMENT keyword.
> I am perfectly fine with :noexport: only prohibiting export but
> still allowing evaluation.
>
> But I propose that COMMENT be more treated like a comment, so more
> like a shorthand for commenting out that subtree using '# '.
> That way, evaluation would be disabled.
>
> I see two benefits:
> 1. It serves the use-case where one wants a subtree to be not
> exported and not evaluated.
> 2. It more resembles Orgs idea of comments.
>
> And since the other use case (no export but still evaluation) is
> still very well supported via :noexport: there would be not too
> much loss.
>
> (IIRC, the COMMENT keyword was close to removal from Orgs syntax
> recently. So, why not add some real additional functionality to
> it?)
>
> WDYT?
>
This sounds like a good compromise to me. As you say, this should
easily and visually support both use cases and is intuitive. I've not
touched the export machinery myself, so I'll leave the implementation to
Nicolas but I definitely support this approach.
Best,
>
> Regards,
> Andreas
>
> PS: IIUC, Samuel proposed the same thing:
> http://permalink.gmane.org/gmane.emacs.orgmode/83459
>
>
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2014-03-14 20:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 12:47 Babel should not work in the subtree marked as not exported zwz
2014-03-11 13:27 ` Ken Mankoff
2014-03-11 13:41 ` Andreas Leha
2014-03-11 13:57 ` Ken Mankoff
2014-03-12 10:53 ` zwz
2014-03-12 22:58 ` Andreas Leha
2014-03-13 14:24 ` Eric Schulte
2014-03-13 22:48 ` Andreas Leha
2014-03-14 1:03 ` Eric Schulte
2014-03-14 5:44 ` Samuel Wales
2014-03-14 13:02 ` zwz
2014-03-14 19:10 ` Samuel Wales
2014-03-14 5:48 ` Samuel Wales
2014-03-14 8:40 ` Sebastien Vauban
2014-03-14 8:41 ` Andreas Leha
2014-03-14 19:59 ` Eric Schulte [this message]
2014-03-15 13:54 ` zwz
2014-03-15 14:46 ` Nicolas Goaziou
2014-03-16 2:48 ` Eric Schulte
2014-03-17 21:13 ` Andreas Leha
2014-03-24 15:15 ` Nicolas Goaziou
2014-03-24 16:05 ` Eric Schulte
2014-03-24 16:21 ` Bastien
2014-03-24 17:28 ` Eric Schulte
2014-03-24 18:06 ` Samuel Wales
2014-03-24 18:49 ` Samuel Wales
2014-03-14 1:10 ` John Hendy
2014-03-14 8:34 ` Sebastien Vauban
2014-03-11 14:03 ` Rainer M Krug
2014-03-12 9:23 ` Sebastien Vauban
2014-03-12 10:46 ` zwz
2014-03-12 11:02 ` zwz
2014-03-12 15:00 ` John Hendy
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=8738ik8rod.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
/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).