From: Eli Zaretskii <eliz@gnu.org>
To: James Hilling <james@literate-devops.io>
Cc: 71655@debbugs.gnu.org
Subject: bug#71655: Eshell external commands do not work under GNU Emacs for Windows
Date: Wed, 19 Jun 2024 22:12:34 +0300 [thread overview]
Message-ID: <86y170oifx.fsf@gnu.org> (raw)
In-Reply-To: <nZSKB41mLU_x3SOTeoG0b9eclfZTn8Lu_T1pkf5LEZ9pWcolOqcnTlxbJGa7lziQvQoKHv-GFqSxX1-SYZu8_xJN2EkGq6uQGXtc1uLG8uc=@literate-devops.io> (bug-gnu-emacs@gnu.org)
> Date: Wed, 19 Jun 2024 15:53:14 +0000
> From: James Hilling via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> There appears to be a potential bug with Eshell when running external commands on GNU Emacs for
> Windows, i.e. not WSL/WSL2/Cygwin.
I don't think this has anything to do with Eshell. Or Emacs, for that
matter. See below.
> To reproduce:
>
> Start Emacs with "-Q", open Eshell with `M-x eshell`, run `winget.exe --help`.
>
> (Eshell) $ winget --help
>
> Opening input file: Invalid argument, C:/Users/MyUser/AppData/Local/Microsoft/WindowsApps/winget.exe
>
> For some reason external commands such as `winget.exe` do not appear to be working properly.
Try
(Eshell) $ ls -l C:/Users/MyUser/AppData/Local/Microsoft/WindowsApps/winget.exe
What do you see? Does what you see explain the error?
I think this page explains what is going on:
https://stackoverflow.com/questions/58296925/what-is-zero-byte-executable-files-in-windows
next prev parent reply other threads:[~2024-06-19 19:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:53 bug#71655: Eshell external commands do not work under GNU Emacs for Windows James Hilling via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 19:12 ` Eli Zaretskii [this message]
2024-06-19 19:22 ` Eli Zaretskii
2024-06-19 19:40 ` Jim Porter
2024-06-20 4:53 ` Eli Zaretskii
2024-06-20 5:34 ` Jim Porter
2024-06-20 7:45 ` Eli Zaretskii
2024-06-22 19:55 ` Jim Porter
2024-06-23 4:36 ` Eli Zaretskii
2024-06-24 1:40 ` Jim Porter
2024-06-24 5:56 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-08 3:26 ` Jim Porter
2024-07-08 11:09 ` Eli Zaretskii
2024-06-19 19:30 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y170oifx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71655@debbugs.gnu.org \
--cc=james@literate-devops.io \
/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 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).