Re: Persistence of variables

[tomas@tuxteam.de]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Mar 21, 2018 at 10:51:23AM +0100, Marcin Borkowski wrote:
> 
> On 2018-03-21, at 10:27, tomas@tuxteam.de wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Wed, Mar 21, 2018 at 10:13:11AM +0100, Marcin Borkowski wrote:
> >>
> >> On 2018-03-21, at 08:25, Marcin Borkowski <mbork@mbork.pl> wrote:
> >
> > [...]
> >
> >> Any thoughts/suggestions?

[...]

> In general, this is a good point.
> 
> But in my use-case, I will have one user besides me (it's a tool for our
> in-house workflow), and I wouldn't care about it too much.

Makes sense.

> If I turn this into a Melpa package (or even a blog post), I would of
> course follow your suggestion.  (The drawback is that the user would
> have to (once) insert something manually into init.el.)

Note that it's not either-or: in the Customize case, the package writes
into init.el if the variable is unset, and into the file specified by
that variable otherwise.

> BTW, is there any demand for such a micro-package?

Tough to say: it is so small that it would make more sense as
"basic infrastructure", to be used by "clients" like Customize.

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlqyMpIACgkQBcgs9XrR2kZElACfbydlPtqIYtt8mLFu0Di0pBMh
QLsAnjMOE18OZnYLkWrrXyz6hsKxjF1y
=uYm1
-----END PGP SIGNATURE-----