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: Sat, 01 Apr 2023 14:37:19 +0300 [thread overview]
Message-ID: <83a5zrzvdc.fsf@gnu.org> (raw)
In-Reply-To: <86o7o77u5h.fsf@gnu.org> (message from Arash Esbati on Sat, 01 Apr 2023 12:51:06 +0200)
> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 01 Apr 2023 12:51:06 +0200
>
> Now I eval (async-shell-command "info -x 2 latex2e") for debug infos:
>
> info: inaccessible directory C not added to INFOPATH
> info: inaccessible directory \msys64\mingw64\local\info;C not added to INFOPATH
> info: inaccessible directory \msys64\mingw64\share\info;C not added to INFOPATH
> info: inaccessible directory \msys64\usr\local\info;C not added to INFOPATH
> info: inaccessible directory \msys64\usr\share\info;C not added to INFOPATH
> info: inaccessible directory \msys64\usr\info;C not added to INFOPATH
> info: inaccessible directory \msys64\share\info;C not added to INFOPATH
> info: inaccessible directory \texlive\2023\texmf-dist\doc\info;C not added to INFOPATH
> info: inaccessible directory \emacs\share\info not added to INFOPATH
> info: adding /usr/share/info to INFOPATH
> info: found file /usr/share/info/dir
> info: looking for file "latex2e"
> info: looking for file latex2e in /usr/share/info
> info: closing -
> info: No menu item 'latex2e' in node '(dir)Top'
>
> info seems to see the Windows style paths and chokes. If I change
> "INFOPATH" to unix style and run the command like this:
>
> (with-environment-variables (("INFOPATH"
> "\
> /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:\
> /C/emacs/share/info"))
> (async-shell-command "info -x 2 latex2e"))
>
> I get:
>
> info: inaccessible directory /C/msys64/mingw64/local/info not added to INFOPATH
> info: adding /C/msys64/mingw64/share/info to INFOPATH
> info: adding /C/msys64/usr/local/info to INFOPATH
> info: adding /C/msys64/usr/share/info to INFOPATH
> info: inaccessible directory /C/msys64/usr/info not added to INFOPATH
> info: inaccessible directory /C/msys64/share/info not added to INFOPATH
> info: adding /C/texlive/2023/texmf-dist/doc/info to INFOPATH
> info: adding /C/emacs/share/info to INFOPATH
> info: duplicate directory /usr/share/info not added to INFOPATH
> info: found file /C/msys64/usr/share/info/dir
> info: found file /C/texlive/2023/texmf-dist/doc/info/dir
> info: found file /C/emacs/share/info/dir
> info: looking for file "latex2e"
> info: looking for file latex2e in /C/msys64/mingw64/share/info
> info: looking for file latex2e in /C/msys64/usr/local/info
> info: looking for file latex2e in /C/msys64/usr/share/info
> info: looking for file latex2e in /C/texlive/2023/texmf-dist/doc/info
> info: found file /C/texlive/2023/texmf-dist/doc/info/latex2e.info
> info: writing node (latex2e.info)Top...
> info: writing node (latex2e.info)About this document...
> [...]
> File: latex2e.info, Node: Top, Next: About this document, Up: (dir)
>
> and it works. So your first idea about "INFOPATH transformation several
> times" was correct. Is there a fix for this? WDYT?
Isn't this an MSYS2 bug? Shouldn't MSYS2 Bash convert INFOPATH to the
MSYS /c/foo/bar format? Or is that handling reserved only for PATH?
IOW, I'd take this up with MSYS2 folks.
Another alternative is to keep all the Info files in a single
/usr/share/info directory, in which case you will not need to set
INFOPATH at all. Why do you need so many distinct directories with
Info files?
Btw, any reason why you use the MSYS port of Info? A native port is
available, and you could even produce it by yourself if my 32-bit port
doesn't suit you for some reason. (I was wondering for a long time
why the MSYS2/MinGW64 project doesn't provide a native Windows build
of Texinfo, since the upstream project supports such a build since
about forever.)
next prev parent reply other threads:[~2023-04-01 11:37 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
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 [this message]
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=83a5zrzvdc.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).