From: Jambunathan K <kjambunathan@gmail.com>
To: Charles Turner <chturne@gmail.com>
Cc: emacs-orgmode@gnu.org, mail@christianmoe.com,
Eric Schulte <eric.schulte@gmx.com>
Subject: Re: Orthogonality of blocks
Date: Thu, 29 Dec 2011 11:44:00 +0530 [thread overview]
Message-ID: <817h1fucpj.fsf@gmail.com> (raw)
In-Reply-To: <4EFB2CFE.9030207@gmail.com> (Charles Turner's message of "Wed, 28 Dec 2011 14:51:42 +0000")
If I look at the figures in the link provided, I am reminded of table.el
tables.
Put your different src blocks in table.el tables, this way even if you
don't get fontification of src blocks atleast you will have a
side-by-side output with both html and latex backends.
Charles Turner <chturne@gmail.com> writes:
> On 27/12/11 21:12, Christian Moe wrote:
>> will do it in HTML. Full example follows below. I'll leave LaTeX to
>> those in the know...
>
> Thanks. This was the "best" solution for me. I quote because the
> abstraction boundary between "how it's rendered" and "what I want to
> be rendered" is getting fuliginous. It would be much better imo to
> have blocks of first-class, and functions of higher-order on those
> blocks, so one could say (side-by-side block1 block2) and the
> side-by-side procedure would deal with the different format
> nuances. The idea is similar to that of the Henderson Escher examples
> in SICP[1], where you have "painters" and functions that combine
> "painters" in interesting ways. Might be fun to investigate how far
> that can go with blocks in org.
>
> @Jambunathan: Your examples render the blocks with sizes proportional
> to the contained text, rather than aligning as a table. I find that
> aesthetically displeasing :-(
>
> Thanks all for the help.
> Charles.
>
> [1] http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-15.html#%_sec_2.2.4
>
>
--
next prev parent reply other threads:[~2011-12-29 6:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-27 19:46 Orthogonality of blocks Charles Turner
2011-12-27 20:37 ` Eric Schulte
2011-12-27 21:12 ` Christian Moe
2011-12-27 21:10 ` Eric Schulte
2011-12-27 23:19 ` Christian Moe
2011-12-27 23:30 ` Nick Dokos
2011-12-28 0:14 ` Torsten Wagner
2011-12-28 4:48 ` Jambunathan K
2011-12-28 5:30 ` Jambunathan K
2011-12-28 7:10 ` Sebastien Vauban
2011-12-28 14:51 ` Charles Turner
2011-12-29 5:18 ` Jambunathan K
2011-12-29 5:49 ` Enhancing table cell alignments and commenting columns (was Re: Orthogonality of blocks) Jambunathan K
2011-12-29 6:06 ` Jambunathan K
2011-12-29 16:22 ` Jambunathan K
2011-12-29 6:14 ` Jambunathan K [this message]
2011-12-30 14:17 ` Orthogonality of blocks 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=817h1fucpj.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=chturne@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.com \
--cc=mail@christianmoe.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).