public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 'kill --list' and 'kill --version' complain "not enough arguments"
Date: Wed, 15 Mar 2023 22:13:03 +0100	[thread overview]
Message-ID: <ZBI03ydruGCB9Frq@calimero.vinschen.de> (raw)
In-Reply-To: <CAOh4nmkxVS92vdDgZOXOShwRENf4TXX7eq3sHmyc6NYdvsKZbQ@mail.gmail.com>

On Mar 15 13:51, Jeremy Hetzler via Cygwin wrote:
> Hello all.
> 
> Both 'kill --list' and 'kill --version' produce a warning "not enough
> arguments".
> 
> > $ uname -a
> > CYGWIN_NT-10.0-22621 DFJWVD3 3.4.6-1.x86_64 2023-02-14 13:23 UTC x86_64 Cygwin
> >
> > $ /bin/kill --list
> > kill: not enough arguments
> > HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP TSTP CONT CHLD TTIN TTOU IO XCPU XFSZ VTALRM PROF WINCH PWR USR1 USR2 RTMIN RTMIN + 1 RTMIN + 2 RTMIN + 3 RTMIN + 4 RTMIN + 5 RTMIN + 6 RTMIN + 7 RTMIN + 8 RTMIN + 9 RTMIN + 10 RTMIN + 11 RTMIN + 12 RTMIN + 13 RTMIN + 14 RTMIN + 15 RTMIN + 16 RTMIN + 17 RTMIN + 18 RTMIN + 19 RTMIN + 20 RTMIN + 21 RTMIN + 22 RTMIN + 23 RTMIN + 24 RTMIN + 25 RTMIN + 26 RTMIN + 27 RTMIN + 28 RTMIN + 29 RTMIN + 30 RTMIN + 31
> >
> > $ /bin/kill --version
> > kill (cygwin) 3.4.6
> > Process Signaller
> > Copyright (C) 1996 - 2023 Cygwin Authors
> > This is free software; see the source for copying conditions.  There is NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> > kill: not enough arguments
> >
> 
> Seems like --list and --version are complete subcommands, like --help,
> and therefore shouldn't produce this warning.

Thanks for the report, I pushed a patch.

A new cygwin test release 3.5.0-0.239.g2a4dd6a23999 is just building and
should be installable via setup shortly.


Corinna

      reply	other threads:[~2023-03-15 21:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 17:51 Jeremy Hetzler
2023-03-15 21:13 ` Corinna Vinschen [this message]

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=ZBI03ydruGCB9Frq@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).