From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: Re: [babel] ledger tutorial on Worg Date: Fri, 03 Sep 2010 15:35:40 -0600 Message-ID: <8762ymo6hf.fsf@gmail.com> References: <871v9lm0s3.wl%ucecesf@ucl.ac.uk> <4296BE2D-051E-47E8-8AA7-24582082DD0F@gmail.com> <87zkw8vzxw.fsf@gmail.com> <87aao1bt8w.fsf@mundaneum.com> <87mxs1co0f.wl%ucecesf@ucl.ac.uk> <87mxs071us.fsf@mundaneum.com> <87tym8b3e0.fsf@gmail.com> <87mxryv9ah.fsf@mundaneum.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=34887 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OrdvM-0000EY-6T for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 17:35:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OrdvI-000474-ML for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 17:35:49 -0400 Received: from mail-gy0-f169.google.com ([209.85.160.169]:45959) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OrdvI-00046z-K3 for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 17:35:48 -0400 Received: by gyf3 with SMTP id 3so1342602gyf.0 for ; Fri, 03 Sep 2010 14:35:48 -0700 (PDT) In-Reply-To: <87mxryv9ah.fsf@mundaneum.com> (=?utf-8?Q?=22S=C3=A9bastien?= Vauban"'s message of "Fri, 03 Sep 2010 22:53:10 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?utf-8?Q?S=C3=A9bastien?= Vauban Cc: emacs-orgmode@gnu.org S=C3=A9bastien Vauban writes: > Hi Eric(s), > Hi Seb, [...] > > 1. I find it weird to have all the parameters of =3D:cmdline=3D not enclo= sed > between quotes. What should be the best option, here? That was a subj= ect, > long ago, on Org-Babel: to quote or not to quote... > I don't know that this was ever explicitly discussed, I believe that the no-quoting behavior may have simply fallen out of the initial implementation. I'd certainly like to hear other people's opinions on this, but I've personally enjoyed not having to place quotes in every instance. > > 2. When the evaluation produces no output, but had well produced output > before, shouldn't Babel have to delete the previously written results = in > the Org buffer? > This is a good point. Currently Babel just quits if it receives a nil result, but I think you're right that we should replace existing results when a nil result has been returned. I'll add this as PROPOSED to the babel task list. Cheers -- Eric