From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id GLiGHLWkbWZjLwAAe85BDQ:P1 (envelope-from ) for ; Sat, 15 Jun 2024 14:27:01 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id GLiGHLWkbWZjLwAAe85BDQ (envelope-from ) for ; Sat, 15 Jun 2024 16:27:01 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=JLjnAb6Y; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1718461621; a=rsa-sha256; cv=none; b=rcZ8nSV1MTU4l+Q/5zAkcGu+/psaB1bKKLJVcNN4UflxIoBmB0W7jA3+0VYUOg4imFMNZS kueu1HH3QwjX29iEIUXS6lIaeGPRtTPkNY6phnsMIU0/W3zKOGCpgxvWKo2Bbhjo4o77gQ 0reftrtZv4dcmL8F7TqVmd+Ec5Y0AKtNbX0A4cfEuJiD9QHC9b23dg7NBSHr6wRZPr6bpR CD5ceSMr4hMFZs7+IwItr9rUylzqVD5D6KJzCC9ZhzqcCmnxSxz2gF+bfA14i2stTV3VLW 4IP8pWNgwR/jVXkI78nFvww7rn9eTTKwddmZzUikCnnkZSjKXSHofMX2sUUuGA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=JLjnAb6Y; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1718461621; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=YGIjHyj83mitkiNbZ5Q68LZTBY1Z+mdYKr7RegymBUM=; b=gGdswRQieuF2AlQOS4kEMygzvU8DmNxcBfrm1sccws3yUiPUEIozPS5GDmu1MHP2plKDWG 8EWOLPGucMIwCOmyYrWU9TeGAVJSx9m7bNs7vc/SjOGzaqSsvTycG4/6da3WriD5UyaMcC kYoGLgVfL0DOnlG3AbufduHtq8CsfJtzYZQT4nW4v3sKoFQmoPuxhnXPuk7WVZuJjZVVht BwW1SPVMsp4b5NMW87bbZIgiubeI95oNoxaWNQDfdt9lB+mgSKhMFDd+PHfUbUsvtTZv16 eoAfK9BvfysZDSqJaIlNB5QR2iZQQAa4T6GqxONU8O3VeKdhjXjqbBinqnvMYQ== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 32E606AFA0 for ; Sat, 15 Jun 2024 16:27:01 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sIU7w-0003Gq-3J; Sat, 15 Jun 2024 10:11:32 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sIU7t-0003F0-KE for emacs-orgmode@gnu.org; Sat, 15 Jun 2024 10:11:29 -0400 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sIU7r-0005GM-AJ for emacs-orgmode@gnu.org; Sat, 15 Jun 2024 10:11:29 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 0A7B4240101 for ; Sat, 15 Jun 2024 16:11:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1718460685; bh=0/uD62P3iOKpn2U3lRVY2piSt3nJSatSdLTRBN7Cvv8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=JLjnAb6YF4ubXFgabDE7U25P6mvmiplW3Poh9wGqeH1BRjrpvGiLuENBOL2xtXHwU JG049VGHJuJZPs5sXWrLZNUylEy++3IBnt/y5GV25E2DZ2N+PwdK/1GxbGd1Q8gkSm MoTNTstuk2eX905VYXooOEO+V9f6irEgV0rUBk5F4JLeq3rPRNDm/YtogmFMYDmSE5 spALDj3go7sYMpcQnh1+oD2y1MpjvkeMWR1oI+QX+Tk2rwaoLzreadaeEt49b9McrO znXCIURJOO0QSsppos8C+lspD16d0ij36HPQsVwl9bPFExiEyZtDcZ+IuUlxPQU0+n qGDebuSv3t0WA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4W1dNr44p2z6tvy; Sat, 15 Jun 2024 16:11:24 +0200 (CEST) From: Ihor Radchenko To: Eli Zaretskii Cc: emacs-orgmode@gnu.org, emacs-devel@gnu.org, Michael Albinus Subject: Re: Please document the caching and its user options In-Reply-To: <86msnmtl5o.fsf@gnu.org> References: <86ed921oxu.fsf@gnu.org> <874j9vllbp.fsf@localhost> <86a5jny72y.fsf@gnu.org> <877cerk0bz.fsf@localhost> <861q4zy0va.fsf@gnu.org> <87y176gyou.fsf@localhost> <86msnmtl5o.fsf@gnu.org> Date: Sat, 15 Jun 2024 14:13:03 +0000 Message-ID: <87a5jmguq8.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Queue-Id: 32E606AFA0 X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: -9.57 X-Spam-Score: -9.57 X-TUID: MEPAMwvKjIeU CCing emacs-devel as I'd like to upgrade this discussion to Emacs-wide context. Eli Zaretskii writes: >> ... I wanted to know what is being cached, why, and in what file/directory. >> > > ... >> Would it be possible for Emacs to define a framework for cache/var/data >> locations? Such framework would not only be useful in the context of >> this discussion, but also to tackle the issue with packages sprinkling >> things randomly into .emacs.d or ~/ (see >> https://github.com/emacscollective/no-littering/) > > I think Emacs already provides all the framework for caching that is > needed. Caching simply means you write some data to file, and all the > building blocks of that already exist, for quite some time, actually. > The only thing that is application dependent is the data to be cached > and how to serialize that, but that cannot be usefully generalized. I was referring to some kind of global option that defines cache directory, data directory, etc. Something akin XDG. Then, Org can place cache inside that directory rather than trying to cook up something independently. Also, caching is not as simple, because caches may contain sensitive data. (see https://list.orgmode.org/orgmode/CAM9ALR8fuSu0YWS1SehRw7sYxprJFX-r2juXd_DgvCYVKQc95Q@mail.gmail.com/) Some users may want to move caches to read-restricted location or even to location dependent on where the cache is originating from (separate caches depending on whether default-directory is from encrypted volume, remote mount, etc) Finally, we got several requests to have caches cleared up upon exiting Emacs, which is also something that should be better managed centrally, by Emacs, for all possible kinds of cache/history data. >> > multisession is an optional package, it is neither preloaded nor >> > turned on by default in Emacs. >> >> It is used by default in emoji.el (C-x 8 e r) > > Which is also optional. And a minor feature at that. It is just for now. TRAMP (by no means a minor feature), has the following TODO item in tramp-cache.el: ;;; TODO: ;; ;; * Use multisession.el, starting with Emacs 29.1. >> (Also, should we open some kind of bug report to track documenting >> multisession in the manual?) > > I don't mind, but it sounds like an exaggeration to me. I kind of agree, if we talk about the current state of affairs. But, I'd like to discuss this in the context I elaborated on above - more centralized cache management. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at