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: Mon, 30 Dec 2024 17:18:01 +0000 Message-ID: <87ed1p2ipi.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> <87r05qtdm3.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="2151"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, 74994@debbugs.gnu.org To: Richard Lawrence Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 30 18:16:50 2024 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 1tSJNq-0000RW-JN for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Dec 2024 18:16:50 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSJNd-000172-Fn; Mon, 30 Dec 2024 12:16:37 -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 1tSJNb-00016k-1Q for emacs-devel@gnu.org; Mon, 30 Dec 2024 12:16:35 -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 1tSJNY-0004DC-Th for emacs-devel@gnu.org; Mon, 30 Dec 2024 12:16:34 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 8346A240027 for ; Mon, 30 Dec 2024 18:16:31 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1735578991; bh=UjEJLoc4FPdTcB82uF9OxX96yEx3VezDW/YiDTDkRPc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=Aadky5Exhrn+HRMG8jXhq0IPD5P2+7d0gA+PLmdBf6/yoxF/srn5LD6CkoTQMVN62 c69lO0SFUFAeIc13KFTib/1eNpytn8y1kt5Qg/GMy6C1cjYd4ASN0KRxJ7Ulm5ckz9 u8SbhPRoS+SjF15auhgmn3HnvVTLV/mp90vQ0vHbxtsmZkDUNAaVi83cpTKcZvmkKm LflssFhS96b5/iAbo3x6xfRYreeIx7EZFokyegCVpD+8uLygwzmOpOnLQyE9up63nD GKAjWdNaIW9ZVpTCZ2oHH5np57K+LdIJsOQeAeOArYueOhC3I17uHWVBe3iA+qt9LF j87FPT0PrUuVQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YMN730Gczz9rxD; Mon, 30 Dec 2024 18:16:30 +0100 (CET) In-Reply-To: <87r05qtdm3.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_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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:327451 Archived-At: Richard Lawrence writes: > Ah, looking over this again, there was one thing that I felt didn't fit > very well with org-element-ast: in iCalendar, "properties" can have both > a "value" and a list of "parameters". These are different types of > objects and it's most natural and useful not to lump them together, but > in the Org element AST they would probably both just be "contents" of a > property node (i.e., child nodes). Thus, in my draft icalendar-ast.el, > instead of using > > (TYPE PROPERTIES CONTENTS) > > as the basic representation for a node, I used > > (TYPE META VALUE CHILDREN). > > The org-element-ast representation is obviously capable of making the > distinction between values and parameters in some other way; but it's > pretty much the only example I can think of where I felt the > org-element-ast representation might not be the best for the needs of > iCalendar. Have you looked into secondary nodes? -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at