Re: Integration of Info manuals in programming modes, Re: Integration of Info manuals in programming modes

[Eli Zaretskii]

> From: James Thomas <jimjoe@gmx.net>
> Date: Sun, 08 Dec 2024 13:43:58 +0530
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> One thing where Info is on-topic here are Emacs integrations.
> >>
> >> I remember how useful it was when I had texinfo links directly
> >> available in Emacs:
> >> https://www.draketo.de/light/english/free-software/read-your-python-module-documentation-emacs
> >
> > Sorry, I don't understand: info-look.el already supports "C-h S" for
> > Python code, assuming you have a Python manual in Info format
> > installed.
> 
> Just wanna chime in that this is not perfect, for other reasons: For
> e.g. 'C-h S' on 'print' does not give the index item "* built-in
> function; print" because, as you can see, it's not named appropriately
> in Sphinx's generation.

Please report that to whoever maintains the Python manual or Sphinx.
info-look.el can fix many problems in the manuals, but not all of
them.

That said, if the "built-in function" part is a general pattern, we
could change the regexps in info-look.el to use that to our advantage;
patches welcome.

> > What other GNU programming packages which have Info manuals and
> > suitable Emacs major modes are not supported by info-look.el?
> 
> Speaking about python, many libraries (such as PyTorch & NumPy) use
> Sphinx, but the info generation has bug when it uses 'numpydoc' that
> requires a little manual fixing of the .texi.

Yes, Sphinx is in many cases a bad idea, but what does this have to do
with the issue at hand here?