From: "Sébastien Gendre" <seb@k-7.ch>
To: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Multiple version of Info manual
Date: Sat, 30 Nov 2024 19:13:49 +0100 [thread overview]
Message-ID: <87a5dga8te.fsf@k-7.ch> (raw)
In-Reply-To: <86ed2t9ia4.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Nov 2024 11:34:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Thank you for your reply.
I have added my reply/remark bellow.
Eli Zaretskii <eliz@gnu.org> writes:
> FWIW, the Python manual in Info format can be found on the Internet
> and downloaded. You don't need to produce it by yourself.
An official version ?
> You will need to make sure each version's manual has a distinct name.
> For example, the manual for Python v3.9 could be called
> python-3.9.info, while the manual for Python v3.13 could be called
> python-3.13.info.
Including the version in the info name is a good idea. But I will need
to write a function to switch the version of Python documentation used
with `C-h S`.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
prev parent reply other threads:[~2024-11-30 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 9:08 Multiple version of Info manual Sébastien Gendre
2024-11-30 9:34 ` Eli Zaretskii
2024-11-30 18:13 ` Sébastien Gendre [this message]
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=87a5dga8te.fsf@k-7.ch \
--to=seb@k-7.ch \
--cc=eliz@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.
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).