Codebase list libgetopt-argvfile-perl / b4bc8f1
Fix typos in POD Florian Schlichting 7 years ago
2 changed file(s) with 109 addition(s) and 0 deletion(s). Raw diff Collapse all Expand all
0 spelling.patch
0 Description: fix typos
1 Author: Florian Schlichting <fsfs@debian.org>
2
3 --- a/ArgvFile.pm
4 +++ b/ArgvFile.pm
5 @@ -173,7 +173,7 @@
6 =item Simple access to typical calling scenarios
7
8 If several options need to be set, but in certain circumstances
9 -are always the same, it could become sligthly nerveracking to type
10 +are always the same, it could become slightly nerveracking to type
11 them in again and again. With an option file, they can be stored
12 I<once> and recalled easily as often as necessary.
13
14 @@ -186,7 +186,7 @@
15 are a few user groups with different but typical ways to call your script.
16 In all these cases, option files may collect options belonging together,
17 and may be combined by the script users to set up a certain call.
18 -In conjunction with the possiblity to I<nest> such collections, this is
19 +In conjunction with the possibility to I<nest> such collections, this is
20 perhaps the most powerful feature provided by this method.
21
22 =item Individual and installationwide default options
23 @@ -294,7 +294,7 @@
24
25 Except for the traditional loading, the complete interface of C<argvFile()>
26 is available via C<use>, but in the typical C<use> syntax without
27 -parantheses.
28 +parentheses.
29
30 # implicit call of argvFile(default=>1, home=>1)
31 use Getopt::ArgvFile default=>1, home=>1;
32 @@ -316,7 +316,7 @@
33
34 B<Basics>
35
36 -An option file hint is simply the filename preceeded by (at least) one
37 +An option file hint is simply the filename preceded by (at least) one
38 "@" character:
39
40 > script -optA argA -optB @optionFile -optC argC
41 @@ -406,25 +406,25 @@
42 into @ARGV.
43
44
45 -B<Relative pathes>
46 +B<Relative paths>
47
48 -Pathes in option files might be relative, as in
49 +Paths in option files might be relative, as in
50
51 -file ../file @../../configs/nested
52
53 If written with the (prepared) start directory in mind, that will work,
54 but it can fail when it was written relatively to the option file location
55 -because by default those pathes will not be resolved when written from
56 +because by default those paths will not be resolved when written from
57 an option file.
58
59 Use parameter C<resolveRelativePathes> to switch to path resolution:
60
61 argvFile(resolveRelativePathes=>1);
62
63 -will cause C<argvFile()> to expand those pathes, both in standard strings
64 +will cause C<argvFile()> to expand those paths, both in standard strings
65 and nested option files.
66
67 - With resolveRelativePathes, both pathes
68 + With resolveRelativePathes, both paths
69 will be resolved:
70
71 -file ../file @../../configs/nested
72 @@ -434,7 +434,7 @@
73
74 B<Environment variables>
75
76 -Similar to relative pathes, environment variables are handled differently
77 +Similar to relative paths, environment variables are handled differently
78 depending if the option is specified at the commandline or from an option
79 file, due to bypassed shell processing. By default, C<argvFile()> does
80 not resolve environment variables. But if required it can be commanded
81 @@ -453,7 +453,7 @@
82 I<current option script> is searched in the current directory.
83
84 By default, all startup option files are expected to be named like
85 -the script, preceeded by a dot, but this can be adapted to individual
86 +the script, preceded by a dot, but this can be adapted to individual
87 needs if preferred, see below.
88
89 Examples:
90 @@ -809,7 +809,7 @@
91 }
92 }
93
94 - # resolve relative pathes, if requested
95 + # resolve relative paths, if requested
96 if (exists $switches{resolveRelativePathes})
97 {
98 # process all strings
99 @@ -931,7 +931,7 @@
100
101 use Getopt::ArgvFile justload=>1;
102
103 -See I<FUNCTIONS> for additional informations.
104 +See I<FUNCTIONS> for additional information.
105
106 =head1 NOTES
107