Re: msys2 build path problems + copy-paste english results in chinese characters

[Eli Zaretskii <eliz@gnu.org>]

> From: Arthur Miller <arthur.miller@live.com>
> Cc: emacs-devel@gnu.org
> Date: Wed, 01 Dec 2021 23:39:23 +0100
> 
> > So M-w followed by C-y works.  What doesn't work?
> I pasted it with the middle mouse button; so now when you asked, I should
> probably say oups :-). It was many months of X11 and very few sessions in win32
> environment.

I don't think I understand the "oups" part: does it mean you figured
out what caused the problem?

> >> >> Also, as seen exec-path is wrong. I started, as recommended, via windows means (shortcuts) instead of
> >> >> msys/mingw prompts.
> >> >
> >> > Wrong how?  I don't see anything about exec-path in the image you
> >> > posted.
> >> 
> >> Look at warning from the native-comp in window below; it can not find assemblern
> >> (gnu as). When looking at exec-path I see no paths from mingw present anywhere,
> >> but I did found "." in the path, which I haven't put there myself.
> >
> > The "." part is added by the MSYS2 Bash.  but I still don't understand
> > why it gets in the way.  Does the directory where you have gas.exe
> It is not considered very safe to have it in the path, so I am very suspicisious
> to that.

MSYS2 does it for good reasons.  Since you invoked Emacs from the
MSYS2 Bash, something that is generally not recommended, you inherit
that, and have to deal with it.

> >                          Does the directory where you have gas.exe
> > appear on the system-wide PATH?
> 
> Nope; I haven't manually added any of msys paths to the system, I thought the
> build would add some default paths to msys dirs.

That's your problem: this is why Emacs started from Bash doesn't find
the assembler.  The assembler (and GCC/Binutils in general) are not
MSYS2 programs, they are native Windows programs.  Their directories
should be on PATH, so that you could invoke them from anywhere on your
system, not just from MSYS2 Bash command line.