From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id uH5IF3Ff52Q7ogAASxT56A (envelope-from ) for ; Thu, 24 Aug 2023 15:47:29 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id wIk/F3Ff52SitAAA9RJhRA (envelope-from ) for ; Thu, 24 Aug 2023 15:47:29 +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 EC06B5ADA5 for ; Thu, 24 Aug 2023 15:47:28 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Q7gPLodl; 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=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1692884849; 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=GkoJpGsrs2WsDANfKKRaRRj2jti6qTzgg4zQ3bYXO4A=; b=CplaKzf2b3z1ofwYReBANw+xoQvkbcxJjK9wmBUneP2aABW+13I8xyMQLIvPWZbTpyd1DM g1fYzAaq1YH3doHVLvutxSLrLRH5/8okP5UW45VdQmHHM97YMNLMTtsmQZZfWoTtjfzhL6 kJ7IbaRFLO1pvHBRrqmZgkhvxvwcmI45B0dmcj+vdvp5frdsKlGIlI6Y05Z03EhQUJwJPM ICpav9eKAxPxgehiVmXX6f5FcH35YsOqagYTPfQtF+kxqUJb097hCy8949a6c6tlEqTz/0 dxp0AxquXCSoJmCMaHV9Fv9ubh2I9Ia9AaodMq6zE+BduW9B5LgntG5KSfrkSA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1692884849; a=rsa-sha256; cv=none; b=pXCLior/vt6ZIAPURfiU2s1ZAZz62uPPKbtQ7uXf9eiobzXSh3Ou2NB6M9N+N8XspMhBL4 Kd15KtS+XpWBHSWkm878uXQnH3JUP8uwXPy6u5+gyvinPYPyCr3V/32+0DaLYe8jpDhdv4 monNCRt8EpsT+ZPIBAcBFy6OFPDj+JZxBeiNnMqstpYkx+l4humD+FKWbRzjnJaGkAc+8z aUxWjzA7f4zIuUk0rO+K2but3m5pMuan2fKN43U/GbrvbvBlod2gdc+wBRVfGUexKuiZzV htTykgXpqWxzohGKL1brGVlsNO6YCVpEEb5gIOPVxhHouWWxYd0z7/WmR8zGrw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=Q7gPLodl; 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=posteo.net Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qZAg0-0003Mf-Nr; Thu, 24 Aug 2023 09:47:08 -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 1qZAfz-0003MW-NI for emacs-orgmode@gnu.org; Thu, 24 Aug 2023 09:47:07 -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 1qZAfw-00081M-Vy for emacs-orgmode@gnu.org; Thu, 24 Aug 2023 09:47:07 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 9F0DC240101 for ; Thu, 24 Aug 2023 15:47:02 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1692884822; bh=ZNJYZjXNBSwG+CIRp3Jkj7GFySdGu3NAxl97xczhQR8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=Q7gPLodlA0rhX7vPxJkX4IrpGCQdE+kcUV8LspT8CsUWB2SQDL/c1vlnEV+Sc1fja mggIVGn9gTSDXRxVtVsI3DzD61Ws5OSoAnonF/e6grTPHlyl2MSExlNs3m9Hg/iRJy AZnFmaH1dpmk8tiQdptuuuPqwGSenHM7OU3MExcli5VWqV9QXV31Y0qYX25j6wKNrS P3R4QnWZCeAHaJyZHMCk1chFwgSl5OuskwvAP2F5y6WOuBtAkxVnZrD+5ZO8WnoH9Z W9wIRolhBft7iY02eQ1VM+0QHjWZVwYn64SN7DNdTK4fNkIOYeRIOmixvvLKjz9V2h +zJDGg+nRNfRw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RWksL03TVz6v0r; Thu, 24 Aug 2023 15:47:01 +0200 (CEST) From: Ihor Radchenko To: Russell Adams Cc: 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: References: <87v8d47jqh.fsf@bzg.fr> <87sf88d5r6.fsf@localhost> <87jztkve0g.fsf@bzg.fr> <874jko3ad6.fsf@localhost> <87a5ugk46o.fsf@bzg.fr> <87msygk3zh.fsf@localhost> <87bkewip2u.fsf@bzg.fr> <87il94k3a6.fsf@localhost> <877cpkk1ki.fsf@localhost> Date: Thu, 24 Aug 2023 13:47:31 +0000 Message-ID: <87v8d4imbw.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_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, 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-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -5.41 X-Spam-Score: -5.41 X-Migadu-Queue-Id: EC06B5ADA5 X-Migadu-Scanner: mx1.migadu.com X-TUID: zi4kBRoMEzAd Russell Adams writes: >> It will. And it will also break some of my workflows :( > > I think that's unfortunate, but perhaps it would improve the health of > the codebase? Removing most features would improve health of the codebase. Like getting rid of agenda with its horrible code. But it does not mean that we should do it. >> > Could we normalize the code if some of the features were enabled in a >> > cookie/flag on a heading? >> >> We would need to put more special cases. Which has pros and cons, >> actually. The downside is more special cases. The upside is that most of >> inlinetask bugs are originating from the same code handling both >> inlinetasks and headings without accounting for their differences. > > It sounds like the code would be cleaner in a single place using a cookie. The cleanest would be something that does not match `org-outline-regexp-bol'. Then, we will avoid all the possible confusion between tasks and inlinetasks. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at