From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xiha Subject: Re: Questions about exporting: subtitle, level formating, custom highlight markers error Date: Tue, 28 Jul 2015 13:38:56 +0200 Message-ID: <55B769D0.8060306@laposte.net> References: <55B4DAEC.7030805@laposte.net> <87egjugfry.fsf@ucl.ac.uk> <55B63847.5050101@laposte.net> <871tftprsd.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------010903020502040103050909" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34897) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZK3CU-0002cU-OW for emacs-orgmode@gnu.org; Tue, 28 Jul 2015 07:37:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZK3CR-0004yL-Cl for emacs-orgmode@gnu.org; Tue, 28 Jul 2015 07:37:38 -0400 Received: from smtpoutz29.laposte.net ([194.117.213.104]:60290 helo=smtp.laposte.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZK3CR-0004xQ-12 for emacs-orgmode@gnu.org; Tue, 28 Jul 2015 07:37:35 -0400 Received: from smtp.laposte.net (localhost [127.0.0.1]) by lpn-prd-vrout017 (Postfix) with ESMTP id A5FBC9DF566 for ; Tue, 28 Jul 2015 13:37:33 +0200 (CEST) Received: from lpn-prd-vrin001 (unknown [10.128.63.2]) by lpn-prd-vrout017 (Postfix) with ESMTP id A30359DF562 for ; Tue, 28 Jul 2015 13:37:33 +0200 (CEST) Received: from lpn-prd-vrin001 (localhost [127.0.0.1]) by lpn-prd-vrin001 (Postfix) with ESMTP id 932F5365C69 for ; Tue, 28 Jul 2015 13:37:33 +0200 (CEST) Received: from [192.168.1.12] (ptr-178-51-32-206.dyn.mobistar.be [178.51.32.206]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lpn-prd-vrin001 (Postfix) with ESMTPSA id 182DA365C38 for ; Tue, 28 Jul 2015 13:37:32 +0200 (CEST) In-Reply-To: <871tftprsd.fsf@ucl.ac.uk> 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: emacs-orgmode@gnu.org This is a multi-part message in MIME format. --------------010903020502040103050909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Thanks Sebastien and Eric, > On Tuesday, 28 Jul 2015 at 09:24, Sebastien Vauban wrote: > > Eric S Fraga ucl.ac.uk> writes: > > [...] > > >> You can always use macros instead? Maybe, if I knew how. I haven't used macros before. I read this=20 and tried #+MACRO: hi =B7$1=B7 Let's {{{hi(test)}}} this. but unsurprisingly that gives the same export error, and moreover within=20 Org does not show the 'highlight' formatting I associated with =B7, but=20 rather the macro formatting. Or did you mean to simply use the fact that any macro gets 'highlighted'=20 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=20 =20 seems more about highlighting particular words, not /any/ words between=20 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=20 make my writing easier. The highlighting nor the markers have to be in=20 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=20 marking like =B7this=B7 be highlighted within Org, yet be exported=20 literally, without highlighting (i.e. '=B7' is treated just like any old=20 character by the exporter)? cheers --------------010903020502040103050909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 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 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
--------------010903020502040103050909--