emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: Fabrice Niessen <public-fni-news-TA4HMoP+1wHrZ44/DZwexQ@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: ":results none" doesn't seem to be documented
Date: Thu, 15 Jan 2015 09:31:05 +0100	[thread overview]
Message-ID: <m21tmwzbqu.fsf@krugs.de> (raw)
In-Reply-To: <86lhl53t0h.fsf@example.com> (Fabrice Niessen's message of "Wed, 14 Jan 2015 23:19:10 +0100")

[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]

Fabrice Niessen <fni-news-TA4HMoP+1wHrZ44/DZwexQ@public.gmane.org>
writes:

> Hello,
>
> Andreas Leha wrote:
>> Kodi Arfer <kodi-F2WQSDlpSWheoWH0uzbU5w@public.gmane.org> writes:
>>> "none" is allowed as an argument to :results (see, for example,
>>> ob-core.el line 704 as of Git d36bd8d), but this isn't mentioned in
>>> results.html. I just learned of its existence while reading
>>> ob-core.el.
>>>
>>> To me, by the way, ":results none" seems like a useful feature rather
>>> than being redundant with ":results silent", because it won't attempt
>>> to print a massive object to the echo area. (Pehaps "silent" wasn't a
>>> great choice of name.)
>>
>> Especially given that ":results none" prints "results silenced" in the
>> echo area.  Should rather be "results nonced" ;-)
>
> They're not the same...
>
> Extract from my modest (and still "work in progress") Org-Babel
> refcard [1]:

Looks very useful - I will see if I have something to contribute.

Cheers,

Rainer

>
> - :results silent ::
>      Sends the commands, echoes the results in the minibuffer (to see
>      code block output), but *does not change the Org mode buffer* (even
>      during export, *no results are inserted* into the exported
>      document).
>      (default for Org and Screen code blocks)
>
> - :results none ::
>      Silents the results, even for the minibuffer.  By definition, such
>      a code block is run for its side effects.
>
> Best regards,
> Fabrice
>
> [1] https://github.com/fniessen/refcard-org-babel

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]

  parent reply	other threads:[~2015-01-15  8:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 21:47 ":results none" doesn't seem to be documented Kodi Arfer
2015-01-14 22:09 ` Andreas Leha
2015-01-14 22:19   ` Fabrice Niessen
2015-01-14 22:27     ` Andreas Leha
2015-01-15  8:30       ` Rainer M Krug
2015-01-15 12:25       ` Fabrice Niessen
2015-01-15  8:31     ` Rainer M Krug [this message]
2015-01-14 22:11 ` Grant Rettke
2015-01-14 23:13 ` Samuel Wales
2015-01-15  9:40   ` Andreas Leha
2015-01-15 19:27     ` Samuel Wales
2015-01-15 20:32       ` Andreas Leha
2015-01-15 23:10         ` Samuel Wales
2015-01-14 23:38 ` John Hendy

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=m21tmwzbqu.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-fni-news-TA4HMoP+1wHrZ44/DZwexQ@plane.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).