From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: org babel, ess, R Date: Mon, 3 Jul 2017 14:52:24 -0500 Message-ID: References: <87mv8o2u9b.fsf@nicolasgoaziou.fr> <3295F295-A14A-43EA-8752-53D1BEBCC31A@agrarianresearch.org> <87fuef1fov.fsf@nicolasgoaziou.fr> <829AC437-872D-453D-8543-B3C147F08B54@agrarianresearch.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49231) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dS7OX-0005kL-9N for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 15:52:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dS7OW-0001Hh-Fs for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 15:52:29 -0400 Received: from mail-io0-x22e.google.com ([2607:f8b0:4001:c06::22e]:36834) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dS7OW-0001EH-Ae for emacs-orgmode@gnu.org; Mon, 03 Jul 2017 15:52:28 -0400 Received: by mail-io0-x22e.google.com with SMTP id z62so61656389ioi.3 for ; Mon, 03 Jul 2017 12:52:26 -0700 (PDT) In-Reply-To: <829AC437-872D-453D-8543-B3C147F08B54@agrarianresearch.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Vikas Rawal Cc: org-mode mailing list , Nicolas Goaziou On Sun, Jul 2, 2017 at 7:17 PM, Vikas Rawal wrote: >> >> Vikas Rawal writes: >> >>> Isn=E2=80=99t is what most users need while editing the code block? The >>> possibility of evaluating the code to test and see what happens? >> >> >> Many languages do not support sessions. So, the only possibility to >> evaluate the code is to evaluate the code block in the source buffer. >> > > Yes, what I am talking about is relevant only when a session is defined. = What I would like is that if in a file the session is defined, C-c=E2=80=99= creates > a window configuration that shows the edit buffer and the session. In oth= er cases, the two windows could show the edit buffer and the original org b= uffer. As a frequent R user, I completely relate to this. As soon as one evaluates code in the session buffer (C-c ') with C-RET, this is the setup you get. I'd add to your wish that upon first visiting a file, if I go into edit mode, I'd like Org to pick up the fact that there's a :session argument with a custom name and use that for C-RET in the edit buffer; otherwise it generates the default *R* session there, but if you C-c C-c the block later it puts it into the custom session name. Perhaps out of habit, I tend to use :session r for every block that needs to share results. I'll make some progress, close shop for the day, and to continue where I left off I need to be sure to C-c C-c something the next time rather than jumping right to editing. If I forget, end up with two buffers and I get asked where I want to evaluate every subsequent bit of code. Anyway, it's easy enough to run one line with C-RET once editing and get the session buffer, but just getting it right away is also what I would prefer. For other languages, even though one can't evaluate in the edit buffer, I still use this view more frequently because I get auto-indenting vs. none (e.g. with python). John > > > Vikas