On Sun, 19 Feb 2006 00:47:53 -0600 "Van Van Cleave" <[EMAIL PROTECTED]> wrote:
> Solved the problem and managed to make myself feel quite dumb in the > process. Simply modify the script so that the line > > sed $'s/.\b\\(.\\)/\\1/g;s/\x1b[^m]\\+m//g' | > > reads > > sed -e 's/.\b\\(.\\)/\\1/g;s/\x1b[^m]\\+m//g' | > > and the script works beautifully. No it doesn't, at least not as it was intended. The 2nd line does something completely different from the 1st. The problem seems to be that bash 3.1 has trouble evaluating $'..' within "$(...)". The folling illustrates the problem: > echo "$(echo $';foo')" bash: foo: command not found whereas > echo $';foo' ;foo works. This looks like a clear bug to me since both lines are supposed to produce the same output. I suggest you file a bug report. I won't. The bug-bash mailing list has disappointed me once too often. BTW, you should mail me directly when you encounter a problem with one of my scripts. I overlooked your first message and would almost have overlooked the whole thread. I only have the time to give (B)LFS support a very cursory glance these days. CC'ing won't help since as long as there's linuxfromscratch.org in the To: or CC: field, it'll end up in my LFS folder where I may overlook it. MSB -- For sale: Parachute. Only used once, never opened, small stain. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
