(I presume no top-posting on this list so my comments follow in-line.)

 

From: Matthias Meulien [mailto:matthias.meul...@delair-tech.com] 
Sent: November-04-16 9:33 AM
To: Michel LaBarre
Cc: Msys2
Subject: Re: [Msys2-users] Recommendation for non-development users

 

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.

Good to know Matthias.  Thank you.

 

 

 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.

I am aware of these conflicts; there are not many in practice with "find" being 
the most prominent.  

In my current world, I use the MKS Toolkit for my Win 7 systems (and don't want 
to pay for upgrade licenses now that I am retired hence my search for a free 
alternative).

When I am in a shell , I put the MKS bin's ahead of Win32 bins so they take 
precedence which is pretty much always what I want.  

When I am in a CMD, I use an env-var (or a trivial CMD) to fully qualify a 
command invocation if I need the nix variant.

 

(For my own stuff, I am a bit casual about executable paths and names in my 
scripts.

When working professionally, I fully qualify all executables from within a CMD, 
and Win32 executables when in a ksh; i.e. I do not fully qualify unix utilities 
when in a unix shell since I controlled the PATH upon initiating a sh script.)

 

 

-- 

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

Reply via email to