Cosmetic changes to the help output and man page.

[whenjobs.git] / tools / whenjobs.pod

diff --git a/tools/whenjobs.pod b/tools/whenjobs.pod
index fe3041b..25dff40 100644 (file)
--- a/tools/whenjobs.pod
+++ b/tools/whenjobs.pod
@@ -149,13 +149,6 @@ source, eg:
 
  whenjobs --lib $builddir/lib -e
 
-=item B<--start> "job name"
-
-Start the job immediately and unconditionally.
-
-This runs the job even if its normal preconditions are not met.  This
-may cause unexpected results, so use with caution.
-
 =item B<--set> variable value
 
 =item B<--type> bool|int|float|string|unit
@@ -176,6 +169,13 @@ variable when setting it by adding the optional I<--type> parameter:
 See the discussion of variable types in the L</REFERENCE> section
 below.
 
+=item B<--start> "job name"
+
+Start the job immediately and unconditionally.
+
+This runs the job even if its normal preconditions are not met.  This
+may cause unexpected results, so use with caution.
+
 =item B<--upload>
 
 Compile the jobs script and upload it to the daemon, without editing.
@@ -403,6 +403,11 @@ that it had last time this when-job ran.
 
 If the when-job has not run yet, then this returns C<"">.
 
+Job state is preserved across file reloads, but I<only> for jobs that
+are explicitly named.  If you find that jobs using C<prev>, C<changes>
+etc are running unnecessarily when the jobs file is edited or
+uploaded, try giving the jobs an explicit name.
+
 =item B<changes> I<variable>
 
 If the named variable has changed since this job last ran, then this