[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Bug? Highlighting inconsistent with export

From: Clément Pit--Claudel
Subject: Re: [O] Bug? Highlighting inconsistent with export
Date: Tue, 30 Aug 2016 12:36:40 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

On 2016-08-30 06:08, Nicolas Goaziou wrote:
> I have no objection to this.

Ok; patch attached :) Here's a test case:


    ⇒ <code>this~~won't~~work</code>

You can see the difference in behaviour by resizing the browser window: the 
second line will break at code boundaries (it uses zero-width spaces) while the 
second line will stay together (it uses word joiners, aka zero-width no-break 

I detailed the change in the commit message.

> However, another option is to get rid of
> `org-emphasis-regexp-components', make every paired "=" character
> trigger verbatim mode and every paired "~" characters trigger code mode,
> but provide a way to escape "=" and "~". It should probably be extended
> to any emphasis markup and special characters like "|", "#"...

I agree, though this seems non-trivial.  Here's another idea (I don't know how 
it compares to other options :): src_<lang>[]{} could be extended to allow 
different delimiters; this would make it more widely usable. For example, the 
following forms would all be equivalent:


This is inspired by LaTeX's \verb syntax, but using paired delimiters.  The 
nice part of this is that it would solve the current issue that makes 
src_<lang> not always usable, namely unmatched curly braces:

    #+PROPERTY: header-args :exports code
    src_elisp{(defun foo () ?})}
    ⇒ <code class="src src-lisp">(defun foo () ?</code>)}

    #+PROPERTY: header-args :exports code
    src_elisp{(defun foo () ?\})} is an ELisp function
    ⇒ <code class="src src-lisp">(defun foo () ?\})</code>

Attachment: 0001-Add-zero-width-spaces-to-org-emphasis-regexp-compone.patch
Description: Text Data

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]