From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: How to save custom variable programmatically?
Date: Tue, 10 Nov 2020 21:43:09 +0100 [thread overview]
Message-ID: <87o8k5eyea.fsf@web.de> (raw)
In-Reply-To: X6rnuNu08WlXrwLi@protected.rcdrun.com
Jean Louis <bugs@gnu.support> writes:
> My strategy is to minimize number of packages used as dependencies so
> I try to use what is built in or to re-use what is inside of Emacs.
Eieio is part of Emacs. The Gnus registry is saved using
eieio-persistent.
This class is relatively new and was a bit buggy in the past, though.
In new Emacs versions it works reliably AFAICT.
> Personally I am using PostgreSQL. Then I just define the table
> definition and that may be similar to eieio.
Might also be interesting.
The Eieio approach has the advantage that (an) Emacs Lisp (object) is
saved as (an) Emacs Lisp (expression). It is slow, however.
Michael.
next prev parent reply other threads:[~2020-11-10 20:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 7:51 How to save custom variable programmatically? Jean Louis
2020-11-10 10:43 ` Robert Pluim
2020-11-10 13:42 ` Jean Louis
2020-11-10 11:23 ` Michael Heerdegen
2020-11-10 13:55 ` Jean Louis
2020-11-10 14:36 ` Michael Heerdegen
2020-11-10 19:19 ` Jean Louis
2020-11-10 20:42 ` Marcin Borkowski
2020-11-10 21:46 ` Jean Louis
2020-11-11 21:20 ` Marcin Borkowski
2020-11-10 20:43 ` Michael Heerdegen [this message]
2020-11-10 21:52 ` Jean Louis
2020-11-11 18:00 ` Michael Heerdegen
2020-11-11 18:05 ` Jean Louis
2020-11-17 12:24 ` Michael Heerdegen
2020-11-17 15:07 ` Jean Louis
2020-11-10 21:15 ` Michael Heerdegen
2020-11-10 21:55 ` Jean Louis
2020-11-11 10:55 ` Michael Heerdegen
2020-11-17 15:44 ` Jean Louis
2020-11-17 16:38 ` Michael Heerdegen
2020-11-17 21:30 ` Stefan Monnier
2020-11-10 16:24 ` Drew Adams
2020-11-10 19:23 ` Jean Louis
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=87o8k5eyea.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).