From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: problem with code blocks
Date: Mon, 08 Aug 2011 09:47:27 +0200 [thread overview]
Message-ID: <80oc00e44w.fsf@somewhere.org> (raw)
In-Reply-To: CAGzSEhd7Usc2hWPmsf-qXoP4Lr9ZBfWPuuhzXWSmcigB0jkuoQ@mail.gmail.com
Hi LanX,
LanX wrote:
> Thanks for the suggestion, but the problem persists!
You see it's easier with an ECM...
> Only replacing the "0" with an "a" helps.
I don't have that problem. I guess it must have been fixed recently. It
clearly is related to [0] being interpreted as a footnote reference... It
should not, when in code. Please update your Org-mode version.
> ----------------------------------------------
> #+LaTeX_CLASS: beamer
> #+startup: beamer
>
> * Lanx
> ** title
>
> #+BEGIN_Example perl
> grep { $_ ->[a] } # <- 0 fails
> X{1,2,3} X{1,2,3} X{1,2,3};
> #+END_Example
>
> ----------------------------------------------
>
> type C-c C-e d (or C-c C-e L)
BTW, putting the language name after `begin_example' is useless. There is no
such concept. You should use the `begin_src' environments, where the language
is accepted as parameter:
#+begin_src perl
grep { $_ ->[0] } # <- 0 does not fail
X{1,2,3} X{1,2,3} X{1,2,3};
#+end_src
Doing so, instead of:
#+begin_src latex
\begin{verbatim}
grep { $_ ->[0] } # <- 0 does not fail
X{1,2,3} X{1,2,3} X{1,2,3};
\end{verbatim}
#+end_src
you'll get:
#+begin_src latex
\lstset{language=Perl}
\begin{lstlisting}
grep { $_ ->[0] } # <- 0 does not fail
X{1,2,3} X{1,2,3} X{1,2,3};
\end{lstlisting}
#+end_src
Best regards,
Seb
--
Sebastien Vauban
prev parent reply other threads:[~2011-08-08 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 23:45 problem with code blocks LanX
2011-08-07 23:48 ` LanX
2011-08-07 23:57 ` Thomas S. Dye
2011-08-08 6:58 ` LanX
2011-08-08 7:47 ` Sebastien Vauban [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=80oc00e44w.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).