From: Omniflux <omniflux+lists@omniflux.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [rfc] User definable terminfo support
Date: Tue, 03 Jan 2006 16:23:17 -0700 [thread overview]
Message-ID: <43BB0765.2020503@omniflux.com> (raw)
In-Reply-To: <87acecgb8n.fsf@xs4all.nl>
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
next prev parent reply other threads:[~2006-01-03 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 22:20 [rfc] User definable terminfo support Omniflux
2006-01-03 22:59 ` Marco Gerards
2006-01-03 23:09 ` Marco Gerards
2006-01-03 23:23 ` Omniflux [this message]
2006-01-03 23:59 ` Marco Gerards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43BB0765.2020503@omniflux.com \
--to=omniflux+lists@omniflux.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.