From: Erik Iverson <eriki@ccbr.umn.edu>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org, Richard Riley <rileyrg@gmail.com>
Subject: Re: org-babel and empty code blocks : publishing html
Date: Thu, 09 Sep 2010 11:43:42 -0500 [thread overview]
Message-ID: <4C890EBE.3080906@ccbr.umn.edu> (raw)
In-Reply-To: <878w3a5158.fsf@gmail.com>
Eric Schulte wrote:
> I'd think adding an ":exports none" header argument should be
> sufficient.
>
If the code block is empty, I doesn't appear so.
If you put in a literal
nil
in the code block, then :exports none does as expected.
> Best -- Eric
>
> Richard Riley <rileyrg@gmail.com> writes:
>
>> On my journal capture template I include a #begin_src and #end_src block
>> as I frequently want to journal code. Being lazy I dont
>> necessarily want to delete this block even if I have no code in that
>> org-entry. Is it possible to suppress the output "nil" which is
>> generated for the html export for empty code blocks?
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-09-09 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 16:20 org-babel and empty code blocks : publishing html Richard Riley
2010-09-09 16:28 ` Erik Iverson
2010-09-09 16:31 ` Eric Schulte
2010-09-09 16:43 ` Erik Iverson [this message]
2010-09-09 17:16 ` Richard Riley
2010-09-09 17:24 ` Richard Riley
2010-09-09 20:43 ` org-babel and empty code blocks : publishing html -- Side note Sébastien Vauban
2010-09-09 20:58 ` Richard Riley
2010-09-10 18:37 ` Re: org-babel and empty code blocks : publishing html Eric Schulte
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=4C890EBE.3080906@ccbr.umn.edu \
--to=eriki@ccbr.umn.edu \
--cc=emacs-orgmode@gnu.org \
--cc=rileyrg@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).