From: Lars Ingebrigtsen <larsi@gnus.org>
To: Okam <okamsn@protonmail.com>
Cc: 50053@debbugs.gnu.org
Subject: bug#50053: [PATCH]: Add new macro `seq-setq`
Date: Sat, 14 Aug 2021 14:18:15 +0200 [thread overview]
Message-ID: <87sfzcte2g.fsf@gnus.org> (raw)
In-Reply-To: <847b7ede-bcb5-1bd1-b91e-f1134a91fe52@protonmail.com> (Okam's message of "Sat, 14 Aug 2021 01:25:40 +0000")
Okam <okamsn@protonmail.com> writes:
> This patch adds the macro `seq-setq`, which is the `setq` version of
> `seq-let`.
>
> This builds upon the new macro `pcase-setq`, which was added in #49809.
Makes sense to me; applied to Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-08-14 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 1:25 bug#50053: [PATCH]: Add new macro `seq-setq` Okam via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-14 12:18 ` Lars Ingebrigtsen [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
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=87sfzcte2g.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50053@debbugs.gnu.org \
--cc=okamsn@protonmail.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).