emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Charles Millar <millarc@verizon.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Inline source does not evaluate when inserted insie a minipage environment
Date: Fri, 22 Sep 2017 23:22:02 +0200	[thread overview]
Message-ID: <87zi9m5szp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <a4464b6d-4836-c9a2-a923-28b7c8315e84@verizon.net> (Charles Millar's message of "Fri, 22 Sep 2017 15:56:58 -0400")

Hello,

Charles Millar <millarc@verizon.net> writes:

> This problem may not be limited to just \begin{minipage}, etc., but to
> other latex commands which may precede text which contains inline
> source code
>
> The following inline code evaluates as expected to 1
>
> This is some text.
> Some more test with an inline  src_sh[:results raw]{echo 1}
> a bit more
>
> However, when I C-c C-c the same code when inside a minipage, I get
> the message " 'C-c C-c' can do nothing useful here"
> \begin{minipage}[t]{4.0in} This is some text.
> Some more test with an inline  src_sh[:results raw]{echo 1}
> a bit more
> \end{minipage}

This is not a bug.

  \begin{minipage}
  ...
  \end{minipage}

defines a LaTeX environment, i.e., pure LaTeX code, and Org doesn't look
into this. This is like $...$ or \(...\), but as block element.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-09-22 21:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 19:56 Inline source does not evaluate when inserted insie a minipage environment Charles Millar
2017-09-22 21:22 ` Nicolas Goaziou [this message]
2017-09-23  0:44   ` Charles Millar
2017-09-23 14:02 ` Eric S Fraga
2017-09-24 20:59   ` Charles Millar
2017-09-25  7:32     ` Eric S Fraga
2017-09-26 23:19       ` Charles Millar

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=87zi9m5szp.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=millarc@verizon.net \
    /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).