From: Steve Hancock <perltidy@users.sourceforge.net>
Date: Thu, 30 May 2019 14:47:20 +0000 (-0700)
Subject: fix comment
X-Git-Tag: 20190601~2
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=41fbe5561bb4b008a3992687f4a9605875ee4df1;p=perltidy.git

fix comment
---

diff --git a/lib/Perl/Tidy.pm b/lib/Perl/Tidy.pm
index 55af333c..bc2c1a12 100644
--- a/lib/Perl/Tidy.pm
+++ b/lib/Perl/Tidy.pm
@@ -1350,18 +1350,18 @@ EOM
                         }
                     }
 
-		    # Make the output file writable unless we are in -b mode.
-		    # The reason is that perltidy does not unlink existing
-		    # output files before writing to them, for safety, so if an
-		    # existing output file is marked not writable then perltidy
-		    # will stop. This can prevent a disaster for a user who
-		    # accidentally enters "-o important_data", but it also
-		    # means that perltidy may fail when rerun with its default
-		    # output file unless it marks its own output files
-		    # writable. The alternative, of always unlinking the
-		    # designated output file, is unsafe, except in -b mode,
-		    # where there is an assumption that a previous backup can
-		    # be unlinked even if not writable.
+                    # Make the output file writable unless we are in -b mode.
+                    # The reason is that perltidy does not unlink existing
+                    # output files before writing to them, for safety, so if an
+                    # existing output file is marked not writable then perltidy
+                    # will stop. This can prevent a disaster for a user who
+                    # accidentally enters "-o important_data", but it also
+                    # means that perltidy may fail when rerun with its default
+                    # output file unless it marks its own output files
+                    # writable. The alternative, of always unlinking the
+                    # designated output file, is unsafe, except in -b mode,
+                    # where there is an assumption that a previous backup can
+                    # be unlinked even if not writable.
                     if ( !$in_place_modify ) {
                         $output_file_permissions |= oct(600);
                     }