From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Persistence of variables
Date: Wed, 28 Mar 2018 15:09:01 +0200 [thread overview]
Message-ID: <86woxwtkia.fsf@zoho.com> (raw)
In-Reply-To: mailman.11329.1522213571.27995.help-gnu-emacs@gnu.org
Marcin Borkowski wrote:
> I think you misunderstood me. Storing data in
> a file is natural. Having a separate file for
> just one variable looks like an overkill.
Then create a file in your home dir called
.pervert - the persistent variable register.
It can be an XML file or just a text file like
this
caliber 5.56
insulation none
tire 650B
LSD ALD-52
("just a text file" doesn't make it any less of
a database than an XML ditto by the way)
Now write a parser that will search the file
for e.g. the key "tire" and return the data
item "650B".
Because you said you at this point only have
a single variable, you don't need to worry
about sorting (at least not for the sake of an
algorithm parsing it being too slow), but it
can be nice to have it sorted anyway - and easy
to do like any Emacs buffer, even automatically
on insert - nice because you might come to
realize this file is handy also for
manual [1] use, e.g. when writing to the math
faculty and having to look up pi (3.1415..) and
so on :) No, seriously!
I'm pretty sure someone already did an Emacs
framework/interface to populate, change, and
retrieve data from such a text DB file?
[1] Remember the words (mantra/motto) of the UK
intelligence service: Knowledge gives
strength to the hands.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2018-03-28 13:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 6:08 Persistence of variables Marcin Borkowski
2018-03-21 6:55 ` Eli Zaretskii
2018-03-21 7:25 ` Marcin Borkowski
2018-03-21 9:13 ` Marcin Borkowski
2018-03-21 9:27 ` tomas
2018-03-21 9:51 ` Marcin Borkowski
2018-03-21 10:23 ` tomas
2018-03-25 17:10 ` Marcin Borkowski
2018-03-21 11:34 ` Emanuel Berg
[not found] ` <mailman.11020.1521632103.27995.help-gnu-emacs@gnu.org>
2018-03-21 11:38 ` Emanuel Berg
2018-03-21 9:53 ` Eric Abrahamsen
2018-03-21 10:26 ` Marcin Borkowski
2018-03-21 15:12 ` Drew Adams
2018-03-21 15:19 ` tomas
2018-03-21 22:16 ` Joost Kremers
2018-03-25 17:15 ` Marcin Borkowski
2018-03-25 18:57 ` Drew Adams
[not found] ` <mailman.11217.1521998149.27995.help-gnu-emacs@gnu.org>
2018-03-28 0:21 ` Emanuel Berg
2018-03-28 5:05 ` Marcin Borkowski
[not found] ` <mailman.11329.1522213571.27995.help-gnu-emacs@gnu.org>
2018-03-28 13:09 ` Emanuel Berg [this message]
[not found] ` <mailman.11032.1521645579.27995.help-gnu-emacs@gnu.org>
2018-03-21 21:43 ` Emanuel Berg
2018-03-24 23:54 ` Robert L.
2018-03-25 17:12 ` Marcin Borkowski
2018-03-26 1:48 ` Eric Abrahamsen
2018-03-28 19:12 ` Marcin Borkowski
[not found] ` <mailman.11031.1521645187.27995.help-gnu-emacs@gnu.org>
2018-03-21 18:00 ` Emanuel Berg
2018-03-21 18:23 ` Eli Zaretskii
[not found] ` <mailman.11045.1521656612.27995.help-gnu-emacs@gnu.org>
2018-03-21 21:30 ` Emanuel Berg
2018-03-22 1:36 ` Rolf Ade
2018-03-22 7:02 ` Eli Zaretskii
[not found] ` <mailman.11076.1521702135.27995.help-gnu-emacs@gnu.org>
2018-03-24 3:06 ` Emanuel Berg
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=86woxwtkia.fsf@zoho.com \
--to=moasen@zoho.com \
--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).