All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] User definable terminfo support
Date: Mon, 02 Jan 2006 22:43:25 +0100	[thread overview]
Message-ID: <87mziei9vm.fsf@xs4all.nl> (raw)
In-Reply-To: <43B99C25.5030404@omniflux.com> (omniflux+lists@omniflux.com's message of "Mon, 02 Jan 2006 14:33:25 -0700")

Omniflux <omniflux+lists@omniflux.com> writes:

> Marco Gerards wrote:
>> What I had in mind is:
>> TERM=vt100, or whatever can be used to select the terminal.  People
>> are used to this from the UNIX commandline.  Besides that, we prefer
>> having variables in GRUB instead of commands.
>> I was wondering if it would be easier to set terminfo descriptions
>> using variables as well.  For example:
>> set vt100='cub=\E[%p1%dD, cub1=^H, cud=\E[%p1%dB, cud1=^J'
>> (I just used some random stuff, but I assume you get the idea)
>> After that:
>> set TERM=vt100
>> That will read and parse the vt100 variable.  We can add several
>> pre-defined variables.
>> Hopefully my explanation makes sense.
>
> This makes sense. I do not like allowing TERM to be set to just any
> variable name (set TERM=PROMPT), but as this is really in the users
> configuration space, I suppose we can place the requirement on the
> user to issue sane assignments, and if they do not, it is their own
> fault, provided I document it well.

Agreed.

> I will make your suggested changes and submit another patch to the
> list as soon as I have time again.

Great!  I am looking forwards to it!

Thanks,
Marco




  reply	other threads:[~2006-01-02 21:45 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
2006-01-02 20:37     ` Marco Gerards
2006-01-02 21:33       ` Omniflux
2006-01-02 21:43         ` Marco Gerards [this message]
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=87mziei9vm.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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.