From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime Newsgroups: gmane.emacs.help Subject: Re: Initialization warnings without compehensive information about problem Date: Tue, 15 Nov 2022 16:48:02 +0000 Message-ID: References: <6370f707.050a0220.24053.6515@mx.google.com> <637108ff.df0a0220.fdf81.e171@mx.google.com> <874jv2g9qn.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40637"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: Emanuel Berg Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 15 17:48:28 2022 Return-path: Envelope-to: geh-help-gnu-emacs@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 1ouz6q-000AKX-7w for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 15 Nov 2022 17:48:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ouz6f-00086u-T9; Tue, 15 Nov 2022 11:48:17 -0500 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 1ouz6Z-000830-7r for help-gnu-emacs@gnu.org; Tue, 15 Nov 2022 11:48:11 -0500 Original-Received: from mail-40137.protonmail.ch ([185.70.40.137]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ouz6X-00046y-JN for help-gnu-emacs@gnu.org; Tue, 15 Nov 2022 11:48:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1668530887; x=1668790087; bh=59ggLRqExBrsKGZoUdbRQGXCiZy1QuV8e09PBrdg0dQ=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=QOKvx14H2bUKnMOXRZ8ix9V+z374KUSEY4k4qLKWPlzmy2U7d4S5X/HwLEo3C7qYR u4VY5HZ8iOtqTMKF4zu0lCE9Y9yCPhf8243HCMV4AiJ06kSZmb3vkjiW9W+iNGoNlN AuanbyZL+sjkWxHcoEfl8mMh5qaSnkRVeK0PiN0YeeSZcfueScT2xNyslUDCYyHp4n MuXPoxJOQw1IkB6V7oH/u/BvLMWEqBKbYUIx7AqC5OqtsoEsCoXKjsE2++r9ks7toO Y6MWjyxZyn5NlgnbQycRS2SY1tDJcDiWLLdD7evD87c3lw9KLOiNDsFXhAIU/xJeIx 6bqbHG8+2QPfA== In-Reply-To: <874jv2g9qn.fsf@dataswamp.org> Feedback-ID: 57735886:user:proton Received-SPF: pass client-ip=185.70.40.137; envelope-from=heimeborgia@protonmail.com; helo=mail-40137.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:140978 Archived-At: ------- Original Message ------- On Sunday, November 13th, 2022 at 3:22 PM, Emanuel Berg wrote: > Bruno Barbier wrote: >=20 > > > It would be more useful for the "Warnings" to give good > > > information rather than the generic .emacs has a problem > > > with a function definition being void. It is a bother that > > > for any problem one has to rerun again with "--debug-init". > >=20 > > You just need to always start emacs with '--debug-init', if > > you really want Emacs to always immediately stop on any > > config issue. >=20 >=20 > But that's 0.018 seconds slower ... >=20 > $ time emacs -f kill-emacs > emacs -f kill-emacs 2.16s user 0.21s system 84% cpu 2.809 total >=20 > $ time emacs --debug-init -f kill-emacs > emacs --debug-init -f kill-emacs 2.23s user 0.19s system 85% cpu 2.826 to= tal I would be far more convenient if the "*Warnings*" could provide a little b= it more information about the problem. Not at the level of --debug-init or byte-compilation, some something one can act on.