From: zwz <zhangweize@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [beamer] a bug in exporting
Date: Thu, 12 May 2011 21:26:26 +0800 [thread overview]
Message-ID: <87liyct5h9.fsf@gmail.com> (raw)
In-Reply-To: 87k4dw1jfi.fsf@ucl.ac.uk
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> zwz <zhangweize@gmail.com> writes:
>
>> In a org file I have
>>
>> * what is x?
>> #+BEGIN_SRC c
>> char (*(*x())[])();
>> #+END_SRC
>> \pause
>> char \fbox{\fbox{(*\fbox{\fbox{(*\fbox{x()})}[]})}()};
>>
>> The latex generated for the last line turned out to be
>> char \fbox\{\fbox\{(*\fbox{\fbox{(*\fbox{x()})}[]})\}()\};
>> which is not expected.
>>
>> Is it a bug? I am using Emacs 23.3.1 and org 7.4, by the way.
>
> I am not sure if the regex for identifying latex snippets inline has
> changed or not but an expression like this one is going to test that
> regex to the limit in any case. I would suggest that you use the latex
> directive directly given that the code is not likely to export sensibly
> to any other target anyway:
>
> * what is x?
> #+BEGIN_SRC c
> char (*(*x())[])();
> #+END_SRC
> \pause
> #+LATEX: char \fbox{\fbox{(*\fbox{\fbox{(*\fbox{x()})}[]})}()};
>
> Code like this reminds me why I left the C world more than 15 years
> ago... ;-)
Problem solved by the latex directive. Thanks.
The C code is from K&R's book. :)
BTW, I also use some code like this in headlines (\textcolor, \fbox),
where I guess the latex directive can not work. Is there any solutions
for this situation or any better way to colorize the text while also
support to export to other target (e.g. html)?
next prev parent reply other threads:[~2011-05-12 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 13:09 [beamer] a bug in exporting zwz
2011-05-12 7:12 ` Eric S Fraga
2011-05-12 13:26 ` zwz [this message]
2011-05-12 22:05 ` Eric S Fraga
2011-05-13 9:40 ` Eric S Fraga
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=87liyct5h9.fsf@gmail.com \
--to=zhangweize@gmail.com \
--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).