From: Eli Barzilay <eli@barzilay.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17507@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#17507: Documentation for `add-text-property' and relatives
Date: Fri, 16 Aug 2019 04:35:35 +0300 [thread overview]
Message-ID: <CALO-gutogOwo1V9_CgJVFRoyCnC9O=5_eOZbM0Sr2v2nrLUyUQ@mail.gmail.com> (raw)
In-Reply-To: <83k1beqz6f.fsf@gnu.org>
In lisps you can mutate properties of an object, but you cannot change
the pointer itself. I think that another way to clarify it would be
to say that "foo" is actually shorthand for #("foo") but the #() is
omitted for brevity. But at this point this is subjective enough to
be ignorable...
On Thu, Aug 15, 2019 at 5:30 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Eli Barzilay <eli@barzilay.org>
> > Date: Thu, 15 Aug 2019 06:41:17 +0300
> > Cc: 17507@debbugs.gnu.org
> >
> > 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...).
>
> Can you explain in more detail what did you think was missing from the
> manual? I've read the original report, and I admit I didn't
> understand what was the essence of your difficulty.
>
> Thanks.
--
((x=>x(x))(x=>x(x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
next prev parent reply other threads:[~2019-08-16 1:35 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 [this message]
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
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='CALO-gutogOwo1V9_CgJVFRoyCnC9O=5_eOZbM0Sr2v2nrLUyUQ@mail.gmail.com' \
--to=eli@barzilay.org \
--cc=17507@debbugs.gnu.org \
--cc=eliz@gnu.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.