On naming variables about bash-coding-style HOT 3 CLOSED

Thanks @cmpitg for your comments.

The problem with #bash is that a variable can't stand with its own name. You have to use a $ to get variable value. Let's see

local _my_var=something

echo "My value is $_my_var, or ${_my_var}. Uppercase version is ${_my_var^^}".
echo "My value is $my_var, or ${my_var}. Uppercase version is ${my_var^^}".

The primary purpose of the underscore (_) is to create a natural distance between the dollar ($) and the variable name. I see that helps my code more readable, esp. when I have no color in my viewer.

This is just a convention, and you may follow it , or not. The most important thing to remember is to make sure your code consistent, by not using different styles in the same project;)

from bash-coding-style.

Thanks @icy.

The primary purpose of the underscore (_) is to create a natural distance between the dollar ($) and the variable name. I see that helps my code more readable, esp. when I have no color in my viewer.

This explains it. Would it be better if a brief rationale is added for some section? Some could be subjective, but I think it'd be better to understand the decision at least. Don't you think?

from bash-coding-style.

Totally agreed. I will update it soon :)

from bash-coding-style.