[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Running external info within Emacs

From: Arash Esbati
Subject: Re: Running external info within Emacs
Date: Sat, 01 Apr 2023 16:45:07 +0200
User-agent: Gnus/5.13 (Gnus v5.13)

Eli Zaretskii <eliz@gnu.org> writes:

> 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?

That's the question.  Until now, I thought that the Msys2 conversion
magic applies to all sort of paths, not only what one has in $PATH.

> IOW, I'd take this up with MSYS2 folks.

Yes, I will ask there.

> 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?

I only added 2 directories for TeXlive and Emacs, the others are
predefined by Msys2 itself.

> Btw, any reason why you use the MSYS port of Info?

Convenience, and until now, I had no problems with MSYS ports.

> 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.)

Using your port will be complicated, I think.  Your tarball contains
libiconv-2.dll and libintl-8.dll which are both part of MinGW64 as well
under /ming64/bin.  Not tested, but that I'm afraid that will trouble in
$PATH in terms of who comes first.

Again, many thanks for your time.

Best, Arash

reply via email to

[Prev in Thread] Current Thread [Next in Thread]