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: Odd warning about `customize-variable' Date: Wed, 11 May 2022 20:38:30 -0400 Message-ID: References: <87y1z8cp67.fsf@gnus.org> <87czgj4mkb.fsf@gnus.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="16566"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 12 02:39:49 2022 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 1nowrs-00048M-9G for ged-emacs-devel@m.gmane-mx.org; Thu, 12 May 2022 02:39:48 +0200 Original-Received: from localhost ([::1]:34378 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nowrq-0002kW-U4 for ged-emacs-devel@m.gmane-mx.org; Wed, 11 May 2022 20:39:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45096) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nowqk-00022Q-1F for emacs-devel@gnu.org; Wed, 11 May 2022 20:38:38 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:14952) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nowqh-0005MM-0Q for emacs-devel@gnu.org; Wed, 11 May 2022 20:38:36 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1067880799; Wed, 11 May 2022 20:38:33 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 8F8F28044E; Wed, 11 May 2022 20:38:31 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1652315911; bh=uvL5vs0Byj5j+dmUKMo4m28L+HAu2ExDxCmOxZjQHwQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=Yq9twek+M3OVkWrVtVFnrER5fSBYCE8Hti7E348wO/RaAnu/R/zSWwr0TCQHVMUfZ NxAfmywyxwDVd69XI3A1R4nPC5CpMERBU7mLfhdb/sH6gtlWwmwm4OyP0BWcJ7qMkq uqXxT4fYBjMQ8ZJWzVHHvnlkoM1xaaiyuquJSTt2Oy4zFjrscQAFD8/6SUhvosCnwM ARwQN+04umXO0cJ0SBva8zb/KGO2QaBKYsmkn0+asbZcv5u+8/xBRSTqYPH6Cb9ubM WlSBcHhFI7ahWmDrntybUTJG7L/+UncmoPbwFXfdPcQ4oDODnj89Bvbn925yV3hEMo HjPFzgxNbf0zw== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 2E93F12077E; Wed, 11 May 2022 20:38:31 -0400 (EDT) In-Reply-To: <87czgj4mkb.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 12 May 2022 02:33:08 +0200") 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" Xref: news.gmane.io gmane.emacs.devel:289657 Archived-At: > Ah, I see (I think). And I guess this was triggered by 620ac67355, > which made message require eudc-capf, which explains why we didn't see > this warning until a couple days ago. Indeed. BTW, I don't understand why it needs to `require` eudc-capf, since eudc-capf already autoloads all its functions. Since `eudc-capf` itself requires `eudc`, I think loading these things more lazily would be beneficial. Stefan