unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58049@debbugs.gnu.org
Subject: bug#58049: 29.0.50; Obsolete url schemes "info" and "man"
Date: Sun, 25 Sep 2022 16:01:20 +0200	[thread overview]
Message-ID: <87edvz1rkf.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkm=j0Nqd7svdTuuOK1Wjy0O6Oas076SSyrnRoXgLLGQsMQ@mail.gmail.com> (Stefan Kangas's message of "Sat, 24 Sep 2022 19:05:13 -0400")

On Sat, 24 Sep 2022 at 19:05, Stefan Kangas wrote:

> Severity: wishlist
>
> I don't think non-standard URLs like these are used much, and they're
> probably not very useful.  They're more likely to cause confusion.
>
>     (url-retrieve-synchronously "info:url#Retrieving URLs")
>     (url-retrieve-synchronously "man:cat")

I can imagine many uses for this.  For instance, a completion table
could provide some kind of "further info" property so you can preview
the documentation of an item mid-completion.  Also, and eldoc source
could provide a "further info" hyperlink pointing to the info or man
page.  (This is mostly speculation, of course.)

If I were to retire something, it would be the (file)node syntax for
info pages.

(My digestif TeX language server provides links to the documentation of
various packages, typically PDF files.  It checks if the PDF exists
locally and gives a file:// link, otherwise a https:// link to CTAN.
But it would be much better to just provide a “texinfo:” link and let
the editor decide how to display that.  Of course I don't do this
because no editor would support it OOTB, but I think the concept makes
sense.)





  parent reply	other threads:[~2022-09-25 14:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 23:05 bug#58049: 29.0.50; Obsolete url schemes "info" and "man" Stefan Kangas
2022-09-25  4:57 ` Eli Zaretskii
2022-09-25 11:52 ` Jean Louis
2022-09-25 14:01 ` Augusto Stoffel [this message]
2022-09-25 14:06   ` Augusto Stoffel
2022-09-25 14:30   ` Lars Ingebrigtsen
2022-09-25 14:41     ` Eli Zaretskii
2022-09-25 14:46       ` Lars Ingebrigtsen
2022-09-25 15:09     ` Stefan Kangas
2022-09-26 10:51       ` Lars Ingebrigtsen
2022-09-26 11:15         ` Stefan Kangas
2022-09-27  6:00     ` Jean Louis
2022-09-27 18:02       ` Stefan Kangas
2022-09-27 20:23         ` Jean Louis

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=87edvz1rkf.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=58049@debbugs.gnu.org \
    --cc=stefankangas@gmail.com \
    /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).