From: Holger Schurig <holgerschurig@gmail.com>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Scrolling issues in edit command
Date: Thu, 31 Mar 2016 15:39:40 +0200 [thread overview]
Message-ID: <87ziterckj.fsf@gmail.com> (raw)
In-Reply-To: <CABDcavYEn0e8GkEzfJnayr32X85dA5tz-dRaMg3H6J8i-aXj0w@mail.gmail.com> (Guillermo Rodriguez Garcia's message of "Wed, 30 Mar 2016 17:38:53 +0200")
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.
I personally connect from Linux via the serial line with kermit to my
target. Kermit has a simple ~/.kermrc file that looks like this:
set line /dev/ttyS0
set baud 115200
set handshake none
set flow-control none
set carrier-watch off
set escape-character ^X
log session ~/.kermlog
connect
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.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-03-31 13:40 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 [this message]
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
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=87ziterckj.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=guille.rodriguez@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