From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: seb@k-7.ch, Stefan Kangas <stefan@marxist.se>,
Noam Postavsky <npostavs@gmail.com>,
31405@debbugs.gnu.org
Subject: bug#31405: 25.3; Python.el doesn't provide infos to info-lookup-symbol
Date: Thu, 12 Aug 2021 16:42:44 +0100 [thread overview]
Message-ID: <87lf56vfd7.fsf@tcd.ie> (raw)
In-Reply-To: <87o8a2hend.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 12 Aug 2021 17:21:58 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> "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, but I haven't
> actually tested.
Thanks, I just tweaked it there and it works OOTB for me.
> And perhaps it should ... look even more for newer
> versions,
And older versions - an update to Debian Stable is imminent, but for now
it still ships Python 3.7 (I run Debian Testing).
> but I don't know quite how -- just loop over a bunch of
> version numbers?
Ideally the info/info-look machinery would match a regexp, no? Perhaps
that's already supported, but I'm unfamiliar with those libraries.
Thanks,
--
Basil
next prev parent reply other threads:[~2021-08-12 15:42 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 [this message]
2021-08-28 9:56 ` Augusto Stoffel
2021-08-28 10:05 ` Eli Zaretskii
2021-08-12 16:06 ` Eli Zaretskii
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=87lf56vfd7.fsf@tcd.ie \
--to=bug-gnu-emacs@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).