From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Hackney <dan@haxney.org>
Cc: Chong Yidong <cyd@gnu.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] Re: package.el changes before the feature freeze
Date: Tue, 09 Oct 2012 13:39:22 -0400 [thread overview]
Message-ID: <jwvk3uzpmxa.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAMqXDZsLGf8Dq5pODWBivc6U9FAv0QRy5NXukmeuhY_qY4sE6Q@mail.gmail.com> (Daniel Hackney's message of "Tue, 9 Oct 2012 13:07:08 -0400")
> the associated test cases). Updating packages cleanly is currently
> bugged; Emacs still expects the docstrings to be at the old location,
> but if it is deleted (which is what `package-menu-mark-upgrades' offers
> to do), you will get "could not find docstring" errors which break
> certain commands.
The general rule is that failure to find the docstring should not
break commands. I've fixed a few such cases recently, but if you find
more, please report them. Even without package.el the file might
disappear or be replaced and that's usually no justification to break the
whole command (e.g. describe-function/variable is still useful even if the
docstring is not found).
Stefan
next prev parent reply other threads:[~2012-10-09 17:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 16:58 package.el changes before the feature freeze Daniel Hackney
2012-09-30 20:21 ` Stefan Monnier
2012-09-30 23:50 ` Daniel Hackney
2012-10-01 1:21 ` Stefan Monnier
2012-10-01 3:11 ` Chong Yidong
2012-10-03 0:33 ` Daniel Hackney
2012-10-03 22:41 ` [PATCH] " Daniel Hackney
2012-10-04 8:16 ` Chong Yidong
2012-10-05 23:13 ` Daniel Hackney
2012-10-06 1:38 ` Stefan Monnier
2012-10-08 2:32 ` Chong Yidong
2012-10-08 19:16 ` Daniel Hackney
2012-10-08 19:50 ` Stefan Monnier
2012-10-09 1:11 ` Daniel Hackney
2012-10-09 6:48 ` Stefan Monnier
2012-10-09 17:07 ` Daniel Hackney
2012-10-09 17:39 ` Stefan Monnier [this message]
2012-10-09 21:39 ` Daniel Hackney
2012-10-09 22:25 ` Glenn Morris
2012-10-12 3:58 ` Chong Yidong
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=jwvk3uzpmxa.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@gnu.org \
--cc=dan@haxney.org \
--cc=emacs-devel@gnu.org \
/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).