From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Upstreaming org-element-ast (was: Improving Emacs' iCalendar support) Date: Sun, 05 Jan 2025 08:33:09 +0000 Message-ID: <87y0zppsmy.fsf@localhost> References: <87ed4dss2x.fsf@ohm.mail-host-address-is-not-set> <87mshq9w5c.fsf@ohm.mail-host-address-is-not-set> <86ed31j6zk.fsf@gnu.org> <87ldx9vsnb.fsf@localhost> <868qt8kj6f.fsf@gnu.org> <87ikscx5io.fsf@localhost> <867c8skhy6.fsf@gnu.org> <87frngx4fx.fsf@localhost> <864j3wkczm.fsf@gnu.org> <87cyhg0zjz.fsf@localhost> <87ttamtf7g.fsf@recursewithless.net> <87h66l2isk.fsf@localhost> <87cyh8guci.fsf@recursewithless.net> <87r05mg9ve.fsf@localhost> <87pll68z8u.fsf@recursewithless.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13032"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Richard Lawrence Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jan 05 09:31:46 2025 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tUM30-0003ES-B3 for ged-emacs-devel@m.gmane-mx.org; Sun, 05 Jan 2025 09:31:46 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tUM2H-000622-Uc; Sun, 05 Jan 2025 03:31:02 -0500 Original-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 1tUM2D-00061i-0l for emacs-devel@gnu.org; Sun, 05 Jan 2025 03:30:57 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tUM29-0003Nj-P0 for emacs-devel@gnu.org; Sun, 05 Jan 2025 03:30:56 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id BDA71240027 for ; Sun, 5 Jan 2025 09:30:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1736065850; bh=m++8eDjdR5Gv9GDxQPKVGaBt82bAVh5K1YiW9EAsMC8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=MvecjErCmc2opRPVn1xDzoB0dB03SfFeofd6qe8VUP1978hZqKI1lMUQIBWDJ0lWZ L0eQTfae4xI7CPQmF1eFshlbW5IBqBANXmM5a8d8z1WYSzBH7aVkXd1SDl/M4qA+yA +eCYzsc/l2WYUc1NJxQz5vUQq+L1s0pA8btbwtEovsEc99sWe6t/Os9rgIsRQbhrKO S39sdsLAM0Mb6N4ybPZHY1IKHQsCQktssUdZKHldYoWjcAgCBp5tsVkDUgTCPEN1Ze mxl1KQ2wmHd3PxFytUpfihWsZSVvU6/ryQ+3+xUA37hZCntzkttDwj3P3GY4qkfAV/ k5QQMg0JD10Xg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YQr9k0RJZz6tyL; Sun, 5 Jan 2025 09:30:49 +0100 (CET) In-Reply-To: <87pll68z8u.fsf@recursewithless.net> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327710 Archived-At: Richard Lawrence writes: >> Or maybe the library can somehow flag to org-element-ast during compile >> time about the properties to be optimized. > > What about asking library users to say something like > > (eval-when-compile (defvar org-element-custom-standard-properties ...)) > > and then using a with-standard-properties macro within > org-element-ast.el to make use of this value at compile time? > > I don't know if that would work if e.g. org-element-ast gets compiled > before the user's code, but an interface like that seems preferable to > me. It will not work. I thought about multiple ways to make things work, but everything seems ugly or confusing as an API. I think that the simplest approach could be just leaving `org-element--standard-properties' constant, but stuffing it with truly generic properties that are common for all the possible parsers. WDYT? -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at