Searched refs:relative_move (Results 1 – 2 of 2) sorted by relevance
566 relative_move(NCURSES_SP_DCLx in relative_move() function846 && ((newcost = relative_move(NCURSES_SP_ARGx in onscreen_mvcur()857 && ((newcost = relative_move(NCURSES_SP_ARGx in onscreen_mvcur()868 && ((newcost = relative_move(NCURSES_SP_ARGx in onscreen_mvcur()879 && ((newcost = relative_move(NCURSES_SP_ARGx in onscreen_mvcur()895 && ((newcost = relative_move(NCURSES_SP_ARGx in onscreen_mvcur()911 (void) relative_move(NCURSES_SP_ARGx in onscreen_mvcur()918 (void) relative_move(NCURSES_SP_ARGx in onscreen_mvcur()925 (void) relative_move(NCURSES_SP_ARGx in onscreen_mvcur()931 (void) relative_move(NCURSES_SP_ARGx in onscreen_mvcur()[all …]
11358 + prevent relative_move() from doing an overwrite if it detects 8-bit11564 + add a check in relative_move() to guard against buffer overflow in13070 + modify relative_move and tputs to avoid an interaction with the13071 BSD-style padding. The relative_move function could produce a string13073 was then interpreted by tputs as padding. Now relative_move will not14418 + correct initialization of vcost in relative_move(), for cursor-down