From: Eli Zaretskii <eliz@gnu.org>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 24179@debbugs.gnu.org
Subject: bug#24179: 24179
Date: Thu, 11 Aug 2016 22:55:58 +0300 [thread overview]
Message-ID: <831t1vf5bl.fsf@gnu.org> (raw)
In-Reply-To: <87twerxiop.fsf@bernoul.li> (message from Jonas Bernoulli on Thu, 11 Aug 2016 20:29:58 +0200)
> 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.
next prev parent reply other threads:[~2016-08-11 19:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 21:15 bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place Alex
2016-08-08 2:39 ` Eli Zaretskii
2016-08-08 5:42 ` Alex
2016-08-08 15:31 ` Eli Zaretskii
2016-08-08 16:35 ` Alex
2016-08-08 16:58 ` Eli Zaretskii
2016-08-08 17:22 ` Alex
2016-08-08 17:35 ` Eli Zaretskii
2016-08-11 15:06 ` Eli Zaretskii
2016-08-11 22:20 ` Alex
2016-08-12 14:17 ` Eli Zaretskii
2016-08-12 22:01 ` Alex
2016-08-13 6:52 ` Eli Zaretskii
2016-08-13 16:59 ` Alex
2016-08-13 17:25 ` Eli Zaretskii
2016-08-14 18:27 ` Eli Zaretskii
2016-08-14 20:05 ` Alex
2016-08-11 16:39 ` bug#24179: 24179 Jonas Bernoulli
2016-08-11 17:15 ` Eli Zaretskii
2016-08-11 18:29 ` Jonas Bernoulli
2016-08-11 19:55 ` Eli Zaretskii [this message]
2016-08-11 20:07 ` Eli Zaretskii
2016-08-11 22:19 ` Jonas Bernoulli
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=831t1vf5bl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24179@debbugs.gnu.org \
--cc=jonas@bernoul.li \
/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.