Bug #850
isogmt can not run script
| Status: | Closed | Start date: | 2016-01-23 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 100% | ||
| Category: | - | |||
| Target version: | Candidate for next bugfix release | |||
| Affected version: | 5.2-svn | Platform: | Linux |
Description
$ isogmt sh test.sh ... ... ERROR: No module named sh was found. This could mean one of three things: ... ...
Associated revisions
Check is command given to isogmt is a module.
This fixes issue #850.
Merge from ^/branches/5.2.2
Check if command given to isogmt is a module.
This fixes issue #850.
History
#1
Updated by Paul over 1 year ago
- Status changed from New to In Progress
I cannot see how the current script could possibly run anything but a module since it always starts with gmt $*.
Could you change
gmt "$@"
to just
"$@"
and let me know if that works as expected.
#2
Updated by Dongdong over 1 year ago
The documentation (http://gmt.soest.hawaii.edu/doc/5.2.1/isogmt.html) says that:
isogmt runs a single GMT command or shell script in isolation mode.
so I tried "isogmt sh test.sh".
Changing
gmt "$@"
to
"$@"
works for scripts, but it is not a good solution. If GMT_INSTALL_MODULE_LINKS is set to be FALSE during GMT installation, it may make commands like `isogmt psxy` fail.
#3
Updated by Remko over 1 year ago
Dongdong is right. There are two things wrong with isogmt:
- The description of what isogmt does is wrong, as it currently cannot run a shell script.
- If we fix this by replacing
gmt "$@"
by"$@"
or just$@
then it cannot work on a module (as replacement ofgmt)
I think we need to rethink this and have isogmt work right both on modules and scripts, as advertised. It will require some switch.
#5
Updated by Remko over 1 year ago
- Assignee set to Remko
- % Done changed from 0 to 100
#6
Updated by Dongdong over 1 year ago
Yes, it works now.
#7
Updated by Remko over 1 year ago
- Status changed from Resolved to Closed