emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] ledger tutorial on Worg
Date: Sun, 05 Sep 2010 22:49:09 +0200	[thread overview]
Message-ID: <877hizvrui.fsf@mundaneum.com> (raw)
In-Reply-To: 8762ymo6hf.fsf@gmail.com

Hi Eric,

"Eric Schulte" wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>> Hi Eric(s),
>>
>
> Hi Seb,
>
> [...]
>>
>> 1. I find it weird to have all the parameters of =:cmdline= not enclosed
>>    between quotes. What should be the best option, here?  That was a subject,
>>    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.

In december 2009, I wrote:

    "I'm a bit confused (as you may have seen in my last posts) about when we
    do have to quote strings and when we do have to avoid doing it. Would you
    have a one-liner explanation about when we have to use quotes?"

See http://www.mail-archive.com/emacs-orgmode-mXXj517/zsQ@public.gmane.org/msg20265.html for
contextual information.

I remembered "you" (Dan or you) answered it somehow, but it must have been
(around that same period) in another thread. Though, I don't find pointers
anymore...

Question is more: is it clear to mix parameters names (such as =:cmdline=) and
long values which are unquoted (such as =registry unknown credit-card= and
many much more options)?

Shouldn't we properly begin and end where the given value is?


>> 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.

I consider this kind of mandatory, for the sake of coherency, and to really
make use of Org-babel every time I want to run some shell commands (and change
them, eventually getting no results then).

Thanks a lot for everything you did and do for us.

Best regards,
  Seb

-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-09-05 20:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 23:06 [babel] ledger tutorial on Worg Eric S Fraga
2010-08-27 14:53 ` Carsten Dominik
2010-08-27 15:27   ` Eric Schulte
2010-08-27 19:33     ` Eric S Fraga
2010-09-01 11:25     ` Sébastien Vauban
2010-09-01 18:33       ` Eric S Fraga
2010-09-02  0:19         ` Eric Schulte
2010-09-02 12:43         ` Sébastien Vauban
2010-09-02 14:56           ` Eric Schulte
2010-09-03 20:53             ` Sébastien Vauban
2010-09-03 21:35               ` Eric Schulte
2010-09-05 20:49                 ` Sébastien Vauban [this message]
2010-09-07 23:03                   ` Eric Schulte
2010-09-08  8:21                     ` Sébastien Vauban
2010-09-08 17:53                       ` Eric Schulte
2010-09-08 21:40                         ` Sébastien Vauban
2010-09-08 22:46                           ` Eric Schulte
2010-09-09 12:14                           ` Sébastien Vauban
2010-09-09 15:29                             ` Eric Schulte
2010-09-09 19:59                               ` Sébastien Vauban
2010-09-09 21:15                                 ` Sébastien Vauban
2010-09-09 21:42                                   ` Dan Davison
2010-09-03  8:33           ` Eric S Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877hizvrui.fsf@mundaneum.com \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).