From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id mHEoHk9K0mRz2AAASxT56A (envelope-from ) for ; Tue, 08 Aug 2023 15:59:43 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id mMfwHU9K0mRRQQEAauVa8A (envelope-from ) for ; Tue, 08 Aug 2023 15:59:43 +0200 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 48D284DFCB for ; Tue, 8 Aug 2023 15:59:43 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=WfuijP5e; 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=gnu.org ARC-Seal: i=1; s=key1; d=yhetil.org; t=1691503183; a=rsa-sha256; cv=none; b=uOXHym3/n5/MshunncJAUvRILpMH9CSrbVY3Z7CZs+rCDvbQDStgsed0yJvSomJzhjMXwY ldND3GYIOi6hXLeoohqd2sFR3G6QNtpE2BmxOp2Gdtrm/Sr6Y34KWYmmX1BTemvy3rc0AV qt2ACLwNRDP0FFb2U3GGNDr3u9It0BQD8nye1jf5pDCsxuYLASvNOBbyqAga+dU0v/n/Hr uXheEJYAcQtrs2mhjW9geCCh8z1ME0gb3rI0VU5Y+fwbUmFsQK12qru1xOHZJCD2bOD0Wt OIJb/e1A/k8ZBtKeppZ1wrT9zMlGAG5OkdQdJy+nKler+prjSlUy5oG/fs2sGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1691503183; 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=Yet6LftSAPWFyH8p5vqkpW19mY12tThrqlPN2KJdj60=; b=QAeZN8Alctksez5PyE1Fm81j/3N9jqWjtOp1JWOabrF8MhK/YQ+eGhZ4ndoWtNArRpHYiq mcWM5J52+T48tbXcIOVIqHiA8hazq4duU8RfJhX9ixlgBrg9qUUIg3IGQ9Tfa1XsCfLWDs gFY08E2plDL6zFwRpzzGb0QntDt89hXCKXJQ887nzmjKdQ/ZUSkPg7fccRw1RMG6LIctCh 8aRnUx658Vguub3jHK+T38cJl3WTgN9YT8/0pTNy9CjzFyPvpPRfDFlHLG1PCrshB0wpLn Bp2S4XjKAQoOVAkzHO0Y1vm8y5ho1TlwDkAeHbL5UXygqs8PzIVHc/ikYOim6w== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=WfuijP5e; 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=gnu.org Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qTMmc-0004Bi-8f; Tue, 08 Aug 2023 09:29:58 -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 1qTMmb-0004Am-21 for emacs-orgmode@gnu.org; Tue, 08 Aug 2023 09:29:57 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qTMma-0001tP-Pp; Tue, 08 Aug 2023 09:29:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=Yet6LftSAPWFyH8p5vqkpW19mY12tThrqlPN2KJdj60=; b=WfuijP5etE5Mrvmnn7xN 1Vjp9jDGPzh68MYszEJu2wLbIn9Bzd0YceWYkQ7tRaahqIrAHmEwV3SUxWcQWyzTl/7OmspHp8FO5 xrO3gFys+bPJwA5QRaggYdYt9dxCBfKkfzp6YY+RllifqfYmxkv2JBwnw7ixQVB1kdrm7A9nkAfAA X04BUDkYS8s/sJGeilcS17qh4fpG865V436JlQguKY9TGeo3dA6+eYtynHzfJyvfDcP/ehNZLpZos 32Cy6hoXhpB6CRVh7u25eDmGABQsHEbnILbhv3BtfmEQh8OE9ioiBH9vrBnOZ8Ce1ZkZn0bIGzgvm GK9L/r+W8mZY/g==; From: Bastien Guerry To: Ihor Radchenko Cc: Max Nikulin , emacs-orgmode@gnu.org Subject: Re: [POLL] Should we accept breaking changes to get rid of Org libraries that perform side effects when loading? In-Reply-To: <87r0odrkbp.fsf@localhost> (Ihor Radchenko's message of "Tue, 08 Aug 2023 08:48:26 +0000") References: <87o7omg4ie.fsf@alphaville.usersys.redhat.com> <87pm91ngb8.fsf@localhost> <87jzz8f3re.fsf@alphaville.usersys.redhat.com> <87mt43agk6.fsf@localhost> <874jq8ohbr.fsf@localhost> <87bkfip3mo.fsf@gnu.org> <87r0odrkbp.fsf@localhost> Date: Tue, 08 Aug 2023 15:29:47 +0200 Message-ID: <875y5pvf04.fsf@bzg.fr> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain 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-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -7.81 X-Migadu-Scanner: mx2.migadu.com X-Migadu-Queue-Id: 48D284DFCB X-Spam-Score: -7.81 X-TUID: Swx4uiNbj9mX Thanks a lot for the detailed clarification. The Elisp coding convention explicitely targets Emacs "editing behavior". The definition of a new function is not a side-effect that affects Emacs editing behavior, so Babel and export libs are OK. Ihor Radchenko writes: > Finally, we have org-mouse.el discussed here, which modifies key > bindings and org-inlinetask.el, which modifies how Org treats headlines > in Org files, modifying syntax. org-mouse.el should not modify default Org _editing_ key bindings. Is it really the case? If so, can we fix this? Does org-inlinetask.el modifies the way non-inline headlines are edited? If so, can we fix this? IIRC org-inlinetask.el only adds editing function for inline tasks, it is an extension, not a modification of the default Org editing behavior, but the limit can be thin here. > With the current state of affairs, it is often enough to > (require 'org-library) to get things work. If we get rid of all the > possible side effects, users will have to adapt their configurations > and we will thus violate "I won't force you to update your > configuration." > > Of course, we can change babel implementation to use explicit registry > like for export backends and force users to call explicit activation > commands in addition to (require 'library). But I am not sure if we are > not crossing the line with such an approach: "I won't use software > correctness as an excuse.". Defining new functions is a desirable "side-effect" of all Elisp library, I don't think we should worry abou this. -- Bastien Guerry