On Saturday 02 August 2003 22.25, R. Bernstein wrote:
> > Here is a small patch (attached) that adds wildcard matching for the V
> > command. Also it fixes what i feel is a bug with V in that it also
> > reports all functions in the scope.
>
> Many thanks. It's encouraging when folks submit patches and
> improvements like this. And improving V was on the TODO list!
>
> The patch has now been applied to CVS with some small changes;
> changes to update help and the documentation have been made.
>
> > I'm not a seasoned bash scripter so there are probably some things that
> > can be fixed. But for now it seems to be quite robust.
>
> I don't consider myself a seasoned bash scripter either. I know I'm
> not suppsed to ask, but well what does this do?
>
> # Uhmn, well, yes... don't ask !
> _Dbg_cmd=`echo -e _Dbg_var=\\${_Dbg_var//\\\n/\\\\\\\\\\\\\\\\\\\\\\\\n}`
Short answer: The wrong thing :)
I really wanted to do: _Dbg_var=${_Dbg_var//
/\\n}
And tried to insert a \n escape sequence for the \n first, couldn't get it to
work. But then i tried doing eval to get a \n there and that would have
worked if i had used the right number of '\' on the left side of the
expression. And after that i found out the obvious way: Put the linebreak
right there in the script :)
>
> I notice that in the output embedded blanks in a variable string comes out
> \n.
>
> Again, thanks
>
>
/Mikael
|
