From: Eli Zaretskii <eliz@gnu.org>
To: sbaugh@janestreet.com
Cc: 65035@debbugs.gnu.org, joaotavora@gmail.com, me@pengjiz.com
Subject: bug#65035: 29.1; Port flycheck-emacs-lisp-initialize-packages to flymake
Date: Sat, 14 Dec 2024 11:33:58 +0200 [thread overview]
Message-ID: <864j36wqux.fsf@gnu.org> (raw)
In-Reply-To: <868qt19hno.fsf@gnu.org> (message from Eli Zaretskii on Sat, 30 Nov 2024 11:48:11 +0200)
Ping! Ping!
> Cc: joaotavora@gmail.com, 65035@debbugs.gnu.org
> Date: Sat, 30 Nov 2024 11:48:11 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> Ping! Can we make some progress with this bug report?
>
> > Cc: joaotavora@gmail.com, 65035@debbugs.gnu.org
> > From: Pengji Zhang <me@pengjiz.com>
> > Date: Thu, 14 Nov 2024 19:18:20 +0800
> >
> > Spencer Baugh <sbaugh@janestreet.com> writes:
> >
> > > I think this should also switch from passing "-Q" to passing just
> > > "-q". If we're include ~/.emacs.d/elpa on load-path, we should include
> > > the site-lisp directories too, which -Q suppresses.
> >
> > I agree. How about the following change?
> >
> > --8<---------------cut here---------------start------------->8---
> > :name "elisp-flymake-byte-compile"
> > :buffer output-buffer
> > :command `(,(expand-file-name invocation-name invocation-directory)
> > - "-Q"
> > + ,@(if elisp-flymake--byte-compile-activate-packages
> > + ;; Add site-lisp directories to `load-path' so
> > + ;; that system-wide packages (installed into
> > + ;; site-lisp/elpa) are activated.
> > + '("-q" "--no-site-file")
> > + '("-Q"))
> > "--batch"
> > ;; "--eval" "(setq load-prefer-newer t)" ; for testing
> > ,@(mapcan (lambda (path) (list "-L" path))
> > --8<---------------cut here---------------end--------------->8---
> >
> > > Probably we should specifically pass "--batch --no-site-file" instead
> > > of "-Q --batch", since --batch also implies -q.
> >
> > I am not sure if it is a good idea to always include the site-lisp
> > directories. I myself want this only when checking my init.el. When
> > developing packages, I prefer a pristine environment.
> >
> >
> >
> >
>
>
>
>
prev parent reply other threads:[~2024-12-14 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 10:04 bug#65035: 29.1; Port flycheck-emacs-lisp-initialize-packages to flymake Antonio Romano via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-23 9:01 ` Pengji Zhang
2024-10-23 10:32 ` Eli Zaretskii
2024-10-23 11:15 ` João Távora
2024-10-25 11:50 ` Pengji Zhang
2024-11-09 9:19 ` Eli Zaretskii
2024-11-10 1:33 ` Pengji Zhang
2024-11-12 21:56 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-14 11:18 ` Pengji Zhang
2024-11-14 13:25 ` Ship Mints
2024-11-30 9:48 ` Eli Zaretskii
2024-12-14 9:33 ` Eli Zaretskii [this message]
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=864j36wqux.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65035@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=me@pengjiz.com \
--cc=sbaugh@janestreet.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).