From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Sergey Organov <sorganov@gmail.com>
Cc: "Daniel Martín" <mardani29@yahoo.es>, emacs-devel@gnu.org
Subject: Re: Tweaking save-some-buffers-action-alist
Date: Fri, 18 Jun 2021 19:02:49 -0400 [thread overview]
Message-ID: <jwv35teaiaf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878s37j857.fsf@osv.gnss.ru> (Sergey Organov's message of "Fri, 18 Jun 2021 22:16:20 +0300")
> Is `nconc` safe here, or should I `copy-seq` the original and modify
> that instead?
The general rule is: If you don't know, then it's not safe.
[ and indeed, it's not safe in this particular case. ]
Stefan
next prev parent reply other threads:[~2021-06-18 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 16:12 Tweaking save-some-buffers-action-alist Sergey Organov
2021-06-17 21:55 ` Daniel Martín
2021-06-18 19:16 ` Sergey Organov
2021-06-18 23:02 ` Stefan Monnier [this message]
2021-06-19 12:31 ` Sergey Organov
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=jwv35teaiaf.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
--cc=sorganov@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).