at_bottom?   at_top?   cancel_search!   col_left   col_right   continue_search_in_buffer   draw   draw_line   draw_line_from_array   draw_line_from_string   ensure_mode_validity   find_text   half_page_down   half_page_up   in_search?   jump_to_col   jump_to_end   jump_to_left   jump_to_line   jump_to_start   line_down   line_up   matching_text_array   new   page_down   page_up   resize   rightcol   search_goto_line   search_goto_pos   search_in_buffer   search_start_line  

COL_JUMP

=

2

botline	[R]	we left leftcol and rightcol as the left and right columns of any content in the current view. but since we‘re operating in a line-centric fashion, rightcol is always leftcol + the buffer width. (whereas botline is topline + at most the buffer height, and can be == to topline in the case that there‘s no content.)
leftcol	[R]	we left leftcol and rightcol as the left and right columns of any content in the current view. but since we‘re operating in a line-centric fashion, rightcol is always leftcol + the buffer width. (whereas botline is topline + at most the buffer height, and can be == to topline in the case that there‘s no content.)
status	[R]	we left leftcol and rightcol as the left and right columns of any content in the current view. but since we‘re operating in a line-centric fashion, rightcol is always leftcol + the buffer width. (whereas botline is topline + at most the buffer height, and can be == to topline in the case that there‘s no content.)
topline	[R]	we left leftcol and rightcol as the left and right columns of any content in the current view. but since we‘re operating in a line-centric fashion, rightcol is always leftcol + the buffer width. (whereas botline is topline + at most the buffer height, and can be == to topline in the case that there‘s no content.)