so I have also replaced in gencmdlist.sh the following line:
#grep -v "^#" | sed -ne "/grub_register_command *( *\"/{s/.*( *\"\([^\"]*\)\".*/\1: $module/;p}" grep -v "^#" | grep -e "grub_register_command *( *\"" | sed -ne "s/.*grub_register_command *( *\"\([^,\"]*\).*/\1: $module/;p"
Oh, really? This is a very standard sed expression, I think. Ummh... What should I do?
It looks like the problem comes from the braces in the expression, if I try a simple one like this:
$ cat test | sed -e "/grub_register/{s/register/test/;p}"
sed: -e expression #1, char 35: Extra characters after commandSo I split the expression in two parts. From my understanding of it, the following is equivalent to the original sed expression:
grep -v "^#" | grep -e "grub_register_command *( *\"" | sed -ne "s/.*( *\"\([^\"]*\)\".*/\1: $module/;p"
which is not the same line than the one I sent in the previous mail (although they give the same command.lst)
-- Vincent Guffens PhD Student UCL/CESAME tel: +32 10 47 80 30 Value your freedom, or you will lose it, teaches history. "Don't bother us with politics," respond those who don't want to learn. -- Richard M. Stallman
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
