unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 31067@debbugs.gnu.org
Subject: bug#31067: 27.0.50; After-string hidden by subsequent invisible text
Date: Fri, 6 Apr 2018 15:39:45 +0000 (UTC)	[thread overview]
Message-ID: <c5808065-9fdd-4c18-9e92-f53d45b78f94@default> (raw)
In-Reply-To: <<83k1tk214a.fsf@gnu.org>>

> You are talking about "covering" here, and I think this discloses the
> mental bias in understanding how before- and after-strings work.
> Unlike most other overlay properties, they do not supply any
> attributes to the characters "covered" by the overlay.  Instead, they
> have effect only at two places: the beginning and the end points of
> the overlay.  Consequently, we check for them only when we are about
> to display something at these two positions.  And in this case, the
> end point is invisible, so we never check any after-strings there.

Sounds like that information is important for a user's mental
model.  Is it presented in the manual?  If not, perhaps it
should be.





  parent reply	other threads:[~2018-04-06 15:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  2:28 bug#31067: 27.0.50; After-string hidden by subsequent invisible text Stefan Monnier
2018-04-05  9:49 ` Eli Zaretskii
2018-04-05 12:23   ` Stefan Monnier
2018-04-05 13:38     ` Eli Zaretskii
2018-04-05 15:55       ` Stefan Monnier
2018-04-05 18:00         ` Eli Zaretskii
2018-04-05 19:15           ` Stefan Monnier
2018-04-06  8:24             ` Eli Zaretskii
2018-04-06 12:28               ` Stefan Monnier
2018-04-06 13:11                 ` Eli Zaretskii
     [not found]             ` <<83k1tk214a.fsf@gnu.org>
2018-04-06 15:39               ` Drew Adams [this message]
2018-04-06 17:10                 ` Eli Zaretskii
     [not found] <<jwvmuyi9yj8.fsf@iro.umontreal.ca>

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c5808065-9fdd-4c18-9e92-f53d45b78f94@default \
    --to=drew.adams@oracle.com \
    --cc=31067@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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.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).