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:debuggingtips [2015/08/07 04:21]
bill_thomson
scripting:debuggingtips [2017/06/07 02:42] (current)
fgrose [Making xtrace more useful] set variables with descriptive words
Line 130: Line 130:
 That helps a lot when the script is long, or when the main script sources many other files. That helps a lot when the script is long, or when the main script sources many other files.
  
 +=== Set flag variables with descriptive words === 
 +If you test variables that flag the state of options, such as with ''​%%if [[ -n $option ]];​%%'',​ consider using descriptive words rather than short codes, such as 0, 1, Y, N, because xtrace will show ''​%%[[ -n word ]]%%''​ rather than ''​%%[[ -n 1 ]]%%''​ when the option is set.
 ===== Debugging commands depending on a set variable ===== ===== Debugging commands depending on a set variable =====
  
Line 306: Line 307:
  
 <note warning> <note warning>
-It's easy tp imagine the ''​^M''​ is bad in other places too. So if you get weird and illogical messages from your script, ​chances are good ''​^M''​ is envolved. Find and eliminate it!+It's easy to imagine the ''​^M''​ is bad in other places too. If you get weird and illogical messages from your script, ​rule out the possibility that''​^M''​ is involved. Find and eliminate it!
 </​note>​ </​note>​
  
  • scripting/debuggingtips.1438921291.txt
  • Last modified: 2015/08/07 04:21
  • by bill_thomson