On Thu 26 Feb 04, 1:49 PM, Doctorcam <[EMAIL PROTECTED]> said: > * Jeff Newmiller ([EMAIL PROTECTED]) wrote: > <snip> > > > > The behavior of the first token on a bash commandline is different than > > its behavior when provided as the argument to an instance of bash... bash > > interprets the _argument_ as a normal path to a script file... which > > amounts to allowing invocation of shell scripts in the current directory. > > When provided as the first token on a commandline, bash is more cautious > > if no slashes are present. > > > > So, just so I understand the reasoning, instead of my blind rote > fumbling, do I understand correctly that the function of the ./ is > merely to identify the directory? Is there more to this than that? I > had the assumption that its function was to identify the following > item as an executable. not an executable. it refers to a directory - a component of a path.
vi ./myfile.txt rm -rf ./.. touch ./* pete -- Make everything as simple as possible, but no simpler. -- Albert Einstein GPG Instructions: http://www.dirac.org/linux/gpg GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D _______________________________________________ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
