Re: $# equals 1 in scripts sourced with no arguments from a login shell when bash 1.x vars are set

[Denis McKeon]

In <m3snh5lp9a.fsf_-_@multivac.cwru.edu> Paul Jarc wrote:
>Dmckeon@swcp.com (Denis McKeon) writes:
>> This is a different manifestation of the problem Philip posted about,
>> caused in this case by a left-over relic in a bash v1 ~/.bash_profile.
>
>And the explanation is the same.  This is intended, documented
>behavior.  It has nothing to do with login shells or startup files,
>and everything to do with the 'set' and 'source' commands.

Paul, thanks for your response - after thrashing about for a few hours
in the man pages, FAQs, and example scripts, I'll agree that this is not
a bug, but a PBEOU - "problem between ears of user."  In my case, the
combination of 15 years of coping with the C shell, and an unexpected
effect of a statement that was valid and effective in a previous release
of bash led me to jump to an inaccurate conclusion.

-- 
Denis McKeon