all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>, help-gnu-emacs@gnu.org
Subject: Re: plist-put: destructive?
Date: Sun, 22 Jan 2017 10:08:18 +0000	[thread overview]
Message-ID: <CAArVCkRO-LnYNaijgKzqaMLy-q+=AqJpngCivuLxxCqWq7ZtCQ@mail.gmail.com> (raw)
In-Reply-To: <87tw8rx6he.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> schrieb am So., 22. Jan. 2017 um
01:57 Uhr:

> Drew Adams <drew.adams@oracle.com> writes:
>
> >> Thanks to you both. I'm working with existing plists, so I'll drop
> >> the setqs, that's a relief.
> >
> > Why is it a relief - a relief from what?  What if something reset your
> "existing plist" to nil behind your back?
>
> The code I'm working has many repeated clauses looking like:
>
> (when thing1
>   (setq the-plist (plist-put the-plist :thing thing1)))
>
> A little more complicated than that, but there will be like seven of
> those in a row. Probably I should just write myself a custom
> bulk-conditional-plist-setter macro, probably using the gv setter, but
> for the time being just being able to remove all the "(setq the-plist"
> makes everything easier to read.
>

 You could also write
(cl-callf plist-put the-plist :thing thing1)


  reply	other threads:[~2017-01-22 10:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 19:13 plist-put: destructive? Eric Abrahamsen
2017-01-21  3:25 ` Stefan Monnier
2017-01-21 10:25   ` tomas
2017-01-21 16:41   ` Eric Abrahamsen
2017-01-21 17:13     ` Drew Adams
2017-01-22  0:50       ` Eric Abrahamsen
2017-01-22 10:08         ` Philipp Stephani [this message]
2017-01-22 13:10           ` Eric Abrahamsen
2017-01-22 17:30         ` Stefan Monnier
2017-01-23  0:31           ` Eric Abrahamsen
2017-01-23  9:01           ` tomas
2017-01-21 23:03     ` Stefan Monnier
2017-01-22  1:15       ` Eric Abrahamsen
2017-01-21  8:13 ` tomas

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='CAArVCkRO-LnYNaijgKzqaMLy-q+=AqJpngCivuLxxCqWq7ZtCQ@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=eric@ericabrahamsen.net \
    --cc=help-gnu-emacs@gnu.org \
    /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.