>
> Ideally I would like to use normal windows paths. e.g. (as a completely
> artificial example)
>
> find d:/mystuff -name "zot*.txt" -print -exec diff {} 'c:\temp\my
> original zot.txt' \; > foo
>
> One reason for being able to use windows-syntax for paths is copying the
> path to a file from an explorer window into a command
>
> being composed.
>
When you drag and drop a file icon from the explorer to one of the msys2
tty, the path name is converted to UNIX style. So it can be consumed as is
by all MSYS2 tools.
> Ideally I would like to be able to invoke all the unix tools from either
> a sh or CMD.
>
Then you'll have conflict issues: find is defined by both environment. I'd
recommand to use one environment at once.
--
Matthias Meulien
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Msys2-users mailing list
Msys2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/msys2-users
