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: Org mode and Emacs Date: Wed, 06 Sep 2023 12:43:55 +0000 Message-ID: <87edjbsc8k.fsf@localhost> References: <83msyemjx8.fsf@gnu.org> <871qfpoij6.fsf@gnu.org> <87fs45ivyo.fsf@localhost> <87h6okga15.fsf@localhost> <87cyz61cbp.fsf@localhost> <87v8cuqtkr.fsf@localhost> <87sf7rsfpd.fsf@localhost> <8334zr32ih.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="20397"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 06 14:43:59 2023 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 1qdrt0-000560-LF for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Sep 2023 14:43:58 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qdrsQ-0003Hq-8F; Wed, 06 Sep 2023 08:43:22 -0400 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 1qdrsO-0003Hf-Qe for emacs-devel@gnu.org; Wed, 06 Sep 2023 08:43:20 -0400 Original-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 1qdrsL-0006VK-HV for emacs-devel@gnu.org; Wed, 06 Sep 2023 08:43:20 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 0A9FC240103 for ; Wed, 6 Sep 2023 14:43:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1694004195; bh=Od0TWpz5w8Cwt+Q9CBFOZaaeVa+ytoMp0ReGK2tj8c0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=aAnEL1fFsdvGYXGcT0J7CVBSLh/bwr0ye8xqxCS5fwgQa5ucELjI1vzc8dlZzoW6l kFrmJHfl99zied2RmFSjH22IkI/GJEBgze/oI9Q8T6gTn6SjadT63HDXheV96H4nKg WI4jNvHJjYqECygis394/ms3wmGSE/F4TnJzMhIL22hvpblb3J8P6dSXJ8sCav45aP EcbUfYwjtm4kIwA5BNSbZDbFh1aPF7kR9LoxqpfrbOz6gsT5UC7TjNKm7ZuG6ADKvv 6Tkr5kNqAUk8aQBo8HGySPLVwCwcOLNkD6RkHqg5+MvjXvrLhqG2tJJxfuqm1QduDL fLLYLVOpdSBkA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Rghqk2BrLz9rxF; Wed, 6 Sep 2023 14:43:14 +0200 (CEST) In-Reply-To: <8334zr32ih.fsf@gnu.org> 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-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:310193 Archived-At: Eli Zaretskii writes: >> I think I need to clarify. This is how export to info works _now_. >> However, nothing stops us from implementing direct export org->info >> without intermediate org->texi step. Someone just needs to do this job. > > Unless the implementation will somehow invoke texi2any under the hood, > this would mean a separate implementation of texi2any in Emacs Lisp, Yes. We already have org2pdf, org2ascii, org2html, but not org2info. > something that I don't recommend: it will need to play a constant > catchup game with the Texinfo development, and it will be probably > quite slow. I am not sure about catchup game. Unless Texinfo drastically changes the output format, we can simply provide default settings to replicate the Texinfo look of the produced html/pdf/plaintext/info files. As for being slow, it is already not the case. Last time we discussed Org export being slow, I have managed to speed things up on par with Texinfo timings on Org manual. In any case, the first step is extending Org markup to be more suitable for software manuals. Whether we use texinfo under the hood or not might be discussed afterwards. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at