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: Tue, 11 Jun 2024 10:05:01 +0000 Message-ID: <871q53u75e.fsf@localhost> References: <171796793548.23337.12512115872160390161@vcs2.savannah.gnu.org> <20240609211858.A2C31C1F9FB@vcs2.savannah.gnu.org> <87a5jtd403.fsf@yahoo.com> <87h6e1lhtd.fsf@kyleam.com> <868qzd9hjg.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="28399"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Kyle Meyer , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jun 11 12:04:18 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 1sGyMT-00076d-CE for ged-emacs-devel@m.gmane-mx.org; Tue, 11 Jun 2024 12:04:17 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sGyLp-0007qd-50; Tue, 11 Jun 2024 06:03:37 -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 1sGyLm-0007q2-1g for emacs-devel@gnu.org; Tue, 11 Jun 2024 06:03:34 -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 1sGyLi-0005Y9-8c for emacs-devel@gnu.org; Tue, 11 Jun 2024 06:03:33 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id F3F71240027 for ; Tue, 11 Jun 2024 12:03:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1718100207; bh=wEz+yoi8DG0YP+Jz70IfWqe3LmnXCS87SoY1aqvI1eg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=lMhEgkOYNTfOFruva9yYkeby7IgvM4wy24lJmF5kULYrW2UXUFDGxN3Wvvjx6NpD5 K/A3PpCXrRT/YzGRZzin9YjHxpBg8E5MydMNN0FqlEhmI/Iv7Spe066RCHwtYRJO7x luULypDpFNBiDIKe25kbZKKM2rsi63vpWfHPLzKbZ/lctpLT9AJLkae+yGa/kbDYeh jVn3czMs7iAbf3L6Hg8KvzqRo2fjjSvm48N4OLdF2Q2Xp/p96XgWQz3toxIiBL5i1a EaX3Fvm3vj/SL5Iz3BjQ+A/4CW5MXlvMGXXGi8ynBEhUmOjKAgm2iZTcPYVsXH3msA D4iKvUMrToktQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Vz44Y01Sdz9rxD; Tue, 11 Jun 2024 12:03:24 +0200 (CEST) In-Reply-To: <868qzd9hjg.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:319966 Archived-At: Eli Zaretskii writes: > There are other issues with this update: > > ELC org/org-macs.elc > > In end of data: > org/org-loaddefs.el:1278:78: Warning: the function `cl-every' is not known to be defined. > > Can this warning be eliminated, please? It can be eliminated, but the warning does not seem to be Org mode's fault. The line in question in org-loaddefs is (custom-autoload 'org-num-skip-tags "org-num" t) (put 'org-num-skip-tags 'safe-local-variable (lambda (val) (and (listp val) (cl-every #'stringp val)))) It is not generated by Org mode, but by loaddefs.el from (defcustom org-num-skip-tags nil "List of tags preventing the numbering of sub-trees. For example, add \"ARCHIVE\" to this list to avoid numbering archived sub-trees. Tag in this list prevent numbering the whole sub-tree, irrespective to `org-use-tag-inheritance', or other means to control tag inheritance." :group 'org-appearance :package-version '(Org . "9.3") :type '(repeat (string :tag "Tag")) :safe (lambda (val) (and (listp val) (cl-every #'stringp val)))) Note that org-num.el where `org-num-skip-tags' is defined does have (require 'cl-lib). IMHO, there is some problem either with loaddefs generation or with the fact that loaddefs file is compiled at all. Of course, we can always convert that lambda into a proper function, which will likely get rid of the warning. (btw, the warning does not appear when running make bootstrap on my side) > Could not read `org-id-locations' from ~/.emacs.d/.org-id-locations, setting it to nil > > Why does it want to read a file from my home directory as part of > building Emacs? That shouldn't happen. Agree. But I am unable to reproduce. Could you please provide more information? > Executing Emacs-Lisp code block at position 643527... > Code block evaluation complete. > Executing Emacs-Lisp code block at position 646480... > Code block evaluation complete. > Executing Emacs-Lisp code block at position 648303... > Code block evaluation complete. > Executing Emacs-Lisp code block at position 648968... > Code block evaluation complete. > Executing Emacs-Lisp code block at position 655333... > Code block evaluation complete. > Executing Emacs-Lisp code block at position 659159... > Code block evaluation complete. > Executing Emacs-Lisp code block at position 659467... > Code block evaluation complete. > Executing Emacs-Lisp code block at position 660552... > Code block evaluation complete. > > Can we please shut up these messages, or at least hide them behind > some $(AM_V_GEN) trick? Why? It is not much different from "scraping loaddefs..." message sequence. Of course, we can hide this, but seeing that some code is evaluated may be useful in the logs. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at