all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noboru Ota <me@nobiot.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] Submitting new package Org-remark
Date: Sat, 29 Jan 2022 10:30:44 +0100	[thread overview]
Message-ID: <8635l6ga7v.fsf@nobiot.com> (raw)
In-Reply-To: <jwvfsp7607t.fsf-monnier+emacs@gnu.org>

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

> Looks good, added,
> [ I used `README.org` for the readme, instead of :make "README-elpa", tho  ]

Thank you, Stefan.

Could we discuss the use of `README.org` and `README-elpa` a bit
further, please? Perhaps we need both :readme and :make specs.

I would like to use an ASCII export of README.org, not the raw
README.org file for the package description.

Currently, `describe-package' shows the raw `README.org` *after* the
package has been installed.  I have observed the following details
below, and thought I should generate `README-elpa` to have the same
`README` before and after installation of package. This way, I can also
have a link to an Info node directly within the description (I provide
an Info node as a user manual).


Observation below in Emacs 27.2 on Windows and Emacs 29.0.50 on Ubuntu
Linux:

1. Before the user installs a package, `describe-package` (and
   `package-list-packages`) displays `package-name-readme.txt`.  ELPA
   generates it and when `README.org` is used as the README file, it
   gets exported to ASCII plain text (I believe this is done in
   functions `elpaa--get-README' and `elpaa--section-to-plain-text' in
   elpa-admin.el)


2. After the user has installed a package, `describe-package` (and
   `package-list-packages`) displays one of these files: "README-elpa"
   "README-elpa.md" "README" "README.rst" "README.org".  When
   `README.org` is used, the raw text is displayed without being
   exported to ASCII format (I believe this is done in function
   `describe-package-1' and `package--get-description')


Warm regards,
Noboru



  reply	other threads:[~2022-01-29  9:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 19:07 [ELPA] Submitting new package Org-remark Noboru Ota
2022-01-28 21:05 ` Stefan Monnier
2022-01-29  9:30   ` Noboru Ota [this message]
2022-01-29 22:26     ` Stefan Monnier
2022-01-30  9:37       ` Noboru Ota
2022-01-30 16:13         ` Stefan Monnier
2022-01-29 20:36 ` Uwe Brauer

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=8635l6ga7v.fsf@nobiot.com \
    --to=me@nobiot.com \
    --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 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.