FWIW, one user's opinion, I find MSYS2 very useful, both for compiling, and for use as a general-purpose command line system (non-development). You just have to try it. When using MSYS2 for compiling, I always use it from within the MSYS2 shell (mintty window). I believe that is required. When using MSYS2 as general-purpose command line system, I also typically use it from within the mintty window. Daniel
On 11/4/2016 7:26 AM, William Kappler wrote: > I have no issue running the Windows CMD with MSYS2's binaries in my > PATH. They probably do conflict, but I've never seen any negative > effects from it. If you make heavy use of shell scripting, I could see > it being a bad idea. > > I would recommend using the MSYS2 shell, though. It is better in a few > ways than CMD. > > > :-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- > *William E. Kappler II* > Software Engineer > Applied Research Associates / Bennett Aerospace > LinkedIn <https://www.linkedin.com/in/williamkappler> · Project Website > <http://onathacar.fredlawl.com/>· SourceForge > <https://sourceforge.net/u/william-kappler/profile/> > > On Fri, Nov 4, 2016 at 9:33 AM, Matthias Meulien > <matthias.meul...@delair-tech.com > <mailto:matthias.meul...@delair-tech.com>> wrote: > > 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 > <mailto:Msys2-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/msys2-users > <https://lists.sourceforge.net/lists/listinfo/msys2-users> > > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
