From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Org mode and Emacs Date: Wed, 06 Sep 2023 18:25:27 +0300 Message-ID: <83pm2v1fyw.fsf@gnu.org> 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> <87edjbsc8k.fsf@localhost> <83r0nb1mb1.fsf@gnu.org> <871qfbsaju.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32576"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 06 17:27:09 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 1qduQv-0008Ke-Kg for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Sep 2023 17:27:09 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qduQ0-000552-RA; Wed, 06 Sep 2023 11:26:12 -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 1qduPt-000543-Kq for emacs-devel@gnu.org; Wed, 06 Sep 2023 11:26:05 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qduPr-0006rL-K2; Wed, 06 Sep 2023 11:26:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=beCN5HfncYms5S1nSyGwqGMsUbXTiz4cSKRSwX+B7IU=; b=cOMjYyeYd/B5 pN1Mz+iwP1prCGBdYhLZ8v3v6R9/mqYVSMuUMypEuvgx07hQcLLzG6TQg+PI/8QjWYiKT6Zm5+eXc QEehcQcJoVC3cFKf8pAxdVzCM+mn6H0Bsy09TZUDqim45cM6OYqS9TddvqoEz3nxFdGZOL5CZXijC yEWEMXzt6aCnzmbp2Rho2f0hOHdi4utl+huF2XeVTe+5PfpOcZPWlEtUK/5BQagW03mMVqA17/zUs HabY0/G8YnxNm7MpYM1S1s6+zMpTY4s6D2CoYNouuBVdpJkQpeIxal1hmWA6EEDijl7l3xYnJD0iz VF5oJ3wNAqeBAZD17iflkw==; In-Reply-To: <871qfbsaju.fsf@localhost> (message from Ihor Radchenko on Wed, 06 Sep 2023 13:20:21 +0000) 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:310205 Archived-At: > From: Ihor Radchenko > Cc: rms@gnu.org, emacs-devel@gnu.org > Date: Wed, 06 Sep 2023 13:20:21 +0000 > > Eli Zaretskii writes: > > >> 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. > > > > Not the output format, but the language: new directives and sometimes > > markup are added with every release of Texinfo. Just read their NEWS > > file. > > The way I see Org markup extension would make it easy to users add new > custom markup, as needed. Then, no frequent changes to the base markup > will be necessary to accommodate for less common use cases. You missed the "new directives" part. I do recommend reading their NEWS to get the idea of the rate at which new features are added to Texinfo. > In other words, I do not see why Org should support every single Texinfo > markup. We just need to provide enough support to be on par in terms of > the needs of manual authors. GNU Manuals use a large portion of what Texinfo provides, and limiting what they could use when they write in Org would mean some Texinfo features cannot be used that way, which is a disadvantage. People will have to think twice before they switch to Org, because at some point they might want to use a feature you decided not to support. > > That was for Org-to-Texinfo conversion. Here we are talking about > > Org-to-Info, which is much more work. > > Why so? Because the production rules are much more complex. I suggest to take a look at the Perl source code of texi2any to see what it entails.