unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 56420@debbugs.gnu.org
Subject: bug#56420: Link to Info manual from describe-package help
Date: Mon, 11 Jul 2022 11:47:15 +0200	[thread overview]
Message-ID: <87k08k2d7g.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmkL7itnoN5MR=jTWzR7PQZpOnAR517j+4rSDX7aT2wKcQ@mail.gmail.com> (Stefan Kangas's message of "Thu, 7 Jul 2022 14:28:34 -0700")

Stefan Kangas <stefan@marxist.se> writes:

>> If you add it the link, I can add code to recognise it.  😀
>
> Now added (to ert.el)!

You have

Info manual `(ert) Top'

in the doc, but the magical phrase is "info node", according to
`help-xref-info-regexp'.  We could add "manual" as an alternative...

"\\<[Ii]nfo[ \t\n]+\\(node\\|anchor\\)[ \t\n]+['`‘]\\([^'’]+\\)['’]"

But this reminds me -- why are we so strict about the Info links,
anyway?  Could `(foo) Bar' in a doc string be anything but a manual
reference?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-07-11  9:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 10:28 bug#56420: Link to Info manual from describe-package help Stefan Kangas
2022-07-06 11:38 ` Lars Ingebrigtsen
2022-07-06 12:36   ` Stefan Kangas
2022-07-07  7:41     ` Lars Ingebrigtsen
2022-07-07 21:28       ` Stefan Kangas
2022-07-11  9:47         ` Lars Ingebrigtsen [this message]
2022-07-11  9:52           ` Visuwesh
2022-07-11  9:59             ` Robert Pluim
2022-07-11 10:02               ` Visuwesh
2022-07-11 10:28                 ` Robert Pluim

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=87k08k2d7g.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56420@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 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).