From: Roland DONAT <roland.donat@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Babel : python generate org source block with an extra comma before * characters
Date: Sun, 13 Jul 2014 18:07:58 +0000 (UTC) [thread overview]
Message-ID: <loom.20140713T195540-699@post.gmane.org> (raw)
In-Reply-To: 87ha2lxr35.fsf@gmail.com
Thorsten Jolitz <tjolitz <at> gmail.com> writes:
>
> This is because this function was applied to the results
>
> ,----[ C-h f org-escape-code-in-region RET ]
> | org-escape-code-in-region is an interactive compiled Lisp function in
> | `org-src.el'.
> |
> | (org-escape-code-in-region BEG END)
> |
> | Escape lines between BEG and END.
> | Escaping happens when a line starts with "*", "#+", ",*" or
> | ",#+" by appending a comma to it.
> |
> | [back]
> `----
>
> Not sure how to get rid of this, maybe via :results raw? I'm not aware
> of a configuration variable for this, but it surely exists.
>
Thank you. It helps me much!
Based on your answer, I copy-paste the code of the function "org-escape-
code-in-region" in a source block in my org buffer and modify the code to
prevent it from inserting the comma. It's a little bit dirty but it works.
Using the raw option produces a correct result but I need the generated code
to be decorated with a drawer to automatically replace the result at each
code execution.
To do so, I tried to use de "drawer" option. It gives me the good result
with a drawer but then when I export my org buffer to latex, the drawers
":RESULTS:" is also exported which is not cool...
Well, thanks again!
Roland.
next prev parent reply other threads:[~2014-07-13 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 13:51 Babel : python generate org source block with an extra comma before * characters Roland DONAT
2014-07-13 14:37 ` Thorsten Jolitz
2014-07-13 18:07 ` Roland DONAT [this message]
2014-07-14 0:15 ` Thorsten Jolitz
2014-07-15 15:35 ` Roland DONAT
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=loom.20140713T195540-699@post.gmane.org \
--to=roland.donat@gmail.com \
--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).