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 17:55:18 +0000 Message-ID: <874ja22e7t.fsf@localhost> References: <171767737644.19678.784876979840850798@vcs2.savannah.gnu.org> <20240606123616.DE7C9C1F9EF@vcs2.savannah.gnu.org> <87h6e6i1mg.fsf@gmail.com> <87sexplbmn.fsf@kyleam.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5846"; 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 19:54:27 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 1sGMkL-0001K7-V2 for ged-emacs-devel@m.gmane-mx.org; Sun, 09 Jun 2024 19:54:26 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sGMjk-00017G-Af; Sun, 09 Jun 2024 13:53:48 -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 1sGMji-000171-UB for emacs-devel@gnu.org; Sun, 09 Jun 2024 13:53:46 -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 1sGMjg-0002iV-Oo for emacs-devel@gnu.org; Sun, 09 Jun 2024 13:53:46 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id A2768240104 for ; Sun, 9 Jun 2024 19:53:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1717955622; bh=zNKonPIG6qI7pwezY5+QMXNGPscJymxEyfjLbi2Jqzc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=TitlAmKoXTDRfKzwj8lTWqSTjXAHAzRcpBaj/TRvy7CtuAxRhdhm1eOn384jLr1yE 8zEei/OgKmwzUlWLtApG4O490p8K9XuFJRURD/b+4UpNGwB7dBxa7EKcToz7V0Cxwp CSkOVVSZ2e/pCIBDgXyf04IO3BLY1Nng1qOlcjtXdTfloyLUH01eICiy1Py45U/w9G njAbrCFoOQP8hgzeSCI39SDGtZyjmFQZED27XUYhdHkrwoiznTIWuBlXkUwJRxnTkg e+/Ee8pNNnLQjaZuds5Mgn5GuuSp4tKv2JjTgxjPgIQJVMtcsxLdVEuVhOyPlsuEQ4 CuYRFznnX50tw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Vy2c5676qz6tlh; Sun, 9 Jun 2024 19:53:41 +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:319932 Archived-At: Stefan Kangas writes: > Kyle Meyer writes: > >> As mentioned by Ihor (+cc) in bug#71394, this change is needed before >> syncing the latest Org release to the Emacs tree due to Org's 715148131 >> (org-manual: Automatically generate export option list, 2023-07-31). > > 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. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at