From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: unable to edit indirect-buffer in fundamental mode without losing pretty printing in base buffer org mode Date: Mon, 28 May 2018 16:32:22 +0100 Message-ID: <878t83u77d.fsf@gmail.com> References: <518DCC34-E435-42F7-A15E-FAE7727033F8@scratch.space> <87muwlt6c1.fsf@gmail.com> <87y3g43mjy.fsf@nicolasgoaziou.fr> <87h8msu96w.fsf@gmail.com> <87d0xg3jns.fsf@nicolasgoaziou.fr> 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]:34916) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fNK8L-00073s-FG for emacs-orgmode@gnu.org; Mon, 28 May 2018 11:32:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fNK8I-0002Xt-BW for emacs-orgmode@gnu.org; Mon, 28 May 2018 11:32:29 -0400 Received: from mail-wr0-x236.google.com ([2a00:1450:400c:c0c::236]:35703) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fNK8I-0002XH-4x for emacs-orgmode@gnu.org; Mon, 28 May 2018 11:32:26 -0400 Received: by mail-wr0-x236.google.com with SMTP id i14-v6so20889221wre.2 for ; Mon, 28 May 2018 08:32:26 -0700 (PDT) In-Reply-To: <87d0xg3jns.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou , Van L Cc: org-mode-email Hi Nicolas, 2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen: >=20 > Aaron Ecay writes: >=20 >> Of course, done in c32938b7f. I did not realize how the freeze for 9.2 >> was working. >=20 > Thank you. >=20 > BTW, I'm considering creating a "next" branch for pending patches that > I'm refraining to push to master. It could help moving forward. +1 on this idea from me. >=20 > We can of course discuss it on the ML, but it would be nice to make > clear what is the problem to solve first. 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. 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 subscripts where the content to be font-locked can vary). Once org supports emacs 25+ only (is it actually the case already?), 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). --=20 Aaron Ecay