From: Ship Mints <shipmints@gmail.com>
To: Pengji Zhang <me@pengjiz.com>
Cc: Spencer Baugh <sbaugh@janestreet.com>,
Eli Zaretskii <eliz@gnu.org>,
joaotavora@gmail.com, 65035@debbugs.gnu.org
Subject: bug#65035: 29.1; Port flycheck-emacs-lisp-initialize-packages to flymake
Date: Thu, 14 Nov 2024 08:25:24 -0500 [thread overview]
Message-ID: <CAN+1HbrM5WzD_8H7XhtuM4z=J-8trHc0PnPRymVqPerX=Xkvbg@mail.gmail.com> (raw)
In-Reply-To: <87msi23vyb.fsf@pengjiz.com>
[-- Attachment #1: Type: text/plain, Size: 2015 bytes --]
Not sure this is 100% relevant to the discussion, but -Q also implies
--no-site-file which inhibits site-start.el. This will interfere with Emacs
builds such as https://github.com/jimeh/emacs-builds for macOS. They
rely on site-start to establish bundled native compiler runtime
dependencies. Running a flymake batch without those dependencies may have
unintended flymake performance implications.
On Thu, Nov 14, 2024 at 6:19 AM Pengji Zhang <me@pengjiz.com> wrote:
> 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.
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2833 bytes --]
prev parent reply other threads:[~2024-11-14 13:25 UTC|newest]
Thread overview: 10+ 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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN+1HbrM5WzD_8H7XhtuM4z=J-8trHc0PnPRymVqPerX=Xkvbg@mail.gmail.com' \
--to=shipmints@gmail.com \
--cc=65035@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.