On Sun, Feb 17, 2019, 3:10 PM L A Walsh <b...@tlinx.org wrote: > > > On 2/16/2019 4:57 AM, Robert Elz wrote: > > Date: Fri, 15 Feb 2019 22:21:25 -0800 > > From: L A Walsh <b...@tlinx.org> > > Message-ID: <5c67abe5.1030...@tlinx.org> > > > > | Thought about that....restarted a fresh shell. Same same. > > | At least I know it's supposed to... > > > > It isn't just BASH_ALIASES - you'll see the same from lots of > > other dynamic variables. > > > --- > Woe! That's what threw me -- it says empty, but it isn't. > > Try actually accessing an element, as in ... > > > > > > On occasion, the output from declare will show all the > > aliases in BASH_ALIASES but I have no idea what sequence of > > commands, of state of the universe, causes that to happen. > > > ----- > > AND -- just did it now, it doesn't even show BASH_ALIASES, but > I know I have aliases defined. Weird! > > So it really is a bug of some sort, not that I use BASH ALIASES > for anything. Was going to, but ... and you're right, lots of > things aren't showing there. > > >
Have you tried starting Bash without any startup files, creating an alias and then checking the array? >
