unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: kfogel@red-bean.com, emacs-devel@gnu.org,
	Adam <adam.niederer@gmail.com>, "T.V Raman" <raman@google.com>
Subject: Re: [NonGNU ELPA] New packages: elquery, file-ring, metamorph
Date: Sun, 03 Apr 2022 03:25:34 -0700	[thread overview]
Message-ID: <86y20mpiox.fsf@stephe-leake.org> (raw)
In-Reply-To: <jwvsfqxosqz.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 01 Apr 2022 09:11:54 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Adam [2022-03-31 23:28:15] wrote:
>> On 3/31/22 08:48, Stefan Monnier wrote:
>>> AFAIK the users *should* already be able to see the
>>> README if they use a recent enough Emacs.
>>> IOW if that doesn't work, please file a bug report.
>> Is this something that is exclusive to ELPA?
>
> No.
>
>> I am able to view READMEs of certain ELPA packages, but no packages
>> from MELPA (including elquery) have READMEs available locally, on
>> 29.0.50.
>
> To view the README, it has to be included in the tarball, so it will
> depend on the MELPA recipe.

Currently, package-menu-describe-package (bound to '?' in *Packages*)
assumes that the README is available locally if the package is
installed. That could be relaxed; it could fetch it from the repository
if not found locally.

-- 
-- Stephe



  reply	other threads:[~2022-04-03 10:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28  3:58 [NonGNU ELPA] New packages: elquery, file-ring, metamorph Adam
2022-03-28  6:59 ` Visuwesh
2022-03-28 17:21   ` T.V Raman
2022-03-29  1:53     ` T.V Raman
2022-03-29  3:43       ` Karl Fogel
2022-03-29  5:23         ` Adam
2022-03-29 13:51           ` T.V Raman
2022-03-31  1:55             ` Adam
2022-03-31 12:48               ` Stefan Monnier
2022-04-01  3:28                 ` Adam
2022-04-01 13:11                   ` Stefan Monnier
2022-04-03 10:25                     ` Stephen Leake [this message]
2022-03-29 13:50         ` T.V Raman
2022-03-29 14:42         ` Stephen Leake
2022-03-29  8:28       ` Stefan Monnier
2022-03-28 22:09   ` Adam
2022-03-28 23:10     ` Ergus
2022-04-01  9:10       ` Augusto Stoffel

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=86y20mpiox.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=adam.niederer@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=raman@google.com \
    /path/to/YOUR_REPLY

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

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

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

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