Shell Programming and Scripting

Neither of your suggestions make any sense.

What's the point of writing

Code:

cp /path/to/app.app/folder/$x.plist

to

Code:

/var/mobile/z_folder/$x.sh

?

---

I agree too for the most part.

All of the suggestions posted above share one and the same problem (at least when I use them with my shell environment):
One of the two variables doesn't get extracted.

Results:
1st doesn't get extracted: swallowed line or part that contains variable
2nd doesn't get extracted: all paths are written into a $x.sh file that magically contains all paths with the variables extracted.

I'd gladly listen to further ideas regarding this.

Till then:

I went another route to achieve what I want:

Code:

while read x
do
  printf "cp /path/to/app/xtzdero204.plist " >> /var/mobile/z_renapps/"$x".sh
  sed -i "s|xtzdero204|$x|g" /var/mobile/z_renapps/"$x".sh
done < /Applications/RenApple.app/applist.txt

You could do it all in sed, no printf, using the 'w filename' to make a copy of the line in the file.

Use printf more for formatting numbers in complex strings. The echo is cheaper for simple strings.

We still do not understand why you wish to make 10,000 individual scripts with slight differences. This kind of "need" usually points to a poor understanding of the shell.

You are probably right about this.

I merge the multiple shells back into one in the next step.
It could probably be acheived in a simpler manner.

On a different standing:

it seems that

Code:

while read x
do
  CODE
done < /TEXT.txt

will only process 52 lines of this text file.
It always stops after the 52's line.

I shall post the full Script I have when someone can help me with understanding why it stops exactly after 52 repetitions.

Well, assuming there are more lines, the answer is that the 52nd line $x poisoned CODE and it hung. Put an echo "x='$x'" before CODE to make sure which line in toxic.

I can think of many different reasons it could be messing up.

Perhaps one of your lines is reading from standard input, wasting it all to the point your loop only gets 52 lines worth before it runs out.

Maybe the 53rd line is different from the previous 52 in some way which exposes a bug latent in your program -- an unchecked divide by zero, an unexpected split due to spaces in a string causing a syntax error in your if-block, and other such things which only worked due to assumptions about your data which eventually stopped being true.

Are any of these your problem? Somehow I doubt it, they're all wild guesses, and I could keep guessing forever in random combinations. We cannot know, and you cannot expect us to know, until you post the code.