Omniflux <[EMAIL PROTECTED]> 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 _______________________________________________ Grub-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/grub-devel
