From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric S Fraga Subject: Re: [beamer] a bug in exporting Date: Thu, 12 May 2011 23:05:31 +0100 Message-ID: <87tyczlglw.fsf@ucl.ac.uk> References: <87tyd1wfhk.fsf@gmail.com> <87k4dw1jfi.fsf@ucl.ac.uk> <87liyct5h9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:32954) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKlr8-0006NZ-Sd for emacs-orgmode@gnu.org; Fri, 13 May 2011 02:28:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QKlr7-0006pC-RX for emacs-orgmode@gnu.org; Fri, 13 May 2011 02:28:10 -0400 Received: from vscane-b.ucl.ac.uk ([144.82.108.141]:36694) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKlr7-0006oy-Lq for emacs-orgmode@gnu.org; Fri, 13 May 2011 02:28:09 -0400 In-Reply-To: <87liyct5h9.fsf@gmail.com> (zwz's message of "Thu, 12 May 2011 21:26:26 +0800") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: zwz Cc: emacs-orgmode@gnu.org zwz writes: > Eric S Fraga writes: > >> zwz 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 The easiest solution would be to save the text as a "box" in latex and use that box within the headline as the latter would be a simple latex directive that org would have no problem with. I don't have my latex book handy but something along the lines of the following should work: --8<---------------cut here---------------start------------->8--- #+latex: \newsavebox{\complexexpression} #+latex: \sbox{\complexexpression}{\fbox{\fbox{(*\fbox{\fbox{(*\fbox{x()})}[]})}()}} * a headline with \usebox{\letterhead} --8<---------------cut here---------------end--------------->8--- Note that I am not particularly experienced in the use of latex boxes... > or any better way to colorize the text while also > support to export to other target (e.g. html)? No idea, sorry. Maybe others can help here. However, for code blocks *not* in headlines, you could use source code blocks (#+begin_src ... #+end_src) but I'm not sure how they export to other targets. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.274.gd6aba)