From: Dmitry Gutov <dgutov@yandex.ru>
To: David Fussner <dfussner@googlemail.com>, 52734@debbugs.gnu.org
Subject: bug#52734: 28.0.90; [PATCH] xref-backend-definitions in etags.el duplicates list
Date: Fri, 24 Dec 2021 02:25:47 +0200 [thread overview]
Message-ID: <1d482bb8-41fc-5446-b655-cd41fb23e8a5@yandex.ru> (raw)
In-Reply-To: <CADF+Rtj96R5c5rn4N8TM_Mvf9ctgqQQF5N=4uEwjfc62yzrxpg@mail.gmail.com>
Hi!
On 22.12.2021 18:01, David Fussner via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
> The variable is new in 28.1, so I thought the bug might want fixing on
> this branch. In my testing, cl-delete appears not to delete ITEMs from
> SEQ if such deletion would leave SEQ empty. I can't find this behavior
> documented anywhere, but I may be looking in the wrong places.
The thing about cl-delete-if is it (like other sequence functions) has
the changed sequence in its return value (which the piece of code under
discussion leaves unused -- a brain fart on my part).
As a destructive function, it also modifies the original structure, but
when the variable is still pointing at the first link of the linked
list, the behavior is basically unpredictable. Even though it might look
right most of the time under usual conditions.
See a different patch in the other email.
prev parent reply other threads:[~2021-12-24 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 15:01 bug#52734: 28.0.90; [PATCH] xref-backend-definitions in etags.el duplicates list David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-23 9:12 ` Eli Zaretskii
2021-12-24 0:27 ` Dmitry Gutov
2021-12-24 7:08 ` Eli Zaretskii
2021-12-24 13:09 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-24 13:20 ` Eli Zaretskii
2021-12-24 13:27 ` Dmitry Gutov
2021-12-24 0:25 ` Dmitry Gutov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1d482bb8-41fc-5446-b655-cd41fb23e8a5@yandex.ru \
--to=dgutov@yandex.ru \
--cc=52734@debbugs.gnu.org \
--cc=dfussner@googlemail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.