From: Christian Moe <mail@christianmoe.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: emacs-orgmode@gnu.org, Charles Turner <chturne@gmail.com>
Subject: Re: Orthogonality of blocks
Date: Wed, 28 Dec 2011 00:19:02 +0100 [thread overview]
Message-ID: <4EFA5266.6010407@christianmoe.com> (raw)
In-Reply-To: <87boqt3em5.fsf@gmx.com>
Oh, right, it gets a bit more complicated if you want better control
of the tabulated blocks, i.e. border separation and spacing between
the table cells. Then you first need to wrap them in a <div>. You
could do that with literal HTML, or (my preference) with
org-special-blocks. Use CSS to display the div as a table, and set
border separation and spacing on it. Reworked example:
#+title: Side by side code blocks
#+style: <style>.parallel {display: table; border-collapse: separate;
border-spacing: 2px 2px;}
#+style: pre.src {display: table-cell}</style>
How to say hello in two languages:
#+begin_parallel
#+name: Perl_hello
#+begin_src perl :results output
# Perl
sub say_hello {
print "Hello, world";
}
say_hello;
#+end_src
#+name: Python_hello
#+begin_src python :results output
# Python
def say_hello():
print("Hello, world")
say_hello()
#+end_src
#+end_parallel
next prev parent reply other threads:[~2011-12-27 23:12 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 [this message]
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 ` Orthogonality of blocks Jambunathan K
2011-12-30 14:17 ` 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=4EFA5266.6010407@christianmoe.com \
--to=mail@christianmoe.com \
--cc=chturne@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.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).