Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
scripting:processtree [2016/07/22 10:32]
tejr [Bash playing with pipes] Fix typo
scripting:processtree [2018/07/24 18:18] (current)
csb [Bash playing with pipes] typo fix
Line 45: Line 45:
 ===== Bash playing with pipes ===== ===== Bash playing with pipes =====
  
-Pipes are a very powerful tool. You can connect the output of one process to the input of another process. We won't delve into pipign ​at this point, we just want to see how it looks in the process tree. Again, we execute some commands, this time, we'll run ''​ls''​ and ''​grep'':​+Pipes are a very powerful tool. You can connect the output of one process to the input of another process. We won't delve into piping ​at this point, we just want to see how it looks in the process tree. Again, we execute some commands, this time, we'll run ''​ls''​ and ''​grep'':​
  
 <​code>​ <​code>​
Line 103: Line 103:
 But if your command is a subprocess that sets variables you want to use in your main script, that won't work. But if your command is a subprocess that sets variables you want to use in your main script, that won't work.
  
-For exactly this purpose, there'​s the ''​source''​ command (also: the //dot// ''​.''​ command). Source doesn'​t execute the script, it importss ​the other script'​s code into the current shell:+For exactly this purpose, there'​s the ''​source''​ command (also: the //dot// ''​.''​ command). Source doesn'​t execute the script, it imports ​the other script'​s code into the current shell:
 <​code>​ <​code>​
 source ./​myvariables.sh source ./​myvariables.sh
  • scripting/processtree.1469183531.txt
  • Last modified: 2016/07/22 10:32
  • by tejr