Hi !

Well, what I ment with "If the line exceeds the 80 chars...."
I mean if you type in a command line, which exceed the line length
of the xterm window or whatever...

Example:

grub> kernel /tftpboot/machine1/boot/bzImage console=ttyS0 root=/dev/nfs
nfsroot=192.168.1.1:/tftpboot/machine1/root

Such a line comes on my xterms:

nfsroot=192..... pboot/machine1/boot/bzImage console=ttyS0 root=/dev/nfs

and so on. What I mean is, that grub writes the command line in the
same line, not in the next one. The reason is the cursor position
query of xterm. It returns the same line. In my implementation I have
the same problem....

One idea to deal with this problem is to shift the contents of 
the command line inside the screen line, like the shells do on 
some displays, like this:

< ine1/boot/bzImage console=ttyS0 root=/dev/nfs nfsroot=192.168.1.1:/...

Another possibility is, to handle that the line is continued in the
next line on the screen (xterm or whatever). Or there is a command line
limit of one line and there is the possibility to use the `\' sign
as in C or makefiles to continue the same command line in the next
one ! (This would be very useful for the config file (menu) !)

By the way, I have problems with the symbols for the borders of the
menu. It would be a good idea to use '+', '-' and '|' in the...

        if (terminal & TERMINAL_SERIAL)
          {
             disp_ul = '+';
                :
                :
          }

... as although the share.h really uses '+', etc for ACS_xxxx, but I
see only 'xmmmmmmmmmmmmmmmmmmmmmmmmmmmm.......'  or other letters.

But I like that you have decided to work on the very important 
serial stuff ! Thanks.

With friendly regards

        Christoph P.


OKUJI Yoshinori wrote:
> 
> From: Christoph Plattner <[EMAIL PROTECTED]>
> Subject: Re: preliminary serial terminal support
> Date: Tue, 22 Aug 2000 23:03:45 +0200
> 
> > * If the line exceeds the 80 chars, then the input is done in the same
> >       line, not in the next. The same is true for my implmentation,
> >       here there seems to be a problem with the cursor position
> >       request.
> 
>   I don't understand what you mean quite well. Can you tell me how to
> reproduce that?
> 
> > * The cursor keys do not work. You can take the key converting from my
> >       implementation I sent you a month (or more) ago. In my
> >       implementation it works (up, down, left, right, HOME, END,
> >       etc....)
> 
>   Right. I just don't have time to steal that from your patch yet. ;)
> 
> Regards,
> Okuji

-- 
-------------------------------------------------------------------------
private:        [EMAIL PROTECTED]
company:        [EMAIL PROTECTED]

Reply via email to