On Wed, Oct 15, 2008 at 03:11:15PM -0700, RMMM wrote:
> I'm trying to create a bash function for use in auto completion, but
> I've run into bash behavior I don't understand. All I want to do is
> generate a list of the file names from a certain directory. I have a
> line
>
> filenames=$(for file
RMMM wrote:
RMMM wrote:
As far as I can tell, the variables $filenames and $filenames1 have the
same values. Yet, they
behave differently when used in an argument. Is there some hidden aspect
to a bash variable
that I'm not seeing?
I just figured out the problem. I was running this in a shel
m. I was running this in a shell with
dircolors. Arggg!
doing
filenames=`ls --color=no mydir`
is all I needed to do. Well ... maybe there's some better way of getting the
filenames
that's immune to any invisible codes.
--
View this message in context:
http://www.nabble.com/Pu
a bash variable
that I'm not seeing?
--
View this message in context:
http://www.nabble.com/Puzzling-discrepancy-in-bash-variables-tp20003296p20003296.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
