From: Timothy Baldwin <tim.lists@majoroak.f2s.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] Widening terminal coordinates, and reading terminal size.
Date: Wed, 6 Oct 2004 22:50:10 +0100 [thread overview]
Message-ID: <200410062250.23986.tim.lists@majoroak.f2s.com> (raw)
In-Reply-To: <87brff97lv.fsf@marco.marco-g.com>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Wednesday 06 Oct 2004 16:41, Marco Gerards wrote:
> How about getdimensions? That is the term that is used in the Hurd.
Perfect.
>
> > Would it be better for grub_getxy and grub_getsizexy (or whatever it is
> > called) to handle the case of null pointers, rather than the terminal
> > drivers?
>
> The case of null pointers? I think when you have a nullpointer this
> is a bug, no?
As it stands, when a result is not wanted, a null pointer may be passed and
will not be dereferneced. In light of you comments the feture will be
removed.
[snip]
> As above is very confusing. In that case I would do:
I will change it.
--
Member AFFS, WYLUG, SWP (UK), ANL, RESPECT, Leeds SA, Leeds Anti-war coalition
No to software patents! No to DRM/EUCD - hands off our computers!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-06 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 2:29 [patch] Widening terminal coordinates, and reading terminal size Timothy Baldwin
2004-10-06 8:55 ` Yoshinori K. Okuji
2004-10-06 15:18 ` Timothy Baldwin
2004-10-06 15:41 ` Marco Gerards
2004-10-06 21:50 ` Timothy Baldwin [this message]
2004-10-06 22:38 ` Marco Gerards
2004-10-07 9:22 ` Yoshinori K. Okuji
2004-10-09 11:03 ` Timothy Baldwin
2004-10-09 18:21 ` Yoshinori K. Okuji
2005-01-08 13:07 ` 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=200410062250.23986.tim.lists@majoroak.f2s.com \
--to=tim.lists@majoroak.f2s.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.