From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: contovob@tcd.ie, stefan@marxist.se, npostavs@gmail.com,
31405@debbugs.gnu.org, seb@k-7.ch
Subject: bug#31405: 25.3; Python.el doesn't provide infos to info-lookup-symbol
Date: Thu, 12 Aug 2021 19:06:03 +0300 [thread overview]
Message-ID: <83im0ad4wk.fsf@gnu.org> (raw)
In-Reply-To: <87o8a2hend.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 12 Aug 2021 17:21:58 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 12 Aug 2021 17:21:58 +0200
> Cc: 31405@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>,
> Noam Postavsky <npostavs@gmail.com>, seb@k-7.ch
>
> "Basil L. Contovounesios" <contovob@tcd.ie> writes:
>
> > In my case I have to override it as
> >
> > (with-eval-after-load 'info-look
> > (info-lookup-add-help
> > :mode 'python-mode
> > :doc-spec '(("(python3.9)Index"))))
> >
> > to match the name and version of the manual installed by Debian.
>
> I've now adjusted the code to look for the 3.9 manual
If Debian is including the version in the file name, and we want to
support that, I think we should have a defcustom for users to control
which version they want Emacs to look for. Or maybe we should allow a
list of file names there, and then we could mention all the known
names for reasonably recent versions of Python.
Again, the Info system is not designed to support that. For example,
hyperlinks from other manuals won't work reliably, and you'd have
trouble with the system-wide DIR file, if you ever dare updating it
outside of Debian's control.
next prev parent reply other threads:[~2021-08-12 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 15:24 bug#31405: 25.3; Python.el doesn't provide infos to info-lookup-symbol Sébastien Gendre
2019-05-07 17:36 ` npostavs
2019-08-23 7:04 ` Stefan Kangas
2021-08-12 14:13 ` Lars Ingebrigtsen
2021-08-12 15:13 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-12 15:21 ` Lars Ingebrigtsen
2021-08-12 15:42 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-28 9:56 ` Augusto Stoffel
2021-08-28 10:05 ` Eli Zaretskii
2021-08-12 16:06 ` Eli Zaretskii [this message]
2021-08-12 16:02 ` Eli Zaretskii
2021-08-13 11:34 ` Lars Ingebrigtsen
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=83im0ad4wk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31405@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
--cc=seb@k-7.ch \
--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).