unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: search-invisible and friends
Date: Fri, 11 Sep 2020 13:37:05 +0200	[thread overview]
Message-ID: <874ko41r4u.fsf@gnus.org> (raw)
In-Reply-To: <83een9kdkl.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Sep 2020 15:42:50 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> The rest of the section makes a point of saying, for each display
> property kind, whether it is replacing or not.

Are we looking at different section of the manual?  The rest of the node
(for me) just says:

---
This function gives each of the first ten characters in the buffer a
‘display’ property which is a string ‘"A"’, but they don’t all get the
same string object.  The first two characters get the same string
object, so they are replaced with one ‘A’; the fact that the display
property was assigned in two separate calls to ‘put-text-property’ is
irrelevant.  Similarly, the next two characters get a second string
(‘concat’ creates a new string object), so they are replaced with one
‘A’; and so on.  Thus, the ten characters appear as five A’s.
---



-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  parent reply	other threads:[~2020-09-11 11:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 12:39 search-invisible and friends Lars Ingebrigtsen
2020-09-09 14:43 ` Eli Zaretskii
2020-09-10 12:38   ` Lars Ingebrigtsen
2020-09-10 14:29     ` Eli Zaretskii
2020-09-10 15:03       ` Stefan Monnier
2020-09-10 18:11         ` Juri Linkov
2020-09-10 20:47           ` Stefan Monnier
2020-09-10 22:10             ` Ihor Radchenko
2020-09-10 22:55               ` Stefan Monnier
2020-09-11  1:03                 ` Ihor Radchenko
2020-09-11  1:42                   ` Stefan Monnier
2020-09-11  5:35         ` Yuri Khan
2020-09-11 11:46           ` Lars Ingebrigtsen
2020-09-11 12:29             ` Eli Zaretskii
2020-09-11 14:40               ` Lars Ingebrigtsen
2020-09-11 14:50                 ` Eli Zaretskii
2020-09-11 14:56                   ` Lars Ingebrigtsen
2020-09-11 15:14                     ` Eli Zaretskii
2020-09-12 11:48                       ` Lars Ingebrigtsen
2020-09-12 15:29               ` Stefan Monnier
2020-09-11 11:41         ` Lars Ingebrigtsen
2020-09-10 18:12     ` Drew Adams
2020-09-09 15:10 ` Stefan Monnier
2020-09-09 15:26   ` Eli Zaretskii
2020-09-09 16:11     ` Stefan Monnier
2020-09-09 16:25       ` Eli Zaretskii
2020-09-10 12:35         ` Lars Ingebrigtsen
2020-09-10 12:42           ` Eli Zaretskii
2020-09-10 13:21             ` Stefan Monnier
2020-09-10 14:42               ` Eli Zaretskii
2020-09-11 11:37             ` Lars Ingebrigtsen [this message]
2020-09-11 12:25               ` Eli Zaretskii
2020-09-09 18:48 ` Juri Linkov
2020-09-10 12:01   ` Lars Ingebrigtsen

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=874ko41r4u.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).