unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 55388-done@debbugs.gnu.org
Subject: bug#55388: 28.1; New libraries that neither belong to a package nor provide a feature
Date: Sun, 17 Sep 2023 16:15:29 -0700	[thread overview]
Message-ID: <CADwFkm=_wCNc3fX+FPKVY_jVmisMNR869LU8nCULd1z20s2ypA@mail.gmail.com> (raw)
In-Reply-To: <8735hetx8s.fsf@bernoul.li> (Jonas Bernoulli's message of "Thu, 12 May 2022 20:35:31 +0200")

Version: 29.2

Jonas Bernoulli <jonas@bernoul.li> writes:

> "lisp/emacs-lisp/shorthands.el" doesn't provide a feature and lacks
> a "Package" library header.  I think "Package: emacs" should be added.

Done.

> Like other files in that directory "lisp/leim/quail/cham.el" neither
> provides a feature nor is it explicitly made part of a package.  Would
> it make sense to add ("leim" . emacs) to `finder--builtins-alist'?
>
> Maybe another such entry should be added for the "obsolete" directory?

Fixed in Bug#62751.

> Unlike other "epa-*" libraries, "lisp/epa-ks.el" isn't made part of
> the "epa" package and fails to provide a feature.

Done.

Thanks for paying attention to this aspect.  I installed the fixes on
emacs-29 (commit 71a1f0fdc9e), and am consequently closing this bug
report.





      parent reply	other threads:[~2023-09-17 23:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 18:35 bug#55388: 28.1; New libraries that neither belong to a package nor provide a feature Jonas Bernoulli
2022-05-13 12:45 ` Lars Ingebrigtsen
2022-06-28 21:37   ` Stefan Kangas
2022-06-29  9:58     ` Lars Ingebrigtsen
2022-06-29 11:35     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-30  8:58       ` Lars Ingebrigtsen
2023-09-17 23:15 ` Stefan Kangas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkm=_wCNc3fX+FPKVY_jVmisMNR869LU8nCULd1z20s2ypA@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=55388-done@debbugs.gnu.org \
    --cc=jonas@bernoul.li \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).