On 25.09.20 15:09, Wolfgang Denk wrote: > Dear Heinrich Schuchardt, > > In message <[email protected]> you wrote: >> >> Further we cannot first introduce a command call and then eliminate it >> due to backward compatibility. We should decide on the final version >> beforehand. > > Full agreement. we need a concept of what is needed / wanted first. > And then we should look how current vrsions of hush fit into this. > >> In the Linux world you can override a command using an alias. So I am >> not sure if a built in command should take precedence over a variable of >> the same name or the other way round. > > This is simple. The PoLA (Principle of Least Astonishment) applies > here. Behaviour must be the same as in other (to some extent POSIX > compatible) shells. A shell should parse it's input, not adhoculate > it.
For me this could be realized by enhancing the run command to allow: run varname1 varname2 ... varnameN --args argv1 argv2 argv3 Arguments argv1, argv2, ... are passed to the script identified by the last variable (varnameN). No new command to learn. Just a new option. Best regards Heinrich
