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: master 5a125fb5a97 1/2: Update to Org 9.7.3 Date: Wed, 12 Jun 2024 12:58:19 +0000 Message-ID: <87tthy71xw.fsf@localhost> References: <171796793548.23337.12512115872160390161@vcs2.savannah.gnu.org> <20240609211858.A2C31C1F9FB@vcs2.savannah.gnu.org> <87ed927ris.fsf@kyleam.com> <86frti1r1w.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="9854"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Kyle Meyer , stefankangas@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 12 14:57:14 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 1sHNXO-0002OD-P7 for ged-emacs-devel@m.gmane-mx.org; Wed, 12 Jun 2024 14:57:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sHNWu-00017I-Pr; Wed, 12 Jun 2024 08:56: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 1sHNWs-00016z-DL for emacs-devel@gnu.org; Wed, 12 Jun 2024 08:56:42 -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 1sHNWq-0007F6-5N for emacs-devel@gnu.org; Wed, 12 Jun 2024 08:56:42 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 9C07B240028 for ; Wed, 12 Jun 2024 14:56:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1718196997; bh=I6F8V5icjjnJ1YXk2Nq8gL4iOyZeCPA//Waqk3gLP7U=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=qHiQkUKtlu6D0mrY3dIdvL3R7z3kGEm3A4fDktEOUK1VnzTtifSw4n1t6ayiQze/E 4HA4U5q7O4kWR2+emKXYcQBnciZLB8Y6Wcek/imFYoDIGhLBINzFJZKSldbW2/djuJ jALK1VaV9BKiBbmguqpdOfD9TiMbLaa9ZSfNCvijc0jOF5i8YXHp4Td4GVIJGvqCPP 1P0PJ6OOj3d6HWpMRrIepFCboyIyhUwdyKf0nwzl01tbXFz8CtfieIQSVizfCLg+wL moNPM1dApX/XFMJdTLTtHYrKbDE4z4i+PKwvRywuWZ8BWxnBw3HVNwmtMIuxA+WON8 hI2b6CxRy3DHg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Vzlsw0XrGz9rxB; Wed, 12 Jun 2024 14:56:36 +0200 (CEST) In-Reply-To: <86frti1r1w.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_H3=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=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:319992 Archived-At: Eli Zaretskii writes: >> > After make bootstrap, I no longer see the Org manual in the info/dir >> > file. git checkout 5a125fb5a9736bd^ fixes the problem. >> >> Thanks for spotting. I don't have time to look at it more closely >> tonight, but I think build-aux/make-info-dir needs to be adjusted for >> Org's b0c3c9057 (ox-texinfo:: Always provide a @direntry, 2024-03-08). > > Thanks, this was indeed the reason. I hope I fixed that now. > > Please in the future take this into consideration when you decide to > modify the way org.org specifies the various Texinfo constructs, as > this affects more than just Org itself. I was not aware that Emacs uses a custom awk script to parse .org source in addition to .texi source. 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? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at