Bad behavior when adding command with the same name as the main command

[DannyBen]

I know this is not maintained (which is sad), but just in case someone picks up maintenance some day, here is a bug that caused me some headache.

The below docopt usage pattern does not work.

Usage:
   run run

Reproduce

Save the below as test.rb

require "docopt"

doc = <<DOCOPT
Usage:
  run ship
  run run

DOCOPT

begin
  p Docopt::docopt(doc)
rescue Docopt::Exit => e
  puts e.message
  exit
end

puts "execution continued"

Then run:

$ ruby test.rb

Expected Behavior

The usage pattern should be displayed, and execution should be halted

Actual Behavior

The execution continues as if a valid usage pattern was provided. Removing the run run usage pattern from the docopt string, restores correct behavior.

I believe the root cause is in #formal_usage

[DannyBen]

Any slim chance that someone can help resolve this?
I am willing to try myself if PRs are accepted.

This is impacting my docopt-based Runfile gem, which has an executable named run.

I am pasting a more realistic example here:

require "docopt"
doc = <<~DOCOPT
  Usage:
    run server start
    run server stop
    run server run
DOCOPT

begin
  pp Docopt::docopt doc
rescue Docopt::Exit => e
  puts e.message
end

Output

# the `run` command is completely omitted
$ ruby test.rb
{"server"=>false, "start"=>false, "stop"=>false}

# ... and not accepted of course
$ ruby test.rb server run
Usage:
  run server start
  run server stop
  run server run

[DannyBen]

Fixed in https://github.com/DannyBen/docopt_ng