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.bugs,gmane.emacs.devel Subject: bug#74994: Upstreaming org-element-ast (was: Improving Emacs' iCalendar support) Date: Mon, 30 Dec 2024 17:16:11 +0000 Message-ID: <87h66l2isk.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38143"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 74994@debbugs.gnu.org, emacs-devel@gnu.org To: Richard Lawrence Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Dec 30 18:15:31 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1tSJMZ-0009jd-Iu for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 30 Dec 2024 18:15:31 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSJM9-0000CG-5P; Mon, 30 Dec 2024 12:15:05 -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 1tSJM7-0000Bw-Ko for bug-gnu-emacs@gnu.org; Mon, 30 Dec 2024 12:15:04 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tSJM7-0003v8-B9 for bug-gnu-emacs@gnu.org; Mon, 30 Dec 2024 12:15:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-Version:Date:References:In-Reply-To:From:To:Subject; bh=MWzZq2Vy5BrMdDsmRp2h6rcVExNRBSixxZ7tF9IbgAY=; b=Vq63X71pfV36zrkxhxrv3YBK/RkXWs56ql3ZeSZ4dCLjfsMAggWYqj8lUnqDp02m040CTwVmSjgbHTCnERwVHdQcaloAzVspzO7N+CxZwyCsgX1gtogacO64HTs/HO/kPeSxZtTFxBU2kWL+R522V+IUIlCMpgFpezSRNQbq6Ski2Fqvz/HeJDVEN2+A5rEiZCgMSD+1cmDhpAN56Cakkv12gGBrqx695cMcCGoQtg/NXU1e6VrNc77I3Ej2PBOYRPIya68aUgX4t6k5aqao8fLW9nEGSLRhwYpaQ8PfqDav+76BP0Azwauh+UVT6exH1aKmZuaAsXwqn0rIgschsQ==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tSJM6-0004i8-4V for bug-gnu-emacs@gnu.org; Mon, 30 Dec 2024 12:15:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Ihor Radchenko Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 30 Dec 2024 17:15:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 74994 X-GNU-PR-Package: emacs Original-Received: via spool by 74994-submit@debbugs.gnu.org id=B74994.173557889218073 (code B ref 74994); Mon, 30 Dec 2024 17:15:02 +0000 Original-Received: (at 74994) by debbugs.gnu.org; 30 Dec 2024 17:14:52 +0000 Original-Received: from localhost ([127.0.0.1]:59671 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tSJLv-0004hP-FK for submit@debbugs.gnu.org; Mon, 30 Dec 2024 12:14:51 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]:59747) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tSJLs-0004h9-RD for 74994@debbugs.gnu.org; Mon, 30 Dec 2024 12:14:49 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 90F27240027 for <74994@debbugs.gnu.org>; Mon, 30 Dec 2024 18:14:42 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1735578882; bh=U7XJiQURvyB9bpLSEv2Bs7eXTcW/kHKYjNj+t40UToo=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=oFC/LxGnyp23+e8Cec0N/nYHbw/4uKErsIrKE/xGRFdyp7v/o/67QI4PGiuWEwCbn BPb/OJZ517LQ1g+fgL0NkNT5YqduKazhUGLi7qQORyEYtIiZTd75yD9ltgy2K6E/PE khkQdG2XWolgckgzYzurYFo7bkkp9agToqlFucdpFgxDx68guYCXEHMnjgheyJBV60 hKuSnKgxcRbIR7Nr3BWPj5XF8i9VAm+FvUzDRPScMty3iUXjULn/IJV3eCSv0JjGMe fuTW1NbvcmDrm7BX0dxZCs1C+kVtGqIwySiQj+BCTUuqX37MExXWjVPq8muSxJOaW+ UFxSHFAwKiJRw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YMN4x4hnhz9rxF; Mon, 30 Dec 2024 18:14:41 +0100 (CET) In-Reply-To: <87ttamtf7g.fsf@recursewithless.net> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:298010 gmane.emacs.devel:327450 Archived-At: Richard Lawrence writes: >> Richard, is there any specific reason why you had to make things from >> scratch? May org-element-ast be changed to fit your needs? > ... > No, it was more that, as things stood, I wanted to wait and see what > would happen with upstreaming org-element-ast. My idea was to make it > easy to switch once that happened, but not to wait to make progress in > the meantime, that's all. org-element-ast is already a part of Emacs. The process of upstreaming in this particular case is simply a question of (1) making the library more useful outside Org mode; (2) renaming it. Renaming is trivial. The main question is making things usable outside Org mode. And that's where your work is the most valuable. So, it was me who is waiting for your input before upstreaming :) > One thing about your question confuses me, namely: > >> ...instead implement a custom parser generator. > > As I understand org-element-ast, it basically just defines the parse > tree representation and various accessors for working with it, not the > parser itself. Was your suggestion that I could also use the Org parser, > not just the parse tree representation? If so, then I misunderstood, and > presumably more code is involved than is found in org-element-ast.el, > right? No, I did not mean that you should use org-element to generate parser. I mostly referred to the way you implement the parser where part of the parser configuration is stored in the AST. But I was reading your patch very quickly and could have misunderstood something. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at