From: Samuel Wales <samologist@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Bastien <bzg@gnu.org>, Nicolas Goaziou <n.goaziou@gmail.com>,
Andreas Leha <andreas.leha@med.uni-goettingen.de>,
emacs-orgmode@gnu.org
Subject: Re: Babel should not work in the subtree marked as not exported
Date: Mon, 24 Mar 2014 11:06:27 -0700 [thread overview]
Message-ID: <CAJcAo8tLNTMj7B3gc8xfneHd5eyH__cFXxHFG-FHmpo_vpBu+Q@mail.gmail.com> (raw)
In-Reply-To: <87ha6nsdwp.fsf@bagel.gateway.pace.com>
now that everybody is happy, agreeing, and singing in a circle holding
hands, i thought i'd stir the pot. :] i hope i don't get wicked
glares. :]
there are a few unresolved questions. there is also something that,
for my workflow at least, is a bug.
i set org-export-with-tasks to nil, because i want to export only
blank headers. this is a GREAT feature.
tldr: call lines are executed when they should not be.
===
i never use export tags. i only use comment for occasional,
temporary, truly commented out things. i cannot use it for more
purposes because it changes sorting and highlighting of todo keywords.
that makes it not worth using for any other purpose.
so i do:
===
***** a
******* REF b
******* NEXT e
******* d
******* MAYBE c
===
which exports a and d, but not b e c. this is perfect. it is exactly
what i want. i get a sense of "this is software working the way it
should" every time i export. i REALLY like how i can intersperse
notes with exported stuff. no tags or comments or anything fancy,
just todo keywords.
except for one thing.
underneath b i like to put babel blocks that are relevant to a. and
above the babel blocks, i might have some call lines. these lines are
for testing. i do c-c c-c on them manually, to test the block.
i also export b while testing, to get all of them at once. but most
of the time i only export a.
this is all well and good -- again, perfect -- but in maint at least,
babel actually executes those call lines upon export of a.
i don't want them exported, because they are only there for testing.
i don't want to comment out the header, because that changes font
lock, turns off the block [which i use], and changes sorting.
to me it's a bug that those call lines are executed.
i'll join the circle if you guys will agree with me on this. :]
samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. And
ANYBODY can get it.
Denmark: free Karina Hansen NOW.
next prev parent reply other threads:[~2014-03-24 18:06 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
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 [this message]
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=CAJcAo8tLNTMj7B3gc8xfneHd5eyH__cFXxHFG-FHmpo_vpBu+Q@mail.gmail.com \
--to=samologist@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--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).