From: Steve Downey <sdowney@gmail.com>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: Src blocks laid out side-by-side
Date: Sat, 8 Feb 2020 14:02:45 -0500 [thread overview]
Message-ID: <CAJEGDKotf4ht2FE+AbQehEF_+fQX4JR0=KWAb6kb8pqRXrBPvA@mail.gmail.com> (raw)
In-Reply-To: <87v9ohl73m.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Only needs to be in the exported document, and doesn't necessarily need to
render that way within org. However, I'd like to avoid having to choose the
export form with custom markup in the org document. I often have documents,
or parts of docs, that are exported to both HTML and latex.
The equivalent that I'm doing in markdown are custom fenced blocks that
pandoc post-processes.
I suppose I could write some markup that on export gets processed to the
appropriate html or latex.
On Sat, Feb 8, 2020, 05:13 Fraga, Eric <e.fraga@ucl.ac.uk> wrote:
> On Friday, 7 Feb 2020 at 17:59, Steve Downey wrote:
> > I have a need to lay out source blocks side by side, in order to present
> > before and after changes to the source. If I could embed a block in a
> > table, that would do it.
>
> Do you need this layout in org file itself or only in an exported
> document from the org file?
>
> For the latter, you can use inline directives to achieve this. E.g. if
> you were exporting to PDF via LaTeX, you could start/end minipages
> around each src block.
>
> --
> : Eric S Fraga via Emacs 28.0.50, Org release_9.3.2-233-gc2bc48
>
[-- Attachment #2: Type: text/html, Size: 1820 bytes --]
prev parent reply other threads:[~2020-02-08 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 22:59 Src blocks laid out side-by-side Steve Downey
2020-02-08 10:13 ` Fraga, Eric
2020-02-08 18:14 ` Berry, Charles via General discussions about Org-mode.
2020-02-08 19:02 ` Steve Downey [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:
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='CAJEGDKotf4ht2FE+AbQehEF_+fQX4JR0=KWAb6kb8pqRXrBPvA@mail.gmail.com' \
--to=sdowney@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).