From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Towards a cleaner build: other output Date: Mon, 17 Jun 2019 18:48:25 -0400 Message-ID: References: <83zhn6zkgf.fsf@gnu.org> <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="189254"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 18 00:48:42 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 1hd0Qc-000n6y-LW for ged-emacs-devel@m.gmane.org; Tue, 18 Jun 2019 00:48:42 +0200 Original-Received: from localhost ([::1]:52406 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hd0Qb-0004Ty-L1 for ged-emacs-devel@m.gmane.org; Mon, 17 Jun 2019 18:48:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38636) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hd0QV-0004Tg-99 for emacs-devel@gnu.org; Mon, 17 Jun 2019 18:48:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hd0QU-00055D-7X for emacs-devel@gnu.org; Mon, 17 Jun 2019 18:48:35 -0400 Original-Received: from [195.159.176.226] (port=53390 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hd0QU-00053i-02 for emacs-devel@gnu.org; Mon, 17 Jun 2019 18:48:34 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hd0QR-000mvm-In for emacs-devel@gnu.org; Tue, 18 Jun 2019 00:48:31 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:QPIiQahJwi3dJLTsIQ+2tH+nIko= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 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:237809 Archived-At: > There's one point I'd argue for more messaging than we have today. Or > at least different messaging: > > GEN loaddefs.el > Not registering prefix "lo" from completion. Affects: > ("locate-completion-entry" "locate-completion-entry-retry" > "locate-completion-db-error" "load-completions-from-file") > Not registering prefix "*" from ielm. Affects: ("*" "**" "***" "*1" "*2" "*3") > (etc) > > When we come to this point in the build process, even on my fastest > machine, it pauses for many seconds. I'm not sure that the "not > registering" thing is useful, but it'd be nice if it gave more feedback > to let us know that it was working on something and not having choked... 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). 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. > 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! Stefan