unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 39609@debbugs.gnu.org
Subject: bug#39609: 26.3; Packaging system: Package documentation in the *Help* buffer
Date: Tue, 24 Nov 2020 22:19:04 +0100	[thread overview]
Message-ID: <86tutelagn.fsf@duenenhof-wilhelm.de> (raw)
In-Reply-To: <87tuuf1rf3.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 27 Oct 2020 18:59:12 +0100")

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

Hello Lars

thank you for looking into this!

Lars Ingebrigtsen <larsi@gnus.org> writes:

> dieter@duenenhof-wilhelm.de (H. Dieter Wilhelm) writes:
>
>> The Elisp manual (GNU Emacs 26.3 (build 1, x86_64-pc-linux-gnu, GTK+
>> Version 3.22.30) of 2019-12-14) states that a README file in the content
>> directory of a package will be used as a package description (C-h P).
>>
>> Please check
>>
>>   (info "(elisp) Multi-file Packages").
>>
>> Yet this isn't working!  By looking at other packages It seems that
>> there must be a file `PACKAGE-NAME-readme.txt' BELOW the content
>> directory to get a description in the package help.

> I tried `C-h P ada-mode RET' and got a *Help* buffer that included the
> README file for the ada-mode package, so I seem to be unable to
> reproduce this bug.

> Do you have a precise recipe to reproduce it, starting from "emacs -Q"?

I prepared a multi-file package for you.  Under Emacs 26.3 or earlier
you won't see any "long description" at all (unless you include a
PACKAGE-NAME-readme.txt in the package archive).  Under 27.1 it shows
now the ;;; Commentary: section of the PACKAGE-NAME.el file.  But NOT
the content of the accompanying README!

Please unpack the archive inform-1.4.tar into an empty DIRECTORY and
install the package interactively with package-install-file pointing to
the DIRECTORY.

Thank you for your help

       Dieter

[-- Attachment #2: inform-1.4.tar --]
[-- Type: application/x-tar, Size: 61440 bytes --]

[-- Attachment #3: Type: text/plain, Size: 56 bytes --]


-- 
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany

  reply	other threads:[~2020-11-24 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 20:59 bug#39609: 26.3; Packaging system: Package documentation in the *Help* buffer H. Dieter Wilhelm
2020-10-27 17:59 ` Lars Ingebrigtsen
2020-11-24 21:19   ` H. Dieter Wilhelm [this message]
2020-11-25  7:04     ` Lars Ingebrigtsen
     [not found]       ` <86h7pcknk9.fsf@duenenhof-wilhelm.de>
2020-11-27  8:50         ` Lars Ingebrigtsen
2021-01-11 16:02           ` Lars Ingebrigtsen

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=86tutelagn.fsf@duenenhof-wilhelm.de \
    --to=dieter@duenenhof-wilhelm.de \
    --cc=39609@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).