unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Augusto Stoffel <arstoffel@gmail.com>,
	Stefan Kangas <stefankangas@gmail.com>,
	58049@debbugs.gnu.org
Subject: bug#58049: 29.0.50; Obsolete url schemes "info" and "man"
Date: Tue, 27 Sep 2022 09:00:02 +0300	[thread overview]
Message-ID: <YzKRYpNAkVIcEQsy@protected.localdomain> (raw)
In-Reply-To: <878rm7bk78.fsf@gnus.org>

* Lars Ingebrigtsen <larsi@gnus.org> [2022-09-25 17:32]:
> Augusto Stoffel <arstoffel@gmail.com> writes:
> 
> > 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.
> 
> Why on Earth would you use URL syntax for something like that?  Just add
> the "further info" property and link that up with a closure from a text
> property or whatever
> 
> I'm all for retiring the info: and man: schemes (since they are 100%
> useless), but don't really see the need to do so piecemeal -- when Emacs
> grows a new URL library that functions better than the current one,
> it'll only support http(s) and file, so all this junk will disappear in
> one fell swoop.

Whatever you wish to remove, maybe I misunderstood it, but please do
not remove functionality from goto-address-mode that I can make any
kinds of links in Emacs buffers:

man:man is link here. I can open it as C-c RET and such links may be
automatically generated in my hyperlinking system, including many
other links.

URL schemes are standard, you do not just delete it because you do not
know how why on Earth would somebody use it.


Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/





  parent reply	other threads:[~2022-09-27  6:00 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
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 [this message]
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=YzKRYpNAkVIcEQsy@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=58049@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=larsi@gnus.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).