From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Running external info within Emacs
Date: Thu, 30 Mar 2023 18:56:49 +0300 [thread overview]
Message-ID: <83ilei44hq.fsf@gnu.org> (raw)
In-Reply-To: <86wn2y5lo6.fsf@gnu.org> (message from Arash Esbati on Thu, 30 Mar 2023 17:00:25 +0200)
> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Thu, 30 Mar 2023 17:00:25 +0200
>
> 'echo $INFOPATH' in a MinGW64 shell returns (line-breaks added manually)
>
> /mingw64/local/info:
> /mingw64/share/info:
> /usr/local/info:
> /usr/share/info:
> /usr/info:/share/info:
> /c/texlive/2023/texmf-dist/doc/info
>
> (getenv "INFOPATH") in Emacs returns:
>
> "C:\\msys64\\mingw64\\local\\info;
> C:\\msys64\\mingw64\\share\\info;
> C:\\msys64\\usr\\local\\info;
> C:\\msys64\\usr\\share\\info;
> C:\\msys64\\usr\\info;
> C:\\msys64\\share\\info;
> C:\\texlive\\2023\\texmf-dist\\doc\\info"
>
> > What is the file name of the latex2e Info file,
>
> latex2e.info
>
> > and does it have a menu entry in the DIR file in any of the
> > directories mentioned in INFOPATH?
>
> Yes, the dir file starts like this:
>
> This is the file .../info/dir, which contains the
> topmost node of the Info hierarchy, called (dir)Top.
> The first time you invoke Info you start off looking at this node.
> \x1f
> File: dir, Node: Top This is the top of the INFO tree
>
> This (the Directory node) gives a menu of major topics.
> Typing "q" exits, "?" lists all Info commands, "d" returns here,
> "h" gives a primer for first-timers,
> "mEmacs<Return>" visits the Emacs manual, etc.
>
> In Emacs, you can click mouse button 2 on a menu item or cross reference
> to select it.
>
> * Menu:
>
> Science
> * Asymptote: (asymptote). Vector graphics language.
> * Asymptote FAQ: (asy-faq). FAQ for Asymptote.
>
> TeX
> * Dvipng: (dvipng). DVI to Portable Network Graphics (PNG).
> * Dvips: (dvips). Translating TeX DVI files to PostScript.
> * Eplain: (eplain). Expanding on plain TeX.
> * EpsPDF: (epspdf). Portable GUI&cmdline EPS/PS/PDF conversion.
> * Kpathsea: (kpathsea). File lookup along search paths.
> * LaTeX2e: (latex2e). LaTeX2e unofficial reference manual.
> [...]
Then this is either a bug in MSYS2 stand-alone Info reader, or
something else is at work here that we don't see.
What happens if you copy latex2e.info to C:\msys64\mingw64\share\info?
next prev parent reply other threads:[~2023-03-30 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:56 Running external info within Emacs Arash Esbati
2023-03-30 13:17 ` Eli Zaretskii
2023-03-30 15:00 ` Arash Esbati
2023-03-30 15:56 ` Eli Zaretskii [this message]
2023-03-31 6:43 ` Arash Esbati
2023-03-31 7:10 ` Eli Zaretskii
2023-03-31 18:09 ` Arash Esbati
2023-03-31 19:07 ` Eli Zaretskii
2023-04-01 10:51 ` Arash Esbati
2023-04-01 11:37 ` Eli Zaretskii
2023-04-01 14:45 ` Arash Esbati
2023-04-01 15:34 ` Eli Zaretskii
2023-04-02 17:04 ` Arash Esbati
2023-04-02 17:14 ` 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
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=83ilei44hq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash@gnu.org \
--cc=emacs-devel@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 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).