emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Possible bug with Org Babel source code blocks and ESS integration
Date: Fri, 12 Dec 2014 07:42:26 +0530	[thread overview]
Message-ID: <C8148BF2-87AF-44A4-B103-6BD338DA8D96@agrarianresearch.org> (raw)

I am having a strange problem with R Source Blocks. Let me explain (I hope the explanation below makes sense).

When I am creating a source block, I typically create the #+BEGIN_SRC and #+END_SRC lines, and then use C-c ' to enter ESS mode, fill the block there, and return to my org buffer using C-c ' again. 

While I am filling in my source block, I sometimes need to refer to my full org file and some other source blocks in there. So my cursor in the Org file moves. Then, if my code block is a little complex, I like to save it while I am editing (C-x C-s). This is where the mess is created. Instead of saving the code in the source block from where ESS was called, the code is saved at the point where my cursor in the org file at the moment is. As a result, I get a copy of the source code text (without the BEGIN_SRC and END_SRC lines) at the place where my cursor is. This obviously creates a total mess and I have to clean it up.

Is this the intended behaviour? I have used source code blocks for years and have not had this problem before. But I cannot say whether this is a new behaviour in org or something in my behaviour has changed. In the past, I perhaps never moved the cursor in my org buffer while editing a source code block. 

Of course, one advice could be not to switch back from the ESS buffer without closing it. But a better thing would be if saving in the ESS buffer saved the source code block in the right place. But I don’t know if that is too much to ask.


             reply	other threads:[~2014-12-12  2:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12  2:12 Vikas Rawal [this message]
2014-12-12  4:41 ` Possible bug with Org Babel source code blocks and ESS integration Aaron Ecay
2014-12-12  4:47   ` Vikas Rawal
2014-12-12  4:57     ` Aaron Ecay

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:

  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=C8148BF2-87AF-44A4-B103-6BD338DA8D96@agrarianresearch.org \
    --to=vikaslists@agrarianresearch.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).