From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Etvcf-0000L4-Q5 for mharc-grub-devel@gnu.org; Tue, 03 Jan 2006 18:31:21 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Etvcd-0000Ky-PR for grub-devel@gnu.org; Tue, 03 Jan 2006 18:31:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Etvcc-0000Ke-53 for grub-devel@gnu.org; Tue, 03 Jan 2006 18:31:19 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Etvcc-0000Ka-0r for grub-devel@gnu.org; Tue, 03 Jan 2006 18:31:18 -0500 Received: from [208.186.28.7] (helo=mail.nebonet.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Etvdu-0006p8-Mz for grub-devel@gnu.org; Tue, 03 Jan 2006 18:32:38 -0500 Received: from localhost (scanner.nebonet.com [208.186.28.8]) by mail.nebonet.com (Postfix) with ESMTP id 1618019E164 for ; Tue, 3 Jan 2006 16:29:34 -0700 (MST) Received: from mail.nebonet.com ([208.186.28.7]) by localhost (scanner.nebonet.com [208.186.28.8]) (amavisd-new, port 10024) with LMTP id 23814-01-2 for ; Tue, 3 Jan 2006 16:29:27 -0700 (MST) Received: from [10.0.1.114] (f4s.dsl.xmission.com [166.70.40.38]) by mail.nebonet.com (Postfix) with ESMTP id 3E29219D9FC for ; Tue, 3 Jan 2006 16:23:49 -0700 (MST) Message-ID: <43BB0765.2020503@omniflux.com> Date: Tue, 03 Jan 2006 16:23:17 -0700 From: Omniflux User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: The development of GRUB 2 References: <43BAF893.5080205@omniflux.com> <87acecgb8n.fsf@xs4all.nl> In-Reply-To: <87acecgb8n.fsf@xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Debian amavisd-new at scanner.nebonet.com Subject: Re: [rfc] User definable terminfo support 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: Tue, 03 Jan 2006 23:31:19 -0000 Marco Gerards wrote: > Why do you have a hook for variables? > > For example, when I do: > > set vt100=... > > It's ok that is does not take effect until you change TERM, IMO. > > So what happens is: > > 1) VT100 is set > 2) TERM is set > 2a) The hook is executed > 2b) VT100 is read by the hook. > 2c) The contents of VT100 is read and parsed. > 2d) From this point of the VT100 stuff can be used and the hook > returns. > What if the user notices a typo in VT100 and changes it. Wouldn't they expect the update to be immediate, and not have to reassign TERM its current value? -- Omniflux