> Nicolas Goaziou writes:
>
> 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 ?
I use the markup to help read language with differing
Hello,
Aaron Ecay 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
Hi Nicolas,
2018ko maiatzak 27an, Nicolas Goaziou-ek idatzi zuen:
>
> Aaron Ecay 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
Aaron Ecay 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
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
Hello,
Aaron Ecay 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
Hi Van,
What you describe is fragile and should not work.
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