From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 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: Wed, 30 May 2018 13:40:09 +0200 [thread overview]
Message-ID: <8736y91iee.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878t83u77d.fsf@gmail.com> (Aaron Ecay's message of "Mon, 28 May 2018 16:32:22 +0100")
Hello,
Aaron Ecay <aaronecay@gmail.com> 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ʼt handle subscripts
> 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ʼs 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,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-05-30 11:40 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
2018-05-30 11:40 ` Nicolas Goaziou [this message]
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=8736y91iee.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--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).