From: Charles Millar <millarc@verizon.net>
To: emacs-orgmode@gnu.org
Subject: Bug - #+begin_comment, etc surrounding minipage
Date: Mon, 20 Aug 2018 15:30:36 -0400 [thread overview]
Message-ID: <1ef17a0f-40ad-2140-c552-29c0fddd6344@verizon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1763 bytes --]
Hi,
When exporting to pdf via LaTeX, the region between the #+begin_comment
and the #+end_comment does not comment out:
*** sub,sub-heading one
#+attr_latex: :options [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage
#+begin_comment
*** sub,sub-heading two
#+attr_latex: :options [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage
*** sub,sub-heading three
#+attr_latex: :options [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage*** sub,sub-heading one
#+attr_latex: :options [t]{2.8in}
#+begin_minipage
some inline shell source code
#+end_minipage
#+attr_latex: :options [t]{1.2in}
#+begin_minipage
some more inline shell source code
#+end_minipage
#+attr_latex: :options [t]{3.0in}
#+begin_minipage
and more inline shell source code
#+end_minipage
#+end_comment
Instead the #+begin_comment and #+end_comment lines are printed out
(sort of weirdly) and everything in between as well.
If I surround the region with a \begin{comment} and \end{comment} - all
is well.
Org mode version 9.1.13 (release_9.1.13-901-g638f32 @
/usr/local/share/org-mode/lisp/)
GNU Emacs 27.0.50 (build 48, x86_64-pc-linux-gnu, GTK+ Version 3.22.29)
of 2018-06-29
Charlie Millar
[-- Attachment #2: Type: text/html, Size: 3160 bytes --]
reply other threads:[~2018-08-20 19:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ef17a0f-40ad-2140-c552-29c0fddd6344@verizon.net \
--to=millarc@verizon.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.