unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Eason Huang" <aqua0210@foxmail.com>,
	"João Távora" <joaotavora@gmail.com>
Cc: 61014@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: Mon, 23 Jan 2023 15:09:53 +0200	[thread overview]
Message-ID: <831qnljt26.fsf@gnu.org> (raw)
In-Reply-To: <tencent_9D5A5F724B34901A37F8C065D78A3633E509@qq.com> (message from Eason Huang on Mon, 23 Jan 2023 10:15:49 +0800)

> From: Eason Huang <aqua0210@foxmail.com>
> Date: Mon, 23 Jan 2023 10:15:49 +0800
> 
> 
> I found that when editing the init.el or eary-ini.el under
> `user-emacs-directory`, flymake will report the warning as below:
> 
> ```
> Warning (initialization): Your `load-path' seems to contain
> your `.emacs.d' directory: /Users/eason/.emacs.d/
> This is likely to cause problems...
> Consider using a subdirectory instead, e.g.: /Users/eason/.emacs.d/lisp
> ```
> 
> And this is because the variable `elisp-flymake-byte-compile-load-path`
> has a defaut value `("./")`
> 
> so flymake adding the `.emacs.d` to the load-path and then also
> complaining about it, it is confusing to users. May be we can improve
> it.
> 
> Steps to reproduce:
> 
> 1. create a new .emacs.d folder in the HOME directory
> 2. create an empty init.e and eary-init.el file in the .emacs.d folder
> 3. Start Emacs and C-x, C-f open the init.el or early.el
> 4. M-x flymake-mode, add some blank lines in the init.el or early.el
> 5. C-x b, Switch to buffer:  *stderr of elisp-flymake-byte-compile*
> Now you will see the warnings.

João, any comments?  The warning comes from startup.el, but it is
triggered by what Flymake does, AFAICT.

> By the way, the message "Your `load-path' seems to contain
> your `.emacs.d' directory" should use `user-emacs-directory` instead,
> because some user will use `~/.config/emacs/` folder instead of
> `.emacs.d`

I fixed this part.





  reply	other threads:[~2023-01-23 13:09 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 [this message]
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
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=831qnljt26.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61014@debbugs.gnu.org \
    --cc=aqua0210@foxmail.com \
    --cc=joaotavora@gmail.com \
    /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).