From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Bug? R: Org babel block execution *drastically* slower than in ESS session directly Date: Sat, 17 Nov 2012 10:12:09 -0700 Message-ID: <87boew9ms6.fsf@gmail.com> References: <874nlappb1.fsf@tajo.ucsd.edu> <878vam1jvh.fsf@tajo.ucsd.edu> <3477.1351723988@alphaville> <11876.1351784283@alphaville> <14621.1351795682@alphaville> <87d2zgrhhr.fsf@gmail.com> <87a9ukr8xy.fsf@gmail.com> <87ehjwa8fg.fsf@med.uni-goettingen.de> <87obixilbh.fsf@gmail.com> <87obix8mos.fsf@med.uni-goettingen.de> <87lie1xplm.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:45265) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TZlvX-0000U3-ET for emacs-orgmode@gnu.org; Sat, 17 Nov 2012 12:11:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TZlvU-0006lm-Bd for emacs-orgmode@gnu.org; Sat, 17 Nov 2012 12:11:31 -0500 Received: from mail-ia0-f169.google.com ([209.85.210.169]:58935) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TZlvU-0006lb-6X for emacs-orgmode@gnu.org; Sat, 17 Nov 2012 12:11:28 -0500 Received: by mail-ia0-f169.google.com with SMTP id r4so2981320iaj.0 for ; Sat, 17 Nov 2012 09:11:26 -0800 (PST) In-Reply-To: <87lie1xplm.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 16 Nov 2012 21:25:09 +0100") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org Achim Gratz writes: > Andreas Leha writes: >> I would suggest simply "none" for the new "really-silent". > > Yes please, especially since I tried ":results none" two days ago to > achieve that effect and wondered why it wouldn't work. :-) > Great, since "none" seems like the obvious choice I just committed a version of this patch which places this behavior behind ":results none". At some point documentation should be added to the relevant portion of the manual, but at least we now have this for those reading the mailing list and for those who simply try "none" with this behavior in mind. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte