[Octave-bug-tracker] [bug #45509] communications-1.2.1 fails during package install in octave-4.0.0

[Mike Miller]

Follow-up Comment #25, bug #45509 (project octave):

So to confirm, TERM=xterm produces this escape sequence when you are on a
local gnome-terminal? Or is it a different TERM? And you are using bash as a
shell? But TERM=<<same terminal>> does not produce the escape sequence when
logged in via ssh? And TERM=vt100 fixes it locally or via ssh?

Can you look at a diff of your entire shell environment in the working vs.
not-working states? I usually do "env | LC_COLLATE=C sort > file.txt".

Can you try a different terminal emulator, xterm or rxvt or konsole, any
differences there?

Your inputrc looks pretty standard. Do you happen to have a ~/.inputrc (in
your HOME directory)?

What is the output of "infocmp | grep 1034"?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45509>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/