all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Running external info within Emacs
Date: Sat, 01 Apr 2023 16:45:07 +0200	[thread overview]
Message-ID: <86y1nbpsp8.fsf@gnu.org> (raw)
In-Reply-To: <83a5zrzvdc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Apr 2023 14:37:19 +0300")

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	other threads:[~2023-04-01 14:45 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
2023-04-01 14:45                   ` Arash Esbati [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86y1nbpsp8.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.