comment on

Thanks for the defense, ++ikegami. :-) I was at least ambiguous: in the modern world of Microsoft pushing PowerShell and de-emphasizing (even taking it out of extended context menus) cmd.exe, I need to train myself to be explicit about testing in cmd (though in this case, the cmd vs ps behavior was effectively the same), so I also ++footpad :-). (Besides, my "in windows" mindset is still often muddied by using gnuwin32 ports to make cmd.exe more usable, and I have to be careful to not include that in pure-windows advice without pointing it out. :-) )

edit: And yes, I understand ikegami's main point wasn't just my defense / validating my ego. ;-) I love the back and forth, with the additional information, and corrections when things are incomplete, ambiguous, or downright wrong. I have learned from this thread, and hope the OP has as well. (When I think I can help the OP, or when I want something clarified to help me learn, or both, are my usual times to participate.)

In reply to Re^6: beginners trap: one liner by pryrt
in thread solved: beginners trap: one liner by toohoo

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks