Hello hadrons and welcome to the monastery and to the wonderful world of perl!
I'm a bit late but I add my own solution: put these programs in your PATH infact you can use gnuwin32 or UnxUtils as I've done since years.
They are really useful and make the poor cmd.exe experience a bit easier to survive to. That said a plain perl solution is by far better in terms of portability.
In your PATH order matters:
C> path
PATH=
C:\EX_D\ulisseDUE\perl5.26.64bit\perl\site\bin; # strawberry perl
+portable
C:\EX_D\ulisseDUE\perl5.26.64bit\perl\bin; # strawberry perl
+portable
C:\EX_D\ulisseDUE\perl5.26.64bit\c\bin; # strawberry perl
+portable
C:\EX_D\ulisseDUE\bin\UnxUtils\usr\local\wbin; # <---------------
+-------- UnxUtils
C:\WINDOWS; # OS
C:\WINDOWS\system32; # OS
C> ls C:\EX_D\ulisseDUE\bin\UnxUtils\usr\local\wbin | grep -E "grep|mv
+|cat|rm"
agrep.exe
cat.exe
egrep.exe
fgrep.exe
grep.exe
mv.exe
mvdir.exe
rm.exe
rman.exe
rmdir.exe
zcat.exe
Just one big caveat: be sure to have the right make (or dmake, gmake..) in front in your path:
L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|