emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting caption with raw results from inline source blocks
Date: Sat, 27 Apr 2013 13:18:49 +0200	[thread overview]
Message-ID: <87bo90w7ae.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 86fvyczdrt.fsf@somewhere.org

"Sebastien Vauban" <sva-news@mygooglest.com>

> Hi Eric,
> Eric Schulte wrote:
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>> Eric Schulte <schulte.eric@gmail.com> writes:
>>>> I'm loath to add /another/ results keyword, but perhaps it would be nice
>>>> to be able to specify that you want the results processed (e.g,
>>>> stripping the newline), but you don't want them to be wrapped as an
>>>> example.  An alternate approach which may be preferable would be to
>>>> expose a defcustom along the lines of org-babel-inline-result-wrapper,
>>>> which could be used by org-babel-examplize-region instead of "=%s=".
>>> What about always removing trailing newline characters in _inline_ src
>>> blocks results?
>> That is certainly an option.  It could be argued that the point of "raw"
>> is to not change the output at all
> That was one point I tried to attract attention onto: since short, we already
> modify the "raw" output (by "cycling" on tables-alike results). We don't have
> anymore a real "raw" results which would completely stay untouched.

I'd also vote for not modifying raw results -- at least in the inline

In the case of the added linebreak, I think it is easy to add from
inside the code block it if I want it, but hard to remove.  For me it
seems really weird that I have to post-process a 'raw' result to get a
'really raw' result.
Also the added newline is inconsistent with the non-raw result, which
gets exported as \texttt{11} and not \texttt{11\\}.
And the added '\n' breaks (at least) inline results in captions.
Does not adding the '\n' break anything at all?

Having said all that, I am also ok with the org-babel-inline-result-wrap
defcustom.  Thanks for implementing that, Eric.


      reply	other threads:[~2013-04-27 11:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24  7:33 Exporting caption with raw results from inline source blocks Andreas Leha
2013-04-26 11:49 ` Andreas Leha
2013-04-26 12:28   ` John Hendy
2013-04-26 12:41     ` Andreas Leha
2013-04-26 12:56       ` John Hendy
2013-04-26 15:34       ` Eric Schulte
2013-04-26 15:44         ` Eric Schulte
2013-04-26 19:56         ` Nicolas Goaziou
2013-04-26 20:20           ` Eric Schulte
2013-04-27  6:30             ` Sebastien Vauban
2013-04-27 11:18               ` Andreas Leha [this message]

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:

  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=87bo90w7ae.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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