From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: [babel, R] Commands are not copied in the iESS buffer upon evaluation Date: Tue, 02 Sep 2014 15:32:40 +0200 Message-ID: <861trub11j.fsf@somewhere.org> References: <8638cfr7ua.fsf@somewhere.org> <8761h9u81b.fsf@gmail.com> <86k35ng5yg.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Charles Berry wrote: > Sebastien Vauban writes: >> Aaron Ecay wrote: >>> 2014ko abuztuak 29an, Sebastien Vauban-ek idatzi zuen: >>> >>>> Does it have something to do with `ess-eval-visibly' not being respect= ed >>>> (whose default is `t')? >>> >>> Indeed, babel=E2=80=99s R support let-binds this variable to nil when e= valuating >>> value-type results in a session. >>=20 >> OK. Can we put it to `t' by default [1] or, at least, have Org Babel >> respect our ESS setting? > > If you Google `ess-eval-visibly slow' you will get a bunch of hits > that show why people prefer `nil' and why that is a good default. OK, I can imagine letting the current default is good. > But it may be OK to allow a user to override. But I really find we should be able to override it, yes! Best regards, Seb --=20 Sebastien Vauban