Re: info '(latex2e)\indent & \noindent' doesn't work with Msys2

[Eli Zaretskii]

> From: Arash Esbati <arash@gnu.org>
> Cc: GavinSmith0123@gmail.com,  bug-texinfo@gnu.org
> Date: Tue, 04 Apr 2023 15:05:01 +0200
> 
> >>   C:\>chcp
> >>   Aktive Codepage: 850.
> >
> > That's likely the problem: this codepage doesn't support Unicode
> > quotes.  What remains to be understood is why doesn't info.exe act
> > accordingly.
> 
> Yes, this seems to be the issue.  In my bash (MinGW64 shell running
> inside Windows Terminal), I did:
> 
>   $ chcp.com 1252
>   $ /c/pathto/my/native/info.exe dir-test-no-coding
> 
> which looks like this:

Which info.exe is that? the one you've built or the one from MSYS2?

> > Is your info.exe built with libiconv, btw?
> 
> I only pass a --prefix to configure and looking at config.log, it has:
> 
>   configure:11566: checking how to link with libiconv
>   configure:11568: result: -liconv
>   configure:11579: checking whether iconv is compatible with its POSIX 
> signature
>   configure:11604: gcc -c -g -O2  conftest.c >&5
>   configure:11604: $? = 0
>   configure:11613: result: yes
> 
> So I'd say yes.

Looks like that.  But here's how to be sure: from the shell prompt
type

  objdump -p /path/to/info.exe | fgrep "DLL Name:"

and you will see all the DLLs that the program was linked against.

> > "In bash" when using what console window?  (Please always state these
> > facts, because otherwise what you tell is ambiguous and can easily
> > mislead.  This issue is complicated and messy enough already, we don't
> > need more complications and confusions.)
> 
> Sure, sorry for being imprecise.  My setup is all the time bash in a
> MinGW64 shell using Windows Terminal.  I start bash like this:
> 
>   c:/msys64/msys2_shell.cmd -defterm -no-start -mingw64
> 
> where -defterm means don't use mintty.

OK.  But as long as we are debugging this problem with ‘dir’ being
displayed as `dirï, please run the info.exe you've built only in the
Command Prompt window and from the cmd.exe prompt, not in mintty and
not from Bash.  If we need to see how info.exe behaves in other
situations, we will mention this explicitly.  OK?