unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tomas@tuxteam.de
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Storing sensitive data indefinitely in variables or buffers: Whether and how to fix?
Date: Thu, 1 Jun 2023 08:51:10 +0200	[thread overview]
Message-ID: <ZHg/3lE9A7/AQ/pG@tuxteam.de> (raw)
In-Reply-To: <877csnd71w.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]

On Thu, Jun 01, 2023 at 06:34:51AM +0000, Ihor Radchenko wrote:
> <tomas@tuxteam.de> writes:
> 
> > I'm already wrangling with Org caching (for now, my sweet spot
> > seems to be directing it to a non-existing directory and ignoring
> > the complaints: paradoxically, Emacs is snappier then).
> 
> You will hit an error, sooner or later. We are going to use cache in more
> scenarios.

I get to keep both parts, I know. I'd definitely prefer an official
switch, but with no code to offer I won't even dare to complain :)

> If your Emacs is snappier without cache, you likely experience slowdowns
> on long sessions. If so, it is another problem you are just postponing.

Actually not. Rather around the start. If interested, I can try
to provide data. But I won't bother people with it without a
request.

> > I'd hate to end up with a setup like the monster browsers have
> > these days: an obscure set of sqlite databases you need a huge
> > amount of dedication to extract some slivers of information from.
> 
> I am sure we will not.
> 
> For multi-session, it is up to you whether to store information in
> SQLite database or in plain text files. The default for
> `multisession-storage' is 'files. I doubt that we are going to change
> this default in the nearest dozen of years (It is Emacs after all :])

It is not specifically about SQLite...

> For org-persist, it is designed to store disposable information that can
> be re-generated any time. Even then, org-persist tries to keep the
> index.eln human-readable.

...but about complexity. Having a generic cache which works for all
applications will make the code (application code and cache data)
necessarily more inscrutable. OTOH, every little application doing
its own thing is problematic in its own way. As an engineer, you
seldom win ;-)

Please, don't take my complaints all too seriously. You are doing
a huge work; although I don't always like the direction taken, I
do admire what you're doing. I feel free to fat-finger it strategically
here and there to fit my needs :-)

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-06-01  6:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 21:25 Storing sensitive data indefinitely in variables or buffers: Whether and how to fix? Jens Schmidt
2023-05-31  8:02 ` Ihor Radchenko
2023-05-31 16:39   ` Adam Porter
2023-05-31 18:17     ` tomas
2023-06-01  6:34       ` Ihor Radchenko
2023-06-01  6:51         ` tomas [this message]
2023-06-01  7:11           ` Ihor Radchenko
2023-05-31 19:05     ` Eli Zaretskii
2023-06-01  6:48       ` Ihor Radchenko
2023-06-01  7:11         ` Eli Zaretskii
2023-06-01  7:29           ` Ihor Radchenko
2023-06-01  7:33             ` Eli Zaretskii
2023-06-01  7:34           ` tomas
2023-05-31 19:37     ` Jens Schmidt
2023-06-01  6:42       ` Ihor Radchenko
2023-06-01 20:10         ` Jens Schmidt
2023-06-01 20:47           ` Adam Porter
2023-06-02  6:30             ` Eli Zaretskii
2023-06-04 23:47               ` Adam Porter
2023-06-05  2:31                 ` Eli Zaretskii
2023-05-31 12:56 ` Eli Zaretskii

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=ZHg/3lE9A7/AQ/pG@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=emacs-devel@gnu.org \
    --cc=yantar92@posteo.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).