unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: edgar@openmail.cc
To: help-gnu-emacs@gnu.org
Subject: Re: replace element in list
Date: Sat, 24 Nov 2018 03:01:18 +0000	[thread overview]
Message-ID: <4e86b305ccbc341ee555657f0006d012@openmail.cc> (raw)
In-Reply-To: <2087821187f90948d25d93c7ea475e66@openmail.cc>

 From Eric
> You'll probably get a bunch of suggestions, but mine is to use `setf'
> and `nth'. You can do:
> 
> (let ((orig '(("a" . "b") ("c" "d")))
>       (obj  '("c" "d"))
>       (new '(":)")))
>   (setf (nth (cl-position obj orig :test #'equal) orig) new)
>   orig)
> 
> Hope that's useful.
> 
> Eric

Thank you, Eric.


 From Drew
> (defun toto (xs old new)
>   (let ((ms  (member old xs)))
>     (unless ms (error "%S is not in %S" old xs))
>     (setcar ms new)
>     xs))

Thanks (I wonder why toto :P ).

 From Stefan
> My suggestion is to not do it:
> - if you do it by modifying the list in place, it means you're using
>   nasty side-effects, which are better avoided when possible
>   (especially with lists).
> - if you want to do it without side-effects, your operation will
>   inevitably be algorithmically inefficient because a list is not
>   designed for that.
> 
> 
> -- Stefan

Thank you.


 From Robert
> Edgar, here is one that avoids the nasty side-effects that Stefan
> mentioned.  It isn't especially efficient, but it is simple and clear.
> Warning: it behaves the same as your original version _only_ if there
> is exactly one matching item.
> 
> (defun my-list-replace-2 (l old-item new-items)
>   (apply 'append
>          (mapcar (lambda (x)
>                    (cond ((equal x old-item) new-items)
>                          (t (list x))))
>                  l)))

Thanks! This is great :). I didn't know that the first element would be 
replaced :S !!


People, you are truly great. Thank you all.

-------------------------------------------------

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  



  parent reply	other threads:[~2018-11-24  3:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22  4:42 replace element in list edgar
2018-11-22  5:18 ` Eric Abrahamsen
2018-11-22  5:39   ` Drew Adams
2018-11-22  6:04     ` Eric Abrahamsen
2018-11-22 13:19 ` Stefan Monnier
     [not found] ` <mailman.4442.1542892802.1284.help-gnu-emacs@gnu.org>
2018-11-23 12:05   ` Robert Munyer
2018-11-24  3:01 ` edgar [this message]
2018-11-24  5:27   ` Drew Adams
2018-11-24  7:22     ` edgar
  -- strict thread matches above, loose matches on Subject: below --
2019-09-02  9:44 Replace " Andreas Röhler
2019-09-02 10:37 ` tomas
2019-09-02 10:41   ` tomas
2019-09-02 10:46     ` tomas
2019-09-02 11:03       ` Michael Heerdegen
2019-09-02 11:05         ` tomas
2019-09-02 13:38           ` Andreas Röhler
2019-09-02 13:29 ` Stefan Monnier
2019-09-02 13:43   ` tomas
2019-09-02 14:00     ` Andreas Röhler
2019-09-02 14:57       ` Stefan Monnier
2019-09-02 20:29         ` Andreas Röhler
2019-09-02 21:32           ` Stefan Monnier
2019-09-03  5:37             ` Andreas Röhler

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=4e86b305ccbc341ee555657f0006d012@openmail.cc \
    --to=edgar@openmail.cc \
    --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.
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).