From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: =?UTF-8?B?UmU6IG9yZyArIGJlYW1lcjogSG93IHRvIGdldCBAxaBAIHRvIGNy?= =?UTF-8?B?ZWF0ZSBcYWxlcnQ/?= Date: Wed, 02 May 2012 13:39:24 +0200 Message-ID: <87lilarevn.fsf@gmail.com> References: <28711.1335922639@alphaville> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:53298) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SPXwr-00033M-Rf for emacs-orgmode@gnu.org; Wed, 02 May 2012 07:42:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SPXwl-0003u4-Cs for emacs-orgmode@gnu.org; Wed, 02 May 2012 07:42:21 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:58818) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SPXwl-0003tt-44 for emacs-orgmode@gnu.org; Wed, 02 May 2012 07:42:15 -0400 Received: by werj55 with SMTP id j55so421718wer.0 for ; Wed, 02 May 2012 04:42:12 -0700 (PDT) In-Reply-To: <28711.1335922639@alphaville> (Nick Dokos's message of "Tue, 01 May 2012 21:37:19 -0400") 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: nicholas.dokos@hp.com Cc: Richard Stanton , "emacs-orgmode@gnu.org" Hello, Nick Dokos writes: > Richard Stanton wrote: > >> I've just started using orgmode to create Beamer presentations, and have a >> question. >> >> In the worg documentation >> (http://orgmode.org/worg/org-tutorials/org-beamer/tutorial.html), it gives >> an example of how enclosing text in "@" signs is supposed to result in >> highlighted red text. When I try it, I get text surrounded by two "@" >> signs... >> >> Following suggestions from this list back in 2010, I tried customizing >> org-export-latex-emphasis-alist to >> >> Value: (("*" "\\textbf{%s}" nil) >> ("/" "\\emph{%s}" nil) >> ("_" "\\underline{%s}" nil) >> ("+" "\\st{%s}" nil) >> ("=" "\\protectedtexttt" t) >> ("~" "\\verb" t) >> ("@" "\\alert{%s}" nil)) >> >> >> but this doesn't seem to help either. >> >> Can anyone tell me how to get this working? >> > > You also need to customize org-emphasis-alist. > > > > Not sure whether this qualifies as a bug or not. It probably does but > even so, it's unlikely to be fixed and that's probably a *good* thing: > IMNSHO, these interfaces are about the clunkiest to be found in org: they > are very "heavy" for the result they produce. > > I hope the new exporter will clean up this area, even at the price of > backward incompatibility (says he, knowing that any such will not affect > him :-]) More or less. Markers are hard coded in the parser. For example, *text* is parsed as (bold (... some properties...) "text") without looking at `org-emphasis-alist'. Then, it's up to each exporter to produce something meaningful with `bold', `italic' `underline', `strike-through', `code' and `verbatim' markup. For a beamer back-end (which is not written yet), I'd suggest to treat `bold' as "\\alert{%s}", for example. Unfortunately, the parser assumes `org-emph-re' is a defconst. I'd like to remove dependency on that variable anyway, but it's difficult to create a perfect test. For example, the following one is a bit naive: #+begin_src emacs-lisp (and (save-excursion (if (bolp) (looking-at "\\*\\w") (backward-char) (looking-at "\\W\\*\\w"))) (save-excursion (re-search-forward "\\w\\*\\(\\W\\|$\\)" paragraph-limit t))) #+end_src Regards, -- Nicolas Goaziou