another noobee thing

This orders the shell to look into your current directory (that is ".")

is it?. thanks for the info.
But, in that way, a executable in that should work, without giving '.' , right?
means, why we need to mention the current dir location, while we are already in the dir, where the binary file is present?

I think all binay executables need "./" to run, unless they are in /bin or /sbin.

Just my opinion. correct me if I am wrong Marc
BTW, that "&&" logic you used to explain is, Good.

Quoting still doesn't work (as neither does most of the forum functionallity).

The shells that follow the POSIX standard look in your PATH variable for binary files to execute. In a regular *nix configuration the current working directory (shown by $PWD as in Print Working Directory) is not in the PATH variable and that's why binaries are not found when you try to execute them without the "./"

When you type the "./" you are doing something like:

PATH=./:$PATH

Effectevely adding your current direcory to the PATH. From then on you can run binaries in your current directory

If you really want to run binaries without the "./" you could add the current directory to your PATH with something like

export PATH=$PWD:$PATH

NOTICE: security risk!

To go even deeper into this: the "." is just a file with the inode number of your current directory, i.e. the same as $PWD

Try this:

diff <(stat . ) <(stat $PWD)

And you'll see that the only difference is the name!

Regards