Evgeniy Dushistov wrote:
> On Tue, May 26, 2009 at 04:11:23PM -0400, Chet Ramey wrote:
>> Nikos Chantziaras wrote:
>>> I have:
>>>
>>> MAILPATH="/home/me/.maildir/new?You have new mail."
>>> MAILCHECK=60
>>>
>>> Bash 3.2 was correctly telling me about new mail arriving. However,
>>> after I up
... the age old convention of using upper case names
for all their shell variables. ...
It reminds some programmers that a '$' is necessary for expansion.
It is somewhat like using all capitals for #define macros in C
(where the expansion is automatic, but still different from other
symbols that
On Tue, May 26, 2009 at 04:11:23PM -0400, Chet Ramey wrote:
> Nikos Chantziaras wrote:
> > I have:
> >
> > MAILPATH="/home/me/.maildir/new?You have new mail."
> > MAILCHECK=60
> >
> > Bash 3.2 was correctly telling me about new mail arriving. However,
> > after I updated to Bash 4.0, I const
2009-10-25, 12:05(-07), Linda Walsh:
> This is not exactly bash specific, but I was looking at a shell script
> recently and they use the age old convention of using upper case
> names for all their shell variables.
[...]
By convention, _environment_ variables are upper-case, which helps
in a sh
This is not exactly bash specific, but I was looking at a shell script
recently and they use the age old convention of using upper case
names for all their shell variables.
At one point I remember this being common practice, but today, ALL
CAPS LOOKS LIKE YOU ARE YELLING OR ARE A FOUR OR FIV
