From: Eliot Moss <moss@cs.umass.edu>
To: Karl Crary <crary@andrew.cmu.edu>, cygwin@cygwin.com
Subject: Re: Cygwin is not passing arguments to Windows apps
Date: Sun, 17 Dec 2023 07:29:19 -0500 [thread overview]
Message-ID: <8c87f8a0-0ea0-422d-aaad-9338220d281a@cs.umass.edu> (raw)
In-Reply-To: <3a47c469-601e-49e8-b9ec-333201a86790@andrew.cmu.edu>
On 12/16/2023 10:55 PM, Karl Crary via Cygwin wrote:
> Dear all,
>
> I am encountering a bug wherein Cygwin is not passing arguments to most Windows programs (although Cygwin programs are
> doing fine).
>
> For example, the following command ought to be dumping a lot of usage information, but instead it starts a command
> prompt, which is what it does when not passed any argument.
>
>
> $ cmd /?
> Microsoft Windows [Version 10.0.22621.2715]
> (c) Microsoft Corporation. All rights reserved.
>
> C:\crary>
>
>
> I am experiencing the same behavior with bash, tcsh, zsh, and also make. In addition to cmd, I've also confirmed that
> arguments are not being passed to wsl, explorer, and (Miktex's) latex. Some third-party apps are getting their
> arguments, including Standard ML of New Jersey.
>
> This is a brand-new install on a brand-new Windows 11 machine. (A Dell Precision 3660 tower, if that matters.) I also
> tried varying the cygwin dll version (a little, not exhaustively) to no effect.
>
> Any theory as to what could be going on would be most appreciated.
>
> My cygcheck output (lightly redacted) follows.
>
> Karl Crary
Cygwin's shell (generally bash) will try to pattern match ("glob") the /?
because of the ? . I get intended results if I type:
cmd '/?'
Because what is in the root directory / may vary from system to system,
behavior without the quotes will may vary.
HTH -- EM
next prev parent reply other threads:[~2023-12-17 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 3:55 Karl Crary
2023-12-17 8:51 ` ASSI
2023-12-17 12:29 ` Eliot Moss [this message]
2023-12-17 13:45 ` Karl Crary
2023-12-17 13:53 ` Brian Inglis
2023-12-17 14:06 ` Brian Inglis
2023-12-17 14:29 ` Karl Crary
2023-12-17 16:05 ` Brian Inglis
2023-12-17 17:01 ` Kevin Schnitzius
2023-12-22 19:13 ` Andrey Repin
2023-12-17 19:45 ` Eliot Moss
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=8c87f8a0-0ea0-422d-aaad-9338220d281a@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=crary@andrew.cmu.edu \
--cc=cygwin@cygwin.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.
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).