From: Richard Stallman <rms@gnu.org>
To: "Nicolas P. Rougier \(inria\)" <nicolas.rougier@inria.fr>
Cc: eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Reading text properties from a yanked text
Date: Thu, 01 Dec 2022 18:25:08 -0500 [thread overview]
Message-ID: <E1p0svU-0003h4-LU@fencepost.gnu.org> (raw)
In-Reply-To: <m1ilj0yhus.fsf@inria.fr> (nicolas.rougier@inria.fr)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > Because once again what you pass to text-properties-at is a
> > different
> > string. You are confusing how a string looks on display when
> > inserted into
> > a buffer with another string that just happens to have the same
> > text.
> Thanks to all of you. I think I'm understanding it now. My
> confusion comes from a more complex code that I'm trying to debug
> and I stumble on this specific case/confusion. Back to debug then.
Is there anything in our documentation that we could change to
help people understand this point?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-12-01 23:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 21:35 Reading text properties from a yanked text Nicolas P. Rougier (inria)
2022-11-26 23:03 ` [External] : " Drew Adams
2022-11-27 6:07 ` Nicolas P. Rougier (inria)
2022-11-27 7:08 ` Stefan Monnier
2022-11-26 23:26 ` Gregory Heytings
2022-11-27 6:08 ` Nicolas P. Rougier (inria)
2022-11-27 6:14 ` Eli Zaretskii
2022-11-27 6:16 ` Nicolas P. Rougier (inria)
2022-11-27 7:10 ` Eli Zaretskii
2022-11-27 7:29 ` Nicolas P. Rougier (inria)
2022-12-01 23:25 ` Richard Stallman [this message]
2022-11-27 7:10 ` Gregory Heytings
2022-11-27 7:14 ` Gregory Heytings
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=E1p0svU-0003h4-LU@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nicolas.rougier@inria.fr \
/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.