all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 17507@debbugs.gnu.org, eli@barzilay.org
Subject: bug#17507: Documentation for `add-text-property' and relatives
Date: Sat, 17 Aug 2019 09:47:18 +0300	[thread overview]
Message-ID: <83pnl4nv9l.fsf@gnu.org> (raw)
In-Reply-To: <87sgq0q3l9.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Fri, 16 Aug 2019 13:04:34 -0700)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Barzilay <eli@barzilay.org>,  17507@debbugs.gnu.org
> Date: Fri, 16 Aug 2019 13:04:34 -0700
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > In Emacs, text properties are stored separately from the text itself.
> > In particular, text properties of a string are not part of the string
> > text, they live in a separate structure, and a string only maintains a
> > reference to that structure.
> 
> Well, isn't that the same thing conceptually as the properties being in
> the string object?

It depends on your concepts.  I'm trying to determine which part of
the related concepts contributed to the confusion reported in the bug
report.





  reply	other threads:[~2019-08-17  6:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  6:25 bug#17507: Documentation for `add-text-property' and relatives Eli Barzilay
2019-08-14 23:57 ` Lars Ingebrigtsen
2019-08-15  3:41   ` Eli Barzilay
2019-08-15 14:30     ` Eli Zaretskii
2019-08-16  1:35       ` Eli Barzilay
2019-08-16  8:46         ` Eli Zaretskii
2019-08-16 20:04           ` Lars Ingebrigtsen
2019-08-17  6:47             ` Eli Zaretskii [this message]
2019-08-17 22:22             ` Richard Stallman
2019-08-16 23:49           ` Eli Barzilay
2019-08-17  6:41             ` Eli Zaretskii
2019-08-17 12:40               ` Eli Barzilay
2019-08-17 12:46                 ` Eli Zaretskii
2019-08-16  1:20     ` 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

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

  git send-email \
    --in-reply-to=83pnl4nv9l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17507@debbugs.gnu.org \
    --cc=eli@barzilay.org \
    --cc=larsi@gnus.org \
    /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.