all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 11915-done@debbugs.gnu.org
Subject: bug#11915: libraries that don't provide a feature or the wrong one
Date: Wed, 18 Jul 2012 07:44:38 -0400	[thread overview]
Message-ID: <jwvd33t2tfj.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CA+7KPGfRgBFpBksqU85bsOz=CeEkabcPoscHofy4jv1M9aa4xQ@mail.gmail.com> (Jonas Bernoulli's message of "Sun, 15 Jul 2012 14:42:47 +0200")

>>> * in the emacs-24 branch:
>>> bug-reference.el and map-ynp.el do not provide a feature.
>> Looks like a bug in bug-reference.el.
> This bug does not appear to be fixed yet.

Should be fixed now.

>> For map-ynp.el, I think it's normal because that file is preloaded.

I added:

> ;; Package: emacs
> to it's header.

>>> misearch.el provides `multi-isearch' instead of `misearch'.
>> That should be fixed,
> This does not appear to be fixed yet.

Should be fixed now.

>>> userlock.el, patcomp.el, forms-d2.el and forms-pass.el also
>>> don't provide a feature but it seems this intentional.
>> userlock should arguably be preloaded.
> Then it should also not be an "independent package" but be part of the
> "emacs" package just like `map-ynp.el'.

Done.

>> patcomp.el is obsolete and not worth fixing,
> Shouldn't it be moved to lisp/obsolete then (or since it was only used by
> maintainers removed right away)?  Also it should not appear in
> `package--builtins'.

It's already been moved to obsolete in trunk a while ago.

>>> However I think they then should not appear in `packages-builtins'.
>> You might be right (at least the etc/forms/*.el files shouldn't be
>> there), tho I'm not sure how important this is.
> It would be easy to make them part of the `forms' package.

Oh, I see, you're looking at the 24.1 code, but in the trunk these files
have been moved to "etc/forms" so they should not be a problem any more.

>>> * in the elpa branch:
>>> markchars.el does not provide a feature.
>> That's an oversight, yes, thank you,
> This does not appear to be fixed yet.

Should be fixed now.


        Stefan





      parent reply	other threads:[~2012-07-18 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 20:52 bug#11915: libraries that don't provide a feature or the wrong one Jonas Bernoulli
2012-07-12 14:33 ` Stefan Monnier
2012-07-12 15:22   ` Eli Zaretskii
     [not found]   ` <CA+7KPGfRgBFpBksqU85bsOz=CeEkabcPoscHofy4jv1M9aa4xQ@mail.gmail.com>
2012-07-18 11:44     ` Stefan Monnier [this message]

Reply instructions:

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

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

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

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

  git send-email \
    --in-reply-to=jwvd33t2tfj.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=11915-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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.