expect script to get its directory ?
up vote
0
down vote
favorite
a bash script can be BASEDIR=$(dirname $0)
but how do I do that in expect script ?
If I use BASEDIR=[dirname $argv0]
I get the error "invalid command name "dirname".
expect
New contributor
add a comment |
up vote
0
down vote
favorite
a bash script can be BASEDIR=$(dirname $0)
but how do I do that in expect script ?
If I use BASEDIR=[dirname $argv0]
I get the error "invalid command name "dirname".
expect
New contributor
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
a bash script can be BASEDIR=$(dirname $0)
but how do I do that in expect script ?
If I use BASEDIR=[dirname $argv0]
I get the error "invalid command name "dirname".
expect
New contributor
a bash script can be BASEDIR=$(dirname $0)
but how do I do that in expect script ?
If I use BASEDIR=[dirname $argv0]
I get the error "invalid command name "dirname".
expect
expect
New contributor
New contributor
New contributor
asked Nov 18 at 7:05
Qiulang
1011
1011
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Various file operations in TCL are organized under the file(n)
procedure which has a dirname
command.
% expect
expect1.1> file dirname $argv0
.
Note however this may not be set, valid, nor checked for validity depending on exactly how the TCL (nor the shell code, for that matter) is run, so you may want error checking; the directory will also vary depending on how the code is run.
% cat dirname
#!/usr/bin/env expect
set basedir [file dirname $argv0]
puts $basedir
% chmod +x dirname
% ./dirname
.
% ~/tmp/dirname
/Users/jhqdoe/tmp
%
Use file normalize
if you always want a fully qualified path.
% expect
expect1.1> set basedir [file normalize [file dirname $argv0]]
/Users/jhqdoe/tmp
There is alo the Tcl_FindExecutable(3)
call, which exposes the executable name (if available) via the info nameofexecutable
command:
% expect
expect1.1> info nameofexecutable
/opt/local/bin/expect
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Various file operations in TCL are organized under the file(n)
procedure which has a dirname
command.
% expect
expect1.1> file dirname $argv0
.
Note however this may not be set, valid, nor checked for validity depending on exactly how the TCL (nor the shell code, for that matter) is run, so you may want error checking; the directory will also vary depending on how the code is run.
% cat dirname
#!/usr/bin/env expect
set basedir [file dirname $argv0]
puts $basedir
% chmod +x dirname
% ./dirname
.
% ~/tmp/dirname
/Users/jhqdoe/tmp
%
Use file normalize
if you always want a fully qualified path.
% expect
expect1.1> set basedir [file normalize [file dirname $argv0]]
/Users/jhqdoe/tmp
There is alo the Tcl_FindExecutable(3)
call, which exposes the executable name (if available) via the info nameofexecutable
command:
% expect
expect1.1> info nameofexecutable
/opt/local/bin/expect
add a comment |
up vote
0
down vote
Various file operations in TCL are organized under the file(n)
procedure which has a dirname
command.
% expect
expect1.1> file dirname $argv0
.
Note however this may not be set, valid, nor checked for validity depending on exactly how the TCL (nor the shell code, for that matter) is run, so you may want error checking; the directory will also vary depending on how the code is run.
% cat dirname
#!/usr/bin/env expect
set basedir [file dirname $argv0]
puts $basedir
% chmod +x dirname
% ./dirname
.
% ~/tmp/dirname
/Users/jhqdoe/tmp
%
Use file normalize
if you always want a fully qualified path.
% expect
expect1.1> set basedir [file normalize [file dirname $argv0]]
/Users/jhqdoe/tmp
There is alo the Tcl_FindExecutable(3)
call, which exposes the executable name (if available) via the info nameofexecutable
command:
% expect
expect1.1> info nameofexecutable
/opt/local/bin/expect
add a comment |
up vote
0
down vote
up vote
0
down vote
Various file operations in TCL are organized under the file(n)
procedure which has a dirname
command.
% expect
expect1.1> file dirname $argv0
.
Note however this may not be set, valid, nor checked for validity depending on exactly how the TCL (nor the shell code, for that matter) is run, so you may want error checking; the directory will also vary depending on how the code is run.
% cat dirname
#!/usr/bin/env expect
set basedir [file dirname $argv0]
puts $basedir
% chmod +x dirname
% ./dirname
.
% ~/tmp/dirname
/Users/jhqdoe/tmp
%
Use file normalize
if you always want a fully qualified path.
% expect
expect1.1> set basedir [file normalize [file dirname $argv0]]
/Users/jhqdoe/tmp
There is alo the Tcl_FindExecutable(3)
call, which exposes the executable name (if available) via the info nameofexecutable
command:
% expect
expect1.1> info nameofexecutable
/opt/local/bin/expect
Various file operations in TCL are organized under the file(n)
procedure which has a dirname
command.
% expect
expect1.1> file dirname $argv0
.
Note however this may not be set, valid, nor checked for validity depending on exactly how the TCL (nor the shell code, for that matter) is run, so you may want error checking; the directory will also vary depending on how the code is run.
% cat dirname
#!/usr/bin/env expect
set basedir [file dirname $argv0]
puts $basedir
% chmod +x dirname
% ./dirname
.
% ~/tmp/dirname
/Users/jhqdoe/tmp
%
Use file normalize
if you always want a fully qualified path.
% expect
expect1.1> set basedir [file normalize [file dirname $argv0]]
/Users/jhqdoe/tmp
There is alo the Tcl_FindExecutable(3)
call, which exposes the executable name (if available) via the info nameofexecutable
command:
% expect
expect1.1> info nameofexecutable
/opt/local/bin/expect
answered Nov 18 at 16:05
thrig
23.6k12955
23.6k12955
add a comment |
add a comment |
Qiulang is a new contributor. Be nice, and check out our Code of Conduct.
Qiulang is a new contributor. Be nice, and check out our Code of Conduct.
Qiulang is a new contributor. Be nice, and check out our Code of Conduct.
Qiulang is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482483%2fexpect-script-to-get-its-directory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown