all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Barzilay <eli@barzilay.org>
Cc: 17507@debbugs.gnu.org
Subject: bug#17507: Documentation for `add-text-property' and relatives
Date: Thu, 15 Aug 2019 18:20:33 -0700	[thread overview]
Message-ID: <875zmxsy72.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CALO-guvv0VYEKxP9tJ0anFAsEntVqsKxgM3CoTtRN2EUhUKpBg@mail.gmail.com> (Eli Barzilay's message of "Thu, 15 Aug 2019 06:41:17 +0300")

Eli Barzilay <eli@barzilay.org> writes:

> Um...  Note that I referred *explicitly* to other lisps and schemes.
> The assumption that I'm talking about would hold for people who are
> used to CL too: a string is indeed more than just a pointer bytes with
> a NUL at the end, yet there is no way to change a *property* of "foo"
> and end up with #("foo" stuff...).

If there were a way to put properties on string objects in a Common Lisp
implementation, I would expect that it would work just as it does in
Emacs: Not wrapping the string in some other object, but just extend the
object itself.

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





      parent reply	other threads:[~2019-08-16  1:20 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
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 [this message]

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=875zmxsy72.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=17507@debbugs.gnu.org \
    --cc=eli@barzilay.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.