unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Robin Tarsiger <rtt@dasyatidae.com>
Cc: emacs-devel@gnu.org
Subject: Re: Ad-hoc list structure tutorializing
Date: Sun, 06 Dec 2020 15:01:21 +0100	[thread overview]
Message-ID: <AM0PR06MB65771D6D3D8ADE46E6E8E5B496CF0@AM0PR06MB6577.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <eead0647-4f53-fed1-c0a3-ceea9e02ecb2@dasyatidae.com> (Robin Tarsiger's message of "Sat, 5 Dec 2020 23:57:01 -0600")

Robin Tarsiger <rtt@dasyatidae.com> writes:

> Richard Stallman wrote:
>> add-to-list is oriented at modifying a variable symbol which need not> be constant.  You can use it with a quoted symbol, of course.
> [etc.]
>
> I will point out more concisely, in case my other message got
> (perhaps rightfully) skipped, that I split off this subthread attempting
> to better describe to Arthur why his new idea for the documentation
> was poorly founded, and preempt certain other related ideas. My rhetorical
> question, intended to help explain why add-to-list exists and is _not_
> simply replaced with other list manipulation forms (in a way which I
> imagined might confuse an elisp novice), was then quoted out of context
> by itself to make it look like I was proposing to do that replacement.
> (I believe this was accidental.) I was _not_ making such a proposal, and
> I gave a longer list of potential reasons why not in the other message.
>
> Since this has become more than cluttered enough already, this is the
> last thing I will post on this topic unless personally asked.
>
> -RTT
Seems like some of my mails never got to the list; I don't see them
myself, but I see them in my out folder. No idea why.

@RTT Anyway, thank you for the explanations, you made it clear why it was
designed the way it was. For what it does, I would illustrate it with a
**List in C, a pointer to a pointer but there are no pointers and
references in Lisp, just symbols and values so it takes a symbol and can
not take a value. What we wish is a pointer to a list. I am not sure but
I think that at least LIST-VAR is better than just SYMBOL, maybe
LIST-SYMBOL; whatever.

@RMS Yes it is old function, but for some peopel it is new. I was just
reading documentation of it and thought it was neither very clear nor
well written: "better be a list" or "quote if if you wish" does not
sound to me as a clear explanation of precondition. Since people have
complained that documentation is incomprehensive, so I just tried to
make it a bit easier to diggest while I was anyway reading it. Didn't
know it would release a storm of comments and proposal for replacement.

Best regards
/a




  reply	other threads:[~2020-12-06 14:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  2:17 Lispref add-to-list - doc is unnecessary convoluted Arthur Miller
2020-12-04  2:27 ` Christopher Dimech
2020-12-04  2:36 ` Robin Tarsiger
2020-12-04  3:29   ` Arthur Miller
2020-12-04  3:35   ` Arthur Miller
2020-12-04  8:35     ` Lars Ingebrigtsen
2020-12-04  8:29 ` Eli Zaretskii
2020-12-04 15:28   ` Arthur Miller
2020-12-04 15:56     ` Robin Tarsiger
2020-12-04 16:14       ` Ad-hoc list structure tutorializing (was: Lispref add-to-list - doc is unnecessary convoluted) Robin Tarsiger
2020-12-04 20:24         ` Ad-hoc list structure tutorializing Stefan Monnier
2020-12-04 21:12           ` Christopher Dimech
2020-12-05  7:45             ` Eli Zaretskii
2020-12-06  5:45               ` Richard Stallman
2020-12-06  5:57                 ` Robin Tarsiger
2020-12-06 14:01                   ` Arthur Miller [this message]
2020-12-06  5:39             ` Richard Stallman
2020-12-04 21:40           ` add-to-list vs cl-pushnew Robin Tarsiger
2020-12-04 21:51             ` Robin Tarsiger
2020-12-04 22:47         ` Sv: Ad-hoc list structure tutorializing (was: Lispref add-to-list - doc is unnecessary convoluted) arthur miller
2020-12-04 17:03     ` Lispref add-to-list - doc is unnecessary convoluted Drew Adams
2020-12-04 17:24       ` arthur miller
2020-12-04 18:02         ` 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=AM0PR06MB65771D6D3D8ADE46E6E8E5B496CF0@AM0PR06MB6577.eurprd06.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=rtt@dasyatidae.com \
    /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).