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 13:20:21 +0000 Message-ID: <871qfbsaju.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> <87edjbsc8k.fsf@localhost> <83r0nb1mb1.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="8720"; 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 15:20:26 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 1qdsSH-00025a-SW for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Sep 2023 15:20:26 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qdsRa-0007B4-6S; Wed, 06 Sep 2023 09:19:44 -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 1qdsRW-0007Af-5p for emacs-devel@gnu.org; Wed, 06 Sep 2023 09:19:38 -0400 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 1qdsRT-0006Hg-B9 for emacs-devel@gnu.org; Wed, 06 Sep 2023 09:19:37 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id EFF91240027 for ; Wed, 6 Sep 2023 15:19:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1694006371; bh=IMC3U3LlmLMNtXKvA6fCE0jUG6Gf6+pDYqnMumDM7F4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=HFEP+LGCJw6aNjWuj90I9iX5oWYNE7P7qAI42NsieyuPXf8VcaaAHzsTijNLYpT4s 0nIyMy2ysYbxA+wSY6T4oV8tk7F8YaFREatyMSVyVPlUpvTU/Ro4bzj+xSGxvkEd7y iYSWuaGoxKqjgyqz3YetDOSwIsvQWEG9T9pxczRLHRKub/e/Ym0eknZLKuR71RgJJ2 fSO5ftW2RzNj06Z+JWp1KxRdK3rb2yH0z6DHQMvBgFWDfA+KP5XR5nIPqD9wprby3D J8IbN6GJSzVS2sSQgXja7EbUTOCI5W6AQIFSekgRznHeamBdSx+Ar6M1A+BL33AaT0 KhnUpTj5k0iNQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RgjdZ4vL4z6tww; Wed, 6 Sep 2023 15:19:30 +0200 (CEST) In-Reply-To: <83r0nb1mb1.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 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:310202 Archived-At: 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. 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. >> 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. > > That was for Org-to-Texinfo conversion. Here we are talking about > Org-to-Info, which is much more work. Why so? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at