Moves run from Proc to the independent-routines page

Author: JJ

doc/Type/Proc.pod6

@@ -145,79 +145,6 @@ your idea of a newline is.
 If C<$merge> is set to True, the standard output and error stream end up
 merged in C<$proc.out>.
 
-=head2 sub run
-
-Defined as:
-
-=for code :method
-sub run(
-    *@args ($, *@),
-    :$in = '-',
-    :$out = '-',
-    :$err = '-',
-    Bool :$bin = False,
-    Bool :$chomp = True,
-    Bool :$merge = False,
-    Str:D :$enc = 'UTF-8',
-    Str:D :$nl = "\n",
-    :$cwd = $*CWD,
-    Hash() :$env = %*ENV
---> Proc:D)
-
-Runs an external command I<without involving a shell> and returns a
-L<Proc|/type/Proc> object. By default, the external command will print to
-standard output and error, and read from standard input.
-
-    run 'touch', '>foo.txt'; # Create a file named >foo.txt
-
-    run <<rm >foo.txt>>; # Another way to use run, using word quoting for the
-                         # arguments
-
-If you want to pass some variables you can still use C«< >», but try
-to avoid using C<« »> as it will do word splitting if you forget to
-quote variables:
-
-    my $file = ‘--my arbitrary filename’;
-    run ‘touch’, ‘--’, $file;  # RIGHT
-    run <touch -->, $file;     # RIGHT
-
-    run «touch -- "$file"»;    # RIGHT but WRONG if you forget quotes
-    run «touch -- $file»;      # WRONG; touches ‘--my’, ‘arbitrary’ and ‘filename’
-    run ‘touch’, $file;        # WRONG; error from `touch`
-    run «touch "$file"»;       # WRONG; error from `touch`
-
-Note that C<--> is required for many programs to disambiguate between
-command-line arguments and
-L<filenames that begin with hyphens|https://mywiki.wooledge.org/BashPitfalls#Filenames_with_leading_dashes>.
-
-A sunk L<Proc|/type/Proc> object for a process that L<exited|/routine/exitcode>
-unsuccessfully will throw. If you wish to ignore such failures, simply
-use L<run|/routine/run> in non-sink context:
-
-    run 'false';     # SUNK! Will throw
-    run('false').so; # OK. Evaluates Proc in Bool context; no sinking
-
-If you want to capture standard output or error instead of having it
-printed directly you can use the C<:out> or C<:err> arguments
-respectively, which will make them available using the
-L<C<Proc.out>|/type/Proc> method:
-
-    my $proc = run 'echo', 'Perl 6 is Great!', :out, :err;
-    $proc.out.slurp(:close).say; # OUTPUT: «Perl 6 is Great!␤»
-    $proc.err.slurp(:close).say; # OUTPUT: «␤»
-
-You can use these arguments to redirect them to a filehandle, thus
-creating a kind of I<pipe>:
-
-    my $ls-alt-handle = open :w, '/tmp/cur-dir-ls-alt.txt';
-    my $proc = run "ls", "-alt", :out($ls-alt-handle);
-    # (The file will contain the output of the ls -alt command)
-
-These argument are quite flexible and admit, for instance, handles to
-redirect them. See L<Proc|/type/Proc> and
-L<Proc::Async|/type/Proc::Async> for more details.
-
-See also L<C<new>|/type/Proc#method_new> for more examples.
 
 =head2 method sink
 

doc/Type/independent-routines.pod6

@@ -365,6 +365,80 @@ spurt 'file-that-already-exists', 'new text', :createonly;
 # OUTPUT: «Failed to open file /home/camelia/file-that-already-exists: file already exists …»
 =end code
 
+=head2 sub run
+
+Defined as:
+
+=for code :method
+sub run(
+    *@args ($, *@),
+    :$in = '-',
+    :$out = '-',
+    :$err = '-',
+    Bool :$bin = False,
+    Bool :$chomp = True,
+    Bool :$merge = False,
+    Str:D :$enc = 'UTF-8',
+    Str:D :$nl = "\n",
+    :$cwd = $*CWD,
+    Hash() :$env = %*ENV
+--> Proc:D)
+
+Runs an external command I<without involving a shell> and returns a
+L<Proc|/type/Proc> object. By default, the external command will print to
+standard output and error, and read from standard input.
+
+    run 'touch', '>foo.txt'; # Create a file named >foo.txt
+
+    run <<rm >foo.txt>>; # Another way to use run, using word quoting for the
+                         # arguments
+
+If you want to pass some variables you can still use C«< >», but try
+to avoid using C<« »> as it will do word splitting if you forget to
+quote variables:
+
+    my $file = ‘--my arbitrary filename’;
+    run ‘touch’, ‘--’, $file;  # RIGHT
+    run <touch -->, $file;     # RIGHT
+
+    run «touch -- "$file"»;    # RIGHT but WRONG if you forget quotes
+    run «touch -- $file»;      # WRONG; touches ‘--my’, ‘arbitrary’ and ‘filename’
+    run ‘touch’, $file;        # WRONG; error from `touch`
+    run «touch "$file"»;       # WRONG; error from `touch`
+
+Note that C<--> is required for many programs to disambiguate between
+command-line arguments and
+L<filenames that begin with hyphens|https://mywiki.wooledge.org/BashPitfalls#Filenames_with_leading_dashes>.
+
+A sunk L<Proc|/type/Proc> object for a process that L<exited|/routine/exitcode>
+unsuccessfully will throw. If you wish to ignore such failures, simply use
+L<run|/routine/run> in non-sink context:
+
+    run 'false';     # SUNK! Will throw
+    run('false').so; # OK. Evaluates Proc in Bool context; no sinking
+
+If you want to capture standard output or error instead of having it
+printed directly you can use the C<:out> or C<:err> arguments
+respectively, which will make them available using the
+L<C<Proc.out>|/type/Proc> method:
+
+    my $proc = run 'echo', 'Perl 6 is Great!', :out, :err;
+    $proc.out.slurp(:close).say; # OUTPUT: «Perl 6 is Great!␤»
+    $proc.err.slurp(:close).say; # OUTPUT: «␤»
+
+You can use these arguments to redirect them to a filehandle, thus
+creating a kind of I<pipe>:
+
+    my $ls-alt-handle = open :w, '/tmp/cur-dir-ls-alt.txt';
+    my $proc = run "ls", "-alt", :out($ls-alt-handle);
+    # (The file will contain the output of the ls -alt command)
+
+These argument are quite flexible and admit, for instance, handles to
+redirect them. See L<Proc|/type/Proc> and
+L<Proc::Async|/type/Proc::Async> for more details.
+
+See also L<C<new>|/type/Proc#method_new> for more examples.
+
 =head2 sub shell
 
     sub shell($cmd --> Proc)