* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
@ 2024-03-14 10:55 awrhygty
2024-03-14 11:25 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-14 10:55 UTC (permalink / raw)
To: 69795
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.
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.
c:\tmp>c:\msys64\usr\bin\ls.exe -ld .
c:\msys64\usr\bin\ls.exe -ld .
drwxr-xr-x 1 user なし 0 Mar 14 19:08 .
c:\tmp>
Process shell finished
In GNU Emacs 29.1 (build 2, x86_64-w64-mingw32) of 2023-08-02 built on
AVALON
Windowing system distributor 'Microsoft Corp.', version 10.0.19045
System Description: Microsoft Windows 10 Pro (v10.0.2009.19045.4170)
Configured using:
'configure --with-modules --without-dbus --with-native-compilation=aot
--without-compress-install --with-tree-sitter CFLAGS=-O2'
Configured features:
ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND SQLITE3 THREADS TIFF
TOOLKIT_SCROLL_BARS TREE_SITTER WEBP XPM ZLIB
(NATIVE_COMP present but libgccjit not available)
Important settings:
value of $LANG: JPN
locale-coding-system: cp932
Major mode: Dired by name
Minor modes in effect:
shell-dirtrack-mode: t
tooltip-mode: t
global-eldoc-mode: t
show-paren-mode: t
electric-indent-mode: t
mouse-wheel-mode: t
tool-bar-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
buffer-read-only: t
line-number-mode: t
indent-tabs-mode: t
transient-mark-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
Load-path shadows:
None found.
Features:
(term/bobcat rect pp shadow sort mail-extr emacsbug message mailcap
yank-media puny rfc822 mml mml-sec password-cache epa derived epg
rfc6068 epg-config gnus-util text-property-search mm-decode mm-bodies
mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail
rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils time-date
thingatpt bat-mode misearch multi-isearch sh-script rx smie treesit
cl-seq executable files-x shell subr-x pcomplete comint ansi-osc
ansi-color ring face-remap help-mode dired-aux cl-loaddefs cl-lib dired
dired-loaddefs japan-util rmc iso-transl tooltip cconv eldoc paren
electric uniquify ediff-hook vc-hooks lisp-float-type elisp-mode mwheel
dos-w32 ls-lisp disp-table term/w32-win w32-win w32-vars term/common-win
tool-bar dnd fontset image regexp-opt fringe tabulated-list replace
newcomment text-mode lisp-mode prog-mode register page tab-bar menu-bar
rfn-eshadow isearch easymenu timer select scroll-bar mouse jit-lock
font-lock syntax font-core term/tty-colors frame minibuffer nadvice seq
simple cl-generic indonesian philippine cham georgian utf-8-lang
misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms
cp51932 hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese composite emoji-zwj charscript charprop case-table
epa-hook jka-cmpr-hook help abbrev obarray oclosure cl-preloaded button
loaddefs theme-loaddefs faces cus-face macroexp files window
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget keymap hashtable-print-readable backquote threads
w32notify w32 lcms2 multi-tty make-network-process native-compile emacs)
Memory information:
((conses 16 99379 14842)
(symbols 48 7869 7)
(strings 32 23809 2665)
(string-bytes 1 647604)
(vectors 16 21674)
(vector-slots 8 1171856 159874)
(floats 8 62 53)
(intervals 56 3960 850)
(buffers 984 17))
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
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
2024-03-14 15:56 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-14 11:25 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
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".
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-14 11:25 ` Eli Zaretskii
@ 2024-03-14 15:56 ` awrhygty
2024-03-14 16:48 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-14 15:56 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
Replacing 'ls -ld .' with 'ls -d .', which outputs only '.',
cmdproxy.exe exits, too.
Replacing 'ls -d .' with 'ls -d . < nul' does not make cmdproxy.exe exit.
> 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".
Is calling MSYS2 commands from #'start-process or #'call-process
not recommended?
I only needed gdb, another binary will do. But I do not know where to
get a reliable gdb binary run with emacs shell-mode.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-14 15:56 ` awrhygty
@ 2024-03-14 16:48 ` Eli Zaretskii
2024-03-15 12:10 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-14 16:48 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Fri, 15 Mar 2024 00:56:02 +0900
>
> Replacing 'ls -ld .' with 'ls -d .', which outputs only '.',
> cmdproxy.exe exits, too.
> Replacing 'ls -d .' with 'ls -d . < nul' does not make cmdproxy.exe exit.
If cmdproxy exits, it probably means cmd.exe that cmdproxy runs
exited. The shell-mode buffer interacts with cmd.exe, not with
cmdproxy. cmdproxy in this scenario is used only to start an inferior
cmd.exe.
You may wish looking in the Windows Event Log, under Application. It
is possible that there's some useful information there about why you
see that shell process finishes, like which program crashed and why.
Or maybe this could be the return of this old problem:
https://lists.gnu.org/archive/html/emacs-devel/2023-01/msg00242.html
> > 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".
>
> Is calling MSYS2 commands from #'start-process or #'call-process
> not recommended?
In general, not recommended, due to the compatibility issues I
described. (But cmdproxy is not involved when start-process or
call-process are used, unless the application is a DOS program.)
> I only needed gdb, another binary will do. But I do not know where to
> get a reliable gdb binary run with emacs shell-mode.
Doesn't MSYS2 provide a MinGW64 build of GDB, not just an MSYS build?
GDB builds natively with MinGW tools, so there should be no problem
for MSYS2 folks to provide a native 64-bit Windows build of GDB.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-14 16:48 ` Eli Zaretskii
@ 2024-03-15 12:10 ` awrhygty
2024-03-15 12:49 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-15 12:10 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
>> From: awrhygty@outlook.com
>> Cc: 69795@debbugs.gnu.org
>> Date: Fri, 15 Mar 2024 00:56:02 +0900
>>
>> Replacing 'ls -ld .' with 'ls -d .', which outputs only '.',
>> cmdproxy.exe exits, too.
>> Replacing 'ls -d .' with 'ls -d . < nul' does not make cmdproxy.exe exit.
>
> If cmdproxy exits, it probably means cmd.exe that cmdproxy runs
> exited. The shell-mode buffer interacts with cmd.exe, not with
> cmdproxy. cmdproxy in this scenario is used only to start an inferior
> cmd.exe.
>
> You may wish looking in the Windows Event Log, under Application. It
> is possible that there's some useful information there about why you
> see that shell process finishes, like which program crashed and why.
Nothing about crash or similar is recorded.
>> I only needed gdb, another binary will do. But I do not know where to
>> get a reliable gdb binary run with emacs shell-mode.
>
> Doesn't MSYS2 provide a MinGW64 build of GDB, not just an MSYS build?
> GDB builds natively with MinGW tools, so there should be no problem
> for MSYS2 folks to provide a native 64-bit Windows build of GDB.
I have installed mingw64/mingw-w64-x86_64-gdb.
I think it is MinGW64 binary.
But gdb.exe sometimes make cmdproxy.exe exit, and sometimes not.
Here is a list of gdb packages.
$ pacman -Ss 'gdb$'
mingw32/mingw-w64-i686-arm-none-eabi-gdb 9.2-8 (mingw-w64-i686-arm-none-eabi-toolchain)
GNU Tools for ARM Embedded Processors - GDB (mingw-w64)
mingw32/mingw-w64-i686-avr-gdb 12.1-1 (mingw-w64-i686-avr-toolchain)
The GNU Debugger for AVR (mingw-w64)
mingw32/mingw-w64-i686-gdb 13.2-3 (mingw-w64-i686-toolchain)
GNU Debugger (mingw-w64)
mingw64/mingw-w64-x86_64-arm-none-eabi-gdb 9.2-8 (mingw-w64-x86_64-arm-none-eabi-toolchain)
GNU Tools for ARM Embedded Processors - GDB (mingw-w64)
mingw64/mingw-w64-x86_64-avr-gdb 12.1-1 (mingw-w64-x86_64-avr-toolchain)
The GNU Debugger for AVR (mingw-w64)
mingw64/mingw-w64-x86_64-gdb 13.2-3 (mingw-w64-x86_64-toolchain) [installed]
GNU Debugger (mingw-w64)
ucrt64/mingw-w64-ucrt-x86_64-arm-none-eabi-gdb 9.2-8 (mingw-w64-ucrt-x86_64-arm-none-eabi-toolchain)
GNU Tools for ARM Embedded Processors - GDB (mingw-w64)
ucrt64/mingw-w64-ucrt-x86_64-avr-gdb 12.1-1 (mingw-w64-ucrt-x86_64-avr-toolchain)
The GNU Debugger for AVR (mingw-w64)
ucrt64/mingw-w64-ucrt-x86_64-gdb 13.2-3 (mingw-w64-ucrt-x86_64-toolchain)
GNU Debugger (mingw-w64)
clang32/mingw-w64-clang-i686-arm-none-eabi-gdb 9.2-8 (mingw-w64-clang-i686-arm-none-eabi-toolchain)
GNU Tools for ARM Embedded Processors - GDB (mingw-w64)
clang32/mingw-w64-clang-i686-avr-gdb 12.1-1 (mingw-w64-clang-i686-avr-toolchain)
The GNU Debugger for AVR (mingw-w64)
clang32/mingw-w64-clang-i686-gdb 13.2-3
GNU Debugger (mingw-w64)
clang64/mingw-w64-clang-x86_64-arm-none-eabi-gdb 9.2-8 (mingw-w64-clang-x86_64-arm-none-eabi-toolchain)
GNU Tools for ARM Embedded Processors - GDB (mingw-w64)
clang64/mingw-w64-clang-x86_64-avr-gdb 12.1-1 (mingw-w64-clang-x86_64-avr-toolchain)
The GNU Debugger for AVR (mingw-w64)
clang64/mingw-w64-clang-x86_64-gdb 13.2-3
GNU Debugger (mingw-w64)
msys/cgdb 0.8.0-2
Curses-based interface to the GNU Debugger
msys/gdb 13.2-1
GNU Debugger (MSYS2 version)
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-15 12:10 ` awrhygty
@ 2024-03-15 12:49 ` Eli Zaretskii
2024-03-16 3:52 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-15 12:49 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Fri, 15 Mar 2024 21:10:06 +0900
>
> > Doesn't MSYS2 provide a MinGW64 build of GDB, not just an MSYS build?
> > GDB builds natively with MinGW tools, so there should be no problem
> > for MSYS2 folks to provide a native 64-bit Windows build of GDB.
>
> I have installed mingw64/mingw-w64-x86_64-gdb.
> I think it is MinGW64 binary.
Yes. But then all the discussion around MSYS2 programs is not
relevant to this issue.
> But gdb.exe sometimes make cmdproxy.exe exit, and sometimes not.
So let's start from the beginning: can you show a recipe, starting
from "emacs -Q", where you invoke GDB from Emacs, and cmdproxy (or
some other sub-process) exits?
Also, did you look at this discussion to which I pointed:
https://lists.gnu.org/archive/html/emacs-devel/2023-01/msg00242.html
It's possible that the process-send-eof mentioned there is somehow
involved in what you see.
> Here is a list of gdb packages.
That's a large list. Are you using GDB for debugging native Windows
programs, or are you using it for debugging other executables (like
ARM or AVR) via gdbserver? Which of these packages do you actually
have installed and are using?
> msys/cgdb 0.8.0-2
> Curses-based interface to the GNU Debugger
> msys/gdb 13.2-1
> GNU Debugger (MSYS2 version)
These two are MSYS2 builds, not native MinGW builds.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-15 12:49 ` Eli Zaretskii
@ 2024-03-16 3:52 ` awrhygty
2024-03-16 8:21 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-16 3:52 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
>> From: awrhygty@outlook.com
>> Cc: 69795@debbugs.gnu.org
>> Date: Fri, 15 Mar 2024 21:10:06 +0900
>>
>> > Doesn't MSYS2 provide a MinGW64 build of GDB, not just an MSYS build?
>> > GDB builds natively with MinGW tools, so there should be no problem
>> > for MSYS2 folks to provide a native 64-bit Windows build of GDB.
>>
>> I have installed mingw64/mingw-w64-x86_64-gdb.
>> I think it is MinGW64 binary.
>
> Yes. But then all the discussion around MSYS2 programs is not
> relevant to this issue.
>
>> But gdb.exe sometimes make cmdproxy.exe exit, and sometimes not.
>
> So let's start from the beginning: can you show a recipe, starting
> from "emacs -Q", where you invoke GDB from Emacs, and cmdproxy (or
> some other sub-process) exits?
I found that setting PATH make the difference.
Start emacs -Q, type 'M-x shell RET',
and input following command lines.
set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
c:\msys64\mingw64\bin\gdb.exe
q
Then cmdproxy.exe exits automatically.
Here is a log.
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.
c:\tmp>set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
c:\tmp>c:\msys64\mingw64\bin\gdb.exe
c:\msys64\mingw64\bin\gdb.exe
GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) q
c:\tmp>
Process shell finished
> Also, did you look at this discussion to which I pointed:
>
> https://lists.gnu.org/archive/html/emacs-devel/2023-01/msg00242.html
>
> It's possible that the process-send-eof mentioned there is somehow
> involved in what you see.
Redefining #'comint-simple-send to remove #'process-send-eof,
cmdproxy.exe behaves same, exits automatically.
(defun comint-simple-send (proc string)
"Default function for sending to PROC input STRING.
This just sends STRING plus a newline. To override this,
set the hook `comint-input-sender'."
(let ((send-string
(if comint-input-sender-no-newline
string
;; Sending as two separate strings does not work
;; on Windows, so concat the \n before sending.
(concat string "\n"))))
(comint-send-string proc send-string)))
>> Here is a list of gdb packages.
>
> That's a large list. Are you using GDB for debugging native Windows
> programs, or are you using it for debugging other executables (like
> ARM or AVR) via gdbserver? Which of these packages do you actually
> have installed and are using?
They are available package names.
I have installed only one of them, which is marked as [installed].
I am not sure which is best.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-16 3:52 ` awrhygty
@ 2024-03-16 8:21 ` Eli Zaretskii
2024-03-16 13:14 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-16 8:21 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Sat, 16 Mar 2024 12:52:19 +0900
>
> > So let's start from the beginning: can you show a recipe, starting
> > from "emacs -Q", where you invoke GDB from Emacs, and cmdproxy (or
> > some other sub-process) exits?
>
> I found that setting PATH make the difference.
> Start emacs -Q, type 'M-x shell RET',
> and input following command lines.
> set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
> c:\msys64\mingw64\bin\gdb.exe
> q
> Then cmdproxy.exe exits automatically.
Please show the value of PATH after "set PATH" above. Like this:
c:\tmp>set PATH
(I have a very different MinGW directory tree here, but I tried to do
something equivalent to what you do above, and couldn't reproduce it:
I get placed at the cmd.exe prompt, as expected.)
And once again: it is not cmdproxy that exits, it's cmd.exe. cmdproxy
will not exit until the process it started, in this case cmd.exe,
exits.
Btw, why do you end each element of PATH with a backslash '\' ? This
is not required. (I don't think it's part of your problem, but
still.)
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-16 8:21 ` Eli Zaretskii
@ 2024-03-16 13:14 ` awrhygty
2024-03-16 17:34 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-16 13:14 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
>> From: awrhygty@outlook.com
>> Cc: 69795@debbugs.gnu.org
>> Date: Sat, 16 Mar 2024 12:52:19 +0900
>>
>> > So let's start from the beginning: can you show a recipe, starting
>> > from "emacs -Q", where you invoke GDB from Emacs, and cmdproxy (or
>> > some other sub-process) exits?
>>
>> I found that setting PATH make the difference.
>> Start emacs -Q, type 'M-x shell RET',
>> and input following command lines.
>> set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
>> c:\msys64\mingw64\bin\gdb.exe
>> q
>> Then cmdproxy.exe exits automatically.
>
> Please show the value of PATH after "set PATH" above. Like this:
>
> c:\tmp>set PATH
Before setting PATH, the value is:
C:\ImageMagick;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\user\AppData\Local\Programs\Python\Python310\Scripts\;C:\Users\user\AppData\Local\Programs\Python\Python310\;C:\Users\user\AppData\Local\Microsoft\WindowsApps;
Then removing directories other than C:\WINDOWS or descendants:
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
Here is a log with the PATH value above.
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.
c:\tmp>set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
c:\tmp>set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
c:\tmp>set PATH
set PATH
PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
c:\tmp>c:\msys64\mingw64\bin\gdb.exe
c:\msys64\mingw64\bin\gdb.exe
GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) q
c:\tmp>
Process shell finished
> (I have a very different MinGW directory tree here, but I tried to do
> something equivalent to what you do above, and couldn't reproduce it:
> I get placed at the cmd.exe prompt, as expected.)
>
> And once again: it is not cmdproxy that exits, it's cmd.exe. cmdproxy
> will not exit until the process it started, in this case cmd.exe,
> exits.
>
> Btw, why do you end each element of PATH with a backslash '\' ? This
> is not required. (I don't think it's part of your problem, but
> still.)
I often use 'C-x C-f' to input a pathname, and 'C-w'(copy) 'C-g'(quit)
in minibuffer. '/' at the last of directory names are automatically
added by completion. Then I replaced '/' with '\'. I have forgotten
that the last '\' is not required (and not inhibited).
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-16 13:14 ` awrhygty
@ 2024-03-16 17:34 ` Eli Zaretskii
2024-03-17 1:06 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-16 17:34 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Sat, 16 Mar 2024 22:14:49 +0900
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >
> > Please show the value of PATH after "set PATH" above. Like this:
> >
> > c:\tmp>set PATH
>
> Before setting PATH, the value is:
> C:\ImageMagick;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\user\AppData\Local\Programs\Python\Python310\Scripts\;C:\Users\user\AppData\Local\Programs\Python\Python310\;C:\Users\user\AppData\Local\Microsoft\WindowsApps;
> Then removing directories other than C:\WINDOWS or descendants:
> C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
I don't understand what you mean by "removing directories other than
C:\WINDOWS or descendants". Why do they need to be removed? And how
did you remove them?
> Here is a log with the PATH value above.
>
> Microsoft Windows [Version 10.0.19045.4170]
> (c) Microsoft Corporation. All rights reserved.
>
> c:\tmp>set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
> set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
Why are you changing the system PATH?
> c:\tmp>set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
> set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
>
> c:\tmp>set PATH
> set PATH
> PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
> PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
>
> c:\tmp>c:\msys64\mingw64\bin\gdb.exe
> c:\msys64\mingw64\bin\gdb.exe
> GNU gdb (GDB) 13.2
> Copyright (C) 2023 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-w64-mingw32".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word".
> (gdb) q
>
> c:\tmp>
> Process shell finished
What happens if you change PATH to include the two addition
directories, c:\msys64\mingw64\bin\ and c:\msys64\usr\bin, before you
start Emacs, and then run GDB from the shell buffer without changing
PATH inside the shell buffer?
Please also show the contents of these two directories you add to
PATH. Maybe the reason for this is something in those directories.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-16 17:34 ` Eli Zaretskii
@ 2024-03-17 1:06 ` awrhygty
2024-03-17 6:18 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-17 1:06 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
>> From: awrhygty@outlook.com
>> Cc: 69795@debbugs.gnu.org
>> Date: Sat, 16 Mar 2024 22:14:49 +0900
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >
>> > Please show the value of PATH after "set PATH" above. Like this:
>> >
>> > c:\tmp>set PATH
>>
>> Before setting PATH, the value is:
>> C:\ImageMagick;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\user\AppData\Local\Programs\Python\Python310\Scripts\;C:\Users\user\AppData\Local\Programs\Python\Python310\;C:\Users\user\AppData\Local\Microsoft\WindowsApps;
>> Then removing directories other than C:\WINDOWS or descendants:
>> C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
>
> I don't understand what you mean by "removing directories other than
> C:\WINDOWS or descendants". Why do they need to be removed? And how
> did you remove them?
I removed obviously unrelated pathnames, which are for imagemagick and
python. They are not supplied by OS. And I removed them by hand.
> What happens if you change PATH to include the two addition
> directories, c:\msys64\mingw64\bin\ and c:\msys64\usr\bin, before you
> start Emacs, and then run GDB from the shell buffer without changing
> PATH inside the shell buffer?
Input following command lines on cmd.exe.
set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
c:\Emacs\emacs-29.1\bin\emacs-29.1.exe -Q
And run gdb in shell-mode, then process automatically finished.
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.
c:\tmp>set PATH
set PATH
PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;C:\ImageMagick;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\user\AppData\Local\Programs\Python\Python310\Scripts\;C:\Users\user\AppData\Local\Programs\Python\Python310\;C:\Users\user\AppData\Local\Microsoft\WindowsApps;
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
c:\tmp>c:\msys64\mingw64\bin\gdb.exe
c:\msys64\mingw64\bin\gdb.exe
GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) q
c:\tmp>
Process shell finished
> Please also show the contents of these two directories you add to
> PATH. Maybe the reason for this is something in those directories.
Here is output of dir command.
dir c:\msys64\mingw64\bin\ c:\msys64\usr\bin\
Volume in drive C has no label.
Volume Serial Number is 5896-C737
Directory of c:\msys64\mingw64\bin
2024/02/20 19:30 <DIR> .
2024/02/20 19:30 <DIR> ..
2023/10/03 18:12 104 2to3
2023/10/03 18:12 104 2to3-3.11
2023/06/28 18:05 27,312 autopoint
2023/09/27 15:57 70,978 bunzip2.exe
2023/09/27 15:57 70,978 bzcat.exe
2023/09/27 15:57 2,140 bzcmp
2023/09/27 15:57 2,140 bzdiff
2023/09/27 15:57 2,054 bzegrep
2023/09/27 15:57 2,054 bzfgrep
2023/09/27 15:57 2,054 bzgrep
2023/09/27 15:57 70,978 bzip2.exe
2023/09/27 15:57 50,679 bzip2recover.exe
2023/09/27 15:57 1,297 bzless
2023/09/27 15:57 1,297 bzmore
2023/10/25 04:54 6,880 c_rehash
2023/10/11 16:03 1,581,454 dbhash.exe
2023/06/28 18:05 121,351 envsubst.exe
2023/07/25 04:20 4,627 gdb-add-index
2023/07/25 04:20 10,469,127 gdb.exe
2023/07/25 04:20 1,590,350 gdbserver.exe
2023/06/28 18:05 122,335 gettext.exe
2023/06/28 18:05 5,190 gettext.sh
2023/06/28 18:05 42,277 gettextize
2023/10/03 18:12 102 idle
2023/10/03 18:12 102 idle3
2023/10/03 18:12 102 idle3.11
2023/06/28 18:05 56,284 libasprintf-0.dll
2023/08/14 17:16 37,388 libatomic-1.dll
2023/09/27 15:57 100,964 libbz2-1.dll
2023/02/19 21:30 43,379 libcharset-1.dll
2023/10/25 04:54 4,904,847 libcrypto-3-x64.dll
2022/11/03 23:16 188,397 libexpat-1.dll
2022/10/29 02:20 33,196 libffi-8.dll
2023/07/14 15:48 132,577 libformw6.dll
2023/08/14 17:16 117,427 libgcc_s_seh-1.dll
2023/06/28 18:05 1,721,253 libgettextlib-0-21-1.dll
2023/06/28 18:05 439,756 libgettextpo-0.dll
2023/06/28 18:05 335,050 libgettextsrc-0-21-1.dll
2023/09/15 16:41 679,747 libgmp-10.dll
2023/09/15 16:41 30,824 libgmpxx-4.dll
2023/08/14 17:16 293,493 libgomp-1.dll
2023/01/10 18:10 274,944 libhistory8.dll
2023/02/19 21:30 1,117,178 libiconv-2.dll
2023/06/28 18:05 140,552 libintl-8.dll
2023/08/03 18:04 183,717 liblzma-5.dll
2023/07/14 15:48 40,529 libmenuw6.dll
2023/09/13 21:57 153,383 libmpc-3.dll
2021/08/29 03:32 41,564 libmpdec++-2.dll
2021/08/29 03:32 195,475 libmpdec-2.dll
2023/09/13 21:51 686,603 libmpfr-6.dll
2023/07/14 15:48 72,349 libncurses++w6.dll
2023/07/14 15:48 512,608 libncursesw6.dll
2023/07/14 15:48 23,041 libpanelw6.dll
2023/10/03 18:12 4,654,219 libpython3.11.dll
2023/10/03 18:12 74,246 libpython3.dll
2023/08/14 17:16 377,417 libquadmath-0.dll
2023/01/10 18:10 559,599 libreadline8.dll
2023/10/11 16:03 1,550,531 libsqlite3-0.dll
2023/10/25 04:54 656,338 libssl-3-x64.dll
2023/08/14 17:16 2,266,606 libstdc++-6.dll
2018/01/17 18:00 18,240 libsystre-0.dll
2023/09/27 21:10 46,373 libtermcap-0.dll
2018/01/17 17:54 92,313 libtre-5.dll
2023/10/25 03:02 60,796 libwinpthread-1.dll
2023/08/31 01:53 56,668 libxxhash.dll
2023/04/05 20:22 1,165,512 libzstd.dll
2023/08/03 18:04 53,968 lzmadec.exe
2023/08/03 18:04 28,754 lzmainfo.exe
2023/06/28 18:05 38,788 msgattrib.exe
2023/06/28 18:05 37,551 msgcat.exe
2023/06/28 18:05 39,988 msgcmp.exe
2023/06/28 18:05 37,208 msgcomm.exe
2023/06/28 18:05 35,051 msgconv.exe
2023/06/28 18:05 35,070 msgen.exe
2023/06/28 18:05 33,878 msgexec.exe
2023/06/28 18:05 43,989 msgfilter.exe
2023/06/28 18:05 93,308 msgfmt.exe
2023/06/28 18:05 154,232 msggrep.exe
2023/06/28 18:05 61,089 msginit.exe
2023/06/28 18:05 70,421 msgmerge.exe
2023/06/28 18:05 48,822 msgunfmt.exe
2023/06/28 18:05 35,988 msguniq.exe
2023/07/14 15:48 8,773 ncursesw6-config
2023/06/28 18:05 121,825 ngettext.exe
2023/10/25 04:54 1,002,431 openssl.exe
2023/10/03 18:12 87 pydoc
2023/10/03 18:12 87 pydoc3
2023/10/03 18:12 87 pydoc3.11
2023/10/03 18:12 3,772 python-config
2023/10/03 18:12 99,407 python.exe
2023/10/03 18:12 3,772 python3-config
2023/10/03 18:12 3,772 python3.11-config
2023/10/03 18:12 99,407 python3.11.exe
2023/10/03 18:12 99,407 python3.exe
2023/10/03 18:12 97,871 python3w.exe
2023/10/03 18:12 97,871 pythonw.exe
2023/04/05 20:22 148,639 pzstd.exe
2023/06/28 18:05 32,699 recode-sr-latin.exe
2023/10/11 16:03 1,589,861 showdb.exe
2023/10/11 16:03 1,571,846 showjournal.exe
2023/10/11 16:03 1,571,759 showstat4.exe
2023/10/11 16:03 1,581,660 showwal.exe
2023/10/11 16:03 1,600,009 sqldiff.exe
2023/10/11 16:03 1,954,102 sqlite3.exe
2023/10/11 16:03 1,618,841 sqlite3_analyzer.exe
2023/04/24 15:04 30,392 sqlite3_analyzer.sh
2023/04/24 15:04 1,674,627 tcl86.dll
2023/04/24 15:04 79,615 tclsh.exe
2023/04/24 15:04 79,615 tclsh86.exe
2023/06/22 17:03 1,530,148 tk86.dll
2023/08/03 18:04 88,029 unxz.exe
2023/06/22 17:03 66,703 wish.exe
2023/06/22 17:03 66,703 wish86.exe
2018/01/17 17:54 36,022 x86_64-w64-mingw32-agrep.exe
2023/07/14 15:48 153,088 x86_64-w64-mingw32-captoinfo.exe
2023/07/14 15:48 49,152 x86_64-w64-mingw32-clear.exe
2023/07/14 15:48 96,256 x86_64-w64-mingw32-infocmp.exe
2023/07/14 15:48 153,088 x86_64-w64-mingw32-infotocap.exe
2023/07/14 15:48 59,392 x86_64-w64-mingw32-reset.exe
2023/07/14 15:48 50,176 x86_64-w64-mingw32-tabs.exe
2023/07/14 15:48 153,088 x86_64-w64-mingw32-tic.exe
2023/07/14 15:48 54,272 x86_64-w64-mingw32-toe.exe
2023/07/14 15:48 59,392 x86_64-w64-mingw32-tput.exe
2023/07/14 15:48 59,392 x86_64-w64-mingw32-tset.exe
2023/06/28 18:05 304,464 xgettext.exe
2022/11/03 23:16 82,678 xmlwf.exe
2023/08/31 01:53 83,771 xxhsum.exe
2023/08/03 18:04 88,029 xz.exe
2023/08/03 18:04 88,029 xzcat.exe
2023/08/03 18:04 7,422 xzcmp
2023/08/03 18:04 53,969 xzdec.exe
2023/08/03 18:04 7,422 xzdiff
2023/08/03 18:04 10,333 xzegrep
2023/08/03 18:04 10,333 xzfgrep
2023/08/03 18:04 10,333 xzgrep
2023/08/03 18:04 1,813 xzless
2023/08/03 18:04 2,190 xzmore
2023/08/19 05:06 120,814 zlib1.dll
2023/04/05 20:22 207,351 zstd.exe
139 File(s) 58,157,640 bytes
Directory of c:\msys64\usr\bin
2024/01/04 10:53 <DIR> .
2024/01/04 10:53 <DIR> ..
2023/02/12 04:45 3,075 addgnupghome
2023/07/14 17:41 50,220 agetty.exe
2023/02/12 04:45 2,217 applygnupgdefaults
2022/11/16 02:07 35,876 arch.exe
2023/01/25 04:50 108,312 ash.exe
2023/10/06 01:05 27,372 autopoint
2023/05/13 05:55 689,533 awk.exe
2022/11/16 02:07 55,390 b2sum.exe
2023/09/26 09:07 7,339 backup
2022/11/16 02:07 41,819 base32.exe
2022/11/16 02:07 41,819 base64.exe
2022/11/16 02:07 34,883 basename.exe
2022/11/16 02:07 49,499 basenc.exe
2023/09/15 03:58 2,290,370 bash.exe
2023/09/15 03:58 6,846 bashbug
2023/07/14 17:41 42,850 blkid.exe
2023/09/06 14:52 29,189 brotli.exe
2023/09/13 00:06 745,114 bsdtar.exe
2022/06/26 16:27 92,176 bunzip2.exe
2022/06/26 16:27 92,176 bzcat.exe
2022/06/26 16:27 2,140 bzcmp
2022/06/26 16:27 2,140 bzdiff
2022/06/26 16:27 2,054 bzegrep
2022/06/26 16:27 2,054 bzfgrep
2022/06/26 16:27 2,054 bzgrep
2022/06/26 16:27 92,176 bzip2.exe
2022/06/26 16:27 14,653 bzip2recover.exe
2022/06/26 16:27 1,297 bzless
2022/06/26 16:27 1,297 bzmore
2023/07/14 17:41 55,775 cal.exe
2023/09/16 00:56 80,384 captoinfo.exe
2022/11/16 02:07 38,719 cat.exe
2023/07/14 17:41 86,040 cfdisk.exe
2023/09/15 21:04 16,395 chattr.exe
2022/11/16 02:07 60,112 chcon.exe
2023/07/15 02:02 3,323 checkupdates
2022/11/16 02:07 66,575 chgrp.exe
2022/11/16 02:07 58,933 chmod.exe
2022/11/16 02:07 69,199 chown.exe
2022/11/16 02:07 43,648 chroot.exe
2023/07/14 17:41 30,782 chrt.exe
2022/11/16 02:07 37,068 cksum.exe
2023/09/16 00:56 10,752 clear.exe
2023/02/08 00:09 225 cmd
2023/07/14 17:41 27,151 col.exe
2023/07/14 17:41 15,362 colcrt.exe
2023/07/14 17:41 23,348 colrm.exe
2023/07/14 17:41 45,088 column.exe
2022/11/16 02:07 40,237 comm.exe
2023/10/26 17:36 <DIR> core_perl
2022/11/16 02:07 114,653 cp.exe
2022/11/16 02:07 112,205 csplit.exe
2023/10/11 16:37 187,910 curl.exe
2022/11/16 02:07 45,102 cut.exe
2023/09/15 21:04 230,838 cygcheck.exe
2023/09/15 21:04 29,668 cygpath.exe
2023/09/15 21:04 43,096 cygwin-console-helper.exe
2023/10/25 04:20 6,879 c_rehash
2023/01/25 04:50 108,312 dash.exe
2022/11/16 02:07 120,177 date.exe
2023/09/16 00:01 11,776 db_archive.exe
2023/09/16 00:01 12,800 db_checkpoint.exe
2023/09/16 00:01 13,312 db_deadlock.exe
2023/09/16 00:01 15,360 db_dump.exe
2023/09/16 00:01 16,896 db_hotbackup.exe
2023/09/16 00:01 26,624 db_load.exe
2023/09/16 00:01 12,800 db_log_verify.exe
2023/09/16 00:01 32,256 db_printlog.exe
2023/09/16 00:01 12,800 db_recover.exe
2023/09/16 00:01 13,824 db_replicate.exe
2023/09/16 00:01 14,336 db_stat.exe
2023/09/16 00:01 20,992 db_tuner.exe
2023/09/16 00:01 12,288 db_upgrade.exe
2023/09/16 00:01 12,800 db_verify.exe
2022/11/16 02:07 90,732 dd.exe
2022/11/16 02:07 104,899 df.exe
2022/11/16 02:07 149,479 dir.exe
2022/11/16 02:07 57,476 dircolors.exe
2023/02/12 04:45 96,635 dirmngr-client.exe
2023/02/12 04:45 381,577 dirmngr.exe
2022/11/16 02:07 34,830 dirname.exe
2023/07/14 07:00 47,410 dnsdomainname.exe
2022/11/16 02:07 168,410 du.exe
2023/09/15 21:04 1,095,761 dumper.exe
2023/04/10 17:23 17,060 dumpsexp.exe
2022/11/16 02:07 35,755 echo.exe
2022/11/16 02:27 28 egrep
2022/11/16 02:07 44,180 env.exe
2023/10/06 01:05 41,233 envsubst.exe
2022/11/16 02:07 38,673 expand.exe
2022/11/16 02:07 111,126 expr.exe
2022/11/16 02:07 77,490 factor.exe
2022/11/16 02:07 33,123 false.exe
2023/07/14 17:41 129,517 fdisk.exe
2022/11/16 02:27 28 fgrep
2023/07/30 18:06 24,225 file.exe
2022/05/15 05:27 267,485 find.exe
2023/07/14 17:41 12,521 findfs.exe
2023/07/14 17:41 28,578 flock.exe
2022/11/16 02:07 43,330 fmt.exe
2022/11/16 02:07 38,204 fold.exe
2023/07/14 17:41 33,506 fsck.cramfs.exe
2023/07/14 17:41 44,159 fsck.minix.exe
2023/07/14 07:00 129,962 ftp.exe
2014/11/04 17:22 33,629 funzip.exe
2023/05/13 05:55 689,533 gawk-5.2.2.exe
2023/05/13 05:55 689,533 gawk.exe
2023/05/13 05:55 6,619 gawkbug
2022/05/14 19:28 125,394 gdbmtool.exe
2022/05/14 19:28 26,273 gdbm_dump.exe
2022/05/14 19:28 29,108 gdbm_load.exe
2023/09/15 21:04 15,685 gencat.exe
2023/09/15 21:04 27,961 getconf.exe
2022/10/23 01:33 21,461 getent.exe
2023/09/15 21:04 14,854 getfacl.exe
2023/07/14 17:41 18,136 getopt.exe
2023/10/06 01:05 40,230 gettext.exe
2023/10/06 01:05 5,190 gettext.sh
2023/10/06 01:05 42,291 gettextize
2022/11/16 02:07 36,574 gkill.exe
2023/09/15 21:04 14,113 gmondump.exe
2023/02/12 04:45 385,918 gpg-agent.exe
2023/02/12 04:45 140,873 gpg-connect-agent.exe
2023/04/10 17:29 33,346 gpg-error.exe
2023/02/12 04:45 189,309 gpg-wks-server.exe
2023/02/12 04:45 1,020,342 gpg.exe
2023/02/12 04:45 155,302 gpgconf.exe
2023/09/16 00:48 80,985 gpgme-json.exe
2023/09/16 00:48 67,403 gpgme-tool.exe
2023/02/12 04:45 27,020 gpgparsemail.exe
2023/02/12 04:45 224,495 gpgscm.exe
2023/02/12 04:45 489,361 gpgsm.exe
2023/02/12 04:45 67,673 gpgsplit.exe
2023/02/12 04:45 132,535 gpgtar.exe
2023/02/12 04:45 433,134 gpgv.exe
2022/11/16 02:27 213,201 grep.exe
2022/11/16 02:07 36,590 groups.exe
2023/08/26 19:50 2,335 gunzip
2023/08/26 19:50 6,436 gzexe
2023/08/26 19:50 106,583 gzip.exe
2023/07/14 17:41 18,546 hardlink.exe
2022/11/16 02:07 45,413 head.exe
2023/07/14 17:41 48,120 hexdump.exe
2023/04/10 17:23 16,584 hmac256.exe
2022/11/16 02:07 33,315 hostid.exe
2022/11/16 02:07 33,894 hostname.exe
2022/06/06 19:22 36,115 iconv.exe
2022/11/16 02:07 43,959 id.exe
2023/10/24 16:08 300,716 info.exe
2023/09/16 00:56 55,808 infocmp.exe
2023/09/16 00:56 80,384 infotocap.exe
2023/10/24 16:08 131,105 install-info.exe
2022/11/16 02:07 148,448 install.exe
2023/07/14 17:41 25,262 ipcmk.exe
2023/07/14 17:41 23,435 isosize.exe
2022/11/16 02:07 51,222 join.exe
2023/02/12 04:45 149,702 kbxutil.exe
2023/09/15 21:04 18,557 kill.exe
2023/09/15 21:04 19,487 ldd.exe
2023/09/15 21:04 18,584 ldh.exe
2023/08/14 09:06 199,610 less.exe
2023/08/14 09:06 12,298 lessecho.exe
2023/08/14 09:06 20,197 lesskey.exe
2022/11/16 02:07 33,822 link.exe
2022/11/16 02:07 77,077 ln.exe
2023/09/15 21:04 26,544 locale.exe
2022/05/15 05:27 147,253 locate.exe
2023/07/14 17:41 40,076 logger.exe
2022/11/16 02:07 33,855 logname.exe
2023/07/14 17:41 15,915 look.exe
2022/11/16 02:07 149,479 ls.exe
2023/09/15 21:04 15,882 lsattr.exe
2023/08/03 15:34 77,445 lzcat.exe
2023/08/03 15:34 7,422 lzcmp
2023/08/03 15:34 7,422 lzdiff
2023/08/03 15:34 10,333 lzegrep
2023/08/03 15:34 10,333 lzfgrep
2023/08/03 15:34 10,333 lzgrep
2023/08/03 15:34 1,813 lzless
2023/08/03 15:34 77,445 lzma.exe
2023/08/03 15:34 15,316 lzmadec.exe
2023/08/03 15:34 14,437 lzmainfo.exe
2023/08/03 15:34 2,190 lzmore
2023/10/25 04:44 40,592 makepkg
2023/10/25 04:44 3,568 makepkg-mingw
2023/10/25 04:44 6,448 makepkg-template
2023/07/14 17:41 28,857 mcookie.exe
2022/11/16 02:07 47,036 md5sum.exe
2023/09/15 21:04 13,998 minidumper.exe
2023/09/03 22:40 12,680 mintheme
2023/09/03 22:40 1,089,613 mintty.exe
2022/11/16 02:07 71,435 mkdir.exe
2022/11/16 02:07 36,564 mkfifo.exe
2023/07/14 17:41 27,776 mkfs.bfs.exe
2023/07/14 17:41 36,224 mkfs.cramfs.exe
2023/07/14 17:41 14,213 mkfs.exe
2023/07/14 17:41 36,958 mkfs.minix.exe
2023/09/15 21:04 23,764 mkgroup.exe
2022/11/16 02:07 39,738 mknod.exe
2023/09/15 21:04 23,300 mkpasswd.exe
2023/07/14 17:41 34,513 mkswap.exe
2022/11/16 02:07 44,192 mktemp.exe
2023/07/14 17:41 39,758 more.exe
2023/09/15 21:04 19,286 mount.exe
2023/04/10 17:23 18,659 mpicalc.exe
2023/10/06 01:05 25,020 msgattrib.exe
2023/10/06 01:05 23,814 msgcat.exe
2023/10/06 01:05 25,023 msgcmp.exe
2023/10/06 01:05 24,037 msgcomm.exe
2023/10/06 01:05 20,738 msgconv.exe
2023/10/06 01:05 20,757 msgen.exe
2023/10/06 01:05 19,445 msgexec.exe
2023/10/06 01:05 28,515 msgfilter.exe
2023/10/06 01:05 82,994 msgfmt.exe
2023/10/06 01:05 108,344 msggrep.exe
2023/10/06 01:05 46,566 msginit.exe
2023/10/06 01:05 56,000 msgmerge.exe
2023/10/06 01:05 33,295 msgunfmt.exe
2023/10/06 01:05 23,293 msguniq.exe
2023/09/15 21:04 2,942,686 msys-2.0.dll
2022/10/23 01:29 41,381 msys-argp-0.dll
2023/07/14 03:30 560,685 msys-asn1-8.dll
2023/10/06 01:05 11,346 msys-asprintf-0.dll
2023/06/20 18:05 68,026 msys-assuan-0.dll
2023/09/14 17:43 28,455 msys-atomic-1.dll
2023/07/14 17:41 241,174 msys-blkid-1.dll
2023/09/06 14:52 138,385 msys-brotlicommon-1.dll
2023/09/06 14:52 54,652 msys-brotlidec-1.dll
2023/09/06 14:52 711,463 msys-brotlienc-1.dll
2022/06/26 16:27 67,277 msys-bz2-1.dll
2022/06/06 19:22 9,460 msys-charset-1.dll
2023/07/14 03:30 10,102 msys-com_err-1.dll
2023/07/17 16:44 199,388 msys-crypt-2.dll
2023/10/25 04:20 4,490,204 msys-crypto-3.dll
2023/10/11 16:37 667,778 msys-curl-4.dll
2023/09/16 00:01 1,607,750 msys-db-5.3.dll
2023/09/16 00:01 1,727,165 msys-db_cxx-5.3.dll
2023/01/29 01:29 177,019 msys-edit-0.dll
2022/10/26 18:36 172,090 msys-expat-1.dll
2023/07/05 18:04 83,665 msys-exslt-0.dll
2023/07/14 17:41 347,366 msys-fdisk-1.dll
2022/10/25 11:53 31,135 msys-ffi-8.dll
2023/09/16 00:56 61,483 msys-formw6.dll
2023/09/14 17:43 109,318 msys-gcc_s-seh-1.dll
2023/04/10 17:23 849,323 msys-gcrypt-20.dll
2022/05/14 19:28 58,868 msys-gdbm-6.dll
2022/05/14 19:28 13,320 msys-gdbm_compat-4.dll
2023/10/06 01:05 1,545,459 msys-gettextlib-0-22-3.dll
2023/10/06 01:05 364,499 msys-gettextpo-0.dll
2023/10/06 01:05 310,932 msys-gettextsrc-0-22-3.dll
2023/08/01 15:13 596,041 msys-gmp-10.dll
2023/08/01 15:13 23,641 msys-gmpxx-4.dll
2023/09/16 00:32 1,795,526 msys-gnutls-30.dll
2023/09/16 00:32 48,170 msys-gnutlsxx-30.dll
2023/09/14 17:43 249,498 msys-gomp-1.dll
2023/04/10 17:29 139,933 msys-gpg-error-0.dll
2023/09/16 00:48 316,218 msys-gpgme-11.dll
2023/09/16 00:48 353,087 msys-gpgmepp-6.dll
2023/07/14 03:30 227,921 msys-gssapi-3.dll
2023/07/14 03:30 201,648 msys-hcrypto-4.dll
2023/07/14 03:30 130,145 msys-hdb-9.dll
2023/07/14 03:30 52,962 msys-heimbase-1.dll
2023/07/14 03:30 33,301 msys-heimntlm-0.dll
2023/01/18 06:29 37,226 msys-history8.dll
2023/06/03 00:04 270,884 msys-hogweed-6.dll
2023/07/14 03:30 281,646 msys-hx509-5.dll
2022/06/06 19:22 1,082,798 msys-iconv-2.dll
2022/11/13 23:55 195,035 msys-idn2-0.dll
2023/10/06 01:05 113,352 msys-intl-8.dll
2023/07/14 03:30 41,052 msys-kadm5clnt-7.dll
2023/07/14 03:30 76,168 msys-kadm5srv-8.dll
2023/07/14 03:30 28,064 msys-kafs-0.dll
2023/07/14 03:30 160,230 msys-kdc-2.dll
2023/07/14 03:30 491,126 msys-krb5-26.dll
2023/07/03 06:03 243,180 msys-ksba-8.dll
2022/08/20 02:37 137,516 msys-lz4-1.dll
2023/08/03 15:34 176,834 msys-lzma-5.dll
2023/07/30 18:06 165,033 msys-magic-1.dll
2023/09/16 00:56 30,532 msys-menuw6.dll
2023/08/24 16:13 649,994 msys-mpfr-6.dll
2023/09/16 00:56 65,378 msys-ncurses++w6.dll
2023/09/16 00:56 333,631 msys-ncursesw6.dll
2023/06/03 00:04 288,179 msys-nettle-8.dll
2023/10/12 03:02 170,524 msys-nghttp2-14.dll
2018/08/08 16:13 16,068 msys-npth-0.dll
2023/07/14 03:30 86,669 msys-otp-0.dll
2023/06/30 18:13 1,382,985 msys-p11-kit-0.dll
2023/09/16 00:56 14,821 msys-panelw6.dll
2023/09/16 01:06 289,270 msys-pcre-1.dll
2022/12/20 17:28 384,470 msys-pcre2-8-0.dll
2023/07/14 03:16 3,502,741 msys-perl5_36.dll
2023/01/01 23:26 71,938 msys-psl-5.dll
2023/09/14 17:43 363,398 msys-quadmath-0.dll
2023/01/18 06:29 264,885 msys-readline8.dll
2023/07/14 03:30 67,079 msys-roken-18.dll
2023/07/14 03:30 14,858 msys-sl-0.dll
2023/07/14 17:41 165,189 msys-smartcols-1.dll
2023/05/27 00:59 1,380,182 msys-sqlite3-0.dll
2023/06/13 14:16 250,887 msys-ssh2-1.dll
2023/10/25 04:20 597,224 msys-ssl-3.dll
2023/09/14 17:43 2,244,703 msys-stdc++-6.dll
2022/08/25 03:42 70,621 msys-tasn1-6.dll
2023/09/16 00:56 63,354 msys-ticw6.dll
2022/11/14 03:32 1,825,160 msys-unistring-5.dll
2023/07/14 17:41 27,681 msys-uuid-1.dll
2023/07/14 03:30 164,937 msys-wind-0.dll
2023/08/10 05:27 1,224,349 msys-xml2-2.dll
2023/07/05 18:04 236,639 msys-xslt-1.dll
2023/08/29 14:58 88,576 msys-z.dll
2023/04/05 19:30 1,125,314 msys-zstd-1.dll
2022/11/16 02:07 122,430 mv.exe
2023/07/14 17:41 27,796 namei.exe
2023/01/20 18:23 362,900 nano.exe
2023/06/03 00:04 18,460 nettle-hash.exe
2023/06/03 00:04 9,761 nettle-lfib-stream.exe
2023/06/03 00:04 18,548 nettle-pbkdf2.exe
2023/10/06 01:05 41,800 ngettext.exe
2022/11/16 02:07 36,525 nice.exe
2022/11/16 02:07 104,060 nl.exe
2022/11/16 02:07 36,594 nohup.exe
2023/07/14 17:41 12,716 nologin.exe
2022/11/16 02:07 36,659 nproc.exe
2022/11/16 02:07 61,464 numfmt.exe
2022/11/16 02:07 86,740 od.exe
2023/10/25 04:20 890,624 openssl.exe
2023/06/30 18:13 100,246 p11-kit.exe
2023/07/15 02:02 11,435 paccache
2023/07/15 02:02 8,739 pacdiff
2023/07/15 02:02 1,687 paclist
2023/07/15 02:02 2,288 paclog-pkglist
2023/10/25 04:44 11,942,834 pacman-conf.exe
2023/10/25 04:44 6,897 pacman-db-upgrade
2023/10/25 04:44 22,112 pacman-key
2023/10/25 04:44 11,993,333 pacman.exe
2023/07/15 02:02 2,915 pacscripts
2023/07/15 02:02 3,649 pacsearch
2023/07/15 02:02 16,972 pacsort.exe
2023/07/15 02:02 11,900,901 pactree.exe
2023/09/15 21:04 24,101 passwd.exe
2022/11/16 02:07 37,588 paste.exe
2022/11/16 02:07 35,362 pathchk.exe
2023/04/18 05:17 24,029 peflags.exe
2023/04/18 05:17 9,646 peflagsall
2023/07/14 03:16 14,315 perl.exe
2023/07/14 03:16 14,315 perl5.36.1.exe
2023/07/14 17:41 48,932 pg.exe
2022/10/08 23:50 79,122 pinentry-w32.exe
2022/10/08 23:50 79,122 pinentry.exe
2022/11/16 02:07 41,090 pinky.exe
2023/06/03 00:04 23,459 pkcs1-conv.exe
2023/09/15 21:04 12,701 pldd.exe
2022/11/16 02:07 73,622 pr.exe
2022/11/16 02:07 33,795 printenv.exe
2022/11/16 02:07 72,003 printf.exe
2023/09/15 21:04 35,580 profiler.exe
2023/09/15 21:04 16,408 ps.exe
2023/01/01 23:26 22,801 psl-make-dafsa
2023/01/01 23:26 17,570 psl.exe
2022/11/16 02:07 130,279 ptx.exe
2022/11/16 02:07 36,148 pwd.exe
2023/07/15 02:02 7,352 rankmirrors
2023/07/14 07:00 58,548 rcp.exe
2022/11/16 02:07 48,491 readlink.exe
2022/11/16 02:07 49,576 realpath.exe
2023/04/18 05:17 901,362 rebase.exe
2023/04/18 05:17 7,151 rebaseall
2023/10/06 01:05 17,029 recode-sr-latin.exe
2023/09/15 21:04 26,591 regtool.exe
2023/07/14 17:41 17,153 rename.exe
2023/07/14 17:41 14,005 renice.exe
2023/10/25 04:44 18,804 repo-add
2023/10/25 04:44 18,804 repo-elephant
2023/10/25 04:44 18,804 repo-remove
2023/09/16 00:56 20,992 reset.exe
2023/09/26 09:07 5,997 restore
2023/07/14 17:41 14,148 rev.exe
2023/07/14 07:00 52,257 rlogin.exe
2022/11/16 02:07 63,813 rm.exe
2022/11/16 02:07 62,247 rmdir.exe
2023/01/20 18:23 362,900 rnano.exe
2023/07/14 07:00 48,927 rsh.exe
2022/11/16 02:07 34,817 runcon.exe
2023/07/14 17:41 58,428 script.exe
2023/07/14 17:41 50,026 scriptlive.exe
2023/07/14 17:41 36,776 scriptreplay.exe
2022/11/19 21:44 178,140 sed.exe
2022/11/16 02:07 68,488 seq.exe
2023/09/15 21:04 22,708 setfacl.exe
2023/09/15 21:04 11,322 setmetamode.exe
2023/07/14 17:41 14,176 setsid.exe
2023/06/03 00:04 29,772 sexp-conv.exe
2023/07/14 17:41 120,965 sfdisk.exe
2023/09/15 03:58 2,290,370 sh.exe
2022/11/16 02:07 50,108 sha1sum.exe
2022/11/16 02:07 56,252 sha224sum.exe
2022/11/16 02:07 56,252 sha256sum.exe
2022/11/16 02:07 61,372 sha384sum.exe
2022/11/16 02:07 61,372 sha512sum.exe
2023/02/08 00:09 2,809 shell
2022/11/16 02:07 58,509 shred.exe
2022/11/16 02:07 54,163 shuf.exe
2023/07/14 03:16 <DIR> site_perl
2022/11/16 02:07 36,003 sleep.exe
2022/11/16 02:07 109,591 sort.exe
2022/11/16 02:07 54,181 split.exe
2023/09/15 21:04 25,393 ssp.exe
2023/02/08 00:09 239 start
2022/11/16 02:07 97,209 stat.exe
2022/11/16 02:07 69,024 stdbuf.exe
2023/09/15 21:04 75,871 strace.exe
2022/11/16 02:07 90,756 stty.exe
2022/11/16 02:07 42,969 sum.exe
2023/07/14 17:41 16,817 swaplabel.exe
2022/11/16 02:07 34,426 sync.exe
2023/09/16 00:56 15,872 tabs.exe
2022/11/16 02:07 107,732 tac.exe
2022/11/16 02:07 56,617 tail.exe
2023/07/14 07:00 59,492 talk.exe
2023/09/26 09:07 497,189 tar.exe
2023/07/14 17:41 30,153 taskset.exe
2022/11/16 02:07 38,794 tee.exe
2023/07/14 07:00 121,779 telnet.exe
2022/11/16 02:07 70,331 test.exe
2023/10/25 04:44 11,890,483 testpkg.exe
2023/09/16 00:56 80,384 tic.exe
2022/05/15 06:25 22,312 time.exe
2022/11/16 02:07 41,752 timeout.exe
2023/09/16 00:56 14,848 toe.exe
2022/11/16 02:07 107,463 touch.exe
2023/09/16 00:56 19,968 tput.exe
2022/11/16 02:07 49,460 tr.exe
2022/11/16 02:07 33,123 true.exe
2022/11/16 02:07 39,679 truncate.exe
2023/06/30 18:13 193,566 trust.exe
2023/09/16 00:56 20,992 tset.exe
2022/11/16 02:07 48,935 tsort.exe
2022/11/16 02:07 33,312 tty.exe
2023/03/29 19:07 18,642 tzselect
2023/09/15 21:04 53,182 tzset.exe
2023/07/14 17:41 19,734 ul.exe
2023/09/15 21:04 12,585 umount.exe
2022/11/16 02:07 35,876 uname.exe
2023/08/26 19:50 2,335 uncompress
2022/11/16 02:07 39,225 unexpand.exe
2022/11/16 02:07 45,019 uniq.exe
2022/11/16 02:07 33,824 unlink.exe
2023/08/03 15:34 77,445 unlzma.exe
2023/08/03 15:34 77,445 unxz.exe
2014/11/04 17:22 173,708 unzip.exe
2014/11/04 17:22 83,158 unzipsfx.exe
2023/04/05 19:30 172,803 unzstd.exe
2023/03/15 07:04 1,373 update-ca-trust
2022/05/15 05:27 9,090 updatedb
2023/07/15 02:02 3,486 updpkgsums
2022/11/16 02:07 35,078 users.exe
2023/07/14 17:41 35,004 uuidd.exe
2023/07/14 17:41 15,424 uuidgen.exe
2023/07/14 17:41 33,826 uuidparse.exe
2022/11/16 02:07 149,479 vdir.exe
2023/07/14 03:16 <DIR> vendor_perl
2023/10/25 04:44 11,771 vercmp.exe
2023/02/12 04:45 15,991 watchgnupg.exe
2022/11/16 02:07 47,366 wc.exe
2023/05/23 01:56 508,536 wget.exe
2023/07/14 17:41 26,523 whereis.exe
2022/05/16 02:47 30,538 which.exe
2022/11/16 02:07 70,291 who.exe
2022/11/16 02:07 33,887 whoami.exe
2023/07/14 17:41 36,914 wipefs.exe
2022/05/15 05:27 68,362 xargs.exe
2023/10/06 01:05 299,138 xgettext.exe
2023/08/10 05:27 18,633 xmlcatalog.exe
2023/08/10 05:27 66,169 xmllint.exe
2023/07/05 18:04 26,993 xsltproc.exe
2023/08/03 15:34 77,445 xz.exe
2023/08/03 15:34 77,445 xzcat.exe
2023/08/03 15:34 7,422 xzcmp
2023/08/03 15:34 15,317 xzdec.exe
2023/08/03 15:34 7,422 xzdiff
2023/08/03 15:34 10,333 xzegrep
2023/08/03 15:34 10,333 xzfgrep
2023/08/03 15:34 10,333 xzgrep
2023/08/03 15:34 1,813 xzless
2023/08/03 15:34 2,190 xzmore
2023/04/10 17:29 31,463 yat2m.exe
2022/11/16 02:07 33,823 yes.exe
2023/08/26 19:50 1,973 zcat
2023/08/26 19:50 1,678 zcmp
2023/08/26 19:50 6,449 zdiff
2023/03/29 19:07 44,958 zdump.exe
2023/08/26 19:50 29 zegrep
2023/08/26 19:50 29 zfgrep
2023/08/26 19:50 2,076 zforce
2023/08/26 19:50 8,208 zgrep
2023/03/29 19:07 51,915 zic.exe
2018/07/27 17:42 189,425 zip.exe
2018/07/27 17:42 83,501 zipcloak.exe
2014/11/04 17:22 2,953 zipgrep
2014/11/04 17:22 173,708 zipinfo.exe
2018/07/27 17:42 80,154 zipnote.exe
2018/07/27 17:42 81,719 zipsplit.exe
2023/08/26 19:50 2,434 zless
2023/08/26 19:50 1,837 zmore
2023/08/26 19:50 4,572 znew
2023/04/05 19:30 172,803 zstd.exe
2023/04/05 19:30 172,803 zstdcat.exe
2023/04/05 19:30 3,869 zstdgrep
2023/04/05 19:30 197 zstdless
2023/04/05 19:30 172,803 zstdmt.exe
2022/11/16 02:07 72,418 [.exe
507 File(s) 125,182,335 bytes
5 Dir(s) 112,400,072,704 bytes free
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-17 1:06 ` awrhygty
@ 2024-03-17 6:18 ` Eli Zaretskii
2024-03-17 16:12 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-17 6:18 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Sun, 17 Mar 2024 10:06:13 +0900
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Before setting PATH, the value is:
> >> C:\ImageMagick;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\user\AppData\Local\Programs\Python\Python310\Scripts\;C:\Users\user\AppData\Local\Programs\Python\Python310\;C:\Users\user\AppData\Local\Microsoft\WindowsApps;
> >> Then removing directories other than C:\WINDOWS or descendants:
> >> C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;
> >
> > I don't understand what you mean by "removing directories other than
> > C:\WINDOWS or descendants". Why do they need to be removed? And how
> > did you remove them?
>
> I removed obviously unrelated pathnames, which are for imagemagick and
> python. They are not supplied by OS. And I removed them by hand.
I don't understand why you did that, but since it doesn't change the
results, we can ignore this aspect.
> > What happens if you change PATH to include the two addition
> > directories, c:\msys64\mingw64\bin\ and c:\msys64\usr\bin, before you
> > start Emacs, and then run GDB from the shell buffer without changing
> > PATH inside the shell buffer?
>
> Input following command lines on cmd.exe.
> set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
> c:\Emacs\emacs-29.1\bin\emacs-29.1.exe -Q
> And run gdb in shell-mode, then process automatically finished.
>
> Microsoft Windows [Version 10.0.19045.4170]
> (c) Microsoft Corporation. All rights reserved.
>
> c:\tmp>set PATH
> set PATH
> PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;C:\ImageMagick;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\user\AppData\Local\Programs\Python\Python310\Scripts\;C:\Users\user\AppData\Local\Programs\Python\Python310\;C:\Users\user\AppData\Local\Microsoft\WindowsApps;
> PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
>
> c:\tmp>c:\msys64\mingw64\bin\gdb.exe
> c:\msys64\mingw64\bin\gdb.exe
> GNU gdb (GDB) 13.2
> Copyright (C) 2023 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-w64-mingw32".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word".
> (gdb) q
>
> c:\tmp>
> Process shell finished
Same result.
> > Please also show the contents of these two directories you add to
> > PATH. Maybe the reason for this is something in those directories.
>
> Here is output of dir command.
Nothing jumps out as an obvious problem, but you did say that setting
PATH affects this? How does it affect the problem? Is there a recipe
where you invoke GDB with a different PATH, and don't see "Process
shell finished" after exiting GDB? If so, can you show a recipe with
that different PATH?
Btw, why do you add these directories to PATH in the first place? The
second one is a directory with MSYS executables, so why do you need it
for running GDB? The first one is for MinGW64 executables, but since
you invoke GDB via n explicit absolute file name, you don't need to
add the directory to PATH.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-17 6:18 ` Eli Zaretskii
@ 2024-03-17 16:12 ` awrhygty
2024-03-17 16:24 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-17 16:12 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
> Nothing jumps out as an obvious problem, but you did say that setting
> PATH affects this? How does it affect the problem? Is there a recipe
> where you invoke GDB with a different PATH, and don't see "Process
> shell finished" after exiting GDB? If so, can you show a recipe with
> that different PATH?
Simply skipping PATH settings, cmdproxy.exe continues normally after
quitting c:\msys64\mingw64\bin\gdb.exe(full path needed.)
> Btw, why do you add these directories to PATH in the first place? The
> second one is a directory with MSYS executables, so why do you need it
> for running GDB? The first one is for MinGW64 executables, but since
> you invoke GDB via n explicit absolute file name, you don't need to
> add the directory to PATH.
If I decide to use MSYS environment generally, those directories are
added to system PATH setting and emacs implicitly refers to the value.
In such case, I will call gdb without directory prefix.
But currently it is problematic and I am likely to search for another
gdb binary.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-17 16:12 ` awrhygty
@ 2024-03-17 16:24 ` Eli Zaretskii
2024-03-18 1:24 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-17 16:24 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Mon, 18 Mar 2024 01:12:18 +0900
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Nothing jumps out as an obvious problem, but you did say that setting
> > PATH affects this? How does it affect the problem? Is there a recipe
> > where you invoke GDB with a different PATH, and don't see "Process
> > shell finished" after exiting GDB? If so, can you show a recipe with
> > that different PATH?
>
> Simply skipping PATH settings, cmdproxy.exe continues normally after
> quitting c:\msys64\mingw64\bin\gdb.exe(full path needed.)
So one of these two directories somehow triggers the problem? Or do
you need both on PATH to trigger the problem, and if you only add
either one of them, the problem does not happen?
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-17 16:24 ` Eli Zaretskii
@ 2024-03-18 1:24 ` awrhygty
2024-03-18 13:05 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-18 1:24 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
>> From: awrhygty@outlook.com
>> Cc: 69795@debbugs.gnu.org
>> Date: Mon, 18 Mar 2024 01:12:18 +0900
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > Nothing jumps out as an obvious problem, but you did say that setting
>> > PATH affects this? How does it affect the problem? Is there a recipe
>> > where you invoke GDB with a different PATH, and don't see "Process
>> > shell finished" after exiting GDB? If so, can you show a recipe with
>> > that different PATH?
>>
>> Simply skipping PATH settings, cmdproxy.exe continues normally after
>> quitting c:\msys64\mingw64\bin\gdb.exe(full path needed.)
>
> So one of these two directories somehow triggers the problem? Or do
> you need both on PATH to trigger the problem, and if you only add
> either one of them, the problem does not happen?
c:\msys64\usr\bin\ matters. And iconv.exe under it makes the difference.
In the log below, the process continues after the first call of gdb.exe,
while iconv.exe does not exist.
And the process finishes after the second call of gdb.exe,
while iconv.exe exists.
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.
c:\tmp>set PATH=c:\msys64\usr\bin\;%PATH%
set PATH=c:\msys64\usr\bin\;%PATH%
c:\tmp>ren c:\msys64\usr\bin\iconv.exe iconv.exe-
ren c:\msys64\usr\bin\iconv.exe iconv.exe-
c:\tmp>c:\msys64\mingw64\bin\gdb.exe --version > nul
c:\msys64\mingw64\bin\gdb.exe --version > nul
c:\tmp>ren c:\msys64\usr\bin\iconv.exe- iconv.exe
ren c:\msys64\usr\bin\iconv.exe- iconv.exe
c:\tmp>c:\msys64\mingw64\bin\gdb.exe --version > nul
c:\msys64\mingw64\bin\gdb.exe --version > nul
c:\tmp>
Process shell finished
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-18 1:24 ` awrhygty
@ 2024-03-18 13:05 ` Eli Zaretskii
2024-03-18 22:54 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-18 13:05 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Mon, 18 Mar 2024 10:24:59 +0900
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So one of these two directories somehow triggers the problem? Or do
> > you need both on PATH to trigger the problem, and if you only add
> > either one of them, the problem does not happen?
>
> c:\msys64\usr\bin\ matters. And iconv.exe under it makes the difference.
> In the log below, the process continues after the first call of gdb.exe,
> while iconv.exe does not exist.
> And the process finishes after the second call of gdb.exe,
> while iconv.exe exists.
So what is special with iconv.exe? What does "iconv --version" say?
Also, what DLLs does it load? You can find out like this:
objdump -x c:\msys64\usr\bin\iconv.exe | grep -F "DLL Name:"
And if you invoke iconv.exe from the shell buffer directly, does it
also cause "Process shell finished"?
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-18 13:05 ` Eli Zaretskii
@ 2024-03-18 22:54 ` awrhygty
2024-03-19 12:32 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-18 22:54 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
>> c:\msys64\usr\bin\ matters. And iconv.exe under it makes the difference.
>> In the log below, the process continues after the first call of gdb.exe,
>> while iconv.exe does not exist.
>> And the process finishes after the second call of gdb.exe,
>> while iconv.exe exists.
>
> So what is special with iconv.exe? What does "iconv --version" say?
Here is the log, and the process finished automatically.
c:\tmp>c:\msys64\usr\bin\iconv.exe --version
c:\msys64\usr\bin\iconv.exe --version
iconv (GNU libiconv 1.17)
Copyright (C) 2000-2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Bruno Haible.
c:\tmp>
Process shell finished
> Also, what DLLs does it load? You can find out like this:
>
> objdump -x c:\msys64\usr\bin\iconv.exe | grep -F "DLL Name:"
I have no objdump. I hope output of ldd.exe helps.
c:\tmp>c:\msys64\usr\bin\ldd.exe c:\msys64\usr\bin\iconv.exe
c:\msys64\usr\bin\ldd.exe c:\msys64\usr\bin\iconv.exe
ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffd19ad0000)
KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7ffd17c60000)
KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7ffd172f0000)
msys-iconv-2.dll => /usr/bin/msys-iconv-2.dll (0x5603f0000)
msys-intl-8.dll => /usr/bin/msys-intl-8.dll (0x430b30000)
msys-2.0.dll => /usr/bin/msys-2.0.dll (0x180040000)
c:\tmp>
Process shell finished
/usr/bin/ is same as c:\msys64\usr\bin\.
c:\tmp>c:\msys64\usr\bin\mount.exe
c:\msys64\usr\bin\mount.exe
C:/msys64 on / type ntfs (binary,noacl,auto)
C:/msys64/usr/bin on /bin type ntfs (binary,noacl,auto)
C: on /c type ntfs (binary,noacl,posix=0,user,noumount,auto)
c:\tmp>
Process shell finished
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-18 22:54 ` awrhygty
@ 2024-03-19 12:32 ` Eli Zaretskii
2024-03-19 13:21 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-19 12:32 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Tue, 19 Mar 2024 07:54:51 +0900
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> c:\msys64\usr\bin\ matters. And iconv.exe under it makes the difference.
> >> In the log below, the process continues after the first call of gdb.exe,
> >> while iconv.exe does not exist.
> >> And the process finishes after the second call of gdb.exe,
> >> while iconv.exe exists.
> >
> > So what is special with iconv.exe? What does "iconv --version" say?
>
> Here is the log, and the process finished automatically.
>
> c:\tmp>c:\msys64\usr\bin\iconv.exe --version
> c:\msys64\usr\bin\iconv.exe --version
> iconv (GNU libiconv 1.17)
> Copyright (C) 2000-2022 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Written by Bruno Haible.
>
> c:\tmp>
> Process shell finished
>
> > Also, what DLLs does it load? You can find out like this:
> >
> > objdump -x c:\msys64\usr\bin\iconv.exe | grep -F "DLL Name:"
>
> I have no objdump. I hope output of ldd.exe helps.
>
> c:\tmp>c:\msys64\usr\bin\ldd.exe c:\msys64\usr\bin\iconv.exe
> c:\msys64\usr\bin\ldd.exe c:\msys64\usr\bin\iconv.exe
> ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffd19ad0000)
> KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7ffd17c60000)
> KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7ffd172f0000)
> msys-iconv-2.dll => /usr/bin/msys-iconv-2.dll (0x5603f0000)
> msys-intl-8.dll => /usr/bin/msys-intl-8.dll (0x430b30000)
> msys-2.0.dll => /usr/bin/msys-2.0.dll (0x180040000)
>
> c:\tmp>
> Process shell finished
>
>
> /usr/bin/ is same as c:\msys64\usr\bin\.
So you have an MSYS build of iconv.exe, and it seems to be causing
these problems. You don't have a MinGW64 build of iconv.exe (in the
c:\msys64\mingw64\bin\ directory). So if GD|B needs to invoke
iconv.exe, it will invoke the MSYS build, as it cannot find any other
one. So my suggestion is to download the MinGW64 build of iconv.exe
and install it in the c:\msys64\mingw64\bin\ directory. It is
supposed to be part of the libiconv package, I think this is it:
https://packages.msys2.org/package/mingw-w64-x86_64-libiconv
Please tell if doing that solves the problem.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-19 12:32 ` Eli Zaretskii
@ 2024-03-19 13:21 ` awrhygty
2024-03-19 13:49 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-19 13:21 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
> So you have an MSYS build of iconv.exe, and it seems to be causing
> these problems. You don't have a MinGW64 build of iconv.exe (in the
> c:\msys64\mingw64\bin\ directory). So if GD|B needs to invoke
> iconv.exe, it will invoke the MSYS build, as it cannot find any other
> one. So my suggestion is to download the MinGW64 build of iconv.exe
> and install it in the c:\msys64\mingw64\bin\ directory. It is
> supposed to be part of the libiconv package, I think this is it:
>
> https://packages.msys2.org/package/mingw-w64-x86_64-libiconv
>
> Please tell if doing that solves the problem.
MinGW64 libiconv package has already been installed,
but MinGW64 iconv package was not.
Now both of them are installed, and gdb seems to work well with shell-mode.
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.
c:\tmp>set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
set PATH=c:\msys64\mingw64\bin\;c:\msys64\usr\bin\;%PATH%
c:\tmp>where gdb
where gdb
c:\msys64\mingw64\bin\gdb.exe
c:\tmp>where iconv
where iconv
c:\msys64\mingw64\bin\iconv.exe
c:\msys64\usr\bin\iconv.exe
c:\tmp>gdb
gdb
GNU gdb (GDB) 13.2
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
c:\home\yagi/.gdbinit:1: Error in sourced command file:
Argument required (expression to compute).
(gdb) q
c:\tmp>iconv --version
iconv --version
iconv (GNU libiconv 1.17)
Copyright (C) 2000-2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Bruno Haible.
c:\tmp>
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-19 13:21 ` awrhygty
@ 2024-03-19 13:49 ` Eli Zaretskii
2024-03-19 14:26 ` awrhygty
0 siblings, 1 reply; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-19 13:49 UTC (permalink / raw)
To: awrhygty; +Cc: 69795
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Tue, 19 Mar 2024 22:21:09 +0900
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So you have an MSYS build of iconv.exe, and it seems to be causing
> > these problems. You don't have a MinGW64 build of iconv.exe (in the
> > c:\msys64\mingw64\bin\ directory). So if GD|B needs to invoke
> > iconv.exe, it will invoke the MSYS build, as it cannot find any other
> > one. So my suggestion is to download the MinGW64 build of iconv.exe
> > and install it in the c:\msys64\mingw64\bin\ directory. It is
> > supposed to be part of the libiconv package, I think this is it:
> >
> > https://packages.msys2.org/package/mingw-w64-x86_64-libiconv
> >
> > Please tell if doing that solves the problem.
>
> MinGW64 libiconv package has already been installed,
> but MinGW64 iconv package was not.
> Now both of them are installed, and gdb seems to work well with shell-mode.
Great.
So it eventually was related to MSYS programs, and I think we can now
close this bug?
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-19 13:49 ` Eli Zaretskii
@ 2024-03-19 14:26 ` awrhygty
2024-03-19 15:50 ` Eli Zaretskii
0 siblings, 1 reply; 22+ messages in thread
From: awrhygty @ 2024-03-19 14:26 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 69795
Eli Zaretskii <eliz@gnu.org> writes:
> So it eventually was related to MSYS programs, and I think we can now
> close this bug?
Yes, please. Thank you for your help.
^ permalink raw reply [flat|nested] 22+ messages in thread
* bug#69795: 29.1; cmdproxy.exe exits automatically after executing MSYS2 commands
2024-03-19 14:26 ` awrhygty
@ 2024-03-19 15:50 ` Eli Zaretskii
0 siblings, 0 replies; 22+ messages in thread
From: Eli Zaretskii @ 2024-03-19 15:50 UTC (permalink / raw)
To: awrhygty; +Cc: 69795-done
> From: awrhygty@outlook.com
> Cc: 69795@debbugs.gnu.org
> Date: Tue, 19 Mar 2024 23:26:39 +0900
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So it eventually was related to MSYS programs, and I think we can now
> > close this bug?
>
> Yes, please.
Done.
> Thank you for your help.
Glad I could help you resolve this tricky issue.
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2024-03-19 15:50 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).