From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] Environment around exported results
Date: Tue, 21 Sep 2010 07:14:31 -0600 [thread overview]
Message-ID: <87mxrbdyhs.fsf@gmail.com> (raw)
In-Reply-To: 87sk14p6y6.fsf@mundaneum.com
Hi Seb,
I think you've made a good point for adding this functionality. I'll
put this on the Babel TODO stack, and reply to this email when we get
something implemented.
Best -- Eric
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>>> Would you mind creating an LaTeX environment around the =results= block, so
>>> that we could have the code colorized (via listings or Minted), and clearly
>>> distinguish the results, if we want so.
>>>
>>> Having an environment would allow one to use non-proportional font for the
>>> results, or a shadowed background, or...
>>
>> Would such an environment be in addition too or in place of wrapping results
>> in the example environment?
>
> I would think of something like this:
>
> \begin{orgresults}
> <... results block ...>
> \end{orgresults}
>
> so that one can customize the =orgresults= environment in LaTeX to get a
> colored background, another font, etc.
>
>
>> What would you suggest for tabular results?
>
> Nothing different for tables: just the same plain default environment around
> the results part.
>
>
>> One very nice property of the current setup is that it relies solely on
>> vanilla Org-mode for export features. If the example export of Org-mode
>> allowed some form of customization through a customizable div class or latex
>> environment would that be sufficient?
>
> The name of the environment could be in a variable, yes.
>
> But please note the above request can come out of a misunderstanding or poor
> knowledge of already existing parametrization of Org-Babel. Put me back on
> tracks if needed...
>
> Best regards,
> Seb
next prev parent reply other threads:[~2010-09-21 13:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 15:16 [babel] Environment around exported results Sébastien Vauban
2010-09-20 4:46 ` Eric Schulte
2010-09-20 19:10 ` Sébastien Vauban
2010-09-21 7:44 ` Sébastien Vauban
2010-09-21 13:14 ` Eric Schulte [this message]
2010-09-24 9:28 ` Sébastien Vauban
2010-09-24 21:01 ` Rainer M Krug
2010-09-27 8:16 ` Sébastien Vauban
2010-11-19 13:27 ` [Babel] Need for an extra literal block construct Sébastien Vauban
2010-11-19 15:17 ` Christian Moe
2010-11-19 20:12 ` Sébastien Vauban
2010-11-19 20:26 ` Sébastien Vauban
2010-11-19 20:38 ` Thomas S. Dye
2010-11-19 22:02 ` Sébastien Vauban
2010-11-19 22:20 ` Thomas S. Dye
2010-11-19 23:00 ` Sébastien Vauban
2010-11-19 22:24 ` Eric Schulte
2010-11-19 23:07 ` Eric Schulte
2010-11-20 7:20 ` Sébastien Vauban
2010-11-22 21:46 ` Sébastien Vauban
2010-11-23 0:42 ` Eric Schulte
2010-11-23 23:15 ` Sébastien Vauban
2010-11-19 23:13 ` Sébastien Vauban
2010-11-19 22:36 ` Dan Davison
2010-11-20 21:50 ` Sébastien Vauban
2010-11-21 10:01 ` Dan Davison
2010-11-22 20:22 ` Sébastien Vauban
2010-11-21 13:41 ` Nicolas Goaziou
2010-11-22 20:30 ` Sébastien Vauban
2010-11-23 19:27 ` Nicolas Goaziou
2010-11-23 23:22 ` Sébastien Vauban
2010-11-24 10:14 ` Nicolas Goaziou
2010-11-19 23:10 ` Christian Moe
2010-11-19 23:23 ` Sébastien 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=87mxrbdyhs.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
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).