From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Scrolling issues in edit command
Date: Thu, 31 Mar 2016 17:36:58 +0200 [thread overview]
Message-ID: <CABDcavZ2HPoPqCJ9Wn_Uu7fapKcqdHEPc9jDjnM7xDvKJ5ahbg@mail.gmail.com> (raw)
In-Reply-To: <87ziterckj.fsf@gmail.com>
Hello,
Thank you for the answer. Some comments below.
2016-03-31 15:39 GMT+02:00 Holger Schurig <holgerschurig@gmail.com>:
> Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com> writes:
>
>> Can anyone provide any hints on why this is
>> happening or how to fix it ?
>
> I guess this is probably because your terminal emulation doesn't match
> what barebox assume.
Uhm, could be, however I have also been using minicom with an older
version of barebox for a long time (2011.05.0, on a different target
board), and never had any problems at all. I only noticed this
behaviour when testing barebox 2016.03.0 on a new board.
[...]
> Kermit is oblivious to any ANSI escape sequences, so my X11 terminal
> emulates them. Here I use the rxvt-unicode binary `urxvt`. The effect is
> that the "edit" commands works.
Perhaps I should clarify what I am seeing. The "edit" command actually
works, more or less. If I scroll up or down one line at a time then
there are no problems. I only see bogus A or B characters inserted
when I do "continuous" scrolling. Also I noticed that ESC [ A is the
ANSI escape sequence for "cursor up", and ESC [ B is the ANSI escape
sequence for "cursor down". Perhaps when I keep the arrow up/down key
pressed, minicom is sending these escape sequences faster than barebox
can handle them, and that's why I see the 'A' and 'B' characters
inserted?
Regards,
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-03-31 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:38 Guillermo Rodriguez Garcia
2016-03-31 13:39 ` Holger Schurig
2016-03-31 15:36 ` Guillermo Rodriguez Garcia [this message]
2016-04-04 6:38 ` Sascha Hauer
2016-04-04 13:34 ` Guillermo Rodriguez Garcia
2016-04-05 7:32 ` Rolf Evers-Fischer
2016-04-04 20:07 ` Uwe Kleine-König
2016-04-05 7:52 ` Guillermo Rodriguez Garcia
2016-04-05 8:14 ` Uwe Kleine-König
2016-04-05 8:40 ` Guillermo Rodriguez Garcia
2016-04-05 9:05 ` Uwe Kleine-König
2016-04-05 9:40 ` Rolf Evers-Fischer
2016-04-05 11:01 ` Guillermo Rodriguez Garcia
2016-04-05 12:23 ` Uwe Kleine-König
2016-04-05 15:31 ` Guillermo Rodriguez Garcia
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=CABDcavZ2HPoPqCJ9Wn_Uu7fapKcqdHEPc9jDjnM7xDvKJ5ahbg@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox