On Sat, 3 Jun 2000, Adrian Skywalker wrote:
If you must put . into your path, put it _after_ the other entries in your
path, not before, so that the existing command is called before the one in
the current directory.
Just a thought, from an admitted newbie.
Greetings,
Adrian
But a VERY GOOD
For you to use the "configure" command the PATH (not sure yet how to set the
PATH) to THAT dir has to be listed. If you use the "./configure" command it
means to run configure IN the dir your in.
HTH
Jaguar
"Barry Winch" [EMAIL PROTECTED] wrote:
Can someone please explain the concept behind ./
.) for your shell, but I have
never tried (and therefore don't know how).
Half your answer! Maybe... :)
Chris.
-Original Message-
From: Barry Winch [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 31, 2000 6:31 PM
To: [EMAIL PROTECTED]
Subject: [newbie] Command execution
Can someone please
In a message dated 6/1/00 6:19:36 AM Mountain Daylight Time,
[EMAIL PROTECTED] writes:
Can someone please explain the concept behind ./ in executing a command.
If I am in the directory where the programme resides and type the programme
name, I get a:
"bash: programme name: command not
On Thu, 01 Jun 2000, you wrote:
Can someone please explain the concept behind ./ in executing a command.
If I am in the directory where the programme resides and type the programme
name, I get a:
"bash: programme name: command not found" message
If, from the same directory I type
Perhaps the confusion here is that Windows looks in the logged directory
FIRST and executes "namedcommand" if found. If the "namedcommand" is not
found it then searches the path, in order, and executes the first match it
finds. I found this handy and will alter my bash preferences to
I'm not sure if this has been answered yet, so here goes: the '.' before
the slash (./) is sort of a 'wildcard'. It means just look in the directory
that I'm in right now. I'm sure that you're aware that just a plain slash
would mean that you want to look in the root directory for said file.
--- [EMAIL PROTECTED] wrote:
Perhaps the confusion here is that Windows looks in the logged
directory
FIRST and executes "namedcommand" if found. If the "namedcommand" is not
found it then searches the path, in order, and executes the first match it
finds. I found this handy and
Can someone please explain the concept behind ./ in executing a command.
The . tells the system to look in the current directory, it is needed when you
are trying to execute a program or shell script and your working directory is
NOT in you path. The PATH environment variable tells the
Can someone please explain the concept behind ./ in executing a command.
If I am in the directory where the programme resides and type the programme
name, I get a:
"bash: programme name: command not found" message
If, from the same directory I type ./programme name everything works as
Barry,
in command line terms the . is the functional equivalent of "this
directory". The / means the root or main directory off of that
indicated. So in effect the ./means the root of the current
directory. IN simple terms, it means the directory you are in! The
reason you do this is because
Barrywhen you type a command at the prompt a search is
made using your 'path'. If the program is not found in the
'path' you get the command not found error. The current
directory is not scanned unless it is actually in your 'path',
so if it is not you need to tell 'bash' that the program
When you ask your shell to execute a command without telling him where
it is, it looks for it in the directories specified in the $PATH
variable ("echo $PATH" to see it).
When you specify a directory (here : the . directory [=the current
directory]), it will search the command in the specified
When you type in a program to be executed, bash will search for the
programs based on what's in your PATH environmental variable.
If you don't have "./" in your PATH, it won't look there
for the program. Just add "./" to your PATH in .bash_profile, it will fix
the problem. It's a matter of
Barry Winch wrote:
Can someone please explain the concept behind ./ in executing a command.
If I am in the directory where the programme resides and type the programme
name, I get a:
"bash: programme name: command not found" message
This is because your PATH is not defined
in your
On Wed, 31 May 2000, Barry Winch wrote:
Can someone please explain the concept behind ./ in executing a command.
If I am in the directory where the programme resides and type the programme
name, I get a:
"bash: programme name: command not found" message
If, from the same directory I type
16 matches
Mail list logo
