From: Daniel Mendler <mail@daniel-mendler.de>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: [ELPA] Display package description as Org-exported text or HTML?
Date: Mon, 31 May 2021 12:53:11 +0200 [thread overview]
Message-ID: <b3f53e41-76a5-0e79-3e52-9b235c94d268@daniel-mendler.de> (raw)
In-Reply-To: <YLS6gaOjp5Jg4HM4@protected.localdomain>
On 5/31/21 12:29 PM, Jean Louis wrote:
> * Daniel Mendler <mail@daniel-mendler.de> [2021-05-31 13:10]:
>> Is it possible to display a package description as Org-exported text or
>> even as HTML on the ELPA website?
>>
>> See for example http://elpa.gnu.org/packages/consult.html, which shows a
>> large Org source file as "Full description".
>
> That is not readable.
> ...
> Thus, it is best to provide README.txt in plain text.
Jean, did you read my question? I am asking how to avoid this problem
you are reiterating.
To make my question more explicit:
Why is ELPA not automatically converting README.org to README.txt and
using it on the ELPA website? Stefan Monnier advised me to not make
generated files part of the repository. Originally, I generated a
vertico.texi file from the README.org. Fortunately the ELPA build
process is doing that automatically for me now. It would be great if the
same build step could be used for the website.
Daniel
next prev parent reply other threads:[~2021-05-31 10:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 10:09 [ELPA] Display package description as Org-exported text or HTML? Daniel Mendler
2021-05-31 10:29 ` Jean Louis
2021-05-31 10:53 ` Daniel Mendler [this message]
2021-05-31 11:04 ` Jean Louis
2021-05-31 12:13 ` Michael Heerdegen
2021-05-31 12:29 ` Jean Louis
2021-05-31 13:19 ` Stefan Monnier
2021-05-31 14:08 ` Michael Heerdegen
2021-05-31 14:59 ` Stefan Monnier
2021-05-31 15:14 ` Michael Heerdegen
2021-05-31 15:36 ` Stefan Monnier
2021-05-31 17:23 ` [ELPA PATCH] Add badge generator to elpa-admin.el Daniel Mendler
2021-05-31 18:02 ` Daniel Mendler
2021-06-04 16:00 ` Michael Heerdegen
2021-05-31 13:12 ` [ELPA] Display package description as Org-exported text or HTML? Stefan Monnier
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=b3f53e41-76a5-0e79-3e52-9b235c94d268@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).