From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: using setq to create lists based on other lists...
Date: Sun, 02 Dec 2018 11:05:08 -0500 [thread overview]
Message-ID: <jwvr2ezj4ur.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: DA4E6CB2-2369-4AC1-B107-FEBC0579F4EE@gmail.com
> When I check "Modifying Existing List Structure" the only things I find of
> any use in my case are setcar/setcdr.
That's because "modifying" is the wrong way to think about it.
That section should start by telling the user that most likely what they
really want to do is something else (i.e. get a similar list structure
with some differences).
> I would certainly have considered that if I had known that setq was
> linking the lists :)
Clearly, "linking the lists" means something to you, but it means
nothing to me, so the manual can't really say something like that.
Stefan
next prev parent reply other threads:[~2018-12-02 16:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 10:53 using setq to create lists based on other lists Jean-Christophe Helary
2018-12-02 15:07 ` Stefan Monnier
2018-12-02 15:41 ` Jean-Christophe Helary
2018-12-02 16:05 ` Stefan Monnier [this message]
2018-12-02 16:23 ` Jean-Christophe Helary
2018-12-02 17:02 ` Stefan Monnier
2018-12-02 17:21 ` Jean-Christophe Helary
2018-12-02 19:11 ` Robert Thorpe
2018-12-02 23:44 ` Jean-Christophe Helary
[not found] ` <mailman.5028.1543765273.1284.help-gnu-emacs@gnu.org>
2018-12-03 13:43 ` Rusi
[not found] <mailman.5010.1543748027.1284.help-gnu-emacs@gnu.org>
2018-12-02 11:21 ` Barry Margolin
2018-12-02 11:51 ` Stephen Berman
2018-12-02 12:22 ` Jean-Christophe Helary
2018-12-02 13:08 ` Stephen Berman
2018-12-02 13:28 ` Jean-Christophe Helary
2018-12-02 14:40 ` Michael Heerdegen
2018-12-02 15:34 ` Jean-Christophe Helary
2018-12-02 15:44 ` Michael Heerdegen
2018-12-02 15:57 ` Jean-Christophe Helary
2018-12-02 15:00 ` Stephen Berman
2018-12-02 15:30 ` Jean-Christophe Helary
[not found] ` <mailman.5026.1543764670.1284.help-gnu-emacs@gnu.org>
2018-12-04 9:00 ` Barry Margolin
2018-12-02 12:03 ` Jean-Christophe Helary
[not found] <mailman.5042.1543777897.1284.help-gnu-emacs@gnu.org>
2018-12-04 9:04 ` Barry Margolin
[not found] ` <(message>
[not found] ` <from>
[not found] ` <Barry>
[not found] ` <Margolin>
[not found] ` <on>
[not found] ` <Tue>
[not found] ` <04>
[not found] ` <Dec>
[not found] ` <2018>
[not found] ` <04:04:52>
2018-12-04 13:56 ` Stefan Monnier
2018-12-05 1:07 ` Robert Thorpe
2018-12-05 2:32 ` Drew Adams
2018-12-05 6:45 ` Jean-Christophe Helary
2018-12-05 8:00 ` Marcin Borkowski
2018-12-05 8:11 ` Jean-Christophe Helary
2018-12-05 14:57 ` Drew Adams
[not found] ` <mailman.5218.1544021892.1284.help-gnu-emacs@gnu.org>
2018-12-05 16:59 ` Barry Margolin
[not found] ` <mailman.5186.1543978155.1284.help-gnu-emacs@gnu.org>
2018-12-05 16:50 ` Barry Margolin
[not found] ` <mailman.5145.1543931778.1284.help-gnu-emacs@gnu.org>
2018-12-05 16:47 ` Barry Margolin
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=jwvr2ezj4ur.fsf-monnier+gmane.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
/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.
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).