# Re: Command Line Processing / Pipes

**URL:** <https://www.ruby-forum.com/t/re-command-line-processing-pipes/61019>\
**Category:** Ruby\
**Created:** [May 19, 2006, 10:13am UTC](https://www.ruby-forum.com/t/re-command-line-processing-pipes/61019 "2006-05-19T10:13:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![stuart\_holden](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/7993a0/32.png) [@stuart\_holden](https://www.ruby-forum.com/u/stuart_holden)\
**Post date:** [May 19, 2006, 10:13am UTC](https://www.ruby-forum.com/t/re-command-line-processing-pipes/61019/1 "2006-05-19T10:13:48Z")

</div>

Hi,

Yes, when I explicitly call ruby rather than rely on the file  
association it works as I would expect. I don’t understand why the  
exception is thrown when ruby isn’t explicitly invoked - as x1 mentioned  
it got to Ruby. The file association step seems to mess everything up.  
Windows never was very good with its command line - ho hum.

This now does what I’d like so I’m very happy. Chris, Robert, A LeDonne,  
x1 and Pit Captain - Thanks!