unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52985@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#52985: describe-package should show README instead of "Commentary" section
Date: Fri, 14 Jan 2022 11:21:59 -0500	[thread overview]
Message-ID: <jwv35lqpa2w.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874k66r9mo.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 14 Jan 2022 09:42:39 +0100")

Lars Ingebrigtsen [2022-01-14 09:42:39] wrote:
> Stefan Kangas <stefan@marxist.se> writes:
>> It would be more useful if `M-x describe-package' would show the README
>> file than the "Commentary" section, for packages where such a file
>> exists.
> Makes sense to me.
>> Perhaps we could even show the included images, somehow.
> Yes, that would be nice.
> I've added Stefan M to the CCs; perhaps he has some comments here.

When preparing the tarball, the (Non)GNU ELPA scripts can be told
whether to use the Commentary or a README file, and AFAIK that's the
info that is then shown by `describe-package`.  Currently the ELPA
protocol only offers a plain text version for that info.  We should
probably improve this part of the protocol.


        Stefan






      reply	other threads:[~2022-01-14 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 19:13 bug#52985: describe-package should show README instead of "Commentary" section Stefan Kangas
2022-01-14  8:42 ` Lars Ingebrigtsen
2022-01-14 16:21   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=jwv35lqpa2w.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=52985@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefan@marxist.se \
    /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).