unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: aqua0210@foxmail.com, joaotavora@gmail.com, 61014-done@debbugs.gnu.org
Subject: bug#61014: 29.0.60; flymake-mode stderr warning is confusing when edit the init.el or eary-init.el
Date: Sun, 12 Feb 2023 14:22:17 +0200	[thread overview]
Message-ID: <83ttzrgjk6.fsf@gnu.org> (raw)
In-Reply-To: <jwvilgknk9i.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 02 Feb 2023 11:01:20 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: João Távora <joaotavora@gmail.com>,
>   aqua0210@foxmail.com,
>   61014@debbugs.gnu.org
> Date: Thu, 02 Feb 2023 11:01:20 -0500
> 
> > 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.
> 
> Before making any change, I'd wait to see some explanation about why
> this message in a hidden " *stderr of elisp-flymake-byte-compile*" buffer
> is a problem.
> 
> I think the choice of `load-path` in the subprocess is a concern (with
> no reliably right answer, sadly), and maybe it would make sense to
> avoid adding the CWD when we're in ~/.emacs.d (presumably using the
> same code used to decide whether to emit the warning under
> discussion :-), but there's no hurry for that.

No further comments, so I've now made that warning be emitted only in
interactive sessions, and I'm boldly marking this bug done.

Thanks.





  parent reply	other threads:[~2023-02-12 12:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23  2:15 bug#61014: 29.0.60; flymake-mode stderr warning is confusing when edit the init.el or eary-init.el Eason Huang
2023-01-23 13:09 ` Eli Zaretskii
2023-01-26 11:16   ` João Távora
2023-01-28 11:21     ` Eli Zaretskii
2023-02-02 10:25       ` Eli Zaretskii
2023-02-02 10:50         ` João Távora
2023-02-02 16:01       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-02 17:15         ` Eli Zaretskii
2023-02-12 12:22         ` Eli Zaretskii [this message]
2023-02-12 14:45           ` Eason Huang
2023-02-12 14:50             ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ttzrgjk6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61014-done@debbugs.gnu.org \
    --cc=aqua0210@foxmail.com \
    --cc=joaotavora@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).