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 wK89OYgd2GMbvQAAbAwnHQ (envelope-from ) for ; Mon, 30 Jan 2023 20:42:01 +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 OBM/OYgd2GO7DgEA9RJhRA (envelope-from ) for ; Mon, 30 Jan 2023 20:42:00 +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 61F48F171 for ; Mon, 30 Jan 2023 20:42:00 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pMa1f-0007xn-CZ; Mon, 30 Jan 2023 14:41:11 -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 1pMa1b-0007rT-IR for emacs-orgmode@gnu.org; Mon, 30 Jan 2023 14:41:08 -0500 Received: from relay-egress-host.us-east-2.a.mail.umich.edu ([18.217.159.240] helo=equal-nisien.relay-egress.a.mail.umich.edu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pMa1W-0000UH-De; Mon, 30 Jan 2023 14:41:07 -0500 Received: from associate-alux.authn-relay.a.mail.umich.edu (ip-10-0-74-230.us-east-2.compute.internal [10.0.74.230]) by equal-nisien.relay-egress.a.mail.umich.edu with ESMTPS id 63D81D30.1648C4A6.66D2318D.619749; Mon, 30 Jan 2023 14:40:32 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=relay-2018-08-29; t=1675107631; bh=ObQLjfeYgMQsR6QJAEzxMrZtWkREFnNztzvsSn86nUg=; h=To:cc:From:Subject:In-reply-to:References:Date; b=JgybH37sjVzGxGqmWf4cckKEedB7hbOPyXCDkltdOp6JX9Beb3zMukXEjxP6xND5v VeoptOhA+QfymBnn2ZCeBlcRjRxiZXm69bR5REKdhZ2bwxGan1NVEHf+QevQsikdgY ntuviXX5rJddSTCatGx1NOexStPHIdked48LdtqhPG5Sotzx9i9vCus2kNnIFj1Ek4 cLheJUPXWcSXvWqbGxBbtYH0s4VQf33/6rUENljOkcbnkllJv+7mjqGTaZyaB17BqO f7OFiU9bA1lD/lckNk3SnXYpW+MSn/Mlf8c2/aHWTfeyItgANgU+Vn7IruPoQe3+sW veFfdW8MHDC7A== Received: from localhost (Mismatch [85.103.28.184]) by associate-alux.authn-relay.a.mail.umich.edu with ESMTPSA id 63D81D2D.243D0039.252D05A.680010; Mon, 30 Jan 2023 14:40:31 -0500 To: Ihor Radchenko cc: Timothy , Bastien , Kyle Meyer , Org-mode , Daniel Mendler From: Greg Minshall Subject: Re: [POLL] Use compat.el in Org? (was: Useful package? Compat.el) In-reply-to: <87357r4y1l.fsf@localhost> References: <87sfx7degz.fsf@gmail.com> <87v8ks6rhf.fsf@localhost> <2153234.1675078540@archlinux> <87357r4y1l.fsf@localhost> Comments: In-reply-to Ihor Radchenko message dated "Mon, 30 Jan 2023 19:33:58 +0000." X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 28.1.91 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2219691.1675107625.1@archlinux> Date: Mon, 30 Jan 2023 22:40:25 +0300 Message-ID: <2219692.1675107625@archlinux> Received-SPF: pass client-ip=18.217.159.240; envelope-from=minshall@umich.edu; helo=equal-nisien.relay-egress.a.mail.umich.edu 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, SPF_HELO_NONE=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=1675107720; a=rsa-sha256; cv=none; b=inVNFexiZr3Y3Fny3XabTewLl/3nfS+Pi0iB6AmXNMajZVDvVHCEYzImbNLexkAz/Rjgfs e+YB7Sbh9qqhmBSYU5rVC3eBSu1jR8uGdDiFGkDgunhP6vrq+h0PaeZ4QZdKxR2znr+QNu nEcDxEv842jGbkl9+JjijinKVMBSIRAYK47CP+qgIAL2j+6EQpHIG3m0+lpB5g13TC4IHu CaxF12tAMWplvub/KaggQ1bbXfqXEO8H9SCcVF5ylZOou1O5hosYuR103ipWnxNrKD1HSJ 3SAwNd2UcbORVRcStyxdYUhxEcXKTFLVW3GHl45XC8q2zpalFL6DE88E4wzsaw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=umich.edu header.s=relay-2018-08-29 header.b=JgybH37s; 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=pass (policy=none) header.from=umich.edu ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1675107720; 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=ObQLjfeYgMQsR6QJAEzxMrZtWkREFnNztzvsSn86nUg=; b=AjQ3Y7XUukzf96sriloDp1+px7i/JjJqBIHtJWclWRCwDx6j06QGaDtRZTbv9KblvtAiDJ XyEJunbdrV5X9EGMCTni35MTPF85E5BgGqsmqfnnn+cnkPr4wCfPwfOjLqzDoGC0pzUzJz islh23+IdXZdGG8pQ7cqoaG3HQdeWK2kHo5qb1+wolLHcs17iizsutqoZ6S9UwPLIUNdns tiuasspbNNzfT8at4E2HbNcrfHh9OLC16k/uPZ17UbZn3QE7M9/GKSQhxgItX0BLgyYHtw kI3I98nBYjhf1N8Ql6NbyIAM807Q3BXD3Mrslj1nLtbmU1EaGDagp5qiuPuaPA== Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=umich.edu header.s=relay-2018-08-29 header.b=JgybH37s; 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=pass (policy=none) header.from=umich.edu X-Migadu-Scanner: scn1.migadu.com X-Migadu-Spam-Score: -5.48 X-Spam-Score: -5.48 X-Migadu-Queue-Id: 61F48F171 X-TUID: +3IfEwCK2f+B Ihor, > >> 1. If compat.el happens to lack support of some function, we will need > >> to contribute to compat.el directly and synchronize Org releases with > >> compat.el releases. > > > > would a separate "org-compat.el" (in addition to compat.el) somehow > > solve this? (i worry about the synch'ing.) > > That's what we already do. > Using compat.el means that we can remove some of the functions from > org-compat.el and instead rely on compat.el where the same functions are > maintained more carefully. 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.) i'm *only* thinking of trying to de-couple org-mode development from that of compat.el, in the mindset that "less cross-dependencies" == "less complication". if that makes sense. cheers, Greg