From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#61014: 29.0.60; flymake-mode stderr warning is confusing when edit the init.el or eary-init.el Date: Thu, 02 Feb 2023 12:25:39 +0200 Message-ID: <83h6w4xt24.fsf@gnu.org> References: <831qnljt26.fsf@gnu.org> <87fsbxlf54.fsf@gmail.com> <83r0veaor9.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36443"; mail-complaints-to="usenet@ciao.gmane.io" Cc: aqua0210@foxmail.com, 61014@debbugs.gnu.org To: joaotavora@gmail.com, monnier@iro.umontreal.ca Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 02 11:26:26 2023 Return-path: Envelope-to: geb-bug-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 1pNWnS-0009Gv-4N for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 02 Feb 2023 11:26:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pNWn6-0006lU-7N; Thu, 02 Feb 2023 05:26:04 -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 1pNWn4-0006l5-Nu for bug-gnu-emacs@gnu.org; Thu, 02 Feb 2023 05:26:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pNWn4-0007gA-3K for bug-gnu-emacs@gnu.org; Thu, 02 Feb 2023 05:26:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pNWn3-0000gW-Rd for bug-gnu-emacs@gnu.org; Thu, 02 Feb 2023 05:26:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 02 Feb 2023 10:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61014 X-GNU-PR-Package: emacs Original-Received: via spool by 61014-submit@debbugs.gnu.org id=B61014.16753335502611 (code B ref 61014); Thu, 02 Feb 2023 10:26:01 +0000 Original-Received: (at 61014) by debbugs.gnu.org; 2 Feb 2023 10:25:50 +0000 Original-Received: from localhost ([127.0.0.1]:60893 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pNWmr-0000g3-So for submit@debbugs.gnu.org; Thu, 02 Feb 2023 05:25:50 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:37926) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pNWmo-0000fm-95 for 61014@debbugs.gnu.org; Thu, 02 Feb 2023 05:25:47 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pNWmh-0007aA-FZ; Thu, 02 Feb 2023 05:25:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=d4BhQS4Id0ukENbYUzlCVVHT5ABd0R/hU3L7qfqsI7o=; b=RFS69ygq4h6slqwZt/Db OmO5xTztC7VKucgCLEu/E0CEHPeraQ7ek1OdC1DW9tPBnFFiOi4tgCEqGdyQbQP9e+Vblr6K7ypd+ YMbjqI/yaaOARISC5tpAnRATuooAhy40aDwSn/1H+dE+xt5Y1f/gLUJusSVxYpTqqCMAS/X/Mgt+F oxcAQElgS3saIzejOG3NTmttk4VqnrYWS22mELPF7nLluxDNoZxF0DleL/HqTwZ5J3QZcmR1zJV9/ g3Cmo8u8Rfe3seKSD6MAYD3oSgZ92DatwvvQggoC4uG8h1iAhaednWqnsqI6QdcUUK1pVZHXR8cHx D30ZVqAcWqRLzw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pNWmg-0000TW-VP; Thu, 02 Feb 2023 05:25:39 -0500 In-Reply-To: <83r0veaor9.fsf@gnu.org> (message from Eli Zaretskii on Sat, 28 Jan 2023 13:21:14 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:254642 Archived-At: Ping! > Cc: aqua0210@foxmail.com, 61014@debbugs.gnu.org > Date: Sat, 28 Jan 2023 13:21:14 +0200 > From: Eli Zaretskii > > > From: João Távora > > Cc: Eason Huang , 61014@debbugs.gnu.org > > Date: Thu, 26 Jan 2023 11:16:39 +0000 > > > > First of all, let's make it clear that this warning happens in a hidden > > Flymake buffer, an implementation detail which stores the stderr output > > of the subprocess(es) invoked. It does not appear in the interactive > > seeion's *Warnings* buffer. Unless I've missed something, the user is > > never confronted with it or hindered by it in any way. It seems to be > > largely benign. > > > > The warning only become visible when switching to a specific hidden > > buffer, like Eason did, and that operation is more accurately described > > as an introspection feature intended for developers, not for users. > > > > So, to summarize, the warning is coming from the subprocess > > non-interactive Emacs spawned by the interactive Emacs where > > flymake-mode is turned on. In the interactive Emacs session, nothing > > special is going on. > > > > The reason elisp-flymake-byte-compile-load-path has a default value of > > "./" is to help with the primary use case for the > > elisp-flymake-byte-compile Flymake backend: developing libraries that > > `require` other .el libraries. Such .el files often live in the same > > directory of the file/buffer you are editing with flymake-mode turned > > on. So when you're editing x/y/z/foo.el and you type > > > > (require 'foo-utils) > > > > elisp-flymake-byte-compile will understand that to syntax-check foo.el > > with the byte-compiler it needs to load "x/u/z/foo-utils.el". > > > > In Eason's case, the user happens to be editing a .el file in a special > > Emacs directory where such a use case is unlikely (though not > > impossible). So every few changes the user does to the buffer, > > flymake-mdoe will invoke a Emacs subprocess and give it this particular > > load-path initialization, that, in the specific acse of ~/.emacs.d, is > > slightly non-orthodox. And thus the subprocess emacs complains with > > this warning which is recorded in the special hidden buffer. > > > > If we're really worries about this, we could special-case this directory > > elisp-mode.el. But I also don't see what the harm could be. So my > > advice is to only do this when someone describes real harm. > > How about disabling this warning in non-interactive sessions? That > should be easy, and I don't see why we would want to emit such a > warning in non-interactive sessions anyway. > > Stefan, am I missing something? > > > >