From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Towards a cleaner build: other output Date: Tue, 18 Jun 2019 01:02:00 +0200 Message-ID: References: <83a7eo9nsh.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="249363"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 18 01:03:06 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hd0eY-0012jc-3C for ged-emacs-devel@m.gmane.org; Tue, 18 Jun 2019 01:03:06 +0200 Original-Received: from localhost ([::1]:52476 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hd0eW-0003N1-IP for ged-emacs-devel@m.gmane.org; Mon, 17 Jun 2019 19:03:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41847) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hd0da-0003Ln-KX for emacs-devel@gnu.org; Mon, 17 Jun 2019 19:02:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hd0dZ-0001bm-Kp for emacs-devel@gnu.org; Mon, 17 Jun 2019 19:02:06 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:48434) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hd0dZ-0001ak-ES for emacs-devel@gnu.org; Mon, 17 Jun 2019 19:02:05 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=stories) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hd0dV-0001xM-0z; Tue, 18 Jun 2019 01:02:03 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAD1BMVEUoJy3T0tursb52iKE/ Wn7yWvCNAAACVklEQVQ4jUWU27HDIAxEdYECIuwCDLgAXgVgoP+a7gqcCR/ODMcraRccmms55oP3 cvuH5my0AOe1IU9bCgCVSgscHW8X/gHvN+BgTUwbZAFYG3Awev3aKoq1fHKhh0Ob3dl7plHr7DWU XHK1apdaU41S5ri9TcUVfo7hfuCeuTqbi8uYyqMKeyc+QkGPEFJOSvo6Do1oOIAbPbx1t18OPR9z LEUJs89v5SW55sy7VK8L1PJK1MqK58iisIWGgDPxAiPUMSbmONsLMtelcAUgPByJtH0kS+fcUoSR 65UsNTIHAAotMPuNHtFdZBCmgPIelIBKKGRuIml7vCAPKCT7hDaabX7ByGGMKsAdBSBQfkEoo00y hdSRorKmuW+6VUCqja70URiOf2BO1JFiH9PJcP8e1FKwxdaHFMz87alq2IAvxSdpMp+HbeyIfStC iX8AOKT4sEdhAejxYEcDXGj1d0hyM6GUof54d/FBBUBdBh2HnQMxmdGPitEeCfmCF7lXC1TdmgaQ sW9zu29zbUfL6phazoUyxp68DGKZorKL6SATpzE7EkPNVHwNeF9b5Gzw5szL4NLcky/y0F7pouFX iJ1qJF9Wb03TRBr38rG+kt40w6gc53aOQh0bSiNgsa4DHqPKuArFtY43lYa4UBCTlBOKicRNizmu Qs9pAqYSRUU4crGiJEXuHNd7tHksx+/C5yNTiSI2OG5f4EnD2ayzIRN1UxKS4Qc7at32XNVtGqV1 u+QYzamo21BcNV4SEVBYbuo1BQxXf40RDsyh6P5n2LGbKie/+T+B/ImluiYywQAAAABJRU5ErkJg gg== In-Reply-To: (Stefan Monnier's message of "Mon, 17 Jun 2019 18:48:25 -0400") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.231.51 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:237813 Archived-At: Stefan Monnier writes: > This is the step that builds the loaddefs.el file (i.e. all the > autoloads). It also happens to build the "prefix" table used to try and > automatically know where to find which definitions, but that's > a side-gig. So the processing doesn't have anything to do with > "completions", really (in the above warnings "completion" refers to the > completion.el package). Ah, I see. > So, yes, you can output some progress messages if you want (it only > takes a long time during bootstrap. On rebuilds it's usually very > fast), but makes it says something about "scraped autoloads from > N files" or something like that. OK; I'll change the patch to that. >> I don't see much value in the "Not registering" messages, because I >> don't see how any developer would respond to the output, but I may be >> totally wrong here. > > Those "not registering" mean that the corresponding definitions will not > be findable via things like `C-h o` until the package is loaded. As for > what the developer should do: cleanup his namespace! :-) -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no