Re: scripts one after the other

2016-03-29 Thread Quinn Fissler
On 26 March 2016 at 01:28, Val Krem wrote: > > is it possible to combine the two scripts in one so that I can define the > varietals at one spot. It would be less prone to error. Yes - you can have a script with a "case" and hard link to another name (you can symlink but

Re: scripts one after the other

2016-03-28 Thread Greg Wooledge
On Sat, Mar 26, 2016 at 01:28:56AM +, Val Krem wrote: > Both scrips do have common variables (var1 , var2 and var3) and also some > input and output folder name defined. > > At the present I have defined the variables and folders path in both scripts. > > Instead of this, is it possible

Re: scripts one after the other

2016-03-26 Thread shawn wilson
On Sat, Mar 26, 2016 at 9:26 AM, Val Krem wrote: > > I'm not sure what you want, but you could always pipe one script into > another and evaluate the input from the later. Or just call the second > script from the first in an if. > (untested) #!/bin/bash # t2.sh read f if [[

Re: scripts one after the other

2016-03-26 Thread John McKown
On Sat, Mar 26, 2016 at 8:26 AM, Val Krem wrote: > > I'm not sure what you want, but you could always pipe one script into > another and evaluate the input from the later. Or just call the second > script from the first in an if. > > > It is not the question of PIPE one script

Re: scripts one after the other

2016-03-26 Thread shawn wilson
On Mar 25, 2016 9:32 PM, "Val Krem" wrote: > > At the present I have defined the variables and folders path in both scripts. > > Instead of this, is it possible to combine the two scripts in one so that I can define the varietals at one spot. It would be less prone to error.