From mboxrd@z Thu Jan 1 00:00:00 1970 From: timor Subject: Re: Show presence of zero width spaces using overlay Date: Tue, 19 Apr 2016 13:38:28 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1asTzC-0003kU-2j for emacs-orgmode@gnu.org; Tue, 19 Apr 2016 07:38:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1asTzA-0000Wx-Vr for emacs-orgmode@gnu.org; Tue, 19 Apr 2016 07:38:30 -0400 Received: from mail-wm0-x243.google.com ([2a00:1450:400c:c09::243]:33098) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1asTzA-0000Wl-OU for emacs-orgmode@gnu.org; Tue, 19 Apr 2016 07:38:28 -0400 Received: by mail-wm0-x243.google.com with SMTP id y144so4346194wmd.0 for ; Tue, 19 Apr 2016 04:38:28 -0700 (PDT) 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" To: mail@nicolasgoaziou.fr Cc: emacs-orgmode@gnu.org Hello Nicolas, 2016-04-19 12:16 GMT+02:00 Nicolas Goaziou : > Actually, this is not really a specification of the problem, which is > quite tricky. The list of characters is but one part of it. Another part > is where escaping should be allowed. Note that allowing to escape > everywhere would be terrible, if only performance-wise. The last part is > about handling it at the parser level (there's also the fontification, > which doesn't use the parser ATM). Good points. I don't understand enough org mode internals to judge how much effort is needed on which level for things like this. Maybe it is viable to start defining and implementing some obvious cases, which can later be generalized into a rule, so that code has not to be rewritten on every level at once. In light of this, I can think of defining the case that bugged me the most like this: In plain-text parts of org documents (i.e. that would be exported as the content of

attributes in html, or to plain text paragraphs in Markdown, etc.), there shall be a way to treat strings in the same way as the surrounding plain text, which would otherwise be handled by org-mode in a special way. Does that help? regards, timor