unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: stefan@marxist.se, 39215@debbugs.gnu.org
Subject: bug#39215: Hyperlinks to man pages in doc strings
Date: Wed, 22 Jan 2020 17:45:04 +0200	[thread overview]
Message-ID: <83ftg7v6kf.fsf@gnu.org> (raw)
In-Reply-To: <iz4kwogmtm.fsf@fencepost.gnu.org> (message from Glenn Morris on Tue, 21 Jan 2020 23:03:01 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Cc: Stefan Kangas <stefan@marxist.se>,  39215@debbugs.gnu.org
> Date: Tue, 21 Jan 2020 23:03:01 -0500
> 
> Eli Zaretskii wrote:
> 
> > Maybe we should teach info.el to display man pages.  The stand-alone
> > Info reader that is part of the Texinfo package does that since time
> > immemoriam.
> 
> (This seems unrelated to the, IMO totally reasonable, feature request.)

My reasoning was that if info.el could do that, then a hyperlink like
`(find)' would "just work", without a need to invent yet another magic
sequence of characters.





  reply	other threads:[~2020-01-22 15:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21  8:55 bug#39215: Hyperlinks to man pages in doc strings Stefan Kangas
2020-01-21 15:36 ` Eli Zaretskii
2020-01-21 16:32   ` Stefan Kangas
2020-01-21 16:56     ` Eli Zaretskii
2020-01-22  4:03       ` Glenn Morris
2020-01-22 15:45         ` Eli Zaretskii [this message]
2020-01-23  1:39       ` Richard Stallman
2020-01-23  3:14         ` Stefan Kangas
2020-01-24  2:58           ` Richard Stallman
2021-09-25  1:07             ` Stefan Kangas
2021-09-25  1:13               ` Lars Ingebrigtsen
2021-09-25  2:10                 ` Stefan Kangas
2021-09-25  1:32               ` Phil Sainty
2021-09-25  2:10                 ` Stefan Kangas

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=83ftg7v6kf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39215@debbugs.gnu.org \
    --cc=rgm@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).