all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>, 37546@debbugs.gnu.org
Subject: bug#37546: 26.3; Implement multi-file package README long description generation as described by elisp manual
Date: Tue, 01 Oct 2019 22:56:11 -0300	[thread overview]
Message-ID: <87pnjfsyf8.fsf@oitofelix.com> (raw)
In-Reply-To: <CADwFkm=_b3azYnCZku8kWGwmumgDB8LqjhTvzq-_k5mzjYd-kQ@mail.gmail.com> (Stefan Kangas's message of "Mon, 30 Sep 2019 19:35:06 +0200")

Hello Stefan,

> Did you see the function package--get-description?

I hadn’t seen that.  It seems that is not available in 26.3, but in master.
Thanks for pointing it out!


> In there, we also consider other names for the README file.  Could we
> perhaps base ourselves on that code somehow?

I think it’s a good idea to try to read all those READMEs in turn until
the first one succeeds, like it’s done there.  Are you proposing
something deeper?


-- 
 88888  FFFFF Bruno Félix Rezende Ribeiro (oitofelix) [0x28D618AF]
 8   8  F     http://oitofelix.freeshell.org/
 88888  FFFF  mailto:oitofelix@gnu.org
 8   8  F     irc://chat.freenode.org/oitofelix
 88888  F     xmpp://oitofelix@riseup.net





  reply	other threads:[~2019-10-02  1:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-29  3:52 bug#37546: 26.3; Implement multi-file package README long description generation as described by elisp manual Bruno Félix Rezende Ribeiro
2019-09-30 17:35 ` Stefan Kangas
2019-10-02  1:56   ` Bruno Félix Rezende Ribeiro [this message]
2019-10-02  9:31     ` Stefan Kangas
2020-01-23 22:21     ` Stefan Kangas

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=87pnjfsyf8.fsf@oitofelix.com \
    --to=oitofelix@gnu.org \
    --cc=37546@debbugs.gnu.org \
    --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 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.