Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Etw5l-0003gO-9K for mharc-grub-devel@gnu.org; Tue, 03 Jan 2006 19:01:25 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Etw5e-0003fK-OS for grub-devel@gnu.org; Tue, 03 Jan 2006 19:01:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Etw5a-0003e7-Tj for grub-devel@gnu.org; Tue, 03 Jan 2006 19:01:17 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Etw5a-0003dq-BW for grub-devel@gnu.org; Tue, 03 Jan 2006 19:01:14 -0500 Received: from [194.109.24.34] (helo=smtp-vbr14.xs4all.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Etw6t-00043Y-16 for grub-devel@gnu.org; Tue, 03 Jan 2006 19:02:35 -0500 Received: from localhost.localdomain (mgerards.xs4all.nl [82.92.27.129]) by smtp-vbr14.xs4all.nl (8.13.3/8.13.3) with ESMTP id k03NxTi3097659 for ; Wed, 4 Jan 2006 00:59:30 +0100 (CET) (envelope-from mgerards@xs4all.nl) Mail-Copies-To: mgerards@xs4all.nl To: The development of GRUB 2 References: <43BAF893.5080205@omniflux.com> <87acecgb8n.fsf@xs4all.nl> <43BB0765.2020503@omniflux.com> From: Marco Gerards Date: Wed, 04 Jan 2006 00:59:33 +0100 In-Reply-To: <43BB0765.2020503@omniflux.com> (omniflux+lists@omniflux.com's message of "Tue, 03 Jan 2006 16:23:17 -0700") Message-ID: <8764p0g8wq.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: [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: Wed, 04 Jan 2006 00:01:23 -0000 Omniflux writes: > 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? It does not happen that often, I think. But if you'd like using hooks for the variables TERM is pointing to, it's fine for me. But I assume you figured out it is way more complex. :-) -- Marco