From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 30943@debbugs.gnu.org, cfindeisen@google.com
Subject: bug#30943: save-hist creates massive cache file
Date: Thu, 29 Mar 2018 21:47:23 +0300 [thread overview]
Message-ID: <83po3md8hw.fsf@gnu.org> (raw)
In-Reply-To: <1rwoxusqjl.fsf@fencepost.gnu.org> (message from Glenn Morris on Thu, 29 Mar 2018 14:08:30 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: eliz@gnu.org, 30943@debbugs.gnu.org
> Date: Thu, 29 Mar 2018 14:08:30 -0400
>
>
> I think it's a reasonable feature request to ask that savehist be
> capable of dealing with additional variables that aren't automatically
> truncated (or if not it should be explicit about it).
That'd require people to register a function to do the truncation. We
could, of course, provide a couple of default functions to do that
with "simple" variables.
> On the other hand, desktop is a superset of savehist and can can already
> do this (apparently, see desktop-globals-to-save).
Yep.
> I wonder if load should pay attention to large-file-warning-threshold
> somehow?
I actually find that to be a nuisance even for visiting files. With
64-bit builds, this warning makes very little sense.
next prev parent reply other threads:[~2018-03-29 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 19:11 bug#30943: save-hist creates massive cache file Chris Findeisen
2018-03-26 14:59 ` Eli Zaretskii
2018-03-27 2:50 ` Chris Findeisen
2018-03-27 19:44 ` Glenn Morris
2018-03-29 16:27 ` Chris Findeisen
2018-03-29 17:09 ` Eli Zaretskii
2018-03-29 18:08 ` Glenn Morris
2018-03-29 18:47 ` Eli Zaretskii [this message]
2018-03-30 5:25 ` Glenn Morris
2018-03-30 8:14 ` Eli Zaretskii
2022-02-15 10:29 ` Lars Ingebrigtsen
2018-03-27 19:12 ` Glenn Morris
2018-03-29 10:49 ` Eli Zaretskii
2018-03-29 17:12 ` Glenn Morris
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=83po3md8hw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30943@debbugs.gnu.org \
--cc=cfindeisen@google.com \
--cc=rgm@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.
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).