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: [ELPA] New package: jami-bot and org-jami-bot Date: Fri, 12 Jan 2024 14:13:50 +0000 Message-ID: <87il3yprkx.fsf@localhost> References: <875y0i7e43.fsf@hoowl.se> <87y1cyqoso.fsf@posteo.net> <83r0inj9oi.fsf@gnu.org> <87y1cupw0g.fsf@localhost> <83y1cuirfc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26903"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, rms@gnu.org, philipk@posteo.net, hanno@hoowl.se, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 12 15:11:38 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 1rOIG2-0006oe-Fq for ged-emacs-devel@m.gmane-mx.org; Fri, 12 Jan 2024 15:11:38 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rOIFF-0000Ai-G3; Fri, 12 Jan 2024 09:10:49 -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 1rOIFC-00008C-Mf for emacs-devel@gnu.org; Fri, 12 Jan 2024 09:10:46 -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 1rOIF8-0001MA-D7 for emacs-devel@gnu.org; Fri, 12 Jan 2024 09:10:46 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 77DF8240029 for ; Fri, 12 Jan 2024 15:10:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1705068638; bh=p+Ju9JUu7pzi0oPvSSf5M/dxFi72/rhAEGN1iTQXk5w=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=T/APFStgsYC4wJpF+bdAQsJK4B0/POrQLFeFb3rBAcJP8RbYiiqZBhoi0VeW4tABw dz1PKCdjYXkdztVYAK6fnrftsSEC+aD2xZ8cW/4TQlOvILTaq0vfhj7KeUJyN4Pnhq Pz6n7xQz8dIpoBuf4uZxrqSy17d1ylrUifR9RqxoSJlbtoR/7/BZKGZsy7AR3gPqNB 4cYdtO3IvwDH+X50/TvAxcxY8gB0VWPwQS8WF9oLrf2feJR0M27RpgkbC1nZkdIcN8 JhHB48zGRuOhFCRGQ65VtmgT72QmU1XG9fa1EF/++nHHzH7s55rOr6Jll+dP3h+djE +ivFbmBfvYJig== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TBNjT3W9jz9rxB; Fri, 12 Jan 2024 15:10:37 +0100 (CET) In-Reply-To: <83y1cuirfc.fsf@gnu.org> 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_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable 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:314902 Archived-At: Eli Zaretskii writes: >> If someone writes a parser that can understand alternative, non-Org >> markup of source files, and produce org-element-ast.el-compatible list >> structure, most of the ox-* exporters should remain functional. > > It would be better to allow alternative data structures to be input to > the export functionality, rather than expect other features to mimic > the Org parser and its outputs. One way or another, there should be some structure to the parser output. Org parser output is just a nested list. org-element-ast.el defines the details of what can be inside that list - independent of the details of Org markup, and compatible with the existing ox-* implementations. Moving away from the nested list is not feasible. Not unless you also want to force all the third-party ox-* libraries to be rewritten or remain incompatible. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at