From: Rainer M Krug <email@example.com> To: emacs-orgmode <firstname.lastname@example.org> Subject: [babel]Skip comments on code blocks on export? Date: Wed, 25 Jan 2012 10:14:07 +0100 [thread overview] Message-ID: <4F1FC7DF.email@example.com> (raw) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi is there a way of skipping comments when exporting R code? The reason is, that I have roxygen tags in my code, which I do not want to bi included when I export the document to a pdf, as they are only irritate readers not familiar with roxygen. On the other hand, I would like to keep them in the code when tangling, as basic documentation and a base for when / if I convert the code to a package. So my question: is there a way of suppressing comments in code on export? I am aware that might be difficult, but possibly a parameter #+PROPERTY: supressLines "##" which supresses all code lines in code blocks starting with ## would be great for this purpose. Or is there another way of handling this issue? Rainer - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D): +49 - (0)3 21 21 25 22 44 email: Rainer@krugs.de Skype: RMkrug -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8fx98ACgkQoYgNqgF2egrXSwCfTba9EsyAvNpkAWzrpFAsefXD rnkAniVRBVJnF8HLUEFll2XexkzRREd2 =56mx -----END PGP SIGNATURE-----
next reply other threads:[~2012-01-25 9:14 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-25 9:14 Rainer M Krug [this message] 2012-01-27 22:46 ` 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=4F1FC7DF.firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [babel]Skip comments on code blocks on export?' \ /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
Code repositories for project(s) associated with this 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).