From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: The + character creating strike-through markup within in-line
 literal / code blocks
Date: Sun, 24 Jun 2018 10:24:48 +0200
Message-ID: <876028twvj.fsf@nicolasgoaziou.fr>
References: <20180624075750.rw4ufcyv2ywbtcdj@s70206.gridserver.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37128)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1fX0KO-0001w1-G5
	for emacs-orgmode@gnu.org; Sun, 24 Jun 2018 04:24:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1fX0KJ-0006k0-IK
	for emacs-orgmode@gnu.org; Sun, 24 Jun 2018 04:24:56 -0400
Received: from relay7-d.mail.gandi.net ([217.70.183.200]:36227)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mail@nicolasgoaziou.fr>)
	id 1fX0KJ-0006ht-Au
	for emacs-orgmode@gnu.org; Sun, 24 Jun 2018 04:24:51 -0400
In-Reply-To: <20180624075750.rw4ufcyv2ywbtcdj@s70206.gridserver.com> (John
	Magolske's message of "Sun, 24 Jun 2018 00:57:51 -0700")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: John Magolske <listmail@b79.net>
Cc: emacs-orgmode@gnu.org

Hello,

John Magolske <listmail@b79.net> writes:

> I'd like to enter some in-line literal code in an org document
> covering OCaml. For example, in this:
>
>     in the expression (x +. y) the +. is a function ...
>
> to show in-line code as literal I tried:
>
>     in the expression =(x +. y)= the =+.= is a function ...
>
> being under the impression that bracketing text with = would enclose
> everything within to be literal. But what's happening -- as evidenced
> by syntax coloring -- is that the first and second + characters here
> create a strike-through region from the middle of one literal region
> to the middle of the other. With (setq org-hide-emphasis-markers t)

It happens because syntax coloring is a bit dumb. It uses regexps but
not the parser. However, if you try, e.g., to export the document, the
plus signs will not be treated as markers.

> Is there some way to get the + to show up as literal within in-line
> sections enclosed by = or ~ ? I suppose I could do something like:
>
>     in the expression src_ocaml{(a +. b)} the src_ocaml{(+.)} is a function ...
>
> But was hoping to use the more succinct = or ~ syntax.

You could insert a zero-width space between "+" and ".", in either or
both occurrences.

> Also tried to remove strike-through emphasis altogether by commenting
> out the strike-through section in org-emphasis-alist like so:
>
> (setq org-emphasis-alist
>       (quote
>        (("*" bold)
>         ("/" italic)
>         ("_" underline)
>         ("=" org-verbatim verbatim)
>         ("~" org-code verbatim)
>         ("+" nil)
>         ;; ("+" (:strike-through t))
>         )))
>
> Then re-started Emacs, but am still having the above issues.

You could try to remove ("+" ...) completely from the variable and
restart Emacs.

Regards,

-- 
Nicolas Goaziou