From: Jakub Wilk Date: Mon, 17 Dec 2018 17:04:29 +0000 (+0100) Subject: fixed typos X-Git-Tag: 20190601~37^2^2 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=7b824e3ba179479b3234c8baf33cd13c3459be66;p=perltidy.git fixed typos --- diff --git a/bin/perltidy b/bin/perltidy index 1529788b..0ca2fbff 100755 --- a/bin/perltidy +++ b/bin/perltidy @@ -1923,7 +1923,7 @@ Here is an example illustrating a welded container within a welded containers: This format option is quite general but there are some limitations. -One limitiation is that any line length limit still applies and can cause long +One limitation is that any line length limit still applies and can cause long welded sections to be broken into multiple lines. Another limitation is that an opening symbol which delimits quoted text cannot @@ -2149,7 +2149,7 @@ controls can be used: The flag B<-sot> is an abbreviation for B<-sop -sohb -sosb>. -The flag B<-sobb> is a abbreviation for B<-bbvt=2 -bbvtl='*'>. This +The flag B<-sobb> is an abbreviation for B<-bbvt=2 -bbvtl='*'>. This will case a cascade of opening block braces to appear on a single line, although this an uncommon occurrence except in test scripts. diff --git a/docs/Tidy.html b/docs/Tidy.html index eb5b16cd..51b92fad 100644 --- a/docs/Tidy.html +++ b/docs/Tidy.html @@ -136,7 +136,7 @@
dump_options
-

If the dump_options parameter is given, it must be the reference to a hash. In this case, the parameters contained in any perltidyrc configuration file will be placed in this hash and perltidy will return immediately. This is equivalent to running perltidy with --dump-options, except that the perameters are returned in a hash rather than dumped to standard output. Also, by default only the parameters in the perltidyrc file are returned, but this can be changed (see the next parameter). This parameter provides a convenient method for external programs to read a perltidyrc file. An example program using this feature, perltidyrc_dump.pl, is included in the distribution.

+

If the dump_options parameter is given, it must be the reference to a hash. In this case, the parameters contained in any perltidyrc configuration file will be placed in this hash and perltidy will return immediately. This is equivalent to running perltidy with --dump-options, except that the parameters are returned in a hash rather than dumped to standard output. Also, by default only the parameters in the perltidyrc file are returned, but this can be changed (see the next parameter). This parameter provides a convenient method for external programs to read a perltidyrc file. An example program using this feature, perltidyrc_dump.pl, is included in the distribution.

Any combination of the dump_ parameters may be used together.

@@ -193,7 +193,7 @@

Parameters which control formatting may be passed in several ways: in a .perltidyrc configuration file, in the perltidyrc parameter, and in the argv parameter.

-

The -syn (--check-syntax) flag may be used with all source and destination streams except for standard input and output. However data streams which are not associated with a filename will be copied to a temporary file before being be passed to Perl. This use of temporary files can cause somewhat confusing output from Perl.

+

The -syn (--check-syntax) flag may be used with all source and destination streams except for standard input and output. However data streams which are not associated with a filename will be copied to a temporary file before being passed to Perl. This use of temporary files can cause somewhat confusing output from Perl.

If the -pbp style is used it will typically be necessary to also specify a -nst flag. This is necessary to turn off the -st flag contained in the -pbp parameter set which otherwise would direct the output stream to the standard output.

diff --git a/docs/perltidy.html b/docs/perltidy.html index b835b9b6..aa141b77 100644 --- a/docs/perltidy.html +++ b/docs/perltidy.html @@ -1530,7 +1530,7 @@

This format option is quite general but there are some limitations.

-

One limitiation is that any line length limit still applies and can cause long welded sections to be broken into multiple lines.

+

One limitation is that any line length limit still applies and can cause long welded sections to be broken into multiple lines.

Another limitation is that an opening symbol which delimits quoted text cannot be included in a welded pair. This is because quote delimiters are treated specially in perltidy.

@@ -1705,7 +1705,7 @@

The flag -sot is an abbreviation for -sop -sohb -sosb.

-

The flag -sobb is a abbreviation for -bbvt=2 -bbvtl='*'. This will case a cascade of opening block braces to appear on a single line, although this an uncommon occurrence except in test scripts.

+

The flag -sobb is an abbreviation for -bbvt=2 -bbvtl='*'. This will case a cascade of opening block braces to appear on a single line, although this an uncommon occurrence except in test scripts.

-sct, --stack-closing-tokens and related flags
diff --git a/lib/Perl/Tidy.pod b/lib/Perl/Tidy.pod index a9a3dcdb..0ebc27be 100644 --- a/lib/Perl/Tidy.pod +++ b/lib/Perl/Tidy.pod @@ -129,7 +129,7 @@ command line string. If the B parameter is given, it must be the reference to a hash. In this case, the parameters contained in any perltidyrc configuration file will be placed in this hash and perltidy will return immediately. This is -equivalent to running perltidy with --dump-options, except that the perameters +equivalent to running perltidy with --dump-options, except that the parameters are returned in a hash rather than dumped to standard output. Also, by default only the parameters in the perltidyrc file are returned, but this can be changed (see the next parameter). This parameter provides a convenient method @@ -214,7 +214,7 @@ B parameter. The B<-syn> (B<--check-syntax>) flag may be used with all source and destination streams except for standard input and output. However data streams which are not associated with a filename will -be copied to a temporary file before being be passed to Perl. This +be copied to a temporary file before being passed to Perl. This use of temporary files can cause somewhat confusing output from Perl. If the B<-pbp> style is used it will typically be necessary to also diff --git a/local-docs/perltidy.1 b/local-docs/perltidy.1 index 621e3915..de2db415 100644 --- a/local-docs/perltidy.1 +++ b/local-docs/perltidy.1 @@ -2051,7 +2051,7 @@ Here is an example illustrating a welded container within a welded containers: .Sp This format option is quite general but there are some limitations. .Sp -One limitiation is that any line length limit still applies and can cause long +One limitation is that any line length limit still applies and can cause long welded sections to be broken into multiple lines. .Sp Another limitation is that an opening symbol which delimits quoted text cannot @@ -2281,7 +2281,7 @@ controls can be used: .Sp The flag \fB\-sot\fR is an abbreviation for \fB\-sop \-sohb \-sosb\fR. .Sp -The flag \fB\-sobb\fR is a abbreviation for \fB\-bbvt=2 \-bbvtl='*'\fR. This +The flag \fB\-sobb\fR is an abbreviation for \fB\-bbvt=2 \-bbvtl='*'\fR. This will case a cascade of opening block braces to appear on a single line, although this an uncommon occurrence except in test scripts. .IP "\fB\-sct\fR, \fB\-\-stack\-closing\-tokens\fR and related flags" 4