From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Scrolling issues in edit command
Date: Tue, 5 Apr 2016 09:52:39 +0200 [thread overview]
Message-ID: <CABDcavbN_G2MOwjxv6Ags=L0GWwj_HGEMom4ks_s9MZB+GEDVg@mail.gmail.com> (raw)
In-Reply-To: <20160404200730.GA1618@pengutronix.de>
2016-04-04 22:07 GMT+02:00 Uwe Kleine-König <u.kleine-koenig@pengutronix.de>:
> Hello,
>
> On Wed, Mar 30, 2016 at 05:38:53PM +0200, Guillermo Rodriguez Garcia wrote:
>> I am trying to setup Barebox on a SAMA5D3-Xplained board. I started
>> with barebox-2016.03.0. So far things are looking good.
>>
>> I have found that I have problems in the 'edit' command, when trying
>> to scroll using the arrow keys. Scrolling up inserts random "A"
>> characters in the text, scrolling down inserts random "B" characters.
>> I am using minicom as the terminal. I don't remember seeing this
>> before with older versions of barebox on different boards.
>
> Can you instrument your serial driver to count/notice overflow events?
You mean in barebox, or in the host where I'm running minicom/microcom?
> It's strange that you're missing chars 3-12 in a longer paste.
>
> Does it help to use
>
> busybox microcom -d 10 ...
>
> ? (That is a feature that is missing from the "fullblown" microcom that
> comes in the microcom package.)
Interesting. I tried that, the result is:
- Still the same problem when scrolling up and down in "edit" (A and B
characters inserted)
- Many more missing chars when pasting "Lorem ipsum.." (_in "edit"_).
Here are three examples:
Loe Ismismyuye iinatestis.
Loe Ismismyuye eiinatest uy.
Loe Ismismyuye iinatest uy.
- The very same text can be pasted perfectly in barebox's command
line, no missing chars. The problem is only with the "edit" command.
What makes "edit" different ?
Guillermo
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-04-05 7:53 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
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 [this message]
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='CABDcavbN_G2MOwjxv6Ags=L0GWwj_HGEMom4ks_s9MZB+GEDVg@mail.gmail.com' \
--to=guille.rodriguez@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=u.kleine-koenig@pengutronix.de \
/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