emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sergey <srg.koshelev@protonmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Code block :results raw replace issue [9.3.7 (9.3.7-22-gbd9785-elpaplus @ /Users/skoshelev/.emacs.d/elpa/26.2/develop/org-plus-contrib-20200824/)]
Date: Tue, 06 Oct 2020 11:59:34 +0200	[thread overview]
Message-ID: <87tuv7u12x.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <UyMS92kpJs66OEqu2QL-soDClhZzBrQxDZRLRqO7_cfdSeFiGuGJcf4_hCayw6PlSHIw5r6KzNMGtD2K9JIKaowYhIGs82p2gF1qDz3q3Ms=@protonmail.com> (Sergey's message of "Tue, 06 Oct 2020 04:10:05 +0000")

Hello,

Sergey <srg.koshelev@protonmail.com> writes:

> Code block header argument ~replace~ seems to not to work in conjunction
> with ~raw~. This leads to output being pre-pended instead of being
> replaced to the results block.
>
> Below is a working example:
>
> #+begin_src python :session *python-test* :results output raw replace
> print('This line will be added every time this code runs')
> #+end_src
>
> #+RESULTS:
> This line will be added every time this code runs

This is expected. With "raw", Org has no way to determine where the
output starts, ends, or even if there is one already. You may want to
use another option if you want to replace results.

Regards,
-- 
Nicolas Goaziou


  reply	other threads:[~2020-10-06 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06  4:10 Bug: Code block :results raw replace issue [9.3.7 (9.3.7-22-gbd9785-elpaplus @ /Users/skoshelev/.emacs.d/elpa/26.2/develop/org-plus-contrib-20200824/)] Sergey
2020-10-06  9:59 ` Nicolas Goaziou [this message]
2020-10-06 13:14   ` Sergey

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=87tuv7u12x.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=srg.koshelev@protonmail.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).