From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1FchcX-0000ep-CR for mharc-grub-devel@gnu.org; Sun, 07 May 2006 07:40:17 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FchcV-0000db-6a for grub-devel@gnu.org; Sun, 07 May 2006 07:40:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FchcT-0000dP-Ih for grub-devel@gnu.org; Sun, 07 May 2006 07:40:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FchcT-0000dK-FT for grub-devel@gnu.org; Sun, 07 May 2006 07:40:13 -0400 Received: from [194.109.24.29] (helo=smtp-vbr9.xs4all.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fchd4-0001ru-7W for grub-devel@gnu.org; Sun, 07 May 2006 07:40:50 -0400 Received: from localhost.localdomain (249-174.surfsnel.dsl.internl.net [145.99.174.249]) by smtp-vbr9.xs4all.nl (8.13.6/8.13.6) with ESMTP id k47BeB6X016981 for ; Sun, 7 May 2006 13:40:11 +0200 (CEST) (envelope-from mgerards@xs4all.nl) Mail-Copies-To: mgerards@xs4all.nl To: The development of GRUB 2 References: <200605070800.43759.okuji@enbug.org> From: Marco Gerards Date: Sun, 07 May 2006 13:42:20 +0200 In-Reply-To: <200605070800.43759.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sun, 7 May 2006 08:00:43 +0200") Message-ID: <87hd42njs3.fsf@xs4all.nl> User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: another script bug X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 May 2006 11:40:15 -0000 "Yoshinori K. Okuji" writes: > As far as I see, the scripting code is really broken. When executing a menu > entry, nothing is executed (setting a variable seems to be executed for an > unknown reason, but there is no echo). Right, and I am able to reproduce this. I know how it is caused but it's not an easy issue to fix properly. This too has a wait a bit, sorry. Can you test it with just a single command in the menu entry? For this specific case things have to work... -- Marco