emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <eric.schulte@gmx.com>
To: Mikhail Titov <mlt@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel, ess] How can I make S-RET to be multi-session friendly?
Date: Fri, 10 Aug 2012 21:37:03 -0600	[thread overview]
Message-ID: <87a9y214m8.fsf@gmx.com> (raw)
In-Reply-To: <9q0sjbuvar7.fsf@gmx.us> (Mikhail Titov's message of "Fri, 10 Aug 2012 13:54:04 -0500")

>> Yes, the order of precedence is
>> system-level < buffer/subtree-level < language-level <
>> code-block-level
> Then I'd say buffer level does NOT override system-level for some
> reason.

I believe you mean the buffer-level does not override the

> I just re-built Emacs from bzr to make sure I'm running somewhat
> recent Org.
> Another weird thing is that when I tried to use Org from git (and not
> the stock one), Emacs freezes deadly on
> (org-clock-persistence-insinuate) unless I kill ntvdm.exe with Task
> Manager (I'm on Windows). But I guess it is a separate story.

I have no idea what could be causing the above, but it seems unrelated.

>>> ,----[ snippet from dot emacs ]
>>> | (setq org-babel-default-header-args:R
>>> |       '((:results . "output") (:session . "*R*")))
>>> `----
>> Given that (:session . "*R*") will be used by default you could simply
>> remove it from your custom setting for org-babel-default-header-args.
> This made a trick. Now indeed I have *Rreport* after C-c C-c on code
> block. However after C-c ' whenever I attempt to S-RET, yet another *R*
> is launched every time instead of evaluating a line.
> So the question perhaps is:
> How to alter [1] such that when I edit code block with C-c ' , S-RET
> executes lines in a proper session. I believe all information is in
> there, I just have no clue how would I extract it, e.g. to which main
> buffer that code editing buffer (I don't know the right name for it)
> belongs to, and what session header is set to in that buffer.
> If there is a way to fetch those, perhaps I'd be able to alter original
> set up in [1].

You can find the name of the original org-mode buffer by running the
following snippet of elisp within the edit buffer.

    ;; -*- emacs-lisp -*-
    (marker-buffer org-edit-src-beg-marker)

The `org-src-in-org-buffer' macro may be used from an edit buffer to run
elisp inside the code block, in the org-mode buffer of the edit buffer.
e.g., the following 

    ;; -*- emacs-lisp -*-
    (org-src-in-org-buffer (message "-->%S" (org-babel-get-src-block-info)))


>>> Footnotes: 
>>> [1]
>>> http://www.kieranhealy.org/blog/archives/2009/10/12/make-shift-enter-do-a-lot-in-ess/

Eric Schulte

  reply	other threads:[~2012-08-11  3:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 18:44 Mikhail Titov
2012-08-09 19:33 ` Achim Gratz
2012-08-10 12:42 ` Eric Schulte
2012-08-10 18:54   ` Mikhail Titov
2012-08-11  3:37     ` Eric Schulte [this message]
2012-08-11 14:33       ` Andrew Young
2012-08-14 13:17         ` Eric Schulte
2012-08-14 21:48           ` Mikhail Titov
2012-08-14 21:59             ` Bastien
2012-08-16 21:06               ` Mikhail Titov
2012-08-17 14:29                 ` Eric Schulte
2012-08-23 22:11                   ` Mikhail Titov

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=87a9y214m8.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mlt@gmx.us \
    --subject='Re: [babel, ess] How can I make S-RET to be multi-session friendly?' \


* 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:


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