emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Xiha <xiha@laposte.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Questions about exporting: subtitle, level formating, custom highlight markers error
Date: Tue, 28 Jul 2015 13:05:42 +0100	[thread overview]
Message-ID: <87y4i01o89.fsf@ucl.ac.uk> (raw)
In-Reply-To: <55B769D0.8060306@laposte.net> (xiha@laposte.net's message of "Tue, 28 Jul 2015 13:38:56 +0200")


You need to differentiate between two aspects: highlighting of text
within a org buffer and what happens to text when exported.  In the new
exporter, I don't think you can implement anything that covers both use
cases.

I am not entirely sure what it is you want.  If you want just one of
these, for the former, font-lock-add-keywords is probably what you want
to pursue.  For the latter, you probably want to use a macro with
@@latex:...@@ and/or @@html:...@@ code embedded in the macro to export
the text the way you want it, as in

    #+macro: coloured @@latex:{\color{red} $1}@@

    This is some {{{coloured(text)}}} when exported.
    
HTH,
eric
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-1293-g985420

  reply	other threads:[~2015-07-28 12:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-26 13:04 Questions about exporting: subtitle, level formating, custom highlight markers error Xiha
2015-07-26 18:44 ` Rasmus
2015-07-27  8:34 ` Eric S Fraga
2015-07-27 13:55   ` Xiha
2015-07-27 15:02     ` Eric S Fraga
2015-07-28  7:24       ` Sebastien Vauban
2015-07-28  8:20         ` Eric S Fraga
2015-07-28 11:38       ` Xiha
2015-07-28 12:05         ` Eric S Fraga [this message]
2015-07-28 13:47           ` Xiha
2015-07-28 15:19             ` John Kitchin
2015-07-29 19:32               ` Xiha
2015-07-29 19:51                 ` Marcin Borkowski
2015-07-28 12:25         ` Nick Dokos

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=87y4i01o89.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=xiha@laposte.net \
    /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).