* special blocks require whitespace
@ 2016-04-13 12:48 prayner
0 siblings, 0 replies; 2+ messages in thread
From: prayner @ 2016-04-13 12:48 UTC (permalink / raw)
To: emacs-orgmode
This is probably documented somewhere but I was surprised that I
needed to add some white space in order to get special blocks
recognized as such.
Here is a simple example:
#+Options: num:nil toc:nil
#+TITLE:
#+AUTHOR:
#+BEGIN_CENTER
this is not handled correctly
#+END_CENTER
#+BEGIN_CENTER
but this is
#+END_CENTER
----------------------------------------------------------------------
Here is the generated LaTeX
% Created 2016-04-13 Wed 22:25
% Intended LaTeX compiler: pdflatex
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage{grffile}
\usepackage{longtable}
\usepackage{wrapfig}
\usepackage{rotating}
\usepackage[normalem]{ulem}
\usepackage{amsmath}
\usepackage{textcomp}
\usepackage{amssymb}
\usepackage{capt-of}
\usepackage{hyperref}
\date{\today}
\title{}
\hypersetup{
pdfauthor={},
pdftitle={},
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs 24.5.1 (Org mode 8.3.3)},
pdflang={English}}
\begin{document}
\#+BEGIN\(_{\text{CENTER}}\)
this is not handled correctly
\#+END\(_{\text{CENTER}}\)
\begin{center}
but this is
\end{center}
\end{document}
----------------------------------------------------------------------
It's hard to see but the difference between the two examples is that
the 2nd has a single space after the #+BEGIN_CENTER
The behaviour arises from
((looking-at "\\+BEGIN_\\(\\S-+\\)")
This is with org version 8.3.3
Should this be considered a bug?
Please respond directly as well as to the list since I'm way behind with this list
regards
Peter
--
Peter Rayner
Leader, Clean Air and Urban Landscapes NESP hub <http://www.nespurban.edu.au>
room 343
School of Earth Sciences, University of Melbourne, 3010, Vic, Australia
tel: work: +61 (0)3 8344 9708; fax: +61 (0)3 8344 7761
mobile +61 402 752 379, skype: petermorag
mail-to: prayner@unimelb.edu.au TWITTER: @raynerstrings
google scholar profile <http://scholar.google.com.au/citations?user=H3up71wAAAAJ&hl=en>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: special blocks require whitespace
[not found] <ee9ba14414cb416badf123599921c256@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
@ 2016-04-13 16:15 ` Eric S Fraga
0 siblings, 0 replies; 2+ messages in thread
From: Eric S Fraga @ 2016-04-13 16:15 UTC (permalink / raw)
To: prayner@unimelb.edu.au; +Cc: emacs-orgmode@gnu.org
On Wednesday, 13 Apr 2016 at 12:48, prayner@unimelb.edu.au wrote:
> This is probably documented somewhere but I was surprised that I
> needed to add some white space in order to get special blocks
> recognized as such.
Your example works fine for me.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.90.1, Org release_8.3.3-535-g7213aa
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-04-13 16:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-13 12:48 special blocks require whitespace prayner
[not found] <ee9ba14414cb416badf123599921c256@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-04-13 16:15 ` Eric S Fraga
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.