Re: surprise with echo

[Kurtis Rader <krader@skepticism.us>]

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

FWIW, the type of learning and experimentation you are undergoing is
extremely useful to yourself and the project. The problem is the difference
between proprietary and open source software. With proprietary software you
have a phone number (email address, web site, etc) that you can use to tell
the company you found a problem and expect it to be fixed. Since you were
paying for support you have, in theory, some leverage.

With open source software reporting a problem is less likely to result in a
fix. However, if you also propose a fix or can convince a contributor to
the project to champion your cause the odds of the problem being fixed are
greatly increased. So it helps if you provide the simplest possible
examples for reproducing the problem and a clear description.

On Thu, Dec 18, 2014 at 10:09 PM, Ray Andrews <rayandrews@eastlink.ca>
wrote:
>
> On 12/18/2014 07:20 PM, Lawrence Velázquez wrote:
>
>> You're making quite a few assumptions about how positional parameters and
>> array substitution work.
>>
> I only just started experimenting with it.  In the case I mentioned, it
> just
> took me by surprise that it killed the whole string. It was in a function
> that
> had just ignored any null strings, then I set the option and the function
> was busted.  Now I know why, so it's all fine. To be honest it never even
> occurred to me that command line args would be affected.  Anyway I get
> it now, thanks.
>
>

-- 
Kurtis Rader
Caretaker of the exceptional canines Junior and Hank