From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: sqlite3 Date: Mon, 06 Dec 2021 13:47:27 -0500 Message-ID: References: <87tufmjyai.fsf@gnus.org> <87ee6pn2bl.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15409"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Stefan Kangas , Arthur Miller , emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 06 19:51:14 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1muJ50-0003ly-5C for ged-emacs-devel@m.gmane-mx.org; Mon, 06 Dec 2021 19:51:14 +0100 Original-Received: from localhost ([::1]:43448 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1muJ4z-0003SR-1D for ged-emacs-devel@m.gmane-mx.org; Mon, 06 Dec 2021 13:51:13 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38374) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muJ1X-0008Ey-4H for emacs-devel@gnu.org; Mon, 06 Dec 2021 13:47:39 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:2817) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muJ1T-000141-Vk for emacs-devel@gnu.org; Mon, 06 Dec 2021 13:47:38 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 5883080595; Mon, 6 Dec 2021 13:47:33 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 12AFF8043C; Mon, 6 Dec 2021 13:47:32 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1638816452; bh=LOyrtyI5u4i7CpHoEOaOR3o4mnpm4uMwkCdIk42VGR8=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=biqzs5dmForRHFeQ9kRkZBSvVtjQ21N9luHud48PIuRie/ukL9xXbrKwiXoLqMqEO 7jarq8M3lnuMZoV9B8sgc/wfDNPWvqtr6QZsvmRKIaeyPygm//eZiR1ib8DM4YRVGF 2/p+gpNqBj7+1Uaol+/M64/8BtmfxfRId2fYPFX/MibGZn2AffxF0DyulBvMyEKlpH +9WnHtDYMOWWrYqpUiELGtA/tUhF+0gyP8zFea/6cK0Bo6O6YDuJkylN/OZnHw9iFh eyAeqgjZtQLjpa/sTBsX/3R/vb++j2KDqQ976SZRZTUewEVPouWS0HxFpOwd2zwPrq h3O2deCnSvrPQ== Original-Received: from alfajor (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 0402F1201C2; Mon, 6 Dec 2021 13:47:32 -0500 (EST) In-Reply-To: <87ee6pn2bl.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 06 Dec 2021 17:08:30 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:281149 Archived-At: > Yeah, I think so. There's not always an obvious difference between > "configuration" and "app data", but if it's something that changes upon > every invocation (as the emojis in emoji--favorites do), it's more "app > data", and that doesn't belong in Customize. (The user may have their > .emacs file in a VC, for instance.) And on the flip side, customization data doesn't need to be too careful with locking because the user is not expected to modify its customization exactly at the same time in two separate processes. Stefan