emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 22:53:11 +0200	[thread overview]
Message-ID: <87d0xg3jns.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87h8msu96w.fsf@gmail.com> (Aaron Ecay's message of "Sun, 27 May 2018 21:37:11 +0100")

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.

>> 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,

Not at all. If you're fontifying sub/superscripts, it changes size of
the whole script (e.g., a_{0123456789}), so it can be obnoxious.

Besides, even if a single character changes its size, the whole line
"jumps". This is distracting.

> whereas for links it is much more (as the whole link becomes un- and
> re-hidden).

Actually, that was only square brackets around the link, not the link
itself, so there was really 2 characters involved. But, see above.

> 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.

We can of course discuss it on the ML, but it would be nice to make
clear what is the problem to solve first.

  reply	other threads:[~2018-05-27 20:53 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 [this message]
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=87d0xg3jns.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).