All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omniflux <omniflux+lists@omniflux.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] User definable terminfo support
Date: Mon, 02 Jan 2006 12:53:43 -0700	[thread overview]
Message-ID: <43B984C7.6070502@omniflux.com> (raw)
In-Reply-To: <87y8219p48.fsf@xs4all.nl>

Marco Gerards wrote:
>>terminfo-definition-support.diff
>>  * term/terminfo.c: Replaced static vt100 definition with user
>>definable definition support.
> 
> Is it possible to do this in a GRUB env. variable, like:
> 
> set TERM=vt100
> 
> And perhaps one variable or function to set the possible terminal
> descriptions.  I think that would be easier for the user to do it this
> way.
> 

This is possible, however...

The reason I chose to use a linked list allowing multiple terminal 
definitions was so multiple entries could be defined at load time, and, 
ideally, the user could then choose the correct one at boot.

This would be helpful in cases where the choice of definitions is 
unknown to the entity creating the configuration, such as a live CD 
distribution or a generalized system recovery disk for computers without 
video cards.

As to using an env. variable to select which terminal definition to use,
I have not looked at the env. code. I doubt I can tie into the env. code 
to tell when the variable has changed, so this would leave the problem 
of no immediate user feedback if an invalid definition name is set.

If you can point to a good place to provide this feedback, I see no 
problem with changing the selection code to use an environment variable 
instead, but I would like to keep support for multiple terminfo definitions.


Did I interpret your comments correctly?

> give will be more useful than the feedback above...  Can you provide a
> ChangeLog entry so the patch can be reviewed and applied?  See the GNU

Should this be provided as part of the patch, or separate, but with the 
patch email?

> At the moment I am working on the menu code, so the syntax will be
> changed really soon.  But at the moment you can do something like:
> 
> title foo
> linux /vmlinux ...
> 
> title bar
> ...

I will try this.

Thanks!

-- 
Omniflux



  reply	other threads:[~2006-01-02 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28  0:34 [PATCH] User definable terminfo support Omniflux
2005-12-31 17:02 ` Marco Gerards
2006-01-02 19:53   ` Omniflux [this message]
2006-01-02 20:37     ` Marco Gerards
2006-01-02 21:33       ` Omniflux
2006-01-02 21:43         ` Marco Gerards
2006-01-02 19:44 ` Marco Gerards
2006-01-02 20:21   ` Omniflux
2006-01-02 20:43     ` 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=43B984C7.6070502@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.