unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "João Távora" <joaotavora@gmail.com>, "Deus Max" <deusmax@gmx.com>
Cc: 33998@debbugs.gnu.org
Subject: bug#33998: 27.0.50; cl-delete does not delete the first list element
Date: Mon, 7 Jan 2019 09:28:54 -0800 (PST)	[thread overview]
Message-ID: <c56ace54-e44a-4a49-afc7-9d5095f5ac63@default> (raw)
In-Reply-To: <CALDnm52cD73S-5d2URWsXt0q0NOAHhf8HeCEB2+cLEz9PKgRWg@mail.gmail.com>

> So, cumbersome as it is, you should always use:
                               ^^^^^^^^^^^^^
> (setq seq (cl-delete thing seq))

FWIW, this is not really true.

`cl-delete' deletes THING from the
_value_ of SEQ.  You might or you
might not want variable SEQ to have
the updated value.  A variable and
its value are two different things.

IOW, that's one common, and important,
use case, but this is not some
always-do-this rule for users.

The manual takes pains to explain
this stuff carefully.  It's better
to just refer to the manual to help
users understand it.  (And you did
that, which is great.)





  reply	other threads:[~2019-01-07 17:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 13:30 bug#33998: 27.0.50; cl-delete does not delete the first list element Deus Max
2019-01-07 17:13 ` João Távora
2019-01-07 17:28   ` Drew Adams [this message]
2019-01-07 18:04     ` João Távora
2019-01-07 18:14       ` Drew Adams
2019-01-08 13:45         ` João Távora
2019-01-08 18:22           ` Drew Adams
2019-01-08 18:31             ` João Távora
2019-01-08 18:45               ` Drew Adams
2019-01-08 18:57                 ` João Távora
2019-01-08 19:07                   ` Drew Adams
2019-01-08 21:38                     ` João Távora
2019-01-09  1:30                       ` Drew Adams
2019-01-07 20:20   ` Deus Max
2019-01-07 20:27     ` Dmitry Gutov
2019-01-07 20:48       ` Deus Max
2019-01-07 21:06       ` João Távora
2019-01-07 22:46         ` Deus Max

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=c56ace54-e44a-4a49-afc7-9d5095f5ac63@default \
    --to=drew.adams@oracle.com \
    --cc=33998@debbugs.gnu.org \
    --cc=deusmax@gmx.com \
    --cc=joaotavora@gmail.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).