From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64960@debbugs.gnu.org
Subject: bug#64960: Documentation for copy-sequence
Date: Mon, 31 Jul 2023 02:31:18 +0000 [thread overview]
Message-ID: <JLhZ56NUvsrDzqeshHwobStJE3X_JfkvtXVyWE8cE64xnGZqyC6ZyoapzpHpivDm0apbRqTJiJp_2dvt3rcAVtxa8B5KhiV8x1zw0xpN6-Y=@proton.me> (raw)
In-Reply-To: <83ila03jnr.fsf@gnu.org>
------- Original Message -------
On Monday, July 31st, 2023 at 2:21 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 30 Jul 2023 19:20:45 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: 64960@debbugs.gnu.org
> >
> > > As the doc string says: the elements are not copied. You get a new
> > > sequence whose elements are shared with the original one.
> >
> > So it returns a copy but elements are not copied. So what happens exactly ?
> > You get a reference to the original ?
>
>
> Yes.
>
> > When I modify the copy, the original remains intact.
>
>
> No, if you modify an element of the copy, the corresponding element of
> the original is also changed. That's what "shared" means.
Except for strings
next prev parent reply other threads:[~2023-07-31 2:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 16:42 bug#64960: Documentation for copy-sequence uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-30 18:36 ` Eli Zaretskii
2023-07-30 19:20 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-30 19:59 ` Dmitry Gutov
2023-07-30 20:09 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-30 20:15 ` Dmitry Gutov
2023-07-30 20:41 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-31 1:13 ` Drew Adams
2023-07-31 1:22 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-31 1:36 ` Drew Adams
2023-07-31 1:50 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-31 2:21 ` Eli Zaretskii
2023-07-31 2:31 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-31 5:24 ` Michael Heerdegen
2023-07-31 6:19 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-01 3:56 ` Michael Heerdegen
2023-08-13 4:27 ` Michael Heerdegen
2023-08-14 10:14 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-14 23:46 ` Michael Heerdegen
2023-08-15 0:43 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-15 23:28 ` Michael Heerdegen
2023-08-16 4:35 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 15:55 ` Stefan Kangas
2023-07-31 14:34 ` Drew Adams
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='JLhZ56NUvsrDzqeshHwobStJE3X_JfkvtXVyWE8cE64xnGZqyC6ZyoapzpHpivDm0apbRqTJiJp_2dvt3rcAVtxa8B5KhiV8x1zw0xpN6-Y=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=64960@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=uzibalqa@proton.me \
/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).