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: Sun, 27 May 2018 21:50:41 +0200 [thread overview]
Message-ID: <87y3g43mjy.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87muwlt6c1.fsf@gmail.com> (Aaron Ecay's message of "Sun, 27 May 2018 17:24:14 +0100")
Hello,
Aaron Ecay <aaronecay@gmail.com> writes:
> OTOH, we need to provide a way to edit those curly braces. I have just
> pushed commit 102832e66 to the master branch. That will cause any
> sub/superscript under the point to have its font lock properties
> removed, so that the braces will become visible for editing. It is
> modeled after a similar feature in emacs built-in
> prettify-symbols-mode.
>
> So, I think that should address your usecase.
As far as the initial problem is concerned, this is an issue with
indirect buffers, a feature that is not well considered even by Emacs
developers. It has clear limitations.
On the other hand, I agree that editing sub/superscripts is not optimal.
In particular, hiding braces and using skeleton pairs for curly brackets
is not a nice editing experience. It would be nice if we could make it
smoother.
However, your fix is not great at all. It was discussed on this ML,
about square brackets in links: it causes "jumpings" during editing,
which some users, including me, find annoying. Even if it was optional,
it would need to be discussed beforehand.
Also, we are in feature freeze for Org 9.2, so this would need, in any
case, to wait for the release.
As a consequence, would you mind reverting the patches related to this
feature?
Thank you.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-05-27 19:50 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 [this message]
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
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=87y3g43mjy.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).