[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24179: 24179
From: |
Eli Zaretskii |
Subject: |
bug#24179: 24179 |
Date: |
Thu, 11 Aug 2016 22:55:58 +0300 |
> From: Jonas Bernoulli <jonas@bernoul.li>
> Cc: 24179@debbugs.gnu.org
> Date: Thu, 11 Aug 2016 20:29:58 +0200
>
> > It looks like I misremembered: before-strings cannot benefit from this
> > feature, because they don't conceal any buffer positions.
>
> The manual mentions "before-strings" in the description of "cursor".
> That should probably be changed in that case.
There's a subtlety here: the before-strings and after-strings can
either conceal some buffer text (i.e. be displayed instead of that
text) or not. The cursor property will only be in effect in the
former case, whereas magit-bame uses the latter.
So the manual is not wrong, it just doesn't reveal this subtlety.
- bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place, (continued)
- bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place, Eli Zaretskii, 2016/08/12
- bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place, Alex, 2016/08/12
- bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place, Eli Zaretskii, 2016/08/13
- bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place, Alex, 2016/08/13
- bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place, Eli Zaretskii, 2016/08/13
- bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place, Eli Zaretskii, 2016/08/14
- bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place, Alex, 2016/08/14
bug#24179: 24179, Jonas Bernoulli, 2016/08/11