GNU bug report logs - #81741
32.0.50; modus-themes is not recognised as a built-in package

Please note: This is a static page, with minimal formatting, updated once a day.
Click here to see this page with the latest information and nicer formatting.

Package: emacs; Reported by: Protesilaos <prot@HIDDEN>; merged with #47423; dated Sat, 29 Aug 2026 20:00:03 UTC; Maintainer for emacs is bug-gnu-emacs@HIDDEN.
Forcibly Merged 47423 81741. Request was from Eli Zaretskii <eliz@HIDDEN> to control <at> debbugs.gnu.org. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 31 Aug 2026 11:17:27 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Aug 31 07:17:27 2026
Received: from localhost ([127.0.0.1]:51021 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x1011-0005Gk-3u
	for submit <at> debbugs.gnu.org; Mon, 31 Aug 2026 07:17:27 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:52168)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1x100x-0005GP-Nu
 for 81741 <at> debbugs.gnu.org; Mon, 31 Aug 2026 07:17:24 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@HIDDEN>)
 id 1x100q-0004NQ-GD; Mon, 31 Aug 2026 07:17:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=iQ4n+P8C9TyIfCBnWdvx0WnbWdTxznme2BF+LQMe31M=; b=pyTvmMYk4j5z
 z6Qv7ctQyEvwTmlXoKgVXjfLDa7YjM+iRarmT7w/g5yMJGL2UvB/dri9w4jN2NzO4Dmoqh+YphFg/
 Tc0T14OfpcSI/t0ecZokCLZgtq5xiVX2+qKUtF4GhtblSiWQt+fIBTRrduACqKvl7tMdol4P4e+8W
 QcyGwBXti/3UqTDN/hBe4k9ETETS9XBhnpCsdlf47NRoHMa+rAMRgVlYE+QZZ9bzZms2kt3ipWbw4
 W+2mSMAvVnmevMPFHTrm88EzeBXlvoYrIrQu+wHWr4ttVy9Tmk7iCRhZmIMKx4TH5eae3yZiyw3vw
 Kw2oF9g/HvjQuZmN1NUcFg==;
Date: Mon, 31 Aug 2026 14:17:13 +0300
Message-Id: <86zey28rpi.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
To: Stefan Monnier <monnier@HIDDEN>
In-Reply-To: <jwvtsobf195.fsf-monnier+emacs@HIDDEN> (message from Stefan
 Monnier on Sun, 30 Aug 2026 22:56:16 -0400)
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
 <86bjajaoe1.fsf@HIDDEN> <875x0r6dhk.fsf@HIDDEN>
 <86a4q3aj0y.fsf@HIDDEN> <871pbf61vq.fsf@HIDDEN>
 <867bl7a65l.fsf@HIDDEN> <87o6ej4ifg.fsf@HIDDEN>
 <865x0r9g6t.fsf@HIDDEN> <jwvtsobf195.fsf-monnier+emacs@HIDDEN>
X-Spam-Score: -0.7 (/)
X-Debbugs-Envelope-To: 81741
Cc: philipk@HIDDEN, prot@HIDDEN, 81741 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

> From: Stefan Monnier <monnier@HIDDEN>
> Cc: Philip Kaludercic <philipk@HIDDEN>,  prot@HIDDEN,
>   81741 <at> debbugs.gnu.org
> Date: Sun, 30 Aug 2026 22:56:16 -0400
> 
> > Towards the complexity mess in package.el.  Themes need special
> > support and considerations, which are different from packages.
> 
> Do they?  What kind of special support and considerations are
> thinking about?

The different load-path, for instance.  Different initialization
considerations and methods.  Native-compilation being probably
irrelevant to themes.  And I'm quite sure this is just a tip of an
iceberg.

What are the problems with starting by providing a dedicated set of
package.el commands that handle only theme installation and upgrade,
and merging them later if experience shows that the differences are
insignificant enough?  Why is this MO rejected without even
considering it seriously?  Premature generalization is not a good
idea, IME.




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 31 Aug 2026 11:02:07 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Aug 31 07:02:06 2026
Received: from localhost ([127.0.0.1]:50979 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0zmA-0001Tc-GY
	for submit <at> debbugs.gnu.org; Mon, 31 Aug 2026 07:02:06 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:51216)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <eliz@HIDDEN>)
 id 1x0zm7-0001Sz-8X; Mon, 31 Aug 2026 07:02:04 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@HIDDEN>)
 id 1x0zm0-0001GA-1u; Mon, 31 Aug 2026 07:01:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=CImKjbabkHFsBOs3gzhkvPUovHRDLuHZtEIiggg+CkA=; b=CrlzcZm7dZ0O
 RMKyPHwzIkw+49BqBIcfa0kkw4791nx3UIAKG5Y/cX5BBimlFFehSSouqnkbhUv1e6MLwapp/N2NJ
 JYDTlRwf5Gkrt5zVhDsajM+NzjSMUfdvCD//IPaLYiPtdDBSK5+wuUsbV1gOHWukO71bgC1ga2A3P
 E98GABi08vywJibdAzMWEINw6hNZfwcyFkqftg99jfOZiBwFt94qKduojXQiygspIPVisMtxmqYrm
 zQTPf3ry409lJWX8g762iGromN6bk/bjt0Yj1UkUE0VqEpDQu7NfvivPVFe1KKTTVp0IMl6M3bnpD
 B5em5sAf1iySV5AxS0KtTw==;
Date: Mon, 31 Aug 2026 14:01:52 +0300
Message-Id: <8633vua6zj.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
To: Stefan Monnier <monnier@HIDDEN>
In-Reply-To: <jwvtsobguuy.fsf-monnier+emacs@HIDDEN> (message from Stefan
 Monnier on Sun, 30 Aug 2026 17:30:15 -0400)
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <jwvtsobguuy.fsf-monnier+emacs@HIDDEN>
X-Spam-Score: -0.7 (/)
X-Debbugs-Envelope-To: 81741
Cc: philipk@HIDDEN, prot@HIDDEN, 81741 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

merge 81741 47423
thanks

> From: Stefan Monnier <monnier@HIDDEN>
> Cc: Protesilaos <prot@HIDDEN>,  Philip Kaludercic
>  <philipk@HIDDEN>,  81741 <at> debbugs.gnu.org
> Date: Sun, 30 Aug 2026 17:30:15 -0400
> 
> >>      (package-built-in-p 'transient)
> >>      ;; => t
> >> 
> >>      (package-built-in-p 'modus-themes)
> >>      ;; => nil
> >
> > Why did you expect or need package.el to recognize themes as packages?
> 
> Sounds like bug#47423

Indeed.




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 31 Aug 2026 02:56:28 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 22:56:28 2026
Received: from localhost ([127.0.0.1]:45849 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0sCB-0000je-Pk
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 22:56:28 -0400
Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:8030)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <monnier@HIDDEN>)
 id 1x0sC9-0000jO-Cm
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 22:56:25 -0400
Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1])
 by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 0D6114412A6;
 Sun, 30 Aug 2026 22:56:19 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca;
 s=mail; t=1788144978;
 bh=2We4+6lXbL6OllEKpP/lXhUZQ4Tm/3/v6rvXzZ6CLpY=;
 h=From:To:Cc:Subject:In-Reply-To:References:Date:From;
 b=J+c/GfrJy2iqmxwJYVprw4YY/MSlrGftBEwczbaL7bDQZoPzWGszGqh7/U6Np9LwA
 NAkgAB9KmqGbBg9w893TVBbryTjTTriORb2lk4+l5Ss+AQdvRzC7Ilqm8toVyPhcgU
 62PieNqdlp74pTU1PUgvYR70NqZg8vU1SP77YFNCA927fXtOLcwVPTeH1hwleyXNQf
 Px1RijEPdEJBWD4R4sM5VGKxa1McDS91RCiZy/k8DZj1cuzrzEk/MyM6xHKWzxfrXp
 7Za+0Sl8jZY8h8qDX1BuBb/3iiUatHGz9HbvrT1ad6jG52j5bjR19VtfaMd5lYkyWz
 NU9Xmkclu9JNw==
Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1])
 by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 0E413441261;
 Sun, 30 Aug 2026 22:56:18 -0400 (EDT)
Received: from alfajor (104-195-193-66.cpe.teksavvy.com [104.195.193.66])
 by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id AA47A1205DD;
 Sun, 30 Aug 2026 22:56:17 -0400 (EDT)
From: Stefan Monnier <monnier@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
In-Reply-To: <865x0r9g6t.fsf@HIDDEN>
Message-ID: <jwvtsobf195.fsf-monnier+emacs@HIDDEN>
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
 <86bjajaoe1.fsf@HIDDEN> <875x0r6dhk.fsf@HIDDEN>
 <86a4q3aj0y.fsf@HIDDEN> <871pbf61vq.fsf@HIDDEN>
 <867bl7a65l.fsf@HIDDEN> <87o6ej4ifg.fsf@HIDDEN>
 <865x0r9g6t.fsf@HIDDEN>
Date: Sun, 30 Aug 2026 22:56:16 -0400
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
X-SPAM-INFO: Spam detection results:  0
 ALL_TRUSTED                -1 Passed through trusted hosts only via SMTP
 AWL 0.151 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DKIM_SIGNED               0.1 Message has a DKIM or DK signature,
 not necessarily valid
 DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
 DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's
 domain
 DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from
 domain
X-SPAM-LEVEL: 
X-Spam-Score: -2.3 (--)
X-Debbugs-Envelope-To: 81741
Cc: Philip Kaludercic <philipk@HIDDEN>, prot@HIDDEN,
 81741 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

> Towards the complexity mess in package.el.  Themes need special
> support and considerations, which are different from packages.

Do they?  What kind of special support and considerations are
thinking about?  Existing themes distributed via ELPA seem to work just
fine, AFAIK.


=== Stefan





Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 31 Aug 2026 02:28:39 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 22:28:39 2026
Received: from localhost ([127.0.0.1]:45519 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0rlH-0007Kv-3w
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 22:28:39 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:53178)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1x0rlE-0007Kb-Je
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 22:28:37 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@HIDDEN>)
 id 1x0rl7-0000kF-OI; Sun, 30 Aug 2026 22:28:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=2U3vi31/ZZYhkZsS1TiIwfQv8Ida/aoa3gSg/l8to+o=; b=fwWXnGYmMV5Y
 Z3jU9A9zEsoTHlxeYjUQGSRk5F5ZFgOfykShpBdi0e7luyJ6llI/FECCfzN+G37UimQHZr/4B/JO1
 v3yVJTiMGaPIigVRvIGI7hjIJ9hOUr6kpB6n7W4iuQ+sRChyHnvkUWeIgle/spPBuZctwifCTu2hM
 20vIgwbZMUOfcU2i4gNhrBP8mvj8l+QTu+HZwzS1P2C+SsNb908ZFBy4HlGSMUldBr0tqfrMiAwPx
 kIgSjoVjumgE1G1jeDNvYV8IdtQ2oDCGnYfPraM9cCTz1y/1UJSvVeoxbfIZgYrOfR3DQkIupdssJ
 Ef85TrXf/sDZ9hvKU4IcFw==;
Date: Mon, 31 Aug 2026 05:28:26 +0300
Message-Id: <865x0r9g6t.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
To: Philip Kaludercic <philipk@HIDDEN>
In-Reply-To: <87o6ej4ifg.fsf@HIDDEN> (message from Philip Kaludercic on
 Sun, 30 Aug 2026 17:39:00 +0000)
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
 <86bjajaoe1.fsf@HIDDEN> <875x0r6dhk.fsf@HIDDEN>
 <86a4q3aj0y.fsf@HIDDEN> <871pbf61vq.fsf@HIDDEN>
 <867bl7a65l.fsf@HIDDEN> <87o6ej4ifg.fsf@HIDDEN>
X-Spam-Score: -0.7 (/)
X-Debbugs-Envelope-To: 81741
Cc: prot@HIDDEN, 81741 <at> debbugs.gnu.org, monnier@HIDDEN
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

> From: Philip Kaludercic <philipk@HIDDEN>
> Cc: prot@HIDDEN,  monnier@HIDDEN,  81741 <at> debbugs.gnu.org
> Date: Sun, 30 Aug 2026 17:39:00 +0000
> 
> Eli Zaretskii <eliz@HIDDEN> writes:
> 
> > Look, you are our package.el and ELPA czar, so it's eventually your
> > decision.  Just take note that my gut feeling here is that we will
> > complicate stuff significantly if we decide to handle themes like we
> > handle packages.  IMO, it would be better to start with separate set
> > of commands, and later merge them if experience teaches us their
> > handling is indeed similar enough.
> >
> > What you do with this opinion of mine is up to you.
> 
> I'm honored, but it is still necessary to emphasize that it is not
> necessary to talk about anything in the future tense.  Themes have been
> distributed as packages for over a decade now, with no complications
> that I know of.

I'm talking about treating themes as packages in package.el.

> >> >> Most packages use the same boiler-plate to initialize
> >> >> `custom-theme-load-path' that turns a "regular package" into a
> >> >> "theme package", without making the distinction formal in
> >> >> package.el.
> >> >
> >> > Why would a package touch custom-theme-load-path?
> >> 
> >> To let Emacs know that installation directory of the package contains a
> >> theme.
> >
> > That's the slippery slope I'm afraid of.
> 
> Slippery slope towards where?

Towards the complexity mess in package.el.  Themes need special
support and considerations, which are different from packages.
Catering to both kinds in the same commands will cause trouble, I'm
afraid.




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 21:30:26 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 17:30:26 2026
Received: from localhost ([127.0.0.1]:43805 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0n6f-0004fI-B8
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 17:30:25 -0400
Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:37219)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <monnier@HIDDEN>)
 id 1x0n6d-0004eS-HS
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 17:30:23 -0400
Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1])
 by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 72608440B9E;
 Sun, 30 Aug 2026 17:30:17 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca;
 s=mail; t=1788125416;
 bh=rviBtn/eacMJFwQZjboND+WjFqtKRhkgeISKDUzjtpQ=;
 h=From:To:Cc:Subject:In-Reply-To:References:Date:From;
 b=EYn0c11qPRj08xjUoePKIXWTH9m6tXsODLJu8iVuO5xGzXT+o+sg652LftM2fPHGo
 DWrUq1Qfmd/3PWP+PpkGz7OuyOy7DUfHB8Dlth/1q1kwORDxt1Xb8mWzrRYD5CjoIJ
 Vyo5m0Hn6OFY3itmhD2weMMj170Kf4XTnYMw3vgt0O0VVNPWVZ1HKpSm+g7KrZJAtY
 CFY8Svy6xydCVikajK4Ixt5eH3eBd4Y+9+76BIaYytfXTRiAtZ5MlIQKwpSH/wLxLx
 tLKi4xQjBU2FYRMs7PRumbx9jjVyP3UYcm2tr1gi4QnqzmzEpRZH0T0H6SQvvZIs7F
 bkIdfpQ5/y0GQ==
Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1])
 by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 8D403440A34;
 Sun, 30 Aug 2026 17:30:16 -0400 (EDT)
Received: from alfajor (104-195-225-123.cpe.teksavvy.com [104.195.225.123])
 by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 4DFE0120403;
 Sun, 30 Aug 2026 17:30:16 -0400 (EDT)
From: Stefan Monnier <monnier@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
In-Reply-To: <86ik4s9qjp.fsf@HIDDEN>
Message-ID: <jwvtsobguuy.fsf-monnier+emacs@HIDDEN>
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN>
Date: Sun, 30 Aug 2026 17:30:15 -0400
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: text/plain
X-SPAM-INFO: Spam detection results:  0
 ALL_TRUSTED                -1 Passed through trusted hosts only via SMTP
 AWL 0.152 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DKIM_SIGNED               0.1 Message has a DKIM or DK signature,
 not necessarily valid
 DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
 DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's
 domain
 DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from
 domain
X-SPAM-LEVEL: 
X-Spam-Score: -2.3 (--)
X-Debbugs-Envelope-To: 81741
Cc: Philip Kaludercic <philipk@HIDDEN>, Protesilaos <prot@HIDDEN>,
 81741 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

>>      (package-built-in-p 'transient)
>>      ;; => t
>> 
>>      (package-built-in-p 'modus-themes)
>>      ;; => nil
>
> Why did you expect or need package.el to recognize themes as packages?

Sounds like bug#47423


=== Stefan





Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 17:39:12 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 13:39:11 2026
Received: from localhost ([127.0.0.1]:42471 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0jUt-0004jY-8e
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 13:39:11 -0400
Received: from mout01.posteo.de ([185.67.36.65]:41239)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <philipk@HIDDEN>)
 id 1x0jUp-0004im-SP
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 13:39:09 -0400
Received: from submission (posteo.de [185.67.36.169]) 
 by mout01.posteo.de (Postfix) with ESMTPS id C9B2E240027
 for <81741 <at> debbugs.gnu.org>; Sun, 30 Aug 2026 19:39:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.net;
 s=1984.8680eb; t=1788111540;
 bh=dGAGPviJ729gtM1ZQgIPIjQgjyM5oMMYJXw87bwtOa0=;
 h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version:
 Content-Type:From;
 b=k8bVM8kdtVSkRzuW8TNERSZFRwU+cP7ksy6hsojsNdLtmfJer9GSqoTcG1fAkgjxA
 s3wU7tUaAdjRzDt7DoUNfjajpjw+bsUZo/Fg2JzJT5jD/RXUM/IJS9xsmRwRUGxtFK
 LUxN8TkMGsxCVM+tWojojhMrPYTMJfWFJ6RjtXaoKNcZ+urYukCMR1TB3pTfsKEm1V
 gGi6V7NsdRrOZVQzPrxl7aI8IUo9kB49WQpmYeyarlhjQrcev+/H2LvHvWcQdyKAgu
 39Q0RM2YvgD3ICb/6FH+Y5ZI+FfGBWA5qJsc62komp78wFivS1t3Nah7cbZO+B0YbU
 7wYAgB7VWo7JQ==
Received: from customer (localhost [127.0.0.1])
 by submission (posteo.de) with ESMTPSA id 4hXzrM6wJWz6tvk;
 Sun, 30 Aug 2026 19:38:59 +0200 (CEST)
From: Philip Kaludercic <philipk@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
In-Reply-To: <867bl7a65l.fsf@HIDDEN>
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
 <86bjajaoe1.fsf@HIDDEN> <875x0r6dhk.fsf@HIDDEN>
 <86a4q3aj0y.fsf@HIDDEN> <871pbf61vq.fsf@HIDDEN>
 <867bl7a65l.fsf@HIDDEN>
OpenPGP: id=philipk@HIDDEN;
 url="https://keys.openpgp.org/vks/v1/by-email/philipk@HIDDEN";
 preference=signencrypt
Date: Sun, 30 Aug 2026 17:39:00 +0000
Message-ID: <87o6ej4ifg.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Score: -3.3 (---)
X-Debbugs-Envelope-To: 81741
Cc: prot@HIDDEN, 81741 <at> debbugs.gnu.org, monnier@HIDDEN
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -4.3 (----)

Eli Zaretskii <eliz@HIDDEN> writes:

>> From: Philip Kaludercic <philipk@HIDDEN>
>> Cc: prot@HIDDEN,  monnier@HIDDEN,  81741 <at> debbugs.gnu.org
>> Date: Sun, 30 Aug 2026 15:53:31 +0000
>> 
>> Eli Zaretskii <eliz@HIDDEN> writes:
>> 
>> >> > I envisioned a separate set of package.el commands to handle
>> >> > installing themes from ELPA.
>> >> 
>> >> I guess that would be imaginable, but I also feel like it invites too
>> >> much complexity and creates the precedence for special-casing that I'd
>> >> like to avoid.
>> >
>> > IMO, it's the other way around: decoupling these two categories will
>> > make each set of package.el commands simpler and easier to maintain.
>> 
>> I am pretty certain that this is not the case, since we currently can
>> install themes using package.el without anything in package.el written
>> specifically to support this.  To have explicit support for themes,
>> whether by having a custom command or some "Package-Kind: theme" header,
>> would be strictly more code.
>
> Look, you are our package.el and ELPA czar, so it's eventually your
> decision.  Just take note that my gut feeling here is that we will
> complicate stuff significantly if we decide to handle themes like we
> handle packages.  IMO, it would be better to start with separate set
> of commands, and later merge them if experience teaches us their
> handling is indeed similar enough.
>
> What you do with this opinion of minde is up to you.

I'm honored, but it is still necessary to emphasize that it is not
necessary to talk about anything in the future tense.  Themes have been
distributed as packages for over a decade now, with no complications
that I know of.

>> >> Most packages use the same boiler-plate to initialize
>> >> `custom-theme-load-path' that turns a "regular package" into a
>> >> "theme package", without making the distinction formal in
>> >> package.el.
>> >
>> > Why would a package touch custom-theme-load-path?
>> 
>> To let Emacs know that installation directory of the package contains a
>> theme.
>
> That's the slippery slope I'm afraid of.

Slippery slope towards where?




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 17:07:47 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 13:07:47 2026
Received: from localhost ([127.0.0.1]:42267 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0j0V-0002j7-2h
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 13:07:47 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:51246)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1x0j0S-0002ig-6Y
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 13:07:45 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@HIDDEN>)
 id 1x0j0K-0005AZ-P6; Sun, 30 Aug 2026 13:07:36 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
 mime-version; bh=8ZSYbd38vbS7Gi64Hg2k4dacl+Av0N1PhIDbKhMG6go=; b=XJA4WnRa0fuB
 8xTHkwuVx5+0YhRKgM/8cs2NeisrnfesNixVquhnCHK5BDQV+BG1nbm63wQ7rQH+v8WFeG8VrZGCw
 PrZUORpuDkM89e2lDjJmPmMkgRrAJf6DG0ZPUVEzIaIyt0BIo0rnb5oaLG+SBmZkho0so4OSiNXCQ
 jB+nrhO0jad24QVc/5AKU7Hhh+RmMoqNe4abClAmkJmBEVkyQHJIJH7y61RCD7ksgNM4r4Af7BjNf
 eauoOmk2rKL8QMZzd3DjNDpXK5JAsB/SCGYZNIb7Tlvl9d+Una8XsfjXVoFUKFpIMVCx8GzDTSUve
 sTu5y9UoV5VfimbNCKKmxA==;
Date: Sun, 30 Aug 2026 20:07:34 +0300
Message-Id: <867bl7a65l.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
To: Philip Kaludercic <philipk@HIDDEN>
In-Reply-To: <871pbf61vq.fsf@HIDDEN> (message from Philip Kaludercic on
 Sun, 30 Aug 2026 15:53:31 +0000)
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
 <86bjajaoe1.fsf@HIDDEN> <875x0r6dhk.fsf@HIDDEN>
 <86a4q3aj0y.fsf@HIDDEN> <871pbf61vq.fsf@HIDDEN>
X-Spam-Score: -0.7 (/)
X-Debbugs-Envelope-To: 81741
Cc: prot@HIDDEN, 81741 <at> debbugs.gnu.org, monnier@HIDDEN
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

> From: Philip Kaludercic <philipk@HIDDEN>
> Cc: prot@HIDDEN,  monnier@HIDDEN,  81741 <at> debbugs.gnu.org
> Date: Sun, 30 Aug 2026 15:53:31 +0000
> 
> Eli Zaretskii <eliz@HIDDEN> writes:
> 
> >> > I envisioned a separate set of package.el commands to handle
> >> > installing themes from ELPA.
> >> 
> >> I guess that would be imaginable, but I also feel like it invites too
> >> much complexity and creates the precedence for special-casing that I'd
> >> like to avoid.
> >
> > IMO, it's the other way around: decoupling these two categories will
> > make each set of package.el commands simpler and easier to maintain.
> 
> I am pretty certain that this is not the case, since we currently can
> install themes using package.el without anything in package.el written
> specifically to support this.  To have explicit support for themes,
> whether by having a custom command or some "Package-Kind: theme" header,
> would be strictly more code.

Look, you are our package.el and ELPA czar, so it's eventually your
decision.  Just take note that my gut feeling here is that we will
complicate stuff significantly if we decide to handle themes like we
handle packages.  IMO, it would be better to start with separate set
of commands, and later merge them if experience teaches us their
handling is indeed similar enough.

What you do with this opinion of minde is up to you.

> >> Most packages use the same boiler-plate to initialize
> >> `custom-theme-load-path' that turns a "regular package" into a
> >> "theme package", without making the distinction formal in
> >> package.el.
> >
> > Why would a package touch custom-theme-load-path?
> 
> To let Emacs know that installation directory of the package contains a
> theme.

That's the slippery slope I'm afraid of.




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 15:53:43 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 11:53:42 2026
Received: from localhost ([127.0.0.1]:41798 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0hqo-0005Fb-3N
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 11:53:42 -0400
Received: from mout02.posteo.de ([185.67.36.66]:42979)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <philipk@HIDDEN>)
 id 1x0hqk-0005FE-PG
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 11:53:40 -0400
Received: from submission (posteo.de [185.67.36.169]) 
 by mout02.posteo.de (Postfix) with ESMTPS id B94CA240103
 for <81741 <at> debbugs.gnu.org>; Sun, 30 Aug 2026 17:53:31 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.net;
 s=1984.8680eb; t=1788105211;
 bh=VPrhPvlFi0jk8CoLuqxeVP6kTK6MmWFL6uUHJzTPmwk=;
 h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version:
 Content-Type:Content-Transfer-Encoding:From;
 b=YJx4EzPzlS+EThWwXp5C1DWlpfyT3/kT6lIeZLIQ81pFpm+24rpBwPITkMaqJYkiv
 Bh7GbpsjGyra6/dvFma3Vi1m0xMARwaumjqy2yj15IKlJkJFwG7f9VlV4nPUaGyblZ
 3kj2N/98y4kYnU1bEQTuKwtcqZ6b0Ww/Ie8kY14aqTS2TKf4kfBK/a8SPhKdao11uL
 ilduUS+f70YEC82OE6A6Ov50vGZsYpyhGLFPLCA/05ErGlRXdMkCeubMJFbOlLhZxE
 +5cNTewZ8F49H0I4NhP7jBBdMHqZA+o06MrKaLBxr1sOOLoRLahsnzCQzXslGBbKQw
 y7a6SH5tOraSQ==
Received: from customer (localhost [127.0.0.1])
 by submission (posteo.de) with ESMTPSA id 4hXxVf72vCz6tvk;
 Sun, 30 Aug 2026 17:53:30 +0200 (CEST)
From: Philip Kaludercic <philipk@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
In-Reply-To: <86a4q3aj0y.fsf@HIDDEN>
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
 <86bjajaoe1.fsf@HIDDEN> <875x0r6dhk.fsf@HIDDEN>
 <86a4q3aj0y.fsf@HIDDEN>
OpenPGP: id=philipk@HIDDEN;
 url="https://keys.openpgp.org/vks/v1/by-email/philipk@HIDDEN";
 preference=signencrypt
Date: Sun, 30 Aug 2026 15:53:31 +0000
Message-ID: <871pbf61vq.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -3.3 (---)
X-Debbugs-Envelope-To: 81741
Cc: prot@HIDDEN, 81741 <at> debbugs.gnu.org, monnier@HIDDEN
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -4.3 (----)

Eli Zaretskii <eliz@HIDDEN> writes:

>> From: Philip Kaludercic <philipk@HIDDEN>
>> Cc: prot@HIDDEN,  monnier@HIDDEN,  81741@HIDDEN=
org
>> Date: Sun, 30 Aug 2026 11:42:48 +0000
>>=20
>> Eli Zaretskii <eliz@HIDDEN> writes:
>>=20
>> >> From: Philip Kaludercic <philipk@HIDDEN>
>> >> Cc: Protesilaos <prot@HIDDEN>,  Stefan Monnier
>> >>  <monnier@HIDDEN>,  81741 <at> debbugs.gnu.org
>> >> Date: Sun, 30 Aug 2026 09:39:29 +0000
>> >>=20
>> >> Eli Zaretskii <eliz@HIDDEN> writes:
>> >>=20
>> >> >> Date: Sat, 29 Aug 2026 22:59:35 +0300
>> >> >> From: Protesilaos <prot@HIDDEN>
>> >> >>=20
>> >> >> Dear maintainers,
>> >> >>=20
>> >> >> The modus-themes are not recognised by package.el as a "built-in" =
theme.
>> >> >> Here is what I tried in =E2=80=99emacs -Q=E2=80=99:
>> >> >>=20
>> >> >>      (require =E2=80=99package)
>> >> >>=20
>> >> >>      (package-built-in-p 'org)
>> >> >>      ;; =3D> t
>> >> >>=20
>> >> >>      (package-built-in-p 'transient)
>> >> >>      ;; =3D> t
>> >> >>=20
>> >> >>      (package-built-in-p 'modus-themes)
>> >> >>      ;; =3D> nil
>> >> >
>> >> > Why did you expect or need package.el to recognize themes as packag=
es?
>> >>=20
>> >> Modus Themes is now also a framework for packages, meaning that other
>> >> packages can instantiate it with their own color scheme.  As such, ot=
her
>> >> packages depend on Modus Themes, and it would be nice to avoid having=
 to
>> >> install the dependency, if Emacs already comes with a recent enough
>> >> version of the Theme.
>> >
>> > My interpretation of the report was that not just modus-themes.el, but
>> > all the other modus-*-theme.el files (and other themes as well) are
>> > expected to be considered as built-in packages.  Apologies if I
>> > misunderstood, and this is _only_ about a single modus-themes.el file.
>>=20
>> The other files are not relevant for package.el to recognize
>> modus-themes as a built-in package.
>
> But Protesilaos said explicitly: "The modus-themes are not recognised
> by package.el as a "built-in" theme".  So it's not just
> modus-themes.el, or at least that's how I read the request.

If I had to guess, I would he meant built-in package.  After all, the
examples above use `package-built-in-p' and not some "theme-built-in-p".

>> > For example:
>> >
>> >> >> I looked into the source and noticed that the =E2=80=99finder-comp=
ile-keywords=E2=80=99
>> >> >> function reads from DIRS or the =E2=80=99load-path=E2=80=99. This =
means that it does not
>> >> >> find the =E2=80=99modus-themes.el=E2=80=99, which is available in =
the=20
>> >> >> =E2=80=99custom-theme-load-path=E2=80=99.
>> >> >>=20
>> >> >> Should we modify =E2=80=99finder-compile-keywords=E2=80=99 to also=
 read from the
>> >> >> =E2=80=99custom-theme-load-path=E2=80=99 or move the =E2=80=99modu=
s-themes.el=E2=80=99 to the lisp/
>> >> >> directory?
>> >
>> > This seems to imply that the request was to consider all themes as
>> > built-in packages, because custom-theme-load-path is not specific to
>> > modus-themes.
>>=20
>> The other themes ought to be part of the same package, or at least that
>> is my understanding.
>>=20
>> >> I think that it would make sense to move modus-themes.el to the lisp/
>> >> directory.  Is there any reason not to do so?  Or rather, why was it
>> >> initially placed elsewhere?
>> >
>> > We could move the file to lisp/ indeed, but it sounds strange to have
>> > it there, since the themes which depend on it are in etc/themes/.
>> > When modus-themes.el is updated on ELPA, aren't the other
>> > modus-*-themes updated as well?  If they are, then how will it help to
>> > consider modus-themes.el a built-in package if the themes themselves
>> > aren't?  What am I missing?
>>=20
>> Yes, they are updated as well.  IIRC the trick is that by updating the
>> package and modus-themes.el, the file will adjust
>> `custom-theme-load-path' so that the ELPA directory with the
>> modus-*-theme.el files are preferred over those in etc/themes/.
>
> That's exactly something I'd like to avoid.  IMO, themes are
> sufficiently different from other packages to make their installation
> and upgrades separate and different.  E.g., installing other packages
> doesn't need to update custom-theme-load-path, so to do this,
> package.el will need to know about themes as "special" packages.  And
> I expect to see other differences.
>
> We shouldn't lump packages and themes together, IMO.

Please tell me if what I am telling you is obvious, but I wouldn't say
we are lumping anything together: a package can contain a theme, without
package.el having to know anything about themes.  All the theme-specific
setup is just part of the package.  This is not hypothetical, but the
way that package.el works right now and how all the themes on GNU and
NonGNU ELPA are distributed, see for instance a random theme:

https://cgit.git.savannah.gnu.org/cgit/emacs/elpa.git/tree/ahungry-theme.el=
?h=3Dexternals/ahungry-theme#n349

It just autoloads a `add-to-list' to add the package installation to
`custom-theme-load-path'.

>> >> > I'm not sure we want to generalize the notion of "package" to theme=
s.
>> >> > Why not consider themes to be separate from packages?  That was the
>> >> > original design of themes, and that's why we have a separate
>> >> > custom-theme-load-path variable in the first place.
>> >> >
>> >> >> The =E2=80=99modus-themes=E2=80=99 package can be used as a basis =
for other themes.
>> >> >> There are plenty of packages already, including a new candidate fo=
r GNU
>> >> >> ELPA.
>> >> >
>> >> > Exactly.  So one more reason not to consider themes to be packages.
>> >> > If we want package.el to support themes, I'd prefer to have a separ=
ate
>> >> > set of commands for that, because otherwise I feel we will make a
>> >> > mess, given how themes are handled differently from packages.
>> >>=20
>> >> I don't understand your reasoning here, or maybe I am misunderstanding
>> >> what separate set of commands you are envisioning?
>> >
>> > I envisioned a separate set of package.el commands to handle
>> > installing themes from ELPA.
>>=20
>> I guess that would be imaginable, but I also feel like it invites too
>> much complexity and creates the precedence for special-casing that I'd
>> like to avoid.
>
> IMO, it's the other way around: decoupling these two categories will
> make each set of package.el commands simpler and easier to maintain.

I am pretty certain that this is not the case, since we currently can
install themes using package.el without anything in package.el written
specifically to support this.  To have explicit support for themes,
whether by having a custom command or some "Package-Kind: theme" header,
would be strictly more code.

>> Most packages use the same boiler-plate to initialize
>> `custom-theme-load-path' that turns a "regular package" into a
>> "theme package", without making the distinction formal in
>> package.el.
>
> Why would a package touch custom-theme-load-path?

To let Emacs know that installation directory of the package contains a
theme.




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 12:29:47 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 08:29:47 2026
Received: from localhost ([127.0.0.1]:40171 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0efT-0002UN-65
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 08:29:47 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:45940)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1x0efQ-0002Ts-4K
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 08:29:45 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@HIDDEN>)
 id 1x0efJ-0003NQ-3P; Sun, 30 Aug 2026 08:29:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From:
 Date; bh=PF7ZCpTpxkMd5q2LOdqWDmJ8mbNDUN0h6KqgYD4y0Ss=; b=eOHyBbpiA0OFO+kY6ou5
 JsSLbCWoiEGPYXMEs39e1hjLJeTeeAtg/Y3mn6ve2AvUr6aOnb+wZMB54WdjocTDMPgx0NgdGDRS6
 kjlped8lRkkE5ZWRqV3GQphr7zEI+DtMcTbPToYyI/PpNvralg629oBLjbI1y6x5lT45DGNE4sRvF
 +L6bMM8LHS3g8zin04AfWm5Wh2wd/8+VceH5zxYhZLzitkcobDx0jrrFSwE1dIFJQkcORTtMpAjpT
 3FcqtiNACYzQsOp+FwonTI3j+zJIM6QQjBKTPEmHtRHdWpSiYyML1pFCzzClexStYsrMnKAchshoh
 Snf8wxIzlPbIDQ==;
Date: Sun, 30 Aug 2026 15:29:33 +0300
Message-Id: <86a4q3aj0y.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
To: Philip Kaludercic <philipk@HIDDEN>
In-Reply-To: <875x0r6dhk.fsf@HIDDEN> (message from Philip Kaludercic on
 Sun, 30 Aug 2026 11:42:48 +0000)
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
 <86bjajaoe1.fsf@HIDDEN> <875x0r6dhk.fsf@HIDDEN>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Spam-Score: -0.7 (/)
X-Debbugs-Envelope-To: 81741
Cc: prot@HIDDEN, 81741 <at> debbugs.gnu.org, monnier@HIDDEN
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

> From: Philip Kaludercic <philipk@HIDDEN>
> Cc: prot@HIDDEN,  monnier@HIDDEN,  81741 <at> debbugs.gnu.org
> Date: Sun, 30 Aug 2026 11:42:48 +0000
> 
> Eli Zaretskii <eliz@HIDDEN> writes:
> 
> >> From: Philip Kaludercic <philipk@HIDDEN>
> >> Cc: Protesilaos <prot@HIDDEN>,  Stefan Monnier
> >>  <monnier@HIDDEN>,  81741 <at> debbugs.gnu.org
> >> Date: Sun, 30 Aug 2026 09:39:29 +0000
> >> 
> >> Eli Zaretskii <eliz@HIDDEN> writes:
> >> 
> >> >> Date: Sat, 29 Aug 2026 22:59:35 +0300
> >> >> From: Protesilaos <prot@HIDDEN>
> >> >> 
> >> >> Dear maintainers,
> >> >> 
> >> >> The modus-themes are not recognised by package.el as a "built-in" theme.
> >> >> Here is what I tried in ’emacs -Q’:
> >> >> 
> >> >>      (require ’package)
> >> >> 
> >> >>      (package-built-in-p 'org)
> >> >>      ;; => t
> >> >> 
> >> >>      (package-built-in-p 'transient)
> >> >>      ;; => t
> >> >> 
> >> >>      (package-built-in-p 'modus-themes)
> >> >>      ;; => nil
> >> >
> >> > Why did you expect or need package.el to recognize themes as packages?
> >> 
> >> Modus Themes is now also a framework for packages, meaning that other
> >> packages can instantiate it with their own color scheme.  As such, other
> >> packages depend on Modus Themes, and it would be nice to avoid having to
> >> install the dependency, if Emacs already comes with a recent enough
> >> version of the Theme.
> >
> > My interpretation of the report was that not just modus-themes.el, but
> > all the other modus-*-theme.el files (and other themes as well) are
> > expected to be considered as built-in packages.  Apologies if I
> > misunderstood, and this is _only_ about a single modus-themes.el file.
> 
> The other files are not relevant for package.el to recognize
> modus-themes as a built-in package.

But Protesilaos said explicitly: "The modus-themes are not recognised
by package.el as a "built-in" theme".  So it's not just
modus-themes.el, or at least that's how I read the request.

> > For example:
> >
> >> >> I looked into the source and noticed that the ’finder-compile-keywords’
> >> >> function reads from DIRS or the ’load-path’. This means that it does not
> >> >> find the ’modus-themes.el’, which is available in the 
> >> >> ’custom-theme-load-path’.
> >> >> 
> >> >> Should we modify ’finder-compile-keywords’ to also read from the
> >> >> ’custom-theme-load-path’ or move the ’modus-themes.el’ to the lisp/
> >> >> directory?
> >
> > This seems to imply that the request was to consider all themes as
> > built-in packages, because custom-theme-load-path is not specific to
> > modus-themes.
> 
> The other themes ought to be part of the same package, or at least that
> is my understanding.
> 
> >> I think that it would make sense to move modus-themes.el to the lisp/
> >> directory.  Is there any reason not to do so?  Or rather, why was it
> >> initially placed elsewhere?
> >
> > We could move the file to lisp/ indeed, but it sounds strange to have
> > it there, since the themes which depend on it are in etc/themes/.
> > When modus-themes.el is updated on ELPA, aren't the other
> > modus-*-themes updated as well?  If they are, then how will it help to
> > consider modus-themes.el a built-in package if the themes themselves
> > aren't?  What am I missing?
> 
> Yes, they are updated as well.  IIRC the trick is that by updating the
> package and modus-themes.el, the file will adjust
> `custom-theme-load-path' so that the ELPA directory with the
> modus-*-theme.el files are preferred over those in etc/themes/.

That's exactly something I'd like to avoid.  IMO, themes are
sufficiently different from other packages to make their installation
and upgrades separate and different.  E.g., installing other packages
doesn't need to update custom-theme-load-path, so to do this,
package.el will need to know about themes as "special" packages.  And
I expect to see other differences.

We shouldn't lump packages and themes together, IMO.

> >> > I'm not sure we want to generalize the notion of "package" to themes.
> >> > Why not consider themes to be separate from packages?  That was the
> >> > original design of themes, and that's why we have a separate
> >> > custom-theme-load-path variable in the first place.
> >> >
> >> >> The ’modus-themes’ package can be used as a basis for other themes.
> >> >> There are plenty of packages already, including a new candidate for GNU
> >> >> ELPA.
> >> >
> >> > Exactly.  So one more reason not to consider themes to be packages.
> >> > If we want package.el to support themes, I'd prefer to have a separate
> >> > set of commands for that, because otherwise I feel we will make a
> >> > mess, given how themes are handled differently from packages.
> >> 
> >> I don't understand your reasoning here, or maybe I am misunderstanding
> >> what separate set of commands you are envisioning?
> >
> > I envisioned a separate set of package.el commands to handle
> > installing themes from ELPA.
> 
> I guess that would be imaginable, but I also feel like it invites too
> much complexity and creates the precedence for special-casing that I'd
> like to avoid.

IMO, it's the other way around: decoupling these two categories will
make each set of package.el commands simpler and easier to maintain.

> Most packages use the same boiler-plate to initialize
> `custom-theme-load-path' that turns a "regular package" into a
> "theme package", without making the distinction formal in
> package.el.

Why would a package touch custom-theme-load-path?




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 11:42:59 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 07:42:59 2026
Received: from localhost ([127.0.0.1]:39883 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0dwA-0007wr-9b
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 07:42:59 -0400
Received: from mout02.posteo.de ([185.67.36.66]:54357)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <philipk@HIDDEN>)
 id 1x0dw7-0007wX-Iz
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 07:42:56 -0400
Received: from submission (posteo.de [185.67.36.169]) 
 by mout02.posteo.de (Postfix) with ESMTPS id D106E240103
 for <81741 <at> debbugs.gnu.org>; Sun, 30 Aug 2026 13:42:48 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.net;
 s=1984.8680eb; t=1788090168;
 bh=1xaEkEbGd1A3wl6UZRdhx3UGxQv3I/X8WQ3CVRX9f8A=;
 h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version:
 Content-Type:Content-Transfer-Encoding:From;
 b=nUoL8xdjaL2NskXD/yVGku+01mj2nqWkSkio/S5Io11jCvenlfjPRiGhpsH7QiJpg
 5QjWmrwhxwfrIkwlHNF2gjuicEi4KN9PG5tYcWcJUZe+hH1d46SAG625itGgeqI71O
 e9GQz2w1Ai0/86ca1hpuCBUaLtzZ/bxbRFoC2AtefAkvv2zIPBZjSaise75NcHXgOS
 D4+ph+j4TNv6oEHBVAir8qhlNDyFcIcpdZzk7bRhRoiV4s6SE0eX2MxffnrzlX4tNg
 M8BQzoDX34KbH42vs6FKSlY6Z5BNhhH1L1PLjrRHfuzNDVkd1l6LmjJy+jVoUkPJ9q
 kWnaPRTxRaD+g==
Received: from customer (localhost [127.0.0.1])
 by submission (posteo.de) with ESMTPSA id 4hXqxN0dz0z6txl;
 Sun, 30 Aug 2026 13:42:47 +0200 (CEST)
From: Philip Kaludercic <philipk@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
In-Reply-To: <86bjajaoe1.fsf@HIDDEN>
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
 <86bjajaoe1.fsf@HIDDEN>
OpenPGP: id=philipk@HIDDEN;
 url="https://keys.openpgp.org/vks/v1/by-email/philipk@HIDDEN";
 preference=signencrypt
Date: Sun, 30 Aug 2026 11:42:48 +0000
Message-ID: <875x0r6dhk.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -2.3 (--)
X-Debbugs-Envelope-To: 81741
Cc: prot@HIDDEN, 81741 <at> debbugs.gnu.org, monnier@HIDDEN
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

Eli Zaretskii <eliz@HIDDEN> writes:

>> From: Philip Kaludercic <philipk@HIDDEN>
>> Cc: Protesilaos <prot@HIDDEN>,  Stefan Monnier
>>  <monnier@HIDDEN>,  81741 <at> debbugs.gnu.org
>> Date: Sun, 30 Aug 2026 09:39:29 +0000
>>=20
>> Eli Zaretskii <eliz@HIDDEN> writes:
>>=20
>> >> Date: Sat, 29 Aug 2026 22:59:35 +0300
>> >> From: Protesilaos <prot@HIDDEN>
>> >>=20
>> >> Dear maintainers,
>> >>=20
>> >> The modus-themes are not recognised by package.el as a "built-in" the=
me.
>> >> Here is what I tried in =E2=80=99emacs -Q=E2=80=99:
>> >>=20
>> >>      (require =E2=80=99package)
>> >>=20
>> >>      (package-built-in-p 'org)
>> >>      ;; =3D> t
>> >>=20
>> >>      (package-built-in-p 'transient)
>> >>      ;; =3D> t
>> >>=20
>> >>      (package-built-in-p 'modus-themes)
>> >>      ;; =3D> nil
>> >
>> > Why did you expect or need package.el to recognize themes as packages?
>>=20
>> Modus Themes is now also a framework for packages, meaning that other
>> packages can instantiate it with their own color scheme.  As such, other
>> packages depend on Modus Themes, and it would be nice to avoid having to
>> install the dependency, if Emacs already comes with a recent enough
>> version of the Theme.
>
> My interpretation of the report was that not just modus-themes.el, but
> all the other modus-*-theme.el files (and other themes as well) are
> expected to be considered as built-in packages.  Apologies if I
> misunderstood, and this is _only_ about a single modus-themes.el file.

The other files are not relevant for package.el to recognize
modus-themes as a built-in package.

> For example:
>
>> >> I looked into the source and noticed that the =E2=80=99finder-compile=
-keywords=E2=80=99
>> >> function reads from DIRS or the =E2=80=99load-path=E2=80=99. This mea=
ns that it does not
>> >> find the =E2=80=99modus-themes.el=E2=80=99, which is available in the=
=20
>> >> =E2=80=99custom-theme-load-path=E2=80=99.
>> >>=20
>> >> Should we modify =E2=80=99finder-compile-keywords=E2=80=99 to also re=
ad from the
>> >> =E2=80=99custom-theme-load-path=E2=80=99 or move the =E2=80=99modus-t=
hemes.el=E2=80=99 to the lisp/
>> >> directory?
>
> This seems to imply that the request was to consider all themes as
> built-in packages, because custom-theme-load-path is not specific to
> modus-themes.

The other themes ought to be part of the same package, or at least that
is my understanding.

>> I think that it would make sense to move modus-themes.el to the lisp/
>> directory.  Is there any reason not to do so?  Or rather, why was it
>> initially placed elsewhere?
>
> We could move the file to lisp/ indeed, but it sounds strange to have
> it there, since the themes which depend on it are in etc/themes/.
> When modus-themes.el is updated on ELPA, aren't the other
> modus-*-themes updated as well?  If they are, then how will it help to
> consider modus-themes.el a built-in package if the themes themselves
> aren't?  What am I missing?

Yes, they are updated as well.  IIRC the trick is that by updating the
package and modus-themes.el, the file will adjust
`custom-theme-load-path' so that the ELPA directory with the
modus-*-theme.el files are preferred over those in etc/themes/.

>> > I'm not sure we want to generalize the notion of "package" to themes.
>> > Why not consider themes to be separate from packages?  That was the
>> > original design of themes, and that's why we have a separate
>> > custom-theme-load-path variable in the first place.
>> >
>> >> The =E2=80=99modus-themes=E2=80=99 package can be used as a basis for=
 other themes.
>> >> There are plenty of packages already, including a new candidate for G=
NU
>> >> ELPA.
>> >
>> > Exactly.  So one more reason not to consider themes to be packages.
>> > If we want package.el to support themes, I'd prefer to have a separate
>> > set of commands for that, because otherwise I feel we will make a
>> > mess, given how themes are handled differently from packages.
>>=20
>> I don't understand your reasoning here, or maybe I am misunderstanding
>> what separate set of commands you are envisioning?
>
> I envisioned a separate set of package.el commands to handle
> installing themes from ELPA.

I guess that would be imaginable, but I also feel like it invites too
much complexity and creates the precedence for special-casing that I'd
like to avoid.  Most packages use the same boiler-plate to initialize
`custom-theme-load-path' that turns a "regular package" into a "theme
package", without making the distinction formal in package.el.




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 10:33:57 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 06:33:57 2026
Received: from localhost ([127.0.0.1]:39197 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0crM-0007oE-Qm
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 06:33:57 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:37672)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1x0crI-0007nt-8c
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 06:33:55 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@HIDDEN>)
 id 1x0crA-0006KM-Jw; Sun, 30 Aug 2026 06:33:44 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From:
 Date; bh=PuOsphNp5HYJ74Zx8pxm+gmKBXntJ2YWmKAAO2RBVhM=; b=kd3YXWbG8FOwKENge2hI
 gv1r7IdJBOPDkJCNCuSFoGPESRsUfc21++k2rzrQM8FPtL/r8/Ty+X/piEfLNFAHf17Tita05UcVB
 xNzIHuo5MmWxcFyIvCrC6Et5qT8MujzcgOXfdnoES0GwERNeRgL5tjKYoc+693bVsdV3pOkgqvtf9
 1VwtScB1HRCPEk7bh809zSwsAYeoJ2oxBnPuj60dRUaJbit3BsuWPfLP4ampz3JQR1P4eVi44M87/
 VpUvXhznFcpJHyfljEdIFz/h1APTFRTwK5DJNWmQR1uID8DQeYs0xGXuDEv/hY+cjkLdzFcwSgvQr
 4n6m0gIMBQB6sQ==;
Date: Sun, 30 Aug 2026 13:33:42 +0300
Message-Id: <86bjajaoe1.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
To: Philip Kaludercic <philipk@HIDDEN>
In-Reply-To: <87cxv054mn.fsf@HIDDEN> (message from Philip Kaludercic on
 Sun, 30 Aug 2026 09:39:29 +0000)
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Spam-Score: -0.7 (/)
X-Debbugs-Envelope-To: 81741
Cc: prot@HIDDEN, 81741 <at> debbugs.gnu.org, monnier@HIDDEN
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

> From: Philip Kaludercic <philipk@HIDDEN>
> Cc: Protesilaos <prot@HIDDEN>,  Stefan Monnier
>  <monnier@HIDDEN>,  81741 <at> debbugs.gnu.org
> Date: Sun, 30 Aug 2026 09:39:29 +0000
> 
> Eli Zaretskii <eliz@HIDDEN> writes:
> 
> >> Date: Sat, 29 Aug 2026 22:59:35 +0300
> >> From: Protesilaos <prot@HIDDEN>
> >> 
> >> Dear maintainers,
> >> 
> >> The modus-themes are not recognised by package.el as a "built-in" theme.
> >> Here is what I tried in ’emacs -Q’:
> >> 
> >>      (require ’package)
> >> 
> >>      (package-built-in-p 'org)
> >>      ;; => t
> >> 
> >>      (package-built-in-p 'transient)
> >>      ;; => t
> >> 
> >>      (package-built-in-p 'modus-themes)
> >>      ;; => nil
> >
> > Why did you expect or need package.el to recognize themes as packages?
> 
> Modus Themes is now also a framework for packages, meaning that other
> packages can instantiate it with their own color scheme.  As such, other
> packages depend on Modus Themes, and it would be nice to avoid having to
> install the dependency, if Emacs already comes with a recent enough
> version of the Theme.

My interpretation of the report was that not just modus-themes.el, but
all the other modus-*-theme.el files (and other themes as well) are
expected to be considered as built-in packages.  Apologies if I
misunderstood, and this is _only_ about a single modus-themes.el file.

For example:

> >> I looked into the source and noticed that the ’finder-compile-keywords’
> >> function reads from DIRS or the ’load-path’. This means that it does not
> >> find the ’modus-themes.el’, which is available in the 
> >> ’custom-theme-load-path’.
> >> 
> >> Should we modify ’finder-compile-keywords’ to also read from the
> >> ’custom-theme-load-path’ or move the ’modus-themes.el’ to the lisp/
> >> directory?

This seems to imply that the request was to consider all themes as
built-in packages, because custom-theme-load-path is not specific to
modus-themes.

> I think that it would make sense to move modus-themes.el to the lisp/
> directory.  Is there any reason not to do so?  Or rather, why was it
> initially placed elsewhere?

We could move the file to lisp/ indeed, but it sounds strange to have
it there, since the themes which depend on it are in etc/themes/.
When modus-themes.el is updated on ELPA, aren't the other
modus-*-themes updated as well?  If they are, then how will it help to
consider modus-themes.el a built-in package if the themes themselves
aren't?  What am I missing?

> > I'm not sure we want to generalize the notion of "package" to themes.
> > Why not consider themes to be separate from packages?  That was the
> > original design of themes, and that's why we have a separate
> > custom-theme-load-path variable in the first place.
> >
> >> The ’modus-themes’ package can be used as a basis for other themes.
> >> There are plenty of packages already, including a new candidate for GNU
> >> ELPA.
> >
> > Exactly.  So one more reason not to consider themes to be packages.
> > If we want package.el to support themes, I'd prefer to have a separate
> > set of commands for that, because otherwise I feel we will make a
> > mess, given how themes are handled differently from packages.
> 
> I don't understand your reasoning here, or maybe I am misunderstanding
> what separate set of commands you are envisioning?

I envisioned a separate set of package.el commands to handle
installing themes from ELPA.




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 09:56:40 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 05:56:40 2026
Received: from localhost ([127.0.0.1]:39056 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0cHH-0005Be-QD
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 05:56:40 -0400
Received: from mail-ua1-x92f.google.com ([2607:f8b0:4864:20::92f]:51369)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
 (Exim 4.84_2) (envelope-from <shipmints@HIDDEN>)
 id 1x0cHE-0005BA-KW
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 05:56:38 -0400
Received: by mail-ua1-x92f.google.com with SMTP id
 a1e0cc1a2514c-97bf90f4b41so1218384241.2
 for <81741 <at> debbugs.gnu.org>; Sun, 30 Aug 2026 02:56:36 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1788083791; cv=none;
 d=google.com; s=arc-20260327;
 b=ifA4Gn5G6niXdR8DLMgKFyn0fNztnFbZw0SxMDurPopx8FXZk2jAIf+Ehg8YS3nX6k
 PXqe08AlpwHCKpXOiZc5tLrF3b0MautCB8kFq1sf9VS+GsKoeTEtDz7jWGQJU/9LCWdt
 D+jR1dGGCSCBTCZb24Kt/udwwXP07teAOvabO+/nRCsP2bGSNH3fzsDrhl0eeuMVUELX
 LuDpr7cRvahJM9WU7c+ZS69nlwx8taZUgO6mQWQc/SsNJH5aAaytLJarlIGH1GJIk/6T
 Dx7t3RlhYaN6NHdySc+zPKPhKcKX5DLXUNBevlUfnZzDDMzJWaTKrN3V9cytFlUUJpYA
 8YPw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
 s=arc-20260327; 
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:dkim-signature;
 bh=D6MlLQ94HOV8hBC4Bf5T8REXy7Ll34wSnyEpdJdymzw=;
 fh=eSA6V+KuqQUA5gYjiQenFmhbClHKD8xvvB/zzIP7JQc=;
 b=Rd8dmQPDCqw9+ciPYd3MjhbwP1bVc9uf0drADE6RWow21S7tmOLfHxjwb+h+R+ccpK
 m8m3ERR+vGNeQXxkzP589ThzsNV5yTw1h/6Y5B81VNhRgV1h9hiY0jnohn9A8jSs6NXg
 CqM3LohDw8eacz/KDPo6qpJqUm+2tlgFpEwUPmYPn5XcwXwaduI8Xth0eW0dyEgrRT3f
 n0wMgcTyGNtf0xVJyyW/tD2tiemIOTxqSDb957iSyOTVHFJPYH0oa8HZ4cpIFi0HIaMy
 0rNCniktOJylkfbZvJtDCcVZ7NJgD5AHAkyrlpicURz2XYt18DXw+ntmlXaO25l2zYt/
 4Xzg==; darn=debbugs.gnu.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20251104; t=1788083791; x=1788688591; darn=debbugs.gnu.org;
 h=content-type:cc:to:subject:message-id:date:from:in-reply-to
 :references:mime-version:from:to:cc:subject:date:message-id:reply-to
 :content-type; bh=D6MlLQ94HOV8hBC4Bf5T8REXy7Ll34wSnyEpdJdymzw=;
 b=dhNTRJzJoaumlfTAszR9O6e0nPAM26gvZhdYcbgCjyuYoCBMQ3JP2NsM/Ab43/Dc89
 pTn6vqbS7vbH+v004KXfJMVFqVyBB1e/tOBSjjjPMwOMi2h+E/CugnGbRzv4YWzSZPzm
 Azkw6lPjSngzJS5ojfu/6I50s2d5/CWIDW3m/pZk+S+/ItbTeG9ZMu0scmRFjkamg7GN
 zYJfvRsW/B3qsGoOS640S1KmZQMKT+WDkI+feTMaJ+bGsOQ9AReC03YQRudktzkp+Eve
 B+90RQmGmL4NnJRZzJCynnZ9J6XorhVXajI8MjzUrkjJo3j1m1SLfm5tAYujx6kJUwc9
 PE5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20251104; t=1788083791; x=1788688591;
 h=content-type:cc:to:subject:message-id:date:from:in-reply-to
 :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc
 :subject:date:message-id:reply-to:content-type;
 bh=D6MlLQ94HOV8hBC4Bf5T8REXy7Ll34wSnyEpdJdymzw=;
 b=eQeSy9WzPy4ZqvZKf7KkzbGfEbqSf4x34tvmz2bwiChv2guE7+zTyz0Xhnk5YJmf82
 DPh/Z61UCFPzA7vbAEJ3no4/yiBguSWFGFSoDf6BrPEh+Hg+sOtVhhy1R5LY1fWXIDoL
 laIXivVFWlR4lZKiTibUMWogfaiHYyw1R0JbVfYgDHuePX+XsXarmDbJGCUJbvo8AuIz
 9N91+tEEyPsoSX/LXb52+Z4kYe0kbZdVY9sKXHjNePL9EgASXlkkzHujQ5Vo3asJLdIR
 JrJYyI6A4la8ootByi9KYhJUlY2p+5rv3gIgZ6wuDw06d7VxsWe+Brt/1QfMQrrDZW9T
 QS5g==
X-Forwarded-Encrypted: i=1;
 AHgh+Ro8u9r4jov+/mFiouqPJizkOuGRCmey/pDgGEzl+g4kAvqvaaYVytCjSPFcGwQkS3O1XROWhA==@debbugs.gnu.org
X-Gm-Message-State: AFuF++kQ4yDTFSvRkR/vIsxl8RbQ/v30L2F3oD7zjFA2wMgvvENNLkgS
 IX7VUIMdEddjTASwX/ZjR64APeL3CG7AAyiaO16Fddj+7XLNg9roGdphfGHkrMX4BNnhsAv4lpv
 Xb+zgpfBj1jbzYyOMrHRAdEYsAFRkgiE=
X-Gm-Gg: AR+sD134sNzMxz+JGTlG+WcfGDgY0kGsAWT9Zy72jm+EjvddR+d3UGJa1dbGrBMXAN5
 PZQQluWB+5XLT+eS4SXIR+QB7s3V6gx4xNdyHMQcBl+lEDiMSOPHgOR3NLZDl3XrJsdXUDPiv84
 fWDL733sgKkihm9CpOKWNRvj5g0kpRnmDMbKzHvJfgRDRHkeFk8MhNjndqODLPuG9qhlBSZuA3B
 rxQaF6iwu5bp93rQsRdBrmMzloz37RGk/ZQMVMVp3CFVDWPpji+HYU0s2Py5XOd3hOH7UyW72Z9
 DkanPey16IEjgXRf1liw3+rzQEKwWRv6YEWPEqCHkwa579YVM3q+OO5tSz5lya3Pwqz+GWcxRpc
 83aTKwyslFUNujNh2sveFDdJZchANqHZNz+G1UXiG/InG+4zh7UcT5OrWjpDrWniVKZVRdtMick
 bApz51Lw05oM3tpmPnr6N8J7I1OdUXnIBSpMRwEzkjYyvn17HdTFag8pimdiZYBVTzStw=
X-Received: by 2002:a05:6102:94d:b0:789:5b58:e105 with SMTP id
 ada2fe7eead31-7895b58e2d2mr2387859137.2.1788083790809; Sun, 30 Aug 2026
 02:56:30 -0700 (PDT)
MIME-Version: 1.0
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN> <87cxv054mn.fsf@HIDDEN>
In-Reply-To: <87cxv054mn.fsf@HIDDEN>
From: =?UTF-8?Q?St=C3=A9phane_Marks?= <shipmints@HIDDEN>
Date: Sun, 30 Aug 2026 05:56:18 -0400
X-Gm-Features: AcwNN1U3xa3qEJXVh83k1eXO1jJBH4Ppg-GKWqF2917xvJTLNOXjcQOuEUUwT1I
Message-ID: <CAN+1HbpYZk-WUsfvMNs941tCCJCayOGG1AG5TDzPz_j8K0JHEw@HIDDEN>
Subject: Re: bug#81741: 32.0.50;
 modus-themes is not recognised as a built-in package
To: Philip Kaludercic <philipk@HIDDEN>
Content-Type: multipart/alternative; boundary="0000000000002e0b9b065a40b38f"
X-Spam-Score: 1.0 (+)
X-Debbugs-Envelope-To: 81741
Cc: Eli Zaretskii <eliz@HIDDEN>, Protesilaos <prot@HIDDEN>,
 81741 <at> debbugs.gnu.org, Stefan Monnier <monnier@HIDDEN>
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: 0.0 (/)

--0000000000002e0b9b065a40b38f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Aug 30, 2026 at 5:40=E2=80=AFAM Philip Kaludercic <philipk@HIDDEN=
et>
wrote:

> Eli Zaretskii <eliz@HIDDEN> writes:
>
> >> Date: Sat, 29 Aug 2026 22:59:35 +0300
> >> From: Protesilaos <prot@HIDDEN>
> >>
> >> Dear maintainers,
> >>
> >> The modus-themes are not recognised by package.el as a "built-in" them=
e.
> >> Here is what I tried in =E2=80=99emacs -Q=E2=80=99:
> >>
> >>      (require =E2=80=99package)
> >>
> >>      (package-built-in-p 'org)
> >>      ;; =3D> t
> >>
> >>      (package-built-in-p 'transient)
> >>      ;; =3D> t
> >>
> >>      (package-built-in-p 'modus-themes)
> >>      ;; =3D> nil
> >
> > Why did you expect or need package.el to recognize themes as packages?
>
> Modus Themes is now also a framework for packages, meaning that other
> packages can instantiate it with their own color scheme.  As such, other
> packages depend on Modus Themes, and it would be nice to avoid having to
> install the dependency, if Emacs already comes with a recent enough
> version of the Theme.
>
> >> I looked into the source and noticed that the =E2=80=99finder-compile-=
keywords=E2=80=99
> >> function reads from DIRS or the =E2=80=99load-path=E2=80=99. This mean=
s that it does not
> >> find the =E2=80=99modus-themes.el=E2=80=99, which is available in the
> >> =E2=80=99custom-theme-load-path=E2=80=99.
> >>
> >> Should we modify =E2=80=99finder-compile-keywords=E2=80=99 to also rea=
d from the
> >> =E2=80=99custom-theme-load-path=E2=80=99 or move the =E2=80=99modus-th=
emes.el=E2=80=99 to the lisp/
> >> directory?
>
> I think that it would make sense to move modus-themes.el to the lisp/
> directory.  Is there any reason not to do so?  Or rather, why was it
> initially placed elsewhere?
>
> > I'm not sure we want to generalize the notion of "package" to themes.
> > Why not consider themes to be separate from packages?  That was the
> > original design of themes, and that's why we have a separate
> > custom-theme-load-path variable in the first place.
> >
> >> The =E2=80=99modus-themes=E2=80=99 package can be used as a basis for =
other themes.
> >> There are plenty of packages already, including a new candidate for GN=
U
> >> ELPA.
> >
> > Exactly.  So one more reason not to consider themes to be packages.
> > If we want package.el to support themes, I'd prefer to have a separate
> > set of commands for that, because otherwise I feel we will make a
> > mess, given how themes are handled differently from packages.
>
> I don't understand your reasoning here, or maybe I am misunderstanding
> what separate set of commands you are envisioning?
>

Maybe it's time to split modus into modus-core, an ELisp package of shared
theme functions, and modus-themes, the built-in themes on top of core
treated like themes.

--0000000000002e0b9b065a40b38f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:monospace"><span style=3D"font-family:Arial,Helvetica,sans-serif;b=
ackground-color:transparent">On Sun, Aug 30, 2026 at 5:40=E2=80=AFAM Philip=
 Kaludercic &lt;<a href=3D"mailto:philipk@HIDDEN">philipk@HIDDEN</a=
>&gt; wrote:</span></div></div><div class=3D"gmail_quote gmail_quote_contai=
ner"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">Eli Zaretskii &lt;<a=
 href=3D"mailto:eliz@HIDDEN" target=3D"_blank">eliz@HIDDEN</a>&gt; writes=
:<br>
<br>
&gt;&gt; Date: Sat, 29 Aug 2026 22:59:35 +0300<br>
&gt;&gt; From: Protesilaos &lt;<a href=3D"mailto:prot@HIDDEN" targ=
et=3D"_blank">prot@HIDDEN</a>&gt;<br>
&gt;&gt; <br>
&gt;&gt; Dear maintainers,<br>
&gt;&gt; <br>
&gt;&gt; The modus-themes are not recognised by package.el as a &quot;built=
-in&quot; theme.<br>
&gt;&gt; Here is what I tried in =E2=80=99emacs -Q=E2=80=99:<br>
&gt;&gt; <br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 (require =E2=80=99package)<br>
&gt;&gt; <br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 (package-built-in-p &#39;org)<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 ;; =3D&gt; t<br>
&gt;&gt; <br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 (package-built-in-p &#39;transient)<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 ;; =3D&gt; t<br>
&gt;&gt; <br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 (package-built-in-p &#39;modus-themes)<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 ;; =3D&gt; nil<br>
&gt;<br>
&gt; Why did you expect or need package.el to recognize themes as packages?=
<br>
<br>
Modus Themes is now also a framework for packages, meaning that other<br>
packages can instantiate it with their own color scheme.=C2=A0 As such, oth=
er<br>
packages depend on Modus Themes, and it would be nice to avoid having to<br=
>
install the dependency, if Emacs already comes with a recent enough<br>
version of the Theme.<br>
<br>
&gt;&gt; I looked into the source and noticed that the =E2=80=99finder-comp=
ile-keywords=E2=80=99<br>
&gt;&gt; function reads from DIRS or the =E2=80=99load-path=E2=80=99. This =
means that it does not<br>
&gt;&gt; find the =E2=80=99modus-themes.el=E2=80=99, which is available in =
the <br>
&gt;&gt; =E2=80=99custom-theme-load-path=E2=80=99.<br>
&gt;&gt; <br>
&gt;&gt; Should we modify =E2=80=99finder-compile-keywords=E2=80=99 to also=
 read from the<br>
&gt;&gt; =E2=80=99custom-theme-load-path=E2=80=99 or move the =E2=80=99modu=
s-themes.el=E2=80=99 to the lisp/<br>
&gt;&gt; directory?<br>
<br>
I think that it would make sense to move modus-themes.el to the lisp/<br>
directory.=C2=A0 Is there any reason not to do so?=C2=A0 Or rather, why was=
 it<br>
initially placed elsewhere?<br>
<br>
&gt; I&#39;m not sure we want to generalize the notion of &quot;package&quo=
t; to themes.<br>
&gt; Why not consider themes to be separate from packages?=C2=A0 That was t=
he<br>
&gt; original design of themes, and that&#39;s why we have a separate<br>
&gt; custom-theme-load-path variable in the first place.<br>
&gt;<br>
&gt;&gt; The =E2=80=99modus-themes=E2=80=99 package can be used as a basis =
for other themes.<br>
&gt;&gt; There are plenty of packages already, including a new candidate fo=
r GNU<br>
&gt;&gt; ELPA.<br>
&gt;<br>
&gt; Exactly.=C2=A0 So one more reason not to consider themes to be package=
s.<br>
&gt; If we want package.el to support themes, I&#39;d prefer to have a sepa=
rate<br>
&gt; set of commands for that, because otherwise I feel we will make a<br>
&gt; mess, given how themes are handled differently from packages.<br>
<br>
I don&#39;t understand your reasoning here, or maybe I am misunderstanding<=
br>
what separate set of commands you are envisioning?<br></blockquote><div><br=
></div><div class=3D"gmail_default" style=3D"font-family:monospace">Maybe i=
t&#39;s time to split modus into modus-core, an ELisp package of shared the=
me functions, and modus-themes, the built-in themes on top of core treated =
like themes.</div></div></div>

--0000000000002e0b9b065a40b38f--




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 09:39:40 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 05:39:40 2026
Received: from localhost ([127.0.0.1]:39023 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0c0p-000492-Od
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 05:39:40 -0400
Received: from mout02.posteo.de ([185.67.36.66]:39617)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <philipk@HIDDEN>)
 id 1x0c0l-00048X-QW
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 05:39:37 -0400
Received: from submission (posteo.de [185.67.36.169]) 
 by mout02.posteo.de (Postfix) with ESMTPS id 97719240101
 for <81741 <at> debbugs.gnu.org>; Sun, 30 Aug 2026 11:39:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.net;
 s=1984.8680eb; t=1788082769;
 bh=GeROL705oknE+wr2tesUUOn/+2ZC1rs/smJCqVbAzRs=;
 h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version:
 Content-Type:Content-Transfer-Encoding:From;
 b=XbYmjZCjG8QOaHW0DhxAbwenZWaAgZgBogBKDaAf1BBruFM9f3NfQdI/zuawud6Uo
 jZJSf3F9AuGvhkWB1H4FndxISBRl41s9m5xcjGpxLBUe/s90HoCI4VqdW1DSCHjdcT
 FJIvVjqPbIkZAyvPguDpfxdfJWeudSEk6Q6JZOEJmPATQu1J6Eu92nQALF8GOytVvT
 fzNhuBmp6ciCC0Z6oCZQ5+aN8SAByPrt1J8nld0isinGxiTJMi6dbux4iJ+8q66/h/
 Isizeok6+4P6XgaKdl6oAMbVY51wTlUOF8WIpP1zZixkDMtOahuHzdfBMl1t6aLUwZ
 nWJNUgaPWvXkQ==
Received: from customer (localhost [127.0.0.1])
 by submission (posteo.de) with ESMTPSA id 4hXnC449w9z6ty3;
 Sun, 30 Aug 2026 11:39:28 +0200 (CEST)
From: Philip Kaludercic <philipk@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#81741: 32.0.50; modus-themes is not recognised as a
 built-in package
In-Reply-To: <86ik4s9qjp.fsf@HIDDEN>
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
 <86ik4s9qjp.fsf@HIDDEN>
OpenPGP: id=philipk@HIDDEN;
 url="https://keys.openpgp.org/vks/v1/by-email/philipk@HIDDEN";
 preference=signencrypt
Date: Sun, 30 Aug 2026 09:39:29 +0000
Message-ID: <87cxv054mn.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -2.3 (--)
X-Debbugs-Envelope-To: 81741
Cc: Protesilaos <prot@HIDDEN>, 81741 <at> debbugs.gnu.org,
 Stefan Monnier <monnier@HIDDEN>
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

Eli Zaretskii <eliz@HIDDEN> writes:

>> Date: Sat, 29 Aug 2026 22:59:35 +0300
>> From: Protesilaos <prot@HIDDEN>
>>=20
>> Dear maintainers,
>>=20
>> The modus-themes are not recognised by package.el as a "built-in" theme.
>> Here is what I tried in =E2=80=99emacs -Q=E2=80=99:
>>=20
>>      (require =E2=80=99package)
>>=20
>>      (package-built-in-p 'org)
>>      ;; =3D> t
>>=20
>>      (package-built-in-p 'transient)
>>      ;; =3D> t
>>=20
>>      (package-built-in-p 'modus-themes)
>>      ;; =3D> nil
>
> Why did you expect or need package.el to recognize themes as packages?

Modus Themes is now also a framework for packages, meaning that other
packages can instantiate it with their own color scheme.  As such, other
packages depend on Modus Themes, and it would be nice to avoid having to
install the dependency, if Emacs already comes with a recent enough
version of the Theme.

>> I looked into the source and noticed that the =E2=80=99finder-compile-ke=
ywords=E2=80=99
>> function reads from DIRS or the =E2=80=99load-path=E2=80=99. This means =
that it does not
>> find the =E2=80=99modus-themes.el=E2=80=99, which is available in the=20
>> =E2=80=99custom-theme-load-path=E2=80=99.
>>=20
>> Should we modify =E2=80=99finder-compile-keywords=E2=80=99 to also read =
from the
>> =E2=80=99custom-theme-load-path=E2=80=99 or move the =E2=80=99modus-them=
es.el=E2=80=99 to the lisp/
>> directory?

I think that it would make sense to move modus-themes.el to the lisp/
directory.  Is there any reason not to do so?  Or rather, why was it
initially placed elsewhere?

> I'm not sure we want to generalize the notion of "package" to themes.
> Why not consider themes to be separate from packages?  That was the
> original design of themes, and that's why we have a separate
> custom-theme-load-path variable in the first place.
>
>> The =E2=80=99modus-themes=E2=80=99 package can be used as a basis for ot=
her themes.
>> There are plenty of packages already, including a new candidate for GNU
>> ELPA.
>
> Exactly.  So one more reason not to consider themes to be packages.
> If we want package.el to support themes, I'd prefer to have a separate
> set of commands for that, because otherwise I feel we will make a
> mess, given how themes are handled differently from packages.

I don't understand your reasoning here, or maybe I am misunderstanding
what separate set of commands you are envisioning?




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at 81741 <at> debbugs.gnu.org:


Received: (at 81741) by debbugs.gnu.org; 30 Aug 2026 04:32:41 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Aug 30 00:32:41 2026
Received: from localhost ([127.0.0.1]:37458 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0XDk-0000rl-Rd
	for submit <at> debbugs.gnu.org; Sun, 30 Aug 2026 00:32:41 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10]:47288)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <eliz@HIDDEN>) id 1x0XDh-0000rB-Ux
 for 81741 <at> debbugs.gnu.org; Sun, 30 Aug 2026 00:32:39 -0400
Received: from fencepost.gnu.org ([2001:470:142:3::e])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@HIDDEN>)
 id 1x0XDa-0001wh-5b; Sun, 30 Aug 2026 00:32:30 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
 s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From:
 Date; bh=TQ1DceSOmzWBZE25Lozd6PFJh0pPztvKA1f4/sOUULA=; b=a1zvpeoVm3stRAudzLC/
 K79QSTkLJzgeA2HXtAlkTfLFe4S16t3GLGjhxwdDjUJ9Jln6gUW0YalooaPwuKPsMy7QBQJNHfiyh
 P1qx9FRTOH18rkKmsy6IHGRIrNp3RDWwAerbRHF9c7QCWqYwck/HfsbXI+WIWJe/iw3YM4Mzvs01S
 wePOh/nH06Mjjxnwt0op2nG9/VHQpOFWgCOYk9LMoEbY6HeWlbfP5kqme2ktnGn7u7Z0YwqEawhkw
 lxJU17LIoIMDULATYLl681ShTRKTsH2ViPV4ia/dDGmSiU5i1vS9IFdnrH5GpixSZqdliCIKg2fTe
 0OqleC9cFVHC0A==;
Date: Sun, 30 Aug 2026 07:32:26 +0300
Message-Id: <86ik4s9qjp.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
To: Protesilaos <prot@HIDDEN>,
 Stefan Monnier <monnier@HIDDEN>,
 Philip Kaludercic <philipk@HIDDEN>
In-Reply-To: <40cd308d3f2662f43c085c7349e49534@HIDDEN> (message from
 Protesilaos on Sat, 29 Aug 2026 22:59:35 +0300)
Subject: Re: bug#81741: 32.0.50;
 modus-themes is not recognised as a built-in package
References: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Spam-Score: -0.7 (/)
X-Debbugs-Envelope-To: 81741
Cc: 81741 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.7 (-)

> Date: Sat, 29 Aug 2026 22:59:35 +0300
> From: Protesilaos <prot@HIDDEN>
> 
> Dear maintainers,
> 
> The modus-themes are not recognised by package.el as a "built-in" theme.
> Here is what I tried in ’emacs -Q’:
> 
>      (require ’package)
> 
>      (package-built-in-p 'org)
>      ;; => t
> 
>      (package-built-in-p 'transient)
>      ;; => t
> 
>      (package-built-in-p 'modus-themes)
>      ;; => nil

Why did you expect or need package.el to recognize themes as packages?

> I looked into the source and noticed that the ’finder-compile-keywords’
> function reads from DIRS or the ’load-path’. This means that it does not
> find the ’modus-themes.el’, which is available in the 
> ’custom-theme-load-path’.
> 
> Should we modify ’finder-compile-keywords’ to also read from the
> ’custom-theme-load-path’ or move the ’modus-themes.el’ to the lisp/
> directory?

I'm not sure we want to generalize the notion of "package" to themes.
Why not consider themes to be separate from packages?  That was the
original design of themes, and that's why we have a separate
custom-theme-load-path variable in the first place.

> The ’modus-themes’ package can be used as a basis for other themes.
> There are plenty of packages already, including a new candidate for GNU
> ELPA.

Exactly.  So one more reason not to consider themes to be packages.
If we want package.el to support themes, I'd prefer to have a separate
set of commands for that, because otherwise I feel we will make a
mess, given how themes are handled differently from packages.




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.

Message received at submit <at> debbugs.gnu.org:


Received: (at submit) by debbugs.gnu.org; 29 Aug 2026 19:59:49 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sat Aug 29 15:59:49 2026
Received: from localhost ([127.0.0.1]:58525 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1x0PDR-0003C0-FF
	for submit <at> debbugs.gnu.org; Sat, 29 Aug 2026 15:59:49 -0400
Received: from lists1p.gnu.org ([2001:470:142::17]:58896)
 by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.84_2) (envelope-from <prot@HIDDEN>)
 id 1x0PDO-0003BE-U6
 for submit <at> debbugs.gnu.org; Sat, 29 Aug 2026 15:59:47 -0400
Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <prot@HIDDEN>)
 id 1x0PDJ-0006Tz-7u
 for bug-gnu-emacs@HIDDEN; Sat, 29 Aug 2026 15:59:41 -0400
Received: from relay6-d.mail.gandi.net ([2001:4b98:dc4:8::226])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <prot@HIDDEN>)
 id 1x0PDG-0004tD-Ve
 for bug-gnu-emacs@HIDDEN; Sat, 29 Aug 2026 15:59:41 -0400
Received: by mail.gandi.net (Postfix) with ESMTPSA id 89E8C3F5D5
 for <bug-gnu-emacs@HIDDEN>; Sat, 29 Aug 2026 19:59:35 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protesilaos.com;
 s=gm1; t=1788033575;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:mime-version:mime-version:content-type:content-type:
 content-transfer-encoding:content-transfer-encoding;
 bh=fgd9ZciWyc9bDcrekfa8gNcRlO3bBEZqfIN837VgMj0=;
 b=Kn9C++fs9JRRBjhaUdh8BfqVs/FlF11Yaz5rFfrPh9cdu0VgwOIBRKHBvZzeGggaePo4rM
 amJdIXNkoJCEk4HZGx95yr5gJWCaxaoTBOxWFM9OalyGc3DYYcwQegjGjei8JFLi8iJt/3
 rllJ2bYCs1wdc2nIRlGOv8lFYi1OqY5xfttLn61Pqf6OtGgGU7bgtie3AOneeLTAHyJUXT
 L2xKlZbUdoy8TfUch6D3XkzL8x77m+BYMU5M6Qq6zIbr42dNh7ePGKpmXY7oAeLxjlJg70
 /A5e58letCmMD24cDKz1zq98fnDPxJgw0RZoPy7ft7Gt4zn5DGgHGunj3Y6Trw==
MIME-Version: 1.0
Date: Sat, 29 Aug 2026 22:59:35 +0300
From: Protesilaos <prot@HIDDEN>
To: bug-gnu-emacs@HIDDEN
Subject: 32.0.50; modus-themes is not recognised as a built-in package
Message-ID: <40cd308d3f2662f43c085c7349e49534@HIDDEN>
X-Sender: prot@HIDDEN
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
X-GND-Sasl: prot@HIDDEN
X-GND-State: clean
X-GND-Score: 0
X-GND-Cause: dmFkZTFIAITjV0YgzHilvN7JTaHdDGSXAWjoBgOY73MSxakxvn2bnlJxmH2ypaMM5J51A73/mnGYNfpWbdhRpPHLOfs7V2u8ex0zNLwm6XxOOFbSMDNnTtxrxubXdVIEm0U3NDdF6zPVnqL31swgBAQVx87URWOVTFN+Kg3tsYPofe2U8G6/wGPnxdGmHqSh3Af1i8Wdfucm6LRCf4IWz8U91HFYBhYlov7XnfCX/DHK/lX+xLaBFlm30ZwGFBPz+kUH+6I1pUWzQWoFmdLFBQov/86Q79YZpxdCpCCaTEVg130EsbYqSf/IAjpvABVfQhDlWiajxQGYXq0QAM99Lm0+3rLlWVefOiyJdcsmMpq+V0m9D5wzTGMXTF+YhqYWZ/UcVjVW0nLAo7JdP/nvExyXs7FLiXVA+xjIU0Fn0g4lN/g+8dwJxXYUNzuVRzywO6wNf52nBHQGShUHnWZV3Rx5UCFHH9wRcxCvqnK06a2xJenXocNfl+7V88AetYWRc9ZC/Cb1O/M1lGocMWiSPtORoBVe3x4mjDCPpkwq9OnK9gx7AhE0WMhSt5V6AXCGVOTXk28be516tYJ0C8e9+uIVtN+xNFqgmjFaqMkxJqnW8r1k+VlNKQV6YheNzdpF0uMsGNMDN/V2ezOHVIQmyIj+ibX4NTnGf8x52kA1TsA0NgMjMw
Received-SPF: pass client-ip=2001:4b98:dc4:8::226;
 envelope-from=prot@HIDDEN; helo=relay6-d.mail.gandi.net
X-Spam_score_int: -20
X-Spam_score: -2.1
X-Spam_bar: --
X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001,
 SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: 0.7 (/)
X-Debbugs-Envelope-To: submit
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -0.3 (/)

Dear maintainers,

The modus-themes are not recognised by package.el as a "built-in" theme.
Here is what I tried in ’emacs -Q’:

     (require ’package)

     (package-built-in-p 'org)
     ;; => t

     (package-built-in-p 'transient)
     ;; => t

     (package-built-in-p 'modus-themes)
     ;; => nil

I looked into the source and noticed that the ’finder-compile-keywords’
function reads from DIRS or the ’load-path’. This means that it does not
find the ’modus-themes.el’, which is available in the 
’custom-theme-load-path’.

Should we modify ’finder-compile-keywords’ to also read from the
’custom-theme-load-path’ or move the ’modus-themes.el’ to the lisp/
directory?

The ’modus-themes’ package can be used as a basis for other themes.
There are plenty of packages already, including a new candidate for GNU
ELPA.

All the best,
Protesilaos (or simply "Prot")




Acknowledgement sent to Protesilaos <prot@HIDDEN>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs@HIDDEN. Full text available.
Report forwarded to bug-gnu-emacs@HIDDEN:
bug#81741; Package emacs. Full text available.
Please note: This is a static page, with minimal formatting, updated once a day.
Click here to see this page with the latest information and nicer formatting.
Last modified: Mon, 31 Aug 2026 12:00:03 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.