[erlang-questions] Line wrapping issue when attaching to running node
Sat Dec 27 18:53:29 CET 2014
I think this might be a bug that was introduced in 17.0, that has been
fixed in 17.4. See OTP-12275 in the erts release notes.
On Sat, Dec 27, 2014 at 5:12 PM, Karolis Petrauskas <>
> I have the same problem and I have no solution for it. I think it is
> related to the terminal specified when starting the node (not when
> attaching to it).
> The only workaround I found was to type commands in a text editor and
> copy/paste them to the terminal.
> On Tue, Dec 23, 2014 at 5:00 PM, Camille Troillard <> wrote:
> > Hello,
> > We are experiencing an annoying problem in integration or production
> environment that deals with incorrect line wrapping when connecting to a
> remote shell.
> > Erlang version:
> > Erlang/OTP 17 [erts-6.2] [source] [64-bit] [smp:4:4] [async-threads:10]
> > Installed on FreeBSD using the `erlang-17.3_3,3` package.
> > We generate a release using rebar. When we want to interact with it, we
> attach to the system like so (assuming the release is named “abc”) :
> > $ ./rel/abc/bin/abc attach
> > ()1>
> > In this situation, whenever you write something that exceeds the width
> of the terminal (typically 80 columns), the line wraps onto a second line,
> which is OK. But if you have an open parenthesis on the first line, that
> is closed on the second line, then the output becomes garbled, text
> overwritten and it is no longer possible to sanely use the shell.
> > This is an example of expected output:
> > ()1>
> > , 2, 3, 4], another_arg).
> > And the actual output (the cursor is on the first line at column 2):
> > ,
> > , 2, 3, 4]
> > Text garbling occurs as soon as I hit the first ‘]’. It also occurs on
> > It does not happen when typing into an erlang shell that was launched
> using `erl` directly.
> > It seems to happen to_erl. The same erratic behaviour is seen when
> attach to a release running on FreeBSD or OS X. It does not matter whether
> the console is running locally or via SSH. Also, it does not seem to
> matter wether the TERM variable is set to ansi, vt100, xterm or
> > I would like to know if someone noticed this problem, and how to fix it.
> > Thanks !
> > Camille
> > _______________________________________________
> > erlang-questions mailing list
> > http://erlang.org/mailman/listinfo/erlang-questions
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions