From mboxrd@z Thu Jan 1 00:00:00 1970 From: aaronecay@gmail.com Subject: Re: [PATCH] * lisp/ob-core.el (org-babel-execute-src-block): insert hash for silent results Date: Fri, 08 Mar 2013 17:24:19 -0500 Message-ID: <87r4jpjzsc.fsf@gmail.com> References: <1362542863-25992-1-git-send-email-aaronecay@gmail.com> <87obetsgma.fsf@Rainer.invalid> <877glhsfus.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:49283) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UE5iE-0001bB-Mb for emacs-orgmode@gnu.org; Fri, 08 Mar 2013 17:24:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UE5i9-0003TM-Cp for emacs-orgmode@gnu.org; Fri, 08 Mar 2013 17:24:26 -0500 Received: from mail-qe0-f45.google.com ([209.85.128.45]:48689) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UE5i9-0003TI-8v for emacs-orgmode@gnu.org; Fri, 08 Mar 2013 17:24:21 -0500 Received: by mail-qe0-f45.google.com with SMTP id b4so1339955qen.32 for ; Fri, 08 Mar 2013 14:24:20 -0800 (PST) In-Reply-To: <877glhsfus.fsf@gmail.com> 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: Eric Schulte Cc: Achim Gratz , emacs-orgmode@gnu.org 2013ko martxoak 8an, Eric Schulte-ek idatzi zuen: >=20 > I would agree. I don't believe *any* changes should take place in the > buffer when a code block is executed with ":results none". A common use case for me is to use a babel block to load a large dataset into R. I want this to be cached, in the sense that I want it not to be run again (by e.g. C-c C-v C-b) unless the code changes. But I also don=E2=80=99t want to see its result in the (mini)buffer. Is there a way to accommodate this usage of the cache functionality? > I prefer leaving the hash with the results, as it is the results which > are "hashed". Also, same input does not always guarantee same output, > e.g., >=20 > #+begin_src sh > date > #+end_src In this case, the code block shouldn=E2=80=99t be marked :cache. Unless the desired (and odd, IMO) behavior is to have a datestamp that is only updated when the user forcibly re-evaluates the block (with C-u C-c C-c). Also, with regard to: > The hyphen should only be required for multi-word functions, e.g., > `listp' has no hyphen but `hash-table-p' does have a hyphen. The context surrounding this code binds cache-p; the lack of a hyphen was just a typo in the patch. I agree that cachep is more idiomatic (in fact, that is what led to the typo), but I tried to make the smallest possible patch to address my intention. --=20 Aaron Ecay