From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: master 5a125fb5a97 1/2: Update to Org 9.7.3 Date: Wed, 12 Jun 2024 10:46:07 -0400 Message-ID: References: <171796793548.23337.12512115872160390161@vcs2.savannah.gnu.org> <20240609211858.A2C31C1F9FB@vcs2.savannah.gnu.org> <87ed927ris.fsf@kyleam.com> <86frti1r1w.fsf@gnu.org> <87tthy71xw.fsf@localhost> <864j9y1fge.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="13119"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Ihor Radchenko , kyle@kyleam.com, stefankangas@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 12 16:46:54 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 1sHPFW-0003F1-D1 for ged-emacs-devel@m.gmane-mx.org; Wed, 12 Jun 2024 16:46:54 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sHPEx-0003bg-OJ; Wed, 12 Jun 2024 10:46:19 -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 1sHPEs-0003bI-2S for emacs-devel@gnu.org; Wed, 12 Jun 2024 10:46:14 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sHPEq-0003R0-BP; Wed, 12 Jun 2024 10:46:13 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 8D578442643; Wed, 12 Jun 2024 10:46:09 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1718203568; bh=LUTrvI+J3vrpe18liSlHqZTdCLFhP5ff2x0dxKZ/Lwk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=IRA9mmQS1hRanUyUIsr5bSJqwbtUk5iRV7PRL4nYYibLlwH6+5tfsfWNjGcNKqkcT am02UAZcWX4O8Wj+PZLkjY+k1idwy2+9iD+vhPtYKuCxlo8xxWtJGJK1Cy0lTeVxL3 oMciUL185x+X/qSNFyRdVnacvDLcaYPeN5oOtQerMVxmABf+onDJs1vT64ew5UEM+7 wsYb/jmpzyXj3Thkn0r7twHqAzkMGqKgxNc0qyTgiv084adqBPQacYQZ69vo8hMtm0 fVZGNK+R9peMpBvSXgpEy9/T2yO2BhvPmvOBBYqcxu9x0pgBsBO/cluD56XSHRfVph csKrJZWpa55Kw== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 4D6BD44263A; Wed, 12 Jun 2024 10:46:08 -0400 (EDT) Original-Received: from lechazo (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 3AFB612077E; Wed, 12 Jun 2024 10:46:08 -0400 (EDT) In-Reply-To: <864j9y1fge.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 12 Jun 2024 16:02:57 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 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:320003 Archived-At: >> The existence of such script implies that .texi files generated by Org >> are not well-formatted. May you please explain why org.org file needs to >> be parsed and why parsing org.texi is not sufficient? > I don't think it has anything to do with formatting of org.texi. The > issue here is that info/DIR file might be generated when org.texi is > not yet available or not yet up-to-date, such as during bootstrap or > after some change in org.org. IOW, the reason for this behavior is > that we want to produce info/DIR from the source files, not from the > generated files. I don't think this argument is very convincing: getting the info "from org.org via an awk script" is not that different from getting it "from org.org via org-export plus install-info". So, I understand it to be simply what we currently have and that changing it could take a fair bit of work for a rather small benefit: it's easier to fix the awk script and move on. Stefan