unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pengji Zhang <me@pengjiz.com>, sbaugh@janestreet.com
Cc: joaotavora@gmail.com, 65035@debbugs.gnu.org
Subject: bug#65035: 29.1; Port flycheck-emacs-lisp-initialize-packages to flymake
Date: Sat, 09 Nov 2024 11:19:15 +0200	[thread overview]
Message-ID: <86y11sn4rw.fsf@gnu.org> (raw)
In-Reply-To: <87ed44s8o7.fsf@pengjiz.com> (message from Pengji Zhang on Fri, 25 Oct 2024 19:50:48 +0800)

> From: Pengji Zhang <me@pengjiz.com>
> Cc: sbaugh@janestreet.com, João Távora
>  <joaotavora@gmail.com>, Eli Zaretskii
>  <eliz@gnu.org>
> Date: Fri, 25 Oct 2024 19:50:48 +0800
> 
> João Távora <joaotavora@gmail.com> writes:
> 
> > Feel free to use my patch of course.  Stefan noted some time ago
> > that -f package-initialize is the wrong flag to ask Emacs -Q to use
> > elpa though, so there's something better.
> 
> Thanks! I prepared a new patch based on yours.

Thanks.  Spencer, any comments?

> +(defcustom elisp-flymake-byte-compile-activate-packages
> +  #'elisp-flymake-byte-compile-user-file-p
> +  "Whether to activate packages for Flymake elisp byte-compilation.
> +If the value is nil, do not activate installed packages.  If the value
> +is a function, it is called with one argument, the source buffer to be
> +checked, and installed packages are activated if the function returns
> +non-nil.  Otherwise, packages are always activated.
> +
> +Note that for efficiency the return value of the predicate function is
> +cached the first time it is called.  Type \\[revert-buffer-quick] to
> +invalidate the cached value."

I think the doc string should explicitly mention
elisp-flymake-byte-compile-user-file-p, since it is used as the
default value of the option.

> +  :type '(choice
> +          (const :tag "Don't activate" nil)
> +          (const :tag "Always activate" t)
> +          (const :tag "Activate for user files"
> +                 elisp-flymake-byte-compile-user-file-p)
> +          (function :tag "Predicate function"))
> +  :group 'lisp)

Please add a :version tag here.





  reply	other threads:[~2024-11-09  9:19 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 [this message]
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

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=86y11sn4rw.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).