emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Xiha <xiha@laposte.net>
To: emacs-orgmode@gnu.org
Subject: Re: Questions about exporting: subtitle, level formating, custom highlight markers error
Date: Tue, 28 Jul 2015 13:38:56 +0200	[thread overview]
Message-ID: <55B769D0.8060306@laposte.net> (raw)
In-Reply-To: <871tftprsd.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

Thanks Sebastien and Eric,

> On Tuesday, 28 Jul 2015 at 09:24, Sebastien Vauban wrote:
> > Eric S Fraga <e.fraga <at> ucl.ac.uk> writes:
>
> [...]
>
> >> You can always use macros instead?

Maybe, if I knew how. I haven't used macros before. I read this 
<http://orgmode.org/manual/Macro-replacement.html> and tried

    #+MACRO: hi ·$1·
    Let's {{{hi(test)}}} this.

but unsurprisingly that gives the same export error, and moreover within 
Org does not show the 'highlight' formatting I associated with ·, but 
rather the macro formatting.

Or did you mean to simply use the fact that any macro gets 'highlighted' 
within Org -- so I should use something like #+MACRO: hi $1 ?

> > Or the `font-lock-add-keywords' mechanism?

In what way? What I read here 
<https://www.gnu.org/software/emacs/manual/html_node/elisp/Customizing-Keywords.html> 
seems more about highlighting particular words, not /any/ words between 
particular markers...?

> I think the OP wanted markers that would export, not just stand out in
> the emacs buffer.

Most importantly, I would like to custom-highlight text /within/ Org, to 
make my writing easier. The highlighting nor the markers have to be in 
the exported document. But if they are there, that is icing on the cake.

I figure - perhaps wrongly! - that it should be easiest to have custom 
marking like ·this· be highlighted within Org, yet be exported 
literally, without highlighting (i.e. '·' is treated just like any old 
character by the exporter)?

cheers

[-- Attachment #2: Type: text/html, Size: 2839 bytes --]

  parent reply	other threads:[~2015-07-28 11:37 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 [this message]
2015-07-28 12:05         ` Eric S Fraga
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=55B769D0.8060306@laposte.net \
    --to=xiha@laposte.net \
    --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).