[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Storing sensitive data indefinitely in variables or buffers: Whether
From: |
Eli Zaretskii |
Subject: |
Re: Storing sensitive data indefinitely in variables or buffers: Whether and how to fix? |
Date: |
Mon, 05 Jun 2023 05:31:38 +0300 |
> Date: Sun, 4 Jun 2023 18:47:07 -0500
> Cc: jschmidt4gnu@vodafonemail.de, emacs-devel@gnu.org, yantar92@posteo.net
> From: Adam Porter <adam@alphapapa.net>
>
> > But I don't really understand why you would care to use alist-get
> > instead of, say, plstore-get. Why does it matter whether the storage
> > is presented as an alist or as an opaque storage with accessor and
> > setter?
>
> I don't mean that it should be an alist specifically. I mean that I'd
> just like to get/put a Lisp object, which I could then use with standard
> Lisp functions like alist-get, plist-get, gethash, as well as map-elt,
> and setf wrappers for setting, etc.
And I ask again: what's the problem of using plstore-get etc. instead?
why does it have to be "standard Lisp functions"?
Re: Storing sensitive data indefinitely in variables or buffers: Whether and how to fix?, Ihor Radchenko, 2023/06/01