From: Eli Zaretskii <eliz@gnu.org>
To: awrhygty@outlook.com
Cc: 69795@debbugs.gnu.org
Subject: bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
Date: Thu, 14 Mar 2024 13:25:37 +0200 [thread overview]
Message-ID: <86h6h99hse.fsf@gnu.org> (raw)
In-Reply-To: <TYZPR01MB3920BF81730B845A7D43F218C3292@TYZPR01MB3920.apcprd01.prod.exchangelabs.com> (awrhygty@outlook.com)
tags 69795 notabug
thanks
> From: awrhygty@outlook.com
> Date: Thu, 14 Mar 2024 19:55:27 +0900
>
>
> I have installed MSYS2 commands.
> When executing some MSYS2 commands in shell-mode buffer,
> cmdproxy.exe exits unintentionally.
>
> The log below has two prompt strings('c:\tmp>'), but the second one is
> displayed with "Process shell finished" simultaneously.
This is not an Emacs bug. MSYS2 programs are subtly incompatible with
the native Windows build of Emacs, and some of those incompatibilities
are indeed in the area of running subprocesses and capturing their
output. In particular, cmdproxy tries hard to accommodate Cygwin and
MSYS programs, but is rarely used with them, and no one stepped
forward to maintain such a combination and keep in good working order
as Cygwin and MSYS evolve. Another bunch of problems is in the area
of text encoding and decoding: Cygwin and MSYS use UTF-8 by default,
something native Windows doesn't yet support well enough. It is
possible that the problem you show was due to this latter issue, since
'ls' displays a non-ASCII file name there.
If you want to run MSYS or Cygwin programs from Emacs, my suggestion
is to use the Cygwin build of Emacs. There are two configurations for
that: either use the Cygwin X server, or use the w32 "toolkit"; the
latter possibility has the look-and-feel very similar to the native
Windows build, so maybe you will prefer it.
Other than that, running MSYS programs from a native build of Emacs
should be considered "not really supported".
next prev parent reply other threads:[~2024-03-14 11:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 10:55 bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands awrhygty
2024-03-14 11:25 ` Eli Zaretskii [this message]
2024-03-14 15:56 ` awrhygty
2024-03-14 16:48 ` Eli Zaretskii
2024-03-15 12:10 ` awrhygty
2024-03-15 12:49 ` Eli Zaretskii
2024-03-16 3:52 ` awrhygty
2024-03-16 8:21 ` Eli Zaretskii
2024-03-16 13:14 ` awrhygty
2024-03-16 17:34 ` Eli Zaretskii
2024-03-17 1:06 ` awrhygty
2024-03-17 6:18 ` Eli Zaretskii
2024-03-17 16:12 ` awrhygty
2024-03-17 16:24 ` Eli Zaretskii
2024-03-18 1:24 ` awrhygty
2024-03-18 13:05 ` Eli Zaretskii
2024-03-18 22:54 ` awrhygty
2024-03-19 12:32 ` Eli Zaretskii
2024-03-19 13:21 ` awrhygty
2024-03-19 13:49 ` Eli Zaretskii
2024-03-19 14:26 ` awrhygty
2024-03-19 15:50 ` 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=86h6h99hse.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69795@debbugs.gnu.org \
--cc=awrhygty@outlook.com \
/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.