From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>, Van L <van@scratch.space>
Cc: org-mode-email <emacs-orgmode@gnu.org>
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 [thread overview]
Message-ID: <878t83u77d.fsf@gmail.com> (raw)
In-Reply-To: <87d0xg3jns.fsf@nicolasgoaziou.fr>
Hi Nicolas,
2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen:
>
> Aaron Ecay <aaronecay@gmail.com> writes:
>
>> Of course, done in c32938b7f. I did not realize how the freeze for 9.2
>> was working.
>
> Thank you.
>
> 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.
>
> 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ʼt 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ʼs
optionality, rather than needing our own).
--
Aaron Ecay
next prev parent reply other threads:[~2018-05-28 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 11:14 unable to edit indirect-buffer in fundamental mode without losing pretty printing in base buffer org mode Van L
2018-05-27 16:24 ` Aaron Ecay
2018-05-27 19:50 ` Nicolas Goaziou
2018-05-27 20:37 ` Aaron Ecay
2018-05-27 20:53 ` Nicolas Goaziou
2018-05-28 15:32 ` Aaron Ecay [this message]
2018-05-30 11:40 ` Nicolas Goaziou
2018-05-31 3:24 ` Van L
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t83u77d.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=van@scratch.space \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).