From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 5971@debbugs.gnu.org
Subject: bug#5971: 23.1.95; `delete' modifies default value instead of buffer-local value
Date: Sun, 18 Apr 2010 22:24:42 -0700 [thread overview]
Message-ID: <A041D87110D144EFA9432E5AAC7D9B70@us.oracle.com> (raw)
In-Reply-To: <jwvhbn8ul47.fsf-monnier+emacs@gnu.org>
> > This doesn't seem right to me.
>
> Why not? That's the whole reason for the existence of two functions:
> `delete' and `remove'.
I'm aware that `delete' modifies the list structure and `remove' uses a copy.
What I don't understand is the interaction with a default value instead of a
buffer-local value. Why would `delete' cause the behavior described?
The same code BTW uses `nconc' apparently without causing such
modify-the-default-value behavior:
(setq wide-n-restrictions
(nconc (nthcdr arg wide-n-restrictions) latest))
What is the relation between `delete's modification of the list structure of a
cons that is a buffer-local value of a variable and its (apparent) modification
of the default value of the variable?
next prev parent reply other threads:[~2010-04-19 5:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 2:41 bug#5971: 23.1.95; `delete' modifies default value instead of buffer-local value Drew Adams
2010-04-19 4:23 ` Stefan Monnier
2010-04-19 5:24 ` Drew Adams [this message]
2010-04-19 6:25 ` Stefan Monnier
2010-04-19 15:09 ` Drew Adams
2010-04-19 15:56 ` Glenn Morris
2010-04-19 16:05 ` Andreas Schwab
2010-04-19 16:15 ` Drew Adams
2010-04-19 16:31 ` Andreas Schwab
2010-04-19 17:03 ` Drew Adams
2010-04-19 18:42 ` Andreas Schwab
2010-04-19 18:58 ` Drew Adams
2010-04-19 20:18 ` Andreas Schwab
2010-04-19 20:31 ` Drew Adams
2010-04-19 20:38 ` Andreas Schwab
2010-04-19 22:06 ` Drew Adams
2010-04-21 7:29 ` Kevin Rodgers
2010-04-21 11:58 ` Drew Adams
2011-07-09 5:47 ` Glenn Morris
2010-04-19 15:09 ` bug#5971: - reopen 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=A041D87110D144EFA9432E5AAC7D9B70@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=5971@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).