[beginner] Why nothing is printed to stdout ?

[Graham Fawcett]

On Tue, 01 Nov 2011 12:18:02 -0700, Jonathan M Davis wrote:

> On Tuesday, November 01, 2011 18:23:52 Graham Fawcett wrote:
>> On Tue, 01 Nov 2011 07:27:44 -0400, Kagamin wrote:
>> > Steven Schveighoffer Wrote:
>> >> Oh I remember doing that too :)  Don't feel bad, everyone does this
>> >> at least once.  I hate that stupid test builtin, nobody ever uses it
>> >> anymore.
>> >> 
>> >> Note, it's not a command line tool, it's a shell builtin, which is
>> >> why it overrides anything in your search path.
>> >> 
>> >> I've since adopted the habit of calling test programs "testme"
>> >> instead of "test" :)
>> > 
>> > Huh, must port windows console to linux ^_^
>> 
>> Too much work! Just put
>> 
>>   alias test='./test'
>> 
>> in your .profile, and be happy. :)
> 
> Though if you don't get used to putting ./ in front of the names of
> binaries that you're running in the current directory, you're going to
> have other problems. The suggestion does fix the occasional screw-up
> with that particular command though.

Agreed; if you're going to use a system, learn how to use it properly.

Then again, there's no shame in using "training wheels" if you're an 
absolute beginner. When I started using Unix, I was glad that the "dir" 
command was available on the system I was using. (I'm not sure if it was 
a binary, or whether a kindly sysop had provided an alias to "ls" for us 
Windows users). Learning is a journey of many small steps!

Graham