From: Michael Heerdegen <michael_heerdegen@web.de>
To: uzibalqa <uzibalqa@proton.me>
Cc: 64960@debbugs.gnu.org, eliz@gnu.org
Subject: bug#64960: Documentation for copy-sequence
Date: Tue, 15 Aug 2023 01:46:37 +0200 [thread overview]
Message-ID: <87v8dhp4pu.fsf@web.de> (raw)
In-Reply-To: <g8dwwfCT_7pDP7UnXs5mHXZbQ147SUror8WF5sYnUyD1lNmTjkryZigcbyPdKPGd4zWK8mCNUZ6Iti4RgK5r3Lnz5GrZOd8ibX4twM0jXAI=@proton.me> (uzibalqa@proton.me's message of "Mon, 14 Aug 2023 10:14:52 +0000")
uzibalqa <uzibalqa@proton.me> writes:
> Although I understand what it does, I om not sure if it would benefit
> about some of the details we discussed.
What in particular? A lot of the stuff discussed is a direct
consequence of the copy being a new sequence object whose elements have
not been copied. The manual tries to describe some implications.
Or should we try to find a better wording (to make more clear that
"modify" doesn't mean "replace") - for what part(s)? What concretely
would have helped you to understand that part of the manual better?
What parts of the documentation have you read so far?
Thx,
Michael.
next prev parent reply other threads:[~2023-08-14 23:46 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
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 [this message]
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=87v8dhp4pu.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).