unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Jorge P. de Morais Neto <jorge+list@disroot.org>
Cc: 38993@debbugs.gnu.org
Subject: bug#38993: 26.3; EBDB saves the database on Emacs exit even when told not to
Date: Tue, 14 Jan 2020 14:53:07 -0800	[thread overview]
Message-ID: <87k15tlkfg.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87pnfm2kkk.fsf@disroot.org> (Jorge P. de Morais Neto's message of "Tue, 14 Jan 2020 11:12:43 -0300")

Jorge P. de Morais Neto <jorge+list@disroot.org> writes:

> Em [2020-01-12 dom 09:38:20-0800], Eric Abrahamsen escreveu:
>
>> I still don't have a good solution for the first problem.  I guess
>> what I'm leaning toward is 1: adding a note to the
>> documentation/manual about this weirdness, and 2: defaulting
>> `ebdb-save-on-exit' to nil.  The average user will be using EBDB
>> interactively, meaning that they'll get the prompt both at "C-x s" and
>> when killing Emacs.  The `ebdb-save-on-exit' option could be reserved
>> for hackers who are using EBDB in some more peculiar fashion.
>
> I think that would be consistent with the rest of Emacs and even other
> desktop applications like LibreOffice.

Cool, that's done.

> But EBDB also has auto-save (as in Emacs 26.3 manual section 18.6 --
> "Auto-Saving: Protection Against Disasters"), right?

Yes, but personally I shut it off on my databases because the
eieio-persistent save routine is horribly slow, and I don't want my
Emacs locking up for several seconds when auto-saving is happening.

>> It looks to me like SourceHut is licensed under the GPL
>> (https://git.sr.ht/~sircmpwn/git.sr.ht/tree/master/LICENSE), so I'm
>> hoping that's an A! Or at least a B.
>
> I lack knowledge of the situation and feel insecure myself in the choice
> of software forge, but still I would like give you the following URL:
> <https://sourcehut.org/alpha-details/>

Oh I know :) I don't put anything in there I don't have mirrored
elsewhere. But I do pay for my account, so the maintainer can get to
beta faster.

New release as soon as I've got the Org tags thing fixed...





  reply	other threads:[~2020-01-14 22:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 18:30 bug#38993: 26.3; EBDB saves the database on Emacs exit even when told not to Jorge P. de Morais Neto
2020-01-06 19:51 ` Eric Abrahamsen
2020-01-06 21:04   ` Jorge P. de Morais Neto
2020-01-06 21:33     ` Eric Abrahamsen
2020-01-07 11:53       ` Jorge P. de Morais Neto
2020-01-07 18:42         ` Eric Abrahamsen
2020-01-08 13:28           ` Jorge P. de Morais Neto
2020-01-08 18:54             ` Eric Abrahamsen
2020-01-11 21:15               ` Jorge P. de Morais Neto
2020-01-12 17:38                 ` Eric Abrahamsen
2020-01-14 14:12                   ` Jorge P. de Morais Neto
2020-01-14 22:53                     ` Eric Abrahamsen [this message]
2020-01-18 19:38                       ` Eric Abrahamsen

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=87k15tlkfg.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=38993@debbugs.gnu.org \
    --cc=jorge+list@disroot.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).