From: Robert Millan <rmh@aybabtu.com>
To: Andy Goth <unununium@aircanopy.net>
Cc: grub-devel@gnu.org
Subject: Re: No scrolling for long input lines
Date: Sun, 9 Nov 2008 23:08:17 +0100 [thread overview]
Message-ID: <20081109220817.GA26683@thorin> (raw)
In-Reply-To: <1720038063.77061223401246968.JavaMail.root@aczmb1>
On Tue, Oct 07, 2008 at 12:40:46PM -0500, Andy Goth wrote:
> (I said I would research this some more, but I haven't had a chance, and I won't get one for a couple days, so rather than wait, I am simply posting what I know.)
>
> In GRUB 1.96, typing an input line longer than the screen is wide does not cause the screen to scroll. Effectively this means once I get to the bottom of the screen, anything I type that's longer than 80 characters (less prompt) I have to type blind. Aside from not being able to see what I type, everything behaves normally.
>
> My GRUB configuration is plain vanilla. GRUB's on a FAT12 floppy read in using biosdisk, there's no grub.cfg file, and I directly type in insmod, ls, linux, initrd, boot, and all that jazz. I haven't made any modifications to the source, and I'm using the 1.96 release I found on alpha.gnu.org. I have the biosdisk and fat modules compiled into the GRUB image.
Andy, I just sent a patch (mail titled "split/refurbish vga_text.mod") which
would allow you to use vga_text.c as a terminal output driver:
insmod vga_text
terminal_output vga_text
I think this should solve your problem. Could you test it?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-11-09 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 17:40 No scrolling for long input lines Andy Goth
2008-10-07 17:48 ` Felix Zielcke
2008-10-07 19:06 ` Andy Goth
2008-11-09 22:08 ` Robert Millan [this message]
[not found] <270343305.88391223432285723.JavaMail.root@aczmb1>
2008-10-08 4:12 ` Andy Goth
2008-10-08 16:40 ` Vesa Jääskeläinen
2008-11-01 12:48 ` Robert Millan
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=20081109220817.GA26683@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=unununium@aircanopy.net \
/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.