unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sun, 30 Jul 2023 19:20:45 +0000	[thread overview]
Message-ID: <PmGKU6vqjN1izFYWTP3QoUh2TVBtQxtOSPtUnCOlM58FswUVZA8PUiy7cxFq5IggQeXH0xe9c3dI6VnSU9mCOgFgomJ7h8bR1CZntYBnfCI=@proton.me> (raw)
In-Reply-To: <83leex2qmn.fsf@gnu.org>






Sent with Proton Mail secure email.

------- Original Message -------
On Monday, July 31st, 2023 at 6:36 AM, Eli Zaretskii <eliz@gnu.org> wrote:


> > Date: Sun, 30 Jul 2023 16:42:28 +0000
> > From: uzibalqa via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" bug-gnu-emacs@gnu.org
> > 
> > Have been reading the documentation for "copy-sequence". The description,
> > specifically
> > 
> > "The elements of a list, vector or record are not copied; they are
> > shared with the original."
> > 
> > is not very clear about what it does and what one gets.
> 
> 
> 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 ?  When I modify the copy, the original 
remains intact.  It would help if the description in broadened, it is currently
too cryptic.





  reply	other threads:[~2023-07-30 19:20 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 [this message]
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
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='PmGKU6vqjN1izFYWTP3QoUh2TVBtQxtOSPtUnCOlM58FswUVZA8PUiy7cxFq5IggQeXH0xe9c3dI6VnSU9mCOgFgomJ7h8bR1CZntYBnfCI=@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).