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: Sun, 27 May 2018 21:37:11 +0100 [thread overview]
Message-ID: <87h8msu96w.fsf@gmail.com> (raw)
In-Reply-To: <87y3g43mjy.fsf@nicolasgoaziou.fr>
Hi Nicolas,
2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen:
[...]
>
> 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?
Of course, done in c32938b7f. I did not realize how the freeze for 9.2
was working.
>
> 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.
I must have missed that discussion. I would say that the “jump” in
this case is only three characters, whereas for links it is much more
(as the whole link becomes un- and re-hidden). I would not like links
to work this way, but for foo-scripts I found it to be quite natural in
my testing. So I hope that we can discuss it (as an optional feature,
certainly) once 9.2 is out.
--
Aaron Ecay
next prev parent reply other threads:[~2018-05-27 20:37 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8msu96w.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.