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 c86995d07e9: Enable code block evaluation when generating .org manuals Date: Sun, 09 Jun 2024 18:45:15 +0000 Message-ID: <87v82i0xc4.fsf@localhost> References: <171767737644.19678.784876979840850798@vcs2.savannah.gnu.org> <20240606123616.DE7C9C1F9EF@vcs2.savannah.gnu.org> <87h6e6i1mg.fsf@gmail.com> <87sexplbmn.fsf@kyleam.com> <874ja22e7t.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15083"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Kyle Meyer , Robert Pluim , emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 09 20:44:37 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 1sGNWv-0003jL-6V for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Jun 2024 20:44:37 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sGNW6-0003JJ-EN; Sun, 09 Jun 2024 14:43:46 -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 1sGNW4-0003J4-Pf for emacs-devel@gnu.org; Sun, 09 Jun 2024 14:43:44 -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 1sGNW2-00030b-5B for emacs-devel@gnu.org; Sun, 09 Jun 2024 14:43:44 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id BCDD6240106 for ; Sun, 9 Jun 2024 20:43:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1717958619; bh=vlHzFoOT9+zO4E5vgWuXmHoDGkNxCg0CnYGyRd5rNBM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=WIl1fxNqeTjKJ/VvFapktx/K3u7aZCBl8E5QBOSSiO1ycJFVMmYHEn0OLUMaw50Bj AXBowMW+M1s3ShbV5UFswMswMf2fSjnov6AMrXIRqMux1y2A97QrtIVirunQLS5E95 sHT5a4X2Qm7pm/jEKcDswWA9jEn7T5XHiy/4/G/buvXTIdHN5b7pQTxyWzNC2Nbjf/ 7fXOcF7WqfnPCfuIsaXnp2eY89Wsbtcpp0zNd0MYbUocjWJIsmVDwuIlQEz52ztXuG TboknC1azr6vIrlv40J4YJ+kyVWMRnwBi3Ld5iN5kbUPqM2ega1jJd7AHFRzRfCA9Y bHzBbP2M7nAoA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Vy3jl1qNWz6twL; Sun, 9 Jun 2024 20:43:39 +0200 (CEST) In-Reply-To: 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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:319936 Archived-At: Stefan Kangas writes: >>> Does it really need to generated automatically on every build, or can it >>> be handled in some other way? For example, we pre-generate our loaddefs >>> files and commit the result. >> >> Preferably, every build, I think. >> >> What we do in Org mode manual is examining an Elisp variable and build a >> table summarizing its values. If that variable changes in the code, the >> manual should reflect this change. > > Right, but the same is true for our loaddefs files (you want them > up-to-date, or you get warnings, etc.), and even for them it's been > enough to have a cronjob regenerate and commit them once per month. > > So I think my question still stands. It is certainly possible. We would need to run pre-processing and then generate the final manuals from yet another intermediate pre-processed .org file. However, I am not sure why would we need to bother with such extra work. What would be the benefit? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at