kill: remove the --table long option

[Managor]

• The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
• The page(s) have at most 8 examples.
• The page description(s) have links to documentation or a homepage.
• The page(s) follow the content guidelines.
• The PR title conforms to the recommended templates.
• Version of the command being documented (if known):
  2.40.2

[Managor]

Not sure what the manual page is on about, --table option does not work.

[acuteenvy]

Not sure what the manual page is on about, --table option does not work.

It works for me.

$ kill --table
1 HUP      2 INT      3 QUIT     4 ILL      5 TRAP     6 ABRT     6 IOT      7 BUS      8 FPE      9 KILL    10 USR1    11 SEGV    12 USR2    13 PIPE    14 ALRM    15 TERM    16 STKFLT  17 CHLD
17 CLD     18 CONT    19 STOP    20 TSTP    21 TTIN    22 TTOU    23 URG     24 XCPU    25 XFSZ    26 VTALRM  27 PROF    28 WINCH   29 IO      29 POLL    30 PWR     31 SYS     34 RTMIN   64 RTMAX
$ kill -L
<same output as above>

I'm on the same version as you (2.40.2). What does kill --table print on your system?

[Managor]

kill --table
-bash: kill: -table: invalid signal specification

[acuteenvy]

This page and man kill document kill from util-linux, but you seem to be using the bash builtin kill.
Try enable -n kill && kill --table.

I guess we have to edit the page to somehow mention it.

[Managor]

That seems to indeed be the case. enable -n kill && kill --table works as expected and prints the signals.

[cyqsimon]

This page and man kill document kill from util-linux, but you seem to be using the bash builtin kill. Try enable -n kill && kill --table.

I guess we have to edit the page to somehow mention it.

Very interesting! I did not know that.

Running kill --help (the shell builtin) gives the following justification, which does make sense.

Kill is a shell builtin for two reasons: it allows job IDs to be used
instead of process IDs, and allows processes to be killed if the limit
on processes that you can create is reached.

[sebastiaanspeck]

A friendly reminder that this PR is still open. Waiting for a decision or a commit

[Managor]

I'm thinking that we should pass this PR because the result would be more universal and then create an issue to either think about it later or forget about it.
@acuteenvy Can you create an issue about this?