@@ -27,7 +27,7 @@ cases not compatible:
27
27
28
28
The only solution here is to avoid mixing Unix/Cygwin and native tools outside
29
29
of makepkg (preferred) or convert them when they get passed between the
30
- different programs. For the latter MSYS2 provides an automatic conversion that
30
+ different programs. For the latter, MSYS2 provides an automatic conversion that
31
31
just works automatically in many cases.
32
32
33
33
## Manual Unix ⟷ Windows Path Conversion
@@ -49,9 +49,9 @@ C:\msys64\mingw64\bin
49
49
50
50
### Process Arguments
51
51
52
- When calling native executables from the context of Cygwin then all the
52
+ When calling native executables from the context of Cygwin, then all the
53
53
arguments that look like Unix paths will get auto converted to Windows. For
54
- example when calling native Python from the context of bash:
54
+ example, when calling native Python from the context of bash:
55
55
56
56
``` shell
57
57
$ python3 -c " import sys; print(sys.argv)" --dir=/foo
@@ -60,9 +60,9 @@ $ python3 -c "import sys; print(sys.argv)" --dir=/foo:/bla
60
60
[' -c' , ' --dir=C:\\msys64\\foo;C:\\msys64\\bla' ]
61
61
```
62
62
63
- While this is helpful in many cases it's also not perfect and in corner cases
63
+ While this is helpful in many cases, it's also not perfect and in corner cases
64
64
converts arguments that look like Unix paths while they are not, or detects
65
- lists of Unix paths where there are none. For these cases you can exclude
65
+ lists of Unix paths where there are none. For these cases, you can exclude
66
66
certain arguments via the ` MSYS2_ARG_CONV_EXCL ` environment variable:
67
67
68
68
``` shell
@@ -98,9 +98,9 @@ one or more environment variable prefixes separated by `;`, like
98
98
` MSYS2_ENV_CONV_EXCL=FOO;BAR;/test ` . It matches the prefix against the following
99
99
string ` KEY=VALUE ` .
100
100
101
- Cygwin special cases some environment variables that are known to be paths or
102
- path lists and does less guessing with them. For example ` HOME ` will never be
103
- interpreted as a path list even if it contains ` : ` .
101
+ Cygwin treats certain environment variables that are known to be paths or path
102
+ lists as special cases and does less guessing with them. For example, ` HOME ` will
103
+ never be interpreted as a path list even if it contains ` : ` .
104
104
105
105
## Windows ⟶ Unix Path Conversion
106
106
0 commit comments