all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: mekeor@posteo.de, 67615@debbugs.gnu.org
Subject: bug#67615: [PATCH v2] * lisp/info.el (Info-url-for-node): Support all Emacs info manuals.
Date: Thu, 07 Dec 2023 09:19:42 +0200	[thread overview]
Message-ID: <83il5a32ep.fsf@gnu.org> (raw)
In-Reply-To: <E1rB4RY-0005nQ-4l@fencepost.gnu.org> (message from Richard Stallman on Wed, 06 Dec 2023 21:48:52 -0500)

> Cc: 67615@debbugs.gnu.org
> From: Richard Stallman <rms@gnu.org>
> Date: Wed, 06 Dec 2023 21:48:52 -0500
> 
>   > - Remove "gawk" and "mairix" manual-names from default value of
>   >   Info-urls since they response with HTTP status "not found".
> 
> What is the intended meaning of Info-urls?  What is the criterion for
> what to include, and what is the reason for choosing that criterion?
> 
> I ask becaise Gawk is a GNU package.  It is reasonable, as a matter of
> general principle, for Emacs to refer people to GAWK and its
> documentation.

We decided first to support manuals that come with Emacs, and Gawk's
manual doesn't.

Supporting all GNU manuals is a much larger job, since there's no
single base URL from which they all can be reached (although many of
them can be reached from the GNU site).  Also, the arrangement of the
manuals of the other packages is slightly different from that of
Emacs, which needs more specialized processing.

So I think for now it should be enough to have only the Emacs manuals
by default, and let users add more associations for other packages if
they like.





  reply	other threads:[~2023-12-07  7:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04  0:04 bug#67615: [PATCH] * lisp/info.el (Info-url-for-node): Support all Emacs info manuals Mekeor Melire
2023-12-04  0:30 ` Mekeor Melire
2023-12-04 10:02   ` bug#67615: [PATCH v2] " Mekeor Melire
2023-12-04 15:51     ` Mekeor Melire
2023-12-04 16:24       ` Eli Zaretskii
2023-12-05  1:06         ` bug#67615: Org-Mode story on how I gathered the list of Emacs-contained online-manuals Mekeor Melire
2023-12-07  2:48       ` bug#67615: [PATCH v2] * lisp/info.el (Info-url-for-node): Support all Emacs info manuals Richard Stallman
2023-12-07  7:19         ` Eli Zaretskii [this message]
2023-12-07 11:56           ` Mekeor Melire
2023-12-07 17:02             ` Eli Zaretskii
2023-12-09  4:05               ` Richard Stallman
2023-12-08  0:15       ` bug#67615: [PATCH v3] * lisp/info.el (Info-url-alist): New option mapping manuals to URLs Mekeor Melire
2023-12-09  9:42         ` Eli Zaretskii
2023-12-09 11:21           ` Mekeor Melire
2023-12-19 23:08             ` bug#67615: [PATCH v4] " Mekeor Melire
2023-12-23 10:05               ` Eli Zaretskii
2024-01-08 21:56                 ` bug#67615: [PATCH v5] " Mekeor Melire
2024-01-13  9:51                   ` Eli Zaretskii
2024-01-20  0:50                     ` bug#67615: [PATCH v6] Add option Info-url-alist Mekeor Melire
2024-01-20  1:41                       ` Orhan Kemal Yüksel
2024-01-20  7:23                       ` Eli Zaretskii
2024-01-21  1:43                         ` bug#67615: [PATCH v7] " Mekeor Melire
2024-01-27 10:21                           ` Eli Zaretskii

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=83il5a32ep.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67615@debbugs.gnu.org \
    --cc=mekeor@posteo.de \
    --cc=rms@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.