From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: unable to edit indirect-buffer in fundamental mode without losing pretty printing in base buffer org mode Date: Wed, 30 May 2018 13:40:09 +0200 Message-ID: <8736y91iee.fsf@nicolasgoaziou.fr> References: <518DCC34-E435-42F7-A15E-FAE7727033F8@scratch.space> <87muwlt6c1.fsf@gmail.com> <87y3g43mjy.fsf@nicolasgoaziou.fr> <87h8msu96w.fsf@gmail.com> <87d0xg3jns.fsf@nicolasgoaziou.fr> <878t83u77d.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46541) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNzSi-0003EK-E5 for emacs-orgmode@gnu.org; Wed, 30 May 2018 07:40:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNzSf-00023S-8i for emacs-orgmode@gnu.org; Wed, 30 May 2018 07:40:16 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:47109) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fNzSe-00021b-Vj for emacs-orgmode@gnu.org; Wed, 30 May 2018 07:40:13 -0400 In-Reply-To: <878t83u77d.fsf@gmail.com> (Aaron Ecay's message of "Mon, 28 May 2018 16:32:22 +0100") 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: Van L Cc: org-mode-email Hello, Aaron Ecay writes: > +1 on this idea from me. I created a "next" branch that we can merge in master once we're out feature freeze. > I describe the problem as: Org tries to be slightly WYSIWYG in terms of > subscripts (with the relevant configuration settings). But the facade > over the underlying textual markup is imperfect. Users sometimes need > to edit the textual markup. I assume you mean that sub/superscript markers are hidden (i.e., relevant configuration settings for WYSIWYG). But in what cases do users need to edit the textual markup? Can they be avoided ? > The patch I created is based on a very similar emacs feature > (prettify-symbols-mode). (Unlike the org feature, the emacs feature > only font-locks a static list of strings; it doesn=CA=BCt handle subscrip= ts > where the content to be font-locked can vary). Once org supports emacs > 25+ only (is it actually the case already?), We officially support Emacs 24.3, even though at least Emacs 24.4 is expected. > I think it would be a good idea to replace the org-entities > font-locking with the emacs built-in feature. Then my patch could > extend that for subscripts (and we could recycle the core emacs > defcustoms which control the feature=CA=BCs optionality, rather than > needing our own). About entities, we need to be able to distinguish between users entities unrelated to Org, and the fixed set of entities in Org. Otherwise, if can re-use code from Emacs, I'm all for it. Regards, --=20 Nicolas Goaziou