all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Glenn Morris <rgm@gnu.org>
Cc: 10814@debbugs.gnu.org
Subject: bug#10814: commentaries reached via finder-list-keywords do not have links
Date: Fri, 22 Oct 2021 20:33:28 -0700	[thread overview]
Message-ID: <CADwFkmk8tRv81fZNW1iUSGpTY2__g3aFx_eh8Yh8O2k8MNLuCg@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmkbgAskN79v0kOE7RS1+GNxekFqP8LT6JO5jqCGbJzu-Q@mail.gmail.com> (Stefan Kangas's message of "Wed, 21 Aug 2019 00:29:10 +0200")

close 10814 29.1
thanks

Stefan Kangas <stefan@marxist.se> writes:

> Glenn Morris <rgm@gnu.org> writes:
>
>> Package: emacs
>> Version: 24.0.93
>> Severity: wishlist
>>
>> Current trunk:
>>
>> emacs -Q -f finder-commentary
>> calendar RET
>>
>> In the *Finder-package* buffer, `appt.el' etc are links that can be
>> clicked to view the named file's commentary.
>>
>> But if you do instead:
>> emacs -Q -f finder-list-keywords
>> select calendar category
>> select calendar package
>>
>> then in the *Help* buffer that appears, the same commentary is shown but
>> there are no links.
>
> This seems to be because there are two similar functions,
> finder-commentary and describe-package to generate this text.

I have now fixed the above issue on master (commit 241574375d).  You
will now see the links using the above recipe.

> Perhaps these two functions should somehow be merged?

I did not do this part, but I added a FIXME.  Hopefully someone will
pick it up at some point.





      reply	other threads:[~2021-10-23  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15  7:54 bug#10814: commentaries reached via finder-list-keywords do not have links Glenn Morris
2019-08-20 22:29 ` Stefan Kangas
2021-10-23  3:33   ` Stefan Kangas [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADwFkmk8tRv81fZNW1iUSGpTY2__g3aFx_eh8Yh8O2k8MNLuCg@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=10814@debbugs.gnu.org \
    --cc=rgm@gnu.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 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.