emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Eric Schulte <schulte.eric@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Silent output in Org, but verbose export
Date: Wed, 07 Sep 2011 09:15:40 -0600	[thread overview]
Message-ID: <87pqjce63n.fsf@gmail.com> (raw)
In-Reply-To: 80ty8oagie.fsf@somewhere.org

Hi Seb,

>
> Now, subquestion: let's suppose I first write this code block...
>
> #+begin_src sh :exports results
> echo "I want to see this in HTML/PDF, but not in Org"
> #+end_src
>
> #+results:
> | I want to see this in HTML/PDF | but not in Org |
>
> then I add the option "silent", and eval it:
>
> #+begin_src sh :results silent :exports results
> echo "I want to see this in HTML/PDF, but not in Org"
> #+end_src
>
> #+results:
> | I want to see this in HTML/PDF | but not in Org |
>
> The =results= line is not removed automatically. I have to delete it myself.
>
> Question: wouldn't it be better to check, when option is =silent=, that there is
> no =results= line, and remove it if there is one?
>

I tried implementing this change (a simple one-line addition) but it
breaks some other pieces of code block evaluation (inline blocks) which
assume that ":results silent" will not affect the contents of the
buffer.

For not at least I think it would be preferable to leave the meaning of
silent to be "do nothing to the buffer" rather than to remove any
possibly pre-existing results.  Possibly at some point in the future
after I've fixed results removal for inline blocks we should revisit
this decision.

Best -- Eric

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

next prev parent reply	other threads:[~2011-09-07 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 15:39 [babel] Silent output in Org, but verbose export Sebastien Vauban
2011-09-06 16:37 ` Eric Schulte
2011-09-07  8:25   ` Rainer M Krug
2011-09-07  8:44   ` Sebastien Vauban
2011-09-07 15:15     ` Eric Schulte [this message]
2011-09-07 20:23       ` Sebastien Vauban

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=87pqjce63n.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.com \
    /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

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