From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id QBrGL/k42GPReQAAbAwnHQ (envelope-from ) for ; Mon, 30 Jan 2023 22:39:05 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id IFvDL/k42GMgTwEA9RJhRA (envelope-from ) for ; Mon, 30 Jan 2023 22:39:05 +0100 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 8151B1A9A1 for ; Mon, 30 Jan 2023 22:39:04 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pMbqz-0005ui-0J; Mon, 30 Jan 2023 16:38:17 -0500 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 1pMbqx-0005uM-7u for emacs-orgmode@gnu.org; Mon, 30 Jan 2023 16:38:15 -0500 Received: from server.qxqx.de ([2a01:4f8:121:346::180] helo=mail.qxqx.de) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pMbqu-0003LG-Fp; Mon, 30 Jan 2023 16:38:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=qxqx.de; s=mail1392553390; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=zIUWpnVdwFmFIcN8dvT74dMkxrTvKfwDwJUpUHOq84A=; b=HPB6MFiIQvB4EO6tvv8V3P8E6T LagPIYcWfS3uhq8UMMU87qFiiWfRBoSis34vYRloFj44nFo09LvhKdFB7OAYccEiUcRwf+Ri0LFVy FOYm0ib96fN4JCRqqEXWbLAk45t1fgrOg0wIlwk8agMaHvGOkLDghueM98/JQt0HTa/A=; Message-ID: <8bcab2ea-43f1-5792-1814-b8e00c6b8f04@daniel-mendler.de> Date: Mon, 30 Jan 2023 22:38:05 +0100 MIME-Version: 1.0 Subject: Re: [POLL] Use compat.el in Org? (was: Useful package? Compat.el) To: Greg Minshall , Ihor Radchenko Cc: Timothy , Bastien , Kyle Meyer , Org-mode References: <87sfx7degz.fsf@gmail.com> <87v8ks6rhf.fsf@localhost> <2153234.1675078540@archlinux> <87357r4y1l.fsf@localhost> <2219692.1675107625@archlinux> Content-Language: en-US From: Daniel Mendler In-Reply-To: <2219692.1675107625@archlinux> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=2a01:4f8:121:346::180; envelope-from=mail@daniel-mendler.de; helo=mail.qxqx.de X-Spam_score_int: -41 X-Spam_score: -4.2 X-Spam_bar: ---- X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham 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 ARC-Seal: i=1; s=key1; d=yhetil.org; t=1675114744; a=rsa-sha256; cv=none; b=ZAdjYzNCxPzgfZZQv5R5WgBpbB8OrNnfdG+8ucaVlWLDs34MHCw3pQMszNMFK1llp5rInR MQya9/z2kaqO763YjP7KJRbbfQSoA2PD75LgqCZsO5uMOGv7Mp5z1mc2n74mFXMKuvAhVs bMgjpqBwhra5prGSrIaKD9YZ1BpSF0UCXGhLPpQvcWiMfSmrJV53ef+GVUCW4xWJja4NVV QATPiT8WSjSKP2JFTiS23J9clzLYMfAYT327D/aTt8q93kBvCa9vOQmTJoEpmwig4uXxw8 kZqwMDws8DAsY8l7pCLvZIJ72DCZPX4E8BCIDP5NDDkv71VWKmEC0B90vuOfSA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=qxqx.de header.s=mail1392553390 header.b=HPB6MFiI; 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"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1675114744; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=zIUWpnVdwFmFIcN8dvT74dMkxrTvKfwDwJUpUHOq84A=; b=lfByy1eGpSaF9K+05FlrUMF06aP3p4K06TPL/gb8OqFxhFi5ccA5p4XGYRGWBVBKBbG3LQ mAKyQF+p0+amwU6RUkT0c5dUWDZ14X2hpWfvlr17yxCHNzJ6V6zjHz5Rr3D9YFTGJDok8j lcoyjaZcDQoMr3eTuyPDvYSYbok1Xw1NL4pYd+eTADijA+aD7Dc6i2gndVI7HqhX8t1bTS 8CRerQyJRVV8lXUbhPtcdP7dm+LRZfhK7QGVboneU2L1JlgD6x/JJFIlwDX1Bw5YfIj5ij aP3c+GJHCJVEGOBsWz/mh/WUbQwM8AAbUuE824sJ0Vgj08SO1bkSiMIH5vmL+g== Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=qxqx.de header.s=mail1392553390 header.b=HPB6MFiI; 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"; dmarc=none X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: 2.42 X-Spam-Score: 2.42 X-Migadu-Queue-Id: 8151B1A9A1 X-TUID: ARqihs7c6M4s On 1/30/23 20:40, Greg Minshall wrote: > i see, yes. i'm just thinking that, for a given release CUR (like i > know anything about org-mode release procedures!) we would use whatever > has been available in compat.el since release CUR-n (for whatever n we > use -- 2?), and supplement that, in org-compat.el, with whatever other > compatibility features *we* (org-mode) need to support releases [CUR-n > .. CUR]. > > (and, presumably, contribute whatever might be appropriate from > org-compat.el to compat.el, so we can prune it out from org-compat.el at > some future point in time.) Sounds good. But note that Compat will at some point have sufficient coverage of the existing APIs, such that Org may not miss anything. From then on new additions will only be made at the time of a new Emacs release. The current Compat already supports many Emacs 29 APIs, which is in time for the upcoming pretest. Compat won't add any APIs which are still part of the unstable development master branch (before the branch cut and feature freeze), which reduces the need for coordination. If you are missing something right now, and want to introduce and use a new backported function, e.g., something new from Emacs 29, instead of going via the org-compat indirection, you could also make an addition directly to Compat, a Compat release can be prepared a short while after, and then you start using the new function in the Org development version. Daniel