Remove repo completion for url+open subcommands

    git hub url file<TAB>

Since the argument can be a repo or a local file, we remove the
repo completion here.

Author: perlpunk

ReadMe.pod

@@ -230,8 +230,7 @@ Most of the commands described below have arguments. This section defines each
 of the argument types. Note that argument values that are strings containing
 whitespace need to be quoted.
 
-Argument variable names are always indicated by angle brackets, like: C<<
-<variable> >>. Arguments listed in square brackets are optional and arguments
+Argument variable names are always indicated by angle brackets, like: C<<<variable> >>. Arguments listed in square brackets are optional and arguments
 followed by C<...> indicate that more than one is allowed.
 
 =over
@@ -577,8 +576,7 @@ issue instead of creating a new one.
 
 If the default remote is a fork, the pull request will target the default
 branch of the parent repository. Otherwise the pull request will target the
-default branch of the default remote itself. Use C<--remote>, C<--branch>, C<--
-parent>, and C<--base> options to change the default source remote, source
+default branch of the default remote itself. Use C<--remote>, C<--branch>, C<--parent>, and C<--base> options to change the default source remote, source
 branch, target remote and target branch (respectively).
 
 This command will open an editor like C<git commit> does. To avoid that you
@@ -709,17 +707,15 @@ This will create a gist with a file '.gitignore'
 
 Search for repositories.
 
-By default it searches in the repository name, but you can change that: C<search-
-repo "libyaml in:description">. For more information, see the search
+By default it searches in the repository name, but you can change that: C<search-repo "libyaml in:description">. For more information, see the search
 documentation at
 L<https://developer.github.com/v3/search/#search-repositories>
 
 =item C<< search-user <query> >>
 
 Search for users.
 
-By default it searches in the login field, but you can change that: C<search-
-user "wall in:fullname">. For more information, see the search documentation
+By default it searches in the login field, but you can change that: C<search-user "wall in:fullname">. For more information, see the search documentation
 at L<https://developer.github.com/v3/search/#search-users>
 
 =item C<< search-issues <query> >>
@@ -1000,8 +996,7 @@ these commands (the C<git hub setup> command automates this):
 
 You can also see all your tokens on the web at L<thispage|https://github.com/settings/applications>.
 
-You can specify your API token to C<git hub> on the commandline with C<--
-token=...> or in the C<GIT_HUB_API_TOKEN> environment variable, but the
+You can specify your API token to C<git hub> on the commandline with C<--token=...> or in the C<GIT_HUB_API_TOKEN> environment variable, but the
 easiest thing to do is just set it in the git-hub config.
 
 Certain token B<scopes> are required for various GitHub API operations. Make
@@ -1050,8 +1045,7 @@ is stale, you may want to try these options:
 
 =head1 Colors
 
-You can have colored output. You can activate that by setting C<git hub config
-color auto>. It accepts the same values as C<git config color.ui> itself.
+You can have colored output. You can activate that by setting C<git hub configcolor auto>. It accepts the same values as C<git config color.ui> itself.
 
 =head1 Examples
 
@@ -1108,11 +1102,9 @@ Assume your current working directory is not a GitHub repo:
     $ # etc...
 
 The C<git hub> command tries to be environmentally aware. If you are in a
-GitHub cloned repo directory, and you don't specify C<< <user> >> or C<<
-<owner> >> or C<< <repo> >> for a command that needs them, then they will be
+GitHub cloned repo directory, and you don't specify C<< <user> >> or C<<<owner> >> or C<< <repo> >> for a command that needs them, then they will be
 pulled from the remote url. Otherwise, if you don't specify a C<< <user> >> it
-will use the one (presumably yours) that you set with the C<git hub config
-login ...> command.
+will use the one (presumably yours) that you set with the C<git hub configlogin ...> command.
 
 =head2 Example 3. Building Complex Commands
 

man/man1/git-hub.1

@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 4.10 (Pod::Simple 3.35)
+.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.35)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -71,7 +71,7 @@
 .\" ========================================================================
 .\"
 .IX Title "STDIN 1"
-.TH STDIN 1 "July 2022" "Generated by Swim v0.1.48" "The Git command for GitHub"
+.TH STDIN 1 "August 2022" "Generated by Swim v0.1.48" "The Git command for GitHub"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l

share/completion.bash

@@ -5,7 +5,7 @@
 _git_hub() {
     local _opts=" -h --help --remote= --branch= --sha= --org= --method= --title= --msg= -c= --count= -a --all -q --quiet -v --verbose -r --raw -j --json -A --use-auth -C --no-cache --token= -d --dryrun -T -O -H -J -R -x"
     local subcommands="cache-clear clone collabs comment config config-keys config-list config-unset follow followers following follows fork forks gist gist-clone gist-delete gist-edit gist-fork gist-get gist-init gist-new gist-star gist-unstar gists git-hub-travis help info irc-enable irc-enable irc-url issue issue-close issue-edit issue-new issue-resolve issues keys keys-add member-add member-get member-remove members notify-list open org org-edit org-get org-members org-repos orgs pr-created pr-diff pr-fetch pr-involves pr-list pr-merge pr-new pr-queue repo repo-delete repo-edit repo-get repo-init repo-new repos scope-add scope-remove scopes search-issues search-repo search-user setup star starred stars team team-delete team-members team-new team-repo-add team-repos teams token-delete token-get token-new tokens trust unfollow unstar untrust unwatch upgrade url user user-edit user-get version watch watchers watching"
-    local repocommands="clone collabs comment fork forks issue issue-close issue-edit issue-new issue-resolve issues open pr-diff pr-fetch pr-list pr-merge repo repo-delete repo-edit repo-get star stars trust unstar untrust unwatch url watch watchers"
+    local repocommands="clone collabs comment fork forks issue issue-close issue-edit issue-new issue-resolve issues pr-diff pr-fetch pr-list pr-merge repo repo-delete repo-edit repo-get star stars trust unstar untrust unwatch watch watchers"
     local subcommand="$(__git_find_on_cmdline "$subcommands")"
 
     if [ -z "$subcommand" ]; then

share/zsh-completion/_git-hub

@@ -54,7 +54,7 @@ _git-hub() {
     ;;
     repo)
         case $line[1] in
-        clone|collabs|comment|fork|forks|issue|issue-close|issue-edit|issue-new|issue-resolve|issues|open|pr-diff|pr-fetch|pr-list|pr-merge|repo|repo-delete|repo-edit|repo-get|star|stars|trust|unstar|untrust|unwatch|url|watch|watchers)
+        clone|collabs|comment|fork|forks|issue|issue-close|issue-edit|issue-new|issue-resolve|issues|pr-diff|pr-fetch|pr-list|pr-merge|repo|repo-delete|repo-edit|repo-get|star|stars|trust|unstar|untrust|unwatch|watch|watchers)
             [[ "$line[2]" =~ ^- ]] && return;
             local repo_to_complete="$line[2]"
             if [[ "$repo_to_complete" =~ "^@/?$" || \

tool/generate-completion.pl

@@ -49,6 +49,7 @@ sub main {
             or die "Bad usage: '$text'";
         (my $name = $usage) =~ s/ .*//;
         push @list, $name;
+        next if $name =~ m/^(open|url)$/; # arg can also be a local file
         if ($usage =~ m#\Q$name\E \(?\[?(<owner>/)?\]?<repo>#) {
             push @repo_cmds, $name;
         }