All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: grub-devel@gnu.org
Subject: Re: cursor position does not follow output
Date: Fri, 8 May 2015 20:09:42 +0200	[thread overview]
Message-ID: <20150508180942.GA5221@aepfle.de> (raw)
In-Reply-To: <20150508180551.GA3996@aepfle.de>

On Fri, May 08, Olaf Hering wrote:

> In my testing with a PV guest I notice that the cursor during input
> remains at the 24th row. The actual output of the help command for
> example lists all possible commands and causes scrolling. If I enter
> something the input does not appear at the bottom but at the 24 row.

The output looks like that:


                          GNU GRUB  version 2.02~beta2

   Minimal BASH-like line editing is supported. For the first word, TAB   
   lists possible command completions. Anywhere else TAB lists possible   
   device or file completions.                                            


grub> s
error: can't find command `s'.
grub> s
error: can't find command `s'.
grub> s
error: can't find command `s'.
grub> s
error: can't find command `s'.
grub> s
error: can't find command `s'.
grub> s
error: can't find command `s'.
grub> s
error: can't find command `s'.
grub> s
error:ssssss find command `s'.
error: can't find command `ssss'.'.
grub> 


That is, whatever I do the input appears in the line with all the 'sss'.
Happens within a screen session and with a plain xterm.

Olaf


  reply	other threads:[~2015-05-08 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 18:05 cursor position does not follow output Olaf Hering
2015-05-08 18:09 ` Olaf Hering [this message]
2015-05-10  9:25   ` Vladimir 'phcoder' Serbinenko
2015-05-08 18:41 ` Andrei Borzenkov
2015-05-11  7:45 ` Olaf Hering
2015-05-11  7:56   ` Vladimir 'phcoder' Serbinenko
2015-05-11  8:11     ` Olaf Hering
2015-05-11  8:33       ` Olaf Hering

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=20150508180942.GA5221@aepfle.de \
    --to=olaf@aepfle.de \
    --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.