Opened 4 years ago

#285 new defect

input_history (ih) improperly handles input lines longer than the screen width

Reported by: Gary Dixon Owned by: Eric Swenson
Priority: major Milestone:
Component: General Version:
Keywords: Cc:

Description

With video system enabled and input_history command attached (as shown in pat output below)...

pat
user_terminal_      tc_io_ -login_channel
          stream_input_output
error_output        syn_ user_i/o -inh close get_line get_chars
user_output         syn_ user_i/o -inh close get_line get_chars
user_input          syn_ user_i/o -inh close put_chars
user_i/o
     window_io_ user_terminal_ -first_line 1 -n_lines 77 -first_column 1 -n_columns 131
          stream_input_output Video

the terminal setup is as follows:

stty -all
Type: VT102_132C_78L
Modes: more_mode=scroll,more,ll=131,pl=77,^vertsp,can,erkl,esc,^rawo,^red,^ctl_char,^edited
Erase: #,  Kill: @
Frame_begin: \000, Frame_end: \000
Delays: vert_nl 0, horz_nl  0.500, const_tab 0, var_tab  0.000, backspace 0, vt_ff 0
output suspend: \023; output resume: \021

When operating in this environment, a typed input line longer that the screen width is split into two input lines, as shown by the following command and its output.

string ...5....1 ...5....2 ...5....3 ...5....4 ...5....5 ...5....6 ...5....7 ...5....8 ...5....9 ...5....0 ...5....1 ...5....2 ...5
\c....3 ...5....4
...5....1 ...5....2 ...5....3 ...5....4 ...5....5 ...5....6 ...5....7 ...5....8 ...5....9 ...5....0 ...5....1 ...5....2 .
r 11:11 0.136 0

Segment 5....3 not found.
r 11:11 0.073 0

In the exact same video environment but with input_history detached, the long command input line is handled properly:

ih detach
r 11:12 0.053 0

string ...5....1 ...5....2 ...5....3 ...5....4 ...5....5 ...5....6 ...5....7 ...5....8 ...5....9 ...5....0 ...5....1 ...5....2 ...5
\c....3 ...5....4
...5....1 ...5....2 ...5....3 ...5....4 ...5....5 ...5....6 ...5....7 ...5....8 ...5....9 ...5....0 ...5....1 ...5....2 ...5....3 .
\c..5....4
r 11:12 0.139 0

Change History (0)

Note: See TracTickets for help on using tickets.