text:
ncurses(3) ncurses(3)
ncurses - CRT screen handling and optimization package
#include <curses.h>
The ncurses library routines give the user a terminal-independent method of updating character screens with reasonable optimization. This implementation is "new curses" (ncurses) and is the approved replacement for 4.4BSD classic curses, which has been discontinued. This describes ncurses version 6.4 (patch 20221231). The ncurses library emulates the curses library of System V Release 4 UNIX, and XPG4 (X/Open Portability Guide) curses (also known as XSI curses). XSI stands for X/Open System Interfaces Extension. The ncurses library is freely redistributable in source form. Differences from the SVr4 curses are summarized under the EXTENSIONS and PORTABILITY sections below and described in detail in the respective EXTENSIONS, PORTABILITY and BUGS sections of individual man pages. The ncurses library also provides many useful extensions, i.e., features which cannot be implemented by a simple add-on library but which require access to the internals of the library. A program using these routines must be linked with the -lncurses option, or (if it has been generated) with the debugging library -lncurses_g. (Your system integrator may also have installed these libraries under the names -lcurses and -lcurses_g.) The ncurses_g library generates trace logs (in a file called "trace" in the current directory) that describe curses actions. See also the section on ALTERNATE CONFIGURATIONS. The ncurses package supports: overall screen, window and pad manipulation; output to windows and pads; reading terminal input; control over terminal and curses input and output options; environment query routines; color manipulation; use of soft label keys; terminfo capabilities; and access to low-level terminal-manipulation routines. Initialization The library uses the locale which the calling program has initialized. That is normally done with setlocale(3): setlocale(LC_ALL, ""); If the locale is not initialized, the library assumes that characters are printable as in ISO-8859-1, to work with certain legacy programs. You should initialize the locale and not rely on specific details of the library when the locale has not been setup. The function initscr or newterm must be called to initialize the library before any of the other routines that deal with windows and screens are used. The routine endwin(3X) must be called before exiting. To get character-at-a-time input without echoing (most interactive, screen oriented programs want this), the following sequence should be used: initscr(); cbreak(); noecho(); Most programs would additionally use the sequence: intrflush(stdscr, FALSE); keypad(stdscr, TRUE); Before a curses program is run, the tab stops of the terminal should be set and its initialization strings, if defined, must be output. This can be done by executing the tput init command after the shell environment variable TERM has been exported. tset(1) is usually responsible for doing this. [See terminfo(5) for further details.] Datatypes The ncurses library permits manipulation of data structures, called windows, which can be thought of as two-dimensional arrays of characters representing all or part of a CRT screen. A default window called stdscr, which is the size of the terminal screen, is supplied. Others may be created with newwin. Note that curses does not handle overlapping windows, that's done by the panel(3X) library. This means that you can either use stdscr or divide the screen into tiled windows and not using stdscr at all. Mixing the two will result in unpredictable, and undesired, effects. Windows are referred to by variables declared as WINDOW *. These data structures are manipulated with routines described here and elsewhere in the ncurses manual pages. Among those, the most basic routines are move and addch. More general versions of these routines are included with names beginning with w, allowing the user to specify a window. The routines not beginning with w affect stdscr. After using routines to manipulate a window, refresh(3X) is called, telling curses to make the user's CRT screen look like stdscr. The characters in a window are actually of type chtype, (character and attribute data) so that other information about the character may also be stored with each character. Special windows called pads may also be manipulated. These are windows which are not constrained to the size of the screen and whose contents need not be completely displayed. See curs_pad(3X) for more information. In addition to drawing characters on the screen, video attributes and colors may be supported, causing the characters to show up in such modes as underlined, in reverse video, or in color on terminals that support such display enhancements. Line drawing characters may be specified to be output. On input, curses is also able to translate arrow and function keys that transmit escape sequences into single values. The video attributes, line drawing characters, and input values use names, defined in <curses.h>, such as A_REVERSE, ACS_HLINE, and KEY_LEFT. Environment variables If the environment variables LINES and COLUMNS are set, or if the program is executing in a window environment, line and column information in the environment will override information read by terminfo. This would affect a program running in an AT&T 630 layer, for example, where the size of a screen is changeable (see ENVIRONMENT). If the environment variable TERMINFO is defined, any program using curses checks for a local terminal definition before checking in the standard place. For example, if TERM is set to att4424, then the compiled terminal definition is found in /opt/local/share/terminfo/a/att4424. (The a is copied from the first letter of att4424 to avoid creation of huge directories.) However, if TERMINFO is set to $HOME/myterms, curses first checks $HOME/myterms/a/att4424, and if that fails, it then checks /opt/local/share/terminfo/a/att4424. This is useful for developing experimental definitions or when write permission in /opt/local/share/terminfo is not available. The integer variables LINES and COLS are defined in <curses.h> and will be filled in by initscr with the size of the screen. The constants TRUE and FALSE have the values 1 and 0, respectively. The curses routines also define the WINDOW * variable curscr which is used for certain low-level operations like clearing and redrawing a screen containing garbage. The curscr can be used in only a few routines. Routine and Argument Names Many curses routines have two or more versions. The routines prefixed with w require a window argument. The routines prefixed with p require a pad argument. Those without a prefix generally use stdscr. The routines prefixed with mv require a y and x coordinate to move to before performing the appropriate action. The mv routines imply a call to move before the call to the other routine. The coordinate y always refers to the row (of the window), and x always refers to the column. The upper left-hand corner is always (0,0), not (1,1). The routines prefixed with mvw take both a window argument and x and y coordinates. The window argument is always specified before the coordinates. In each case, win is the window affected, and pad is the pad affected; win and pad are always pointers to type WINDOW. Option setting routines require a Boolean flag bf with the value TRUE or FALSE; bf is always of type bool. Most of the data types used in the library routines, such as WINDOW, SCREEN, bool, and chtype are defined in <curses.h>. Types used for the terminfo routines such as TERMINAL are defined in <term.h>. This manual page describes functions which may appear in any configuration of the library. There are two common configurations of the library: ncurses the "normal" library, which handles 8-bit characters. The normal (8-bit) library stores characters combined with attributes in chtype data. Attributes alone (no corresponding character) may be stored in chtype or the equivalent attr_t data. In either case, the data is stored in something like an integer. Each cell (row and column) in a WINDOW is stored as a chtype. ncursesw the so-called "wide" library, which handles multibyte characters (see the section on ALTERNATE CONFIGURATIONS). The "wide" library includes all of the calls from the "normal" library. It adds about one third more calls using data types which store multibyte characters: cchar_t corresponds to chtype. However it is a structure, because more data is stored than can fit into an integer. The characters are large enough to require a full integer value - and there may be more than one character per cell. The video attributes and color are stored in separate fields of the structure. Each cell (row and column) in a WINDOW is stored as a cchar_t. The setcchar(3X) and getcchar(3X) functions store and retrieve the data from a cchar_t structure. wchar_t stores a "wide" character. Like chtype, this may be an integer. wint_t stores a wchar_t or WEOF - not the same, though both may have the same size. The "wide" library provides new functions which are analogous to functions in the "normal" library. There is a naming convention which relates many of the normal/wide variants: a "_w" is inserted into the name. For example, waddch becomes wadd_wch. Routine Name Index The following table lists the curses routines provided in the "normal" and "wide" libraries and the names of the manual pages on which they are described. Routines flagged with "*" are ncurses-specific, not described by XPG4 or present in SVr4. curses Routine Name Manual Page Name ============================================= COLOR_PAIR curs_color(3X) PAIR_NUMBER curs_attr(3X) add_wch curs_add_wch(3X) add_wchnstr curs_add_wchstr(3X) add_wchstr curs_add_wchstr(3X) addch curs_addch(3X) addchnstr curs_addchstr(3X) addchstr curs_addchstr(3X) addnstr curs_addstr(3X) addnwstr curs_addwstr(3X) addstr curs_addstr(3X) addwstr curs_addwstr(3X) alloc_pair new_pair(3X)* assume_default_colors default_colors(3X)* attr_get curs_attr(3X) attr_off curs_attr(3X) attr_on curs_attr(3X) attr_set curs_attr(3X) attroff curs_attr(3X) attron curs_attr(3X) attrset curs_attr(3X) baudrate curs_termattrs(3X) beep curs_beep(3X) bkgd curs_bkgd(3X) bkgdset curs_bkgd(3X) bkgrnd curs_bkgrnd(3X) bkgrndset curs_bkgrnd(3X) border curs_border(3X) border_set curs_border_set(3X) box curs_border(3X) box_set curs_border_set(3X) can_change_color curs_color(3X) cbreak curs_inopts(3X) chgat curs_attr(3X) clear curs_clear(3X) clearok curs_outopts(3X) clrtobot curs_clear(3X) clrtoeol curs_clear(3X) color_content curs_color(3X) color_set curs_attr(3X) copywin curs_overlay(3X) curs_set curs_kernel(3X) curses_trace curs_trace(3X)* curses_version curs_extend(3X)* def_prog_mode curs_kernel(3X) def_shell_mode curs_kernel(3X) define_key define_key(3X)* del_curterm curs_terminfo(3X) delay_output curs_util(3X) delch curs_delch(3X) deleteln curs_deleteln(3X) delscreen curs_initscr(3X) delwin curs_window(3X) derwin curs_window(3X) doupdate curs_refresh(3X) dupwin curs_window(3X) echo curs_inopts(3X) echo_wchar curs_add_wch(3X) echochar curs_addch(3X) endwin curs_initscr(3X) erase curs_clear(3X) erasechar curs_termattrs(3X) erasewchar curs_termattrs(3X) exit_curses curs_memleaks(3X)* exit_terminfo curs_memleaks(3X)* extended_color_content curs_color(3X)* extended_pair_content curs_color(3X)* extended_slk_color curs_slk(3X)* filter curs_util(3X) find_pair new_pair(3X)* flash curs_beep(3X) flushinp curs_util(3X) free_pair new_pair(3X)* get_wch curs_get_wch(3X) get_wstr curs_get_wstr(3X) getattrs curs_attr(3X) getbegx curs_legacy(3X)* getbegy curs_legacy(3X)* getbegyx curs_getyx(3X) getbkgd curs_bkgd(3X) getbkgrnd curs_bkgrnd(3X) getcchar curs_getcchar(3X) getch curs_getch(3X) getcurx curs_legacy(3X)* getcury curs_legacy(3X)* getmaxx curs_legacy(3X)* getmaxy curs_legacy(3X)* getmaxyx curs_getyx(3X) getmouse curs_mouse(3X)* getn_wstr curs_get_wstr(3X) getnstr curs_getstr(3X) getparx curs_legacy(3X)* getpary curs_legacy(3X)* getparyx curs_getyx(3X) getstr curs_getstr(3X) getsyx curs_kernel(3X) getwin curs_util(3X) getyx curs_getyx(3X) halfdelay curs_inopts(3X) has_colors curs_color(3X) has_ic curs_termattrs(3X) has_il curs_termattrs(3X) has_key curs_getch(3X)* has_mouse curs_mouse(3X)* hline curs_border(3X) hline_set curs_border_set(3X) idcok curs_outopts(3X) idlok curs_outopts(3X) immedok curs_outopts(3X) in_wch curs_in_wch(3X) in_wchnstr curs_in_wchstr(3X) in_wchstr curs_in_wchstr(3X) inch curs_inch(3X) inchnstr curs_inchstr(3X) inchstr curs_inchstr(3X) init_color curs_color(3X) init_extended_color curs_color(3X)* init_extended_pair curs_color(3X)* init_pair curs_color(3X) initscr curs_initscr(3X) innstr curs_instr(3X) innwstr curs_inwstr(3X) ins_nwstr curs_ins_wstr(3X) ins_wch curs_ins_wch(3X) ins_wstr curs_ins_wstr(3X) insch curs_insch(3X) insdelln curs_deleteln(3X) insertln curs_deleteln(3X) insnstr curs_insstr(3X) insstr curs_insstr(3X) instr curs_instr(3X) intrflush curs_inopts(3X) inwstr curs_inwstr(3X) is_cleared curs_opaque(3X)* is_idcok curs_opaque(3X)* is_idlok curs_opaque(3X)* is_immedok curs_opaque(3X)* is_keypad curs_opaque(3X)* is_leaveok curs_opaque(3X)* is_linetouched curs_touch(3X) is_nodelay curs_opaque(3X)* is_notimeout curs_opaque(3X)* is_pad curs_opaque(3X)* is_scrollok curs_opaque(3X)* is_subwin curs_opaque(3X)* is_syncok curs_opaque(3X)* is_term_resized resizeterm(3X)* is_wintouched curs_touch(3X) isendwin curs_initscr(3X) key_defined key_defined(3X)* key_name curs_util(3X) keybound keybound(3X)* keyname curs_util(3X) keyok keyok(3X)* keypad curs_inopts(3X) killchar curs_termattrs(3X) killwchar curs_termattrs(3X) leaveok curs_outopts(3X) longname curs_termattrs(3X) mcprint curs_print(3X)* meta curs_inopts(3X) mouse_trafo curs_mouse(3X)* mouseinterval curs_mouse(3X)* mousemask curs_mouse(3X)* move curs_move(3X) mvadd_wch curs_add_wch(3X) mvadd_wchnstr curs_add_wchstr(3X) mvadd_wchstr curs_add_wchstr(3X) mvaddch curs_addch(3X) mvaddchnstr curs_addchstr(3X) mvaddchstr curs_addchstr(3X) mvaddnstr curs_addstr(3X) mvaddnwstr curs_addwstr(3X) mvaddstr curs_addstr(3X) mvaddwstr curs_addwstr(3X) mvchgat curs_attr(3X) mvcur curs_terminfo(3X) mvdelch curs_delch(3X) mvderwin curs_window(3X) mvget_wch curs_get_wch(3X) mvget_wstr curs_get_wstr(3X) mvgetch curs_getch(3X) mvgetn_wstr curs_get_wstr(3X) mvgetnstr curs_getstr(3X) mvgetstr curs_getstr(3X) mvhline curs_border(3X) mvhline_set curs_border_set(3X) mvin_wch curs_in_wch(3X) mvin_wchnstr curs_in_wchstr(3X) mvin_wchstr curs_in_wchstr(3X) mvinch curs_inch(3X) mvinchnstr curs_inchstr(3X) mvinchstr curs_inchstr(3X) mvinnstr curs_instr(3X) mvinnwstr curs_inwstr(3X) mvins_nwstr curs_ins_wstr(3X) mvins_wch curs_ins_wch(3X) mvins_wstr curs_ins_wstr(3X) mvinsch curs_insch(3X) mvinsnstr curs_insstr(3X) mvinsstr curs_insstr(3X) mvinstr curs_instr(3X) mvinwstr curs_inwstr(3X) mvprintw curs_printw(3X) mvscanw curs_scanw(3X) mvvline curs_border(3X) mvvline_set curs_border_set(3X) mvwadd_wch curs_add_wch(3X) mvwadd_wchnstr curs_add_wchstr(3X) mvwadd_wchstr curs_add_wchstr(3X) mvwaddch curs_addch(3X) mvwaddchnstr curs_addchstr(3X) mvwaddchstr curs_addchstr(3X) mvwaddnstr curs_addstr(3X) mvwaddnwstr curs_addwstr(3X) mvwaddstr curs_addstr(3X) mvwaddwstr curs_addwstr(3X) mvwchgat curs_attr(3X) mvwdelch curs_delch(3X) mvwget_wch curs_get_wch(3X) mvwget_wstr curs_get_wstr(3X) mvwgetch curs_getch(3X) mvwgetn_wstr curs_get_wstr(3X) mvwgetnstr curs_getstr(3X) mvwgetstr curs_getstr(3X) mvwhline curs_border(3X) mvwhline_set curs_border_set(3X) mvwin curs_window(3X) mvwin_wch curs_in_wch(3X) mvwin_wchnstr curs_in_wchstr(3X) mvwin_wchstr curs_in_wchstr(3X) mvwinch curs_inch(3X) mvwinchnstr curs_inchstr(3X) mvwinchstr curs_inchstr(3X) mvwinnstr curs_instr(3X) mvwinnwstr curs_inwstr(3X) mvwins_nwstr curs_ins_wstr(3X) mvwins_wch curs_ins_wch(3X) mvwins_wstr curs_ins_wstr(3X) mvwinsch curs_insch(3X) mvwinsnstr curs_insstr(3X) mvwinsstr curs_insstr(3X) mvwinstr curs_instr(3X) mvwinwstr curs_inwstr(3X) mvwprintw curs_printw(3X) mvwscanw curs_scanw(3X) mvwvline curs_border(3X) mvwvline_set curs_border_set(3X) napms curs_kernel(3X) newpad curs_pad(3X) newterm curs_initscr(3X) newwin curs_window(3X) nl curs_inopts(3X) nocbreak curs_inopts(3X) nodelay curs_inopts(3X) noecho curs_inopts(3X) nofilter curs_util(3X)* nonl curs_inopts(3X) noqiflush curs_inopts(3X) noraw curs_inopts(3X) notimeout curs_inopts(3X) overlay curs_overlay(3X) overwrite curs_overlay(3X) pair_content curs_color(3X) pecho_wchar curs_pad(3X)* pechochar curs_pad(3X) pnoutrefresh curs_pad(3X) prefresh curs_pad(3X) printw curs_printw(3X) putp curs_terminfo(3X) putwin curs_util(3X) qiflush curs_inopts(3X) raw curs_inopts(3X) redrawwin curs_refresh(3X) refresh curs_refresh(3X) reset_color_pairs curs_color(3X)* reset_prog_mode curs_kernel(3X) reset_shell_mode curs_kernel(3X) resetty curs_kernel(3X) resize_term resizeterm(3X)* resizeterm resizeterm(3X)* restartterm curs_terminfo(3X) ripoffline curs_kernel(3X) savetty curs_kernel(3X) scanw curs_scanw(3X) scr_dump curs_scr_dump(3X) scr_init curs_scr_dump(3X) scr_restore curs_scr_dump(3X) scr_set curs_scr_dump(3X) scrl curs_scroll(3X) scroll curs_scroll(3X) scrollok curs_outopts(3X) set_curterm curs_terminfo(3X) set_term curs_initscr(3X) setcchar curs_getcchar(3X) setscrreg curs_outopts(3X) setsyx curs_kernel(3X) setupterm curs_terminfo(3X) slk_attr curs_slk(3X)* slk_attr_off curs_slk(3X) slk_attr_on curs_slk(3X) slk_attr_set curs_slk(3X) slk_attroff curs_slk(3X) slk_attron curs_slk(3X) slk_attrset curs_slk(3X) slk_clear curs_slk(3X) slk_color curs_slk(3X) slk_init curs_slk(3X) slk_label curs_slk(3X) slk_noutrefresh curs_slk(3X) slk_refresh curs_slk(3X) slk_restore curs_slk(3X) slk_set curs_slk(3X) slk_touch curs_slk(3X) slk_wset curs_slk(3X)* standend curs_attr(3X) standout curs_attr(3X) start_color curs_color(3X) subpad curs_pad(3X) subwin curs_window(3X) syncok curs_window(3X) term_attrs curs_termattrs(3X) termattrs curs_termattrs(3X) termname curs_termattrs(3X) tgetent curs_termcap(3X) tgetflag curs_termcap(3X) tgetnum curs_termcap(3X) tgetstr curs_termcap(3X) tgoto curs_termcap(3X) tigetflag curs_terminfo(3X) tigetnum curs_terminfo(3X) tigetstr curs_terminfo(3X) timeout curs_inopts(3X) tiparm curs_terminfo(3X)* touchline curs_touch(3X) touchwin curs_touch(3X) tparm curs_terminfo(3X) tputs curs_termcap(3X) tputs curs_terminfo(3X) trace curs_trace(3X)* typeahead curs_inopts(3X) unctrl curs_util(3X) unget_wch curs_get_wch(3X) ungetch curs_getch(3X) ungetmouse curs_mouse(3X)* untouchwin curs_touch(3X) use_default_colors default_colors(3X)* use_env curs_util(3X) use_extended_names curs_extend(3X)* use_legacy_coding legacy_coding(3X)* use_tioctl curs_util(3X)* vid_attr curs_terminfo(3X) vid_puts curs_terminfo(3X) vidattr curs_terminfo(3X) vidputs curs_terminfo(3X) vline curs_border(3X) vline_set curs_border_set(3X) vw_printw curs_printw(3X) vw_scanw curs_scanw(3X) vwprintw curs_printw(3X) vwscanw curs_scanw(3X) wadd_wch curs_add_wch(3X) wadd_wchnstr curs_add_wchstr(3X) wadd_wchstr curs_add_wchstr(3X) waddch curs_addch(3X) waddchnstr curs_addchstr(3X) waddchstr curs_addchstr(3X) waddnstr curs_addstr(3X) waddnwstr curs_addwstr(3X) waddstr curs_addstr(3X) waddwstr curs_addwstr(3X) wattr_get curs_attr(3X) wattr_off curs_attr(3X) wattr_on curs_attr(3X) wattr_set curs_attr(3X) wattroff curs_attr(3X) wattron curs_attr(3X) wattrset curs_attr(3X) wbkgd curs_bkgd(3X) wbkgdset curs_bkgd(3X) wbkgrnd curs_bkgrnd(3X) wbkgrndset curs_bkgrnd(3X) wborder curs_border(3X) wborder_set curs_border_set(3X) wchgat curs_attr(3X) wclear curs_clear(3X) wclrtobot curs_clear(3X) wclrtoeol curs_clear(3X) wcolor_set curs_attr(3X) wcursyncup curs_window(3X) wdelch curs_delch(3X) wdeleteln curs_deleteln(3X) wecho_wchar curs_add_wch(3X) wechochar curs_addch(3X) wenclose curs_mouse(3X)* werase curs_clear(3X) wget_wch curs_get_wch(3X) wget_wstr curs_get_wstr(3X) wgetbkgrnd curs_bkgrnd(3X) wgetch curs_getch(3X) wgetdelay curs_opaque(3X)* wgetn_wstr curs_get_wstr(3X) wgetnstr curs_getstr(3X) wgetparent curs_opaque(3X)* wgetscrreg curs_opaque(3X)* wgetstr curs_getstr(3X) whline curs_border(3X) whline_set curs_border_set(3X) win_wch curs_in_wch(3X) win_wchnstr curs_in_wchstr(3X) win_wchstr curs_in_wchstr(3X) winch curs_inch(3X) winchnstr curs_inchstr(3X) winchstr curs_inchstr(3X) winnstr curs_instr(3X) winnwstr curs_inwstr(3X) wins_nwstr curs_ins_wstr(3X) wins_wch curs_ins_wch(3X) wins_wstr curs_ins_wstr(3X) winsch curs_insch(3X) winsdelln curs_deleteln(3X) winsertln curs_deleteln(3X) winsnstr curs_insstr(3X) winsstr curs_insstr(3X) winstr curs_instr(3X) winwstr curs_inwstr(3X) wmouse_trafo curs_mouse(3X)* wmove curs_move(3X) wnoutrefresh curs_refresh(3X) wprintw curs_printw(3X) wredrawln curs_refresh(3X) wrefresh curs_refresh(3X) wresize wresize(3X)* wscanw curs_scanw(3X) wscrl curs_scroll(3X) wsetscrreg curs_outopts(3X) wstandend curs_attr(3X) wstandout curs_attr(3X) wsyncdown curs_window(3X) wsyncup curs_window(3X) wtimeout curs_inopts(3X) wtouchln curs_touch(3X) wunctrl curs_util(3X) wvline curs_border(3X) wvline_set curs_border_set(3X) Depending on the configuration, additional sets of functions may be available: curs_memleaks(3X) - curses memory-leak checking curs_sp_funcs(3X) - curses screen-pointer extension curs_threads(3X) - curses thread support curs_trace(3X) - curses debugging routines
Routines that return an integer return ERR upon failure and an integer value other than ERR upon successful completion, unless otherwise noted in the routine descriptions. As a general rule, routines check for null pointers passed as parameters, and handle this as an error. All macros return the value of the w version, except setscrreg, wsetscrreg, getyx, getbegyx, and getmaxyx. The return values of setscrreg, wsetscrreg, getyx, getbegyx, and getmaxyx are undefined (i.e., these should not be used as the right-hand side of assignment statements). Functions with a "mv" prefix first perform a cursor movement using wmove, and return an error if the position is outside the window, or if the window pointer is null. Most "mv"-prefixed functions (except variadic functions such as mvprintw) are provided both as macros and functions. Routines that return pointers return NULL on error.
The following environment symbols are useful for customizing the runtime behavior of the ncurses library. The most important ones have been already discussed in detail. CC command-character When set, change occurrences of the command_character (i.e., the cmdch capability) of the loaded terminfo entries to the value of this variable. Very few terminfo entries provide this feature. Because this name is also used in development environments to represent the C compiler's name, ncurses ignores it if it does not happen to be a single character. BAUDRATE The debugging library checks this environment variable when the application has redirected output to a file. The variable's numeric value is used for the baudrate. If no value is found, ncurses uses 9600. This allows testers to construct repeatable test-cases that take into account costs that depend on baudrate. COLUMNS Specify the width of the screen in characters. Applications running in a windowing environment usually are able to obtain the width of the window in which they are executing. If neither the COLUMNS value nor the terminal's screen size is available, ncurses uses the size which may be specified in the terminfo database (i.e., the cols capability). It is important that your application use a correct size for the screen. This is not always possible because your application may be running on a host which does not honor NAWS (Negotiations About Window Size), or because you are temporarily running as another user. However, setting COLUMNS and/or LINES overrides the library's use of the screen size obtained from the operating system. Either COLUMNS or LINES symbols may be specified independently. This is mainly useful to circumvent legacy misfeatures of terminal descriptions, e.g., xterm which commonly specifies a 65 line screen. For best results, lines and cols should not be specified in a terminal description for terminals which are run as emulations. Use the use_env function to disable all use of external environment (but not including system calls) to determine the screen size. Use the use_tioctl function to update COLUMNS or LINES to match the screen size obtained from system calls or the terminal database. ESCDELAY Specifies the total time, in milliseconds, for which ncurses will await a character sequence, e.g., a function key. The default value, 1000 milliseconds, is enough for most uses. However, it is made a variable to accommodate unusual applications. The most common instance where you may wish to change this value is to work with slow hosts, e.g., running on a network. If the host cannot read characters rapidly enough, it will have the same effect as if the terminal did not send characters rapidly enough. The library will still see a timeout. Note that xterm mouse events are built up from character sequences received from the xterm. If your application makes heavy use of multiple-clicking, you may wish to lengthen this default value because the timeout applies to the composed multi-click event as well as the individual clicks. In addition to the environment variable, this implementation provides a global variable with the same name. Portable applications should not rely upon the presence of ESCDELAY in either form, but setting the environment variable rather than the global variable does not create problems when compiling an application. HOME Tells ncurses where your home directory is. That is where it may read and write auxiliary terminal descriptions: $HOME/.termcap $HOME/.terminfo LINES Like COLUMNS, specify the height of the screen in characters. See COLUMNS for a detailed description. MOUSE_BUTTONS_123 This applies only to the OS/2 EMX port. It specifies the order of buttons on the mouse. OS/2 numbers a 3-button mouse inconsistently from other platforms: 1 = left 2 = right 3 = middle. This variable lets you customize the mouse. The variable must be three numeric digits 1-3 in any order, e.g., 123 or 321. If it is not specified, ncurses uses 132. NCURSES_ASSUMED_COLORS Override the compiled-in assumption that the terminal's default colors are white-on-black (see default_colors(3X)). You may set the foreground and background color values with this environment variable by proving a 2-element list: foreground,background. For example, to tell ncurses to not assume anything about the colors, set this to "-1,-1". To make it green-on-black, set it to "2,0". Any positive value from zero to the terminfo max_colors value is allowed. NCURSES_CONSOLE2 This applies only to the MinGW port of ncurses. The Console2 program's handling of the Microsoft Console API call CreateConsoleScreenBuffer is defective. Applications which use this will hang. However, it is possible to simulate the action of this call by mapping coordinates, explicitly saving and restoring the original screen contents. Setting the environment variable NCGDB has the same effect. NCURSES_GPM_TERMS This applies only to ncurses configured to use the GPM interface. If present, the environment variable is a list of one or more terminal names against which the TERM environment variable is matched. Setting it to an empty value disables the GPM interface; using the built-in support for xterm, etc. If the environment variable is absent, ncurses will attempt to open GPM if TERM contains "linux". NCURSES_NO_HARD_TABS Ncurses may use tabs as part of the cursor movement optimization. In some cases, your terminal driver may not handle these properly. Set this environment variable to disable the feature. You can also adjust your stty(1) settings to avoid the problem. NCURSES_NO_MAGIC_COOKIE Some terminals use a magic-cookie feature which requires special handling to make highlighting and other video attributes display properly. You can suppress the highlighting entirely for these terminals by setting this environment variable. NCURSES_NO_PADDING Most of the terminal descriptions in the terminfo database are written for real "hardware" terminals. Many people use terminal emulators which run in a windowing environment and use curses-based applications. Terminal emulators can duplicate all of the important aspects of a hardware terminal, but they do not have the same limitations. The chief limitation of a hardware terminal from the standpoint of your application is the management of dataflow, i.e., timing. Unless a hardware terminal is interfaced into a terminal concentrator (which does flow control), it (or your application) must manage dataflow, preventing overruns. The cheapest solution (no hardware cost) is for your program to do this by pausing after operations that the terminal does slowly, such as clearing the display. As a result, many terminal descriptions (including the vt100) have delay times embedded. You may wish to use these descriptions, but not want to pay the performance penalty. Set the NCURSES_NO_PADDING environment variable to disable all but mandatory padding. Mandatory padding is used as a part of special control sequences such as flash. NCURSES_NO_SETBUF This setting is obsolete. Before changes o started with 5.9 patch 20120825 and o continued though 5.9 patch 20130126 ncurses enabled buffered output during terminal initialization. This was done (as in SVr4 curses) for performance reasons. For testing purposes, both of ncurses and certain applications, this feature was made optional. Setting the NCURSES_NO_SETBUF variable disabled output buffering, leaving the output in the original (usually line buffered) mode. In the current implementation, ncurses performs its own buffering and does not require this workaround. It does not modify the buffering of the standard output. The reason for the change was to make the behavior for interrupts and other signals more robust. One drawback is that certain nonconventional programs would mix ordinary stdio calls with ncurses calls and (usually) work. This is no longer possible since ncurses is not using the buffered standard output but its own output (to the same file descriptor). As a special case, the low-level calls such as putp still use the standard output. But high-level curses calls do not. NCURSES_NO_UTF8_ACS During initialization, the ncurses library checks for special cases where VT100 line-drawing (and the corresponding alternate character set capabilities) described in the terminfo are known to be missing. Specifically, when running in a UTF-8 locale, the Linux console emulator and the GNU screen program ignore these. Ncurses checks the TERM environment variable for these. For other special cases, you should set this environment variable. Doing this tells ncurses to use Unicode values which correspond to the VT100 line-drawing glyphs. That works for the special cases cited, and is likely to work for terminal emulators. When setting this variable, you should set it to a nonzero value. Setting it to zero (or to a nonnumber) disables the special check for "linux" and "screen". As an alternative to the environment variable, ncurses checks for an extended terminfo capability U8. This is a numeric capability which can be compiled using tic -x. For example # linux console, if patched to provide working # VT100 shift-in/shift-out, with corresponding font. linux-vt100|linux console with VT100 line-graphics, U8#0, use=linux, # uxterm with vt100Graphics resource set to false xterm-utf8|xterm relying on UTF-8 line-graphics, U8#1, use=xterm, The name "U8" is chosen to be two characters, to permit it to be used by applications that use ncurses' termcap interface. NCURSES_TRACE During initialization, the ncurses debugging library checks the NCURSES_TRACE environment variable. If it is defined, to a numeric value, ncurses calls the trace function, using that value as the argument. The argument values, which are defined in curses.h, provide several types of information. When running with traces enabled, your application will write the file trace to the current directory. See curs_trace(3X) for more information. TERM Denotes your terminal type. Each terminal type is distinct, though many are similar. TERM is commonly set by terminal emulators to help applications find a workable terminal description. Some of those choose a popular approximation, e.g., "ansi", "vt100", "xterm" rather than an exact fit. Not infrequently, your application will have problems with that approach, e.g., incorrect function-key definitions. If you set TERM in your environment, it has no effect on the operation of the terminal emulator. It only affects the way applications work within the terminal. Likewise, as a general rule (xterm(1) being a rare exception), terminal emulators which allow you to specify TERM as a parameter or configuration value do not change their behavior to match that setting. TERMCAP If the ncurses library has been configured with termcap support, ncurses will check for a terminal's description in termcap form if it is not available in the terminfo database. The TERMCAP environment variable contains either a terminal description (with newlines stripped out), or a file name telling where the information denoted by the TERM environment variable exists. In either case, setting it directs ncurses to ignore the usual place for this information, e.g., /etc/termcap. TERMINFO ncurses can be configured to read from multiple terminal databases. The TERMINFO variable overrides the location for the default terminal database. Terminal descriptions (in terminal format) are stored in terminal databases: o Normally these are stored in a directory tree, using subdirectories named by the first letter of the terminal names therein. This is the scheme used in System V, which legacy Unix systems use, and the TERMINFO variable is used by curses applications on those systems to override the default location of the terminal database. o If ncurses is built to use hashed databases, then each entry in this list may be the path of a hashed database file, e.g., /usr/share/terminfo.db rather than /usr/share/terminfo/ The hashed database uses less disk-space and is a little faster than the directory tree. However, some applications assume the existence of the directory tree, reading it directly rather than using the terminfo library calls. o If ncurses is built with a support for reading termcap files directly, then an entry in this list may be the path of a termcap file. o If the TERMINFO variable begins with "hex:" or "b64:", ncurses uses the remainder of that variable as a compiled terminal description. You might produce the base64 format using infocmp(1M): TERMINFO="$(infocmp -0 -Q2 -q)" export TERMINFO The compiled description is used if it corresponds to the terminal identified by the TERM variable. Setting TERMINFO is the simplest, but not the only way to set location of the default terminal database. The complete list of database locations in order follows: o the last terminal database to which ncurses wrote, if any, is searched first o the location specified by the TERMINFO environment variable o $HOME/.terminfo o locations listed in the TERMINFO_DIRS environment variable o one or more locations whose names are configured and compiled into the ncurses library, i.e., o no default value (corresponding to the TERMINFO_DIRS variable) o /opt/local/share/terminfo (corresponding to the TERMINFO variable) TERMINFO_DIRS Specifies a list of locations to search for terminal descriptions. Each location in the list is a terminal database as described in the section on the TERMINFO variable. The list is separated by colons (i.e., ":") on Unix, semicolons on OS/2 EMX. There is no corresponding feature in System V terminfo; it is an extension developed for ncurses. TERMPATH If TERMCAP does not hold a file name then ncurses checks the TERMPATH environment variable. This is a list of filenames separated by spaces or colons (i.e., ":") on Unix, semicolons on OS/2 EMX. If the TERMPATH environment variable is not set, ncurses looks in the files /etc/termcap, /usr/share/misc/termcap and $HOME/.termcap, in that order. The library may be configured to disregard the following variables when the current user is the superuser (root), or if the application uses setuid or setgid permissions: $TERMINFO, $TERMINFO_DIRS, $TERMPATH, as well as $HOME.
Several different configurations are possible, depending on the configure script options used when building ncurses. There are a few main options whose effects are visible to the applications developer using ncurses: --disable-overwrite The standard include for ncurses is as noted in SYNOPSIS: #include <curses.h> This option is used to avoid filename conflicts when ncurses is not the main implementation of curses of the computer. If ncurses is installed disabling overwrite, it puts its headers in a subdirectory, e.g., #include <ncurses/curses.h> It also omits a symbolic link which would allow you to use -lcurses to build executables. --enable-widec The configure script renames the library and (if the --disable-overwrite option is used) puts the header files in a different subdirectory. All of the library names have a "w" appended to them, i.e., instead of -lncurses you link with -lncursesw You must also enable the wide-character features in the header file when compiling for the wide-character library to use the extended (wide-character) functions. The symbol which enables these features has changed since XSI Curses, Issue 4: o Originally, the wide-character feature required the symbol _XOPEN_SOURCE_EXTENDED but that was only valid for XPG4 (1996). o Later, that was deemed conflicting with _XOPEN_SOURCE defined to 500. o As of mid-2018, none of the features in this implementation require a _XOPEN_SOURCE feature greater than 600. However, X/Open Curses, Issue 7 (2009) recommends defining it to 700. o Alternatively, you can enable the feature by defining NCURSES_WIDECHAR with the caveat that some other header file than curses.h may require a specific value for _XOPEN_SOURCE (or a system-specific symbol). The curses.h file which is installed for the wide-character library is designed to be compatible with the normal library's header. Only the size of the WINDOW structure differs, and very few applications require more than a pointer to WINDOWs. If the headers are installed allowing overwrite, the wide-character library's headers should be installed last, to allow applications to be built using either library from the same set of headers. --with-pthread The configure script renames the library. All of the library names have a "t" appended to them (before any "w" added by --enable-widec). The global variables such as LINES are replaced by macros to allow read-only access. At the same time, setter-functions are provided to set these values. Some applications (very few) may require changes to work with this convention. --with-shared --with-normal --with-debug --with-profile The shared and normal (static) library names differ by their suffixes, e.g., libncurses.so and libncurses.a. The debug and profiling libraries add a "_g" and a "_p" to the root names respectively, e.g., libncurses_g.a and libncurses_p.a. --with-termlib Low-level functions which do not depend upon whether the library supports wide-characters, are provided in the tinfo library. By doing this, it is possible to share the tinfo library between wide/normal configurations as well as reduce the size of the library when only low-level functions are needed. Those functions are described in these pages: o curs_extend(3X) - miscellaneous curses extensions o curs_inopts(3X) - curses input options o curs_kernel(3X) - low-level curses routines o curs_termattrs(3X) - curses environment query routines o curs_termcap(3X) - curses emulation of termcap o curs_terminfo(3X) - curses interfaces to terminfo database o curs_util(3X) - miscellaneous curses utility routines --with-trace The trace function normally resides in the debug library, but it is sometimes useful to configure this in the shared library. Configure scripts should check for the function's existence rather than assuming it is always in the debug library.
/opt/local/share/tabset directory containing initialization files for the terminal capability database /opt/local/share/terminfo terminal capability database
terminfo(5) and related pages whose names begin "curs_" for detailed routine descriptions. curs_variables(3X) user_caps(5) for user-defined capabilities
The ncurses library can be compiled with an option (-DUSE_GETCAP) that falls back to the old-style /etc/termcap file if the terminal setup code cannot find a terminfo entry corresponding to TERM. Use of this feature is not recommended, as it essentially includes an entire termcap compiler in the ncurses startup code, at significant cost in core and startup cycles. The ncurses library includes facilities for capturing mouse events on certain terminals (including xterm). See the curs_mouse(3X) manual page for details. The ncurses library includes facilities for responding to window resizing events, e.g., when running in an xterm. See the resizeterm(3X) and wresize(3X) manual pages for details. In addition, the library may be configured with a SIGWINCH handler. The ncurses library extends the fixed set of function key capabilities of terminals by allowing the application designer to define additional key sequences at runtime. See the define_key(3X) key_defined(3X), and keyok(3X) manual pages for details. The ncurses library can exploit the capabilities of terminals which implement the ISO-6429 SGR 39 and SGR 49 controls, which allow an application to reset the terminal to its original foreground and background colors. From the users' perspective, the application is able to draw colored text on a background whose color is set independently, providing better control over color contrasts. See the default_colors(3X) manual page for details. The ncurses library includes a function for directing application output to a printer attached to the terminal device. See the curs_print(3X) manual page for details.
The ncurses library is intended to be BASE-level conformant with XSI Curses. The EXTENDED XSI Curses functionality (including color support) is supported. A small number of local differences (that is, individual differences between the XSI Curses and ncurses calls) are described in PORTABILITY sections of the library man pages. Error checking In many cases, X/Open Curses is vague about error conditions, omitting some of the SVr4 documentation. Unlike other implementations, this one checks parameters such as pointers to WINDOW structures to ensure they are not null. The main reason for providing this behavior is to guard against programmer error. The standard interface does not provide a way for the library to tell an application which of several possible errors were detected. Relying on this (or some other) extension will adversely affect the portability of curses applications. Extensions versus portability Most of the extensions provided by ncurses have not been standardized. Some have been incorporated into other implementations, such as PDCurses or NetBSD curses. Here are a few to consider: o The routine has_key is not part of XPG4, nor is it present in SVr4. See the curs_getch(3X) manual page for details. o The routine slk_attr is not part of XPG4, nor is it present in SVr4. See the curs_slk(3X) manual page for details. o The routines getmouse, mousemask, ungetmouse, mouseinterval, and wenclose relating to mouse interfacing are not part of XPG4, nor are they present in SVr4. See the curs_mouse(3X) manual page for details. o The routine mcprint was not present in any previous curses implementation. See the curs_print(3X) manual page for details. o The routine wresize is not part of XPG4, nor is it present in SVr4. See the wresize(3X) manual page for details. o The WINDOW structure's internal details can be hidden from application programs. See curs_opaque(3X) for the discussion of is_scrollok, etc. o This implementation can be configured to provide rudimentary support for multi-threaded applications. See curs_threads(3X) for details. o This implementation can also be configured to provide a set of functions which improve the ability to manage multiple screens. See curs_sp_funcs(3X) for details. Padding differences In historic curses versions, delays embedded in the capabilities cr, ind, cub1, ff and tab activated corresponding delay bits in the UNIX tty driver. In this implementation, all padding is done by sending NUL bytes. This method is slightly more expensive, but narrows the interface to the UNIX kernel significantly and increases the package's portability correspondingly. Header files The header file <curses.h> automatically includes the header files <stdio.h> and <unctrl.h>. X/Open Curses has more to say, but does not finish the story: The inclusion of <curses.h> may make visible all symbols from the headers <stdio.h>, <term.h>, <termios.h>, and <wchar.h>. Here is a more complete story: o Starting with BSD curses, all implementations have included <stdio.h>. BSD curses included <curses.h> and <unctrl.h> from an internal header "curses.ext" ("ext" was a short name for externs). BSD curses used <stdio.h> internally (for printw and scanw), but nothing in <curses.h> itself relied upon <stdio.h>. o SVr2 curses added newterm(3X), which relies upon <stdio.h>. That is, the function prototype uses FILE. SVr4 curses added putwin and getwin, which also use <stdio.h>. X/Open Curses documents all three of these functions. SVr4 curses and X/Open Curses do not require the developer to include <stdio.h> before including <curses.h>. Both document curses showing <curses.h> as the only required header. As a result, standard <curses.h> will always include <stdio.h>. o X/Open Curses is inconsistent with respect to SVr4 regarding <unctrl.h>. As noted in curs_util(3X), ncurses includes <unctrl.h> from <curses.h> (like SVr4). o X/Open's comments about <term.h> and <termios.h> may refer to HP-UX and AIX: HP-UX curses includes <term.h> from <curses.h> to declare setupterm in curses.h, but ncurses (and Solaris curses) do not. AIX curses includes <term.h> and <termios.h>. Again, ncurses (and Solaris curses) do not. o X/Open says that <curses.h> may include <term.h>, but there is no requirement that it do that. Some programs use functions declared in both <curses.h> and <term.h>, and must include both headers in the same module. Very old versions of AIX curses required including <curses.h> before including <term.h>. Because ncurses header files include the headers needed to define datatypes used in the headers, ncurses header files can be included in any order. But for portability, you should include <curses.h> before <term.h>. o X/Open Curses says "may make visible" because including a header file does not necessarily make all symbols in it visible (there are ifdef's to consider). For instance, in ncurses <wchar.h> may be included if the proper symbol is defined, and if ncurses is configured for wide-character support. If the header is included, its symbols may be made visible. That depends on the value used for _XOPEN_SOURCE feature test macro. o X/Open Curses documents one required header, in a special case: <stdarg.h> before <curses.h> to prototype the vw_printw and vw_scanw functions (as well as the obsolete the vwprintw and vwscanw functions). Each of those uses a va_list parameter. The two obsolete functions were introduced in SVr3. The other functions were introduced in X/Open Curses. In between, SVr4 curses provided for the possibility that an application might include either <varargs.h> or <stdarg.h>. Initially, that was done by using void* for the va_list parameter. Later, a special type (defined in <stdio.h>) was introduced, to allow for compiler type-checking. That special type is always available, because <stdio.h> is always included by <curses.h>. None of the X/Open Curses implementations require an application to include <stdarg.h> before <curses.h> because they either have allowed for a special type, or (like ncurses) include <stdarg.h> directly to provide a portable interface.
If standard output from a ncurses program is re-directed to something which is not a tty, screen updates will be directed to standard error. This was an undocumented feature of AT&T System V Release 3 curses.
Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey. Based on pcurses by Pavel Curtis. ncurses(3)
ncurses 6.4 - Generated Fri Jan 6 15:57:38 CST 2023


text:
Fill Out Your Profile to share more about you. Learn more...
Take Our Poll: How well do you feel your family understands your diagnosis?
High Risk of Recurrence or Second Breast Cancer
Archives for April 2015
Discussion List
Join Us on Zoom: Upcoming virtual meetups. Read more...
Give your account some personality! Add a profile photo.

subset: commoncrawl


text:
Or search by topic
Published 2011 Revised 2019
Bricks are 20cm long and 10cm high. How high could an arch be built without mortar on a flat horizontal surface, to overhang by 1 metre? How big an overhang is it possible to make like this?
Explain why, when moving heavy objects on rollers, the object moves twice as fast as the rollers. Try a similar experiment yourself.
Given the graph of a supply network and the maximum capacity for flow in each section find the maximum flow across the network.


text:
10 Things To Do Before You Become A Parent
I heard a song once - one of those songs that you hear on the radio in someone else's car, or over the soundsystem at the grocery store - that had a refrain about some woman regretting the fact, in her middle age, that she'd never driven a sports car around Paris, or something to that effect. I can't remember exactly; what stuck with me, mostly, was the thought that well, I'd been to Paris. So - I thought - I probably wouldn't have that regret. Which, as it turned out, was quite right: I'm not yet in my middle age, but I can see it on the horizon, and I'm happy to report that there seem to be no travel-related regrets forthcoming.
That said, I do have some regrets, of a sort; they're just not of the bucket-list variety. My regrets - such as they are, now that I'm a parent, with responsibilities and accountabilities and very limited ability to do as I please - are more of the man, I wish I'd appreciated that when kind of regret. (Regret is a bit strong. Let's call these retrospective yearnings.) I was thinking about this yesterday, as I lay on the couch with a cranium-rattling headache, trying to amuse the baby by weakly nudging a rattle toward him with my foot. In that moment, the idea that I might ever regret something like not being able to take off to Paris for the weekend struck me as absurd. Paris, schmaris. What I regretted most in that moment was the fact that in my pre-motherhood life I did not appreciate the luxury of being able to take to my bed when I was sick. Which got me thinking: if I knew then what I know now, what would I have done more often or appreciated more before I became a parent?
1. Get sick, and like it: I know, being sick is supposed to be a miserable thing. But is it, really? Assuming that your symptoms are not too brutal, and/or that you're able to medicate yourself into a happy stupor, there is much to enjoy about being sick. You stay in bed all day, drinking hot steamy drinks and slurping chicken soup and watching bad game shows and soap operas and Dr. Phil and maybe thumbing through some tabloids and napping and just generally enjoying the Vicks VapoRub-scented experience of convalescence. If you live with someone - and especially if that someone is a spouse or romantically beholden to you in anyway - you can bitch and whine at them and they will bring you more soup.
You cannot do this when you have small children. There are no sick days when you have small children. When you have small children, you cannot take to your bed and watch television and huff VapoRub. You have to parent. So what it you're dripping snot on the head of your wailing baby? That baby isn't going to feed/soothe/change himself. You're on duty, bitch. Deal with it.
2. Take naps. Take lots of naps. The kind where you doze off on the couch before dinner, the kind where you nod off at your desk at work, the kind where you just say screw Monday and go back to bed for an hour. Because what I said above about being on duty? That applies 24-7. Which means, no, you can't just take twenty minutes to "rest your eyes." Unless the baby is having his own nap, in which case you're welcome to try to nap, but I'm guessing that you might want to shower/bathe/eat, too, and you've probably only got forty minutes, so.
3. Shower/bathe. Enjoy your showers. Take lots of them, and make them long and hot. Also, baths, if you're a bath person. Long hot baths at all hours of the day. Twice a day, even! With bubbles and oils and magazines.
Oh, sure, it's not like you're forced to stop bathing and showering when the kids come along, but you will find that your bathing/shower regimen is seriously curtailed. You'll skip days - those days when eating and sleeping seem more pressing than cleanliness - and when you finally do get around to performing some ablutions? You'll be scrambling through that shower in less than three minutes because the baby is in his crib, shrieking, or you'll be splashing briefly in a lukewarm tub because the hot water tank got drained when the toddler's tub needed to be refilled, twice, after she a) brought a roll of toilet paper into the tub, because b) her 'poo-poo was coming.'
You will miss long, hot, leisurely baths and showers, I promise you. Enjoy them now.
4. Have a drink or two at lunch. You know how, sometimes, you go out for lunch on a Saturday and someone says, why don't we order a bottle of wine/get margaritas/have a beer? and you spend the afternoon eating and talking and drinking and working up a delicious buzz? And it's, like, totally fine, because you know that you can go home and have a nap and a bath before thinking about what your evening looks like? Yeah, you can't do that when you have small children, because a) you're probably not having lunch anywhere that sells a decent bottle of wine, and b) naps? baths? Ha. See above.
5. Cultivate and appreciate a hangover. Hangovers suck, right? Wrong. Hangovers only suck if you can't take a day off to recover from them. Hangovers, properly tended to, are similar to being sick, only with a little added frisson of shame to make things interesting. When you don't have small children, you can spend your hangover day in bed, watching television and eating potato chips and warding off that buzz of guilt with Oreos and chocolate milk. When you do have small children, you can't do this, for reasons that I've already stated. But you're probably not drinking all that much, either, so it's kind of a moot point.
6. Stay up late/sleep in. See above re: hangovers/being sick. You just really don't get to spend a lot of time in bed when you have small children.
7. Have sex whenever you want. Ditto.
8. Spend a rainy day watching an entire season of Buffy the Vampire Slayer. There's a theme emerging here, I know: things that you do while curled up in blankets on the sofa or in bed while eating junk food. I can't recommend these activities highly enough. I miss them desperately. If you asked me, would you like to take the family on a Caribbean vacation, or would you like to spend a week, by yourself, just laying around watching DVDs and reading books and eating cookie dough? I would really have to think about that.
Because, seriously: Paris, Barcelona, Tulum, whatever. Whenever I do get around to going back to those places, I'll probably want to take the kids anyway, because I want to see it all through their eyes and I want them to see what I've seen, blah blah blah. But a day off, where I do nothing but lounge and nap and snack and just generally indulge in some lazy-assed laziness? That place, I want to go to there. ALONE.
9. Eat chocolate chip cookie dough (or guilty pleasure food of choice) without any regard for who might be watching. I love cookie dough. I think that cookie dough is better than cookies. But I would strongly prefer that my three-year old eat, say, apple slices and cheese, rather than cookie dough, and so I conceal my cookie dough habit from her as best I can, with varying degrees of success. Just yesterday I was trying to nibble a hunk of chocolate chip cookie dough, torn from the end of a Pillsbury cookie dough package, when I was confronted by my daughter, who demanded to know what I was eating. It's cheese, I told her. Spicy cheese. The kind you don't like.
Those look like chocolate, she said, pointing at the chocolate chips.
They're raisins, I said. Spicy cheese raisins. Then I shoved the rest of it in my mouth and swallowed before she could get a closer look. It kind of ruined my enjoyment of the experience, quite frankly.
10. Take more naps. Seriously. I adore my children, and wouldn't trade them for anything in the world, but really: most days, I would pay serious cash money for a nap.
Or a long hot bath. Or some uninterrupted cookie dough indulgence. Or a day off. I wish that I'd known that back in the days when I could have them all for free.
But now you know. You're welcome.
(Parents: what would you add to this list? Would you take Paris or the Caribbean over Lounge Week? Am I the only lazy-assed layabout out here in momosphere-land? Or would you one-up me and demand two weeks? You know, enough time to watch all back-seasons of Lost and maybe also Battlestar Galactica?)
Labels: Being Bad


text:
One of the good things about the mangoes being out now is that there are no local fruits available and I can spend some time focusing on them. I find that during the summer when the local fruits start becoming available that it is rather like a whirlwind of one after the other or many at the same time and I don't get to fully enjoy any of them to the extent that I might like to. I had been wanting to try making a mango bread for a while and now was the time while it was still cool out and I don't mind having the oven on. For some reason I associate mangos with curries and chutneys and the first thing that I thought about for a mango bread was a curried mango bread. I had made, and enjoyed a curried chocolate chip banana bread a while ago and I was looking forward to trying a curried mango bread.
I found a recipe for Dorie Greenspan's Fresh Mango Bread on gatronomy that looked like a good starting point. Of course the first thing that I did was replace some of the all purpose flour with some whole wheat flour to make it a touch healthier. Next up was replacing the spices with some curry powder and some freshly grated ginger and garlic along with a chopped chili pepper for some heat. Raisins commonly go with chutney's so I left them in to accompany the mangoes and I had a recipe for a curried mango bread.
Like other quick breads the curried mango bread came together quickly and easily. One thing that I did notice about this recipe was that the batter was a bit drier that I was used to but everything worked out. This mango bread takes a bit longer to bake than some other quick breads that I have made but the toothpick test worked like a charm as usual and I got it out at the right time. Because this cake is in the oven longer than normal you might want to keep an eye on the crust and if it is getting too dark, cover it with foil.
The curried mango bread turned out really well! My apartment was filled with an amazing aroma of baking bread and warm curry. I could hardly keep myself from cutting off a slice as soon as it came out of the oven but I let it cool a bit first so that I could take some photos. The mango bread was nice and light and moist and the large chunks of mangoes in it were still fresh and juicy. The curry powder added a really nice hint of spices and warmth without overpowering any of the breads other flavours. The thing that I liked most about this bread was the crust. After baking in the oven for so long the crust was nice and thick though it gives way easily when you bite into it and it tastes like it has caramelized. I really liked both the texture and the caramelized flavour of the crust which along with the soft, moist and tasty inside makes this one of my favorite quick breads yet!
The mango and cardamom jam that I made earlier went really well on the curried mango bread for even more mango flavour!
Curried Mango Bread
- 1 1/2 cups all-purpose flour
- 1 cup whole wheat flour
- 1 teaspoon baking powder
- 1 teaspoon baking soda
- 1 cup sugar
- 1 tablespoon curry powder
- 1/4 teaspoon salt
- 3 large eggs
- 3/4 cup oil
- 1/2 cup light brown sugar (packed)
- 1 tablespoon garlic (grated)
- 1 tablespoon ginger (grated)
- 1 red chili (chopped)
- 1 lime (zest only)
- 2 cups mango (peeled, stoned and diced)
- 3/4 cup raisins
- Mix the flours, baking powder, baking soda, sugar, curry powder, and salt in a large bowl.
- Mix the eggs, oil, sugar, garlic, ginger, chili and lime zest in another large bowl.
- Mix the dry ingredients in to the wet ingredients.
- Mix the mango and raisins into the the batter.
- Pour the batter into a greased 9×5 inch loaf pan.
- Bake in a preheated 350F/180C oven until a tooth pick pushed into the center comes out clean, about 90 minutes.


text:
Or search by topic
Place four pebbles on the sand in the form of a square. Keep adding as few pebbles as necessary to double the area. How many extra pebbles are added each time?
Suppose we allow ourselves to use three numbers less than 10 and multiply them together. How many different products can you find? How do you know you've got them all?
Investigate the different shaped bracelets you could make from 18 different spherical beads. How do they compare if you use 24 beads?


text:
So many times I thought my dreams were over, but now that I look back at my "un-perfect" road to my dreams...I realize how perfect they actually were! Take a look at my dream-road timeline!
This is my crazy up and down, un-perfect path to my dreams, that I now see was totally perfect!
I dreamed of being an actress or fashion designer.
I get married at 17 find out I'm pregnant right before I turn 18....everyone tells me my future is over, now I'll never work in the movie biz!
I spend 2 years just taking care of my baby, but I'm in a verbally abusive and controlling marriage.
I finally leave, move home.
Go to beauty school.
Right when I graduate I get offered to work on a movie!
I love it!
Move to Hollywood.
It's hard being a single mom in LA, by yourself. I only had my roommate or my childhood friend, Jim, to help babysit, while I worked on photoshoots and my restaurant job. I was paying $550 a month just for my son's daycare...and had to turn down jobs because I didn't have anyone to watch him.
After doing this for a while....I decide to move back to my parents.
Now I really think my dreams are over.
I meet a guy...we get married, I'm pregnant again. (Now I really think things are over.)
I work on photoshoots and tv shows doing make-up, all the way until I'm 8 months pregnant, and get offered to travel with the tv show, but I can't because I was due with my baby girl!
This marriage is not good either, we hardly knew each other when we got married.
I try to work any make-up jobs I can get....I had to have my husband bring my daughter, after I'd been there for 2 hours, to breastfeed her in the photographer's office...the client walked in and was like, "what are you doing?!?"...
My mom even drove her around so she would sleep on one photo shoot, then I would have to borrow the photographers car, drive out of the location, meet my mom, breastfeed my daughter, then when she was about to fall asleep, my mom would take off driving, and I'd go back to the shoot!
Right when we are talking about getting divorced....I find out I'm pregnant again! Oh brother! Now I'm really done with!!
I had a photo shoot for VANS shoes when my son was 10 weeks old...my mom was up in the hotel where we were shooting with my son while he slept, then I would run up and breastfeed him, and pump milk for my mom (the only time he ever drank from bottle!). This was really hard.
I get divorced.
I am a single mom, trying to take care of my 3 kids with no money from fathers....and I have no idea how I'm going to work, since my mom was moving away!
I prayed and asked God to find a way for me to take care of my babies!
My friend tells me about youtube.
I start making videos.
I realize that touching people's hearts means more to me than any of the dreams I had of being in movies or designing clothes, or even doing make-up. I wanted to make people's hearts over, I wanted to fill them with love and hope.
My dream had a very bumpy road, that looked so far away. I remember sitting in my little tiny house, that only had a few windows, was really old and dark, crying, thinking my dreams will NEVER come true! Sitting at my gramma's house with my mom, my 3 kids, after I moved out from my husband's house, crying, again thinking...I am NEVER gonna have any of my dreams come true.
But little did I know, that, all of that was getting me to the place, I needed to be to find my real dream...and the dream wasn't even about me...it was about all of you....reaching your hearts...pouring love into each one of you...and hopefully watering the garden of YOUR dreams!
Having my Glaminars..is so much more than just staring your make-up career, it's about lighting a fire in your heart, filling you up with hope, and filling your heart up with love and happiness to shine in the world!
Thanks you all for being my dream come true! Each and every one of you are my little dreams! I love you and I am honored to be a part of your life!
huge huge love, your imperfect-perfect dream path coach, kandee


text:
* indicates required field
By clicking the button above you agree to our Terms of Use. We take your privacy seriously. For more information please read our Privacy Policy.
White Paper from OCT in Clinical Practice IQ Center
OCT- optical coherence tomography; is a critical tool in the diagnosis and management of vitreomacular interface abnormalities. With the creation of spectral-domain OCT systems, the ability of retinal physicians to evaluate the macular structure has been greatly improved. In this article an overview will be given of OCT and the management of vitreomacular interface abnormalities.
Ensure that document matches include...
...all of these word(s):
...and optionally include these word(s):
...but do not have these word(s):
Enter your phrase:
Enter the first few characters of a word:
There are 2 types of basic queries: Terms and Phrases. A Term is a single word search. A Phrase would wrap a string of words in quotes and find matches on the extact string.
Boolean Operators You can combine basic queries with Boolean operators to form a more complex query. Boolean operators define the relationships between Terms or Phrases. Our search supports the following Boolean operators: AND, "+", OR, NOT and "-". Please note that Boolean operators must be all uppercase.
AND example search: default AND document This is the default operator. It will be used if there is no Boolean operator between two terms. For example: default document is the same as default AND document. In this case both terms need to exist within a listing to find a match on that listing.The + character is synonymous with using AND.
OR example search: default OR document In this case just one of the terms needs to exist within a listing to find a match on that listing.
NOT example search: default NOT "document type" The NOT operator excludes documents that contain the term (or phrase) after NOT. So a listing match would have to include the word default but not the phrase "document type". The - character is synonymous with using NOT.
Wildcard/Prefix queries You can perform "wildcard" or "prefix" queries using the '*' operator. Whereas all of the previous search found exact matches on the whole term or phrase, a wildcard search will find partial matches. example search: ehr* This query will match all documents containing words beginning with the prefix 'ehr' like the word Ehrlichia.


text:
Welcome Patrollers and Friends! A resource for Nissan Patrol enthusiasts in Africa - LAUNCHED April 2009.
Skip to content
In order to login you must be registered. Registering takes only a few moments but gives you increased capabilities. The board administrator may also grant additional permissions to registered users. Before you register please ensure you are familiar with our terms of use and related policies. Please ensure you read any forum rules as you navigate around the board.
Terms of use | Privacy policy


text:
Cookie Usage
Colour Key
Sudden Death
Monthly Poll
Caption Comp
eMail Author
Photo Galleries
Design Lineage
Size Charts
Science / Tech
Maps / Politics
Site Guide
What's New
The Arsenal of Freedom
Your View
Title :
The Arsenal of Freedom
Series :
The Next Generation
Rating :
Overall Ep :
First Aired :
11 Apr 1988
Stardate :
Director :
Les Landau
Year :
Writers :
Maurice Hurley
Robert Lewin
Season Ep :
x 20
Main Cast :
LeVar Burton
Geordi La Forge
Denise Crosby
Natasha Yar
Michael Dorn
Worf Rozhenko
Jonathan Frakes
William T. Riker
Gates McFadden
Beverly Crusher
Marina Sirtis
Deanna Troi
Brent Spiner
Patrick Stewart
Jean-Luc Picard
Wil Wheaton
Wesley Crusher
Guest Cast :
Julia Nickson
Ensign Lian T'su
George De La Pena
Lieutenant Orfil Solis
Marco Rodriguez
Captain Paul Rice
Vyto Ruginis
Chief Engineer Logan
Vincent Schiavelli
Holographic Salesman
When Worf tries to target the cloaked vessel in orbit, it fires on the ship from almost directly behind. In reply, he fires directly ahead.
Great Moment :
Picard's gentle insistence that Geordi return the ship to him in one piece.
Body Count :
Factoid :
This is the first episode where we see the Enterprise-D fire multiple torpedoes simultaneously from a single tube. Marko Rodriguez, who plays Captain Rice in this episode, also played Glinn Telle in "The Wounded".
The Enterprise-D arrives at the planet Minos in the Lorenze Cluster, having been assigned to investigate the disappearance of the USS Drake. Scans of the planet indicate no life forms there despite it being listed as a civilised and technologically advanced world. The ship is greeted by a holographic projection, an automated salesman who offers a variety of weapons for sale - the chief industry of minos.
Riker leads an Away Team down to the planet where they encounter another projection, taking the form of Captain Rice of the Drake. The projection is being created in an apparent attempt to get information from the Away Team regarding their ship. On discovery the device encases Riker in a forcefield before being destroyed by Yar.
With Riker immobilised within the field Captain Picard himself beams down with Dr. Crusher to lead the Away Team, leaving Geordi in charge on the ship. Data begins working to free Riker, but a new weapon drone arrives soon afterwards. In the ensuing battle Crusher and Picard are seperated from the rest and fall into an underground chamber, trapping them both and breaking Crusher's leg in the process. Data and Yar manage to destroy the second weapon, although with some difficulty since it is a superior version which is able to dodge phaser fire quite well. The weapon discharges have disrupted communications, and Tasha goes to search for the two missing officers manually whilst Data continues trying to free Riker. She is unsuccessful, but Data does manage to free Riker from his imprisonment unharmed.
Geordi is considering beaming up the Away Team when the shields on the ship are raised automatically; a cloaked vessel of some sort fires on the Enterprise-D with a powerful beam weapon. Although the ship's sensors can get some idea of the location of the weapon as it fires, this is insufficient to get a lock on and the Enterprise is essentially fighting blind. One of the engineering officers, Logan, suggests that Geordi relinquish command to him since he is of higher rank and experience, but Geordi declines on the grounds that Picard left him in command so the responsibility remains his. He asks Worf to extrapolate the alien weapon's attack plan based on its previous actions, hoping to be able to get a good enough idea of its pattern to allow the ship to bracket the area and score a hit.
On Minos a third weapon arrives; again Yar and Data manage to hit it with combined phaser fire, but this one proves to be equipped with a deflector shield which their phasers cannot penetrate. Yar suggests that the combined weapons of all three members of the landing party might collapse the shield, and they manage to destroy the drone this way. Data points out that the weapons continue to improve in response to every defeat, and Yar conceeds that since this one took everything they had there may be no stopping the next weapon.
In the underground chamber Picard tries to give Crusher some first aid at her direction. He learns that she has some knowledge of primitive medicine, a result of her grandmother's experience on a Federation colony which underwent some unspecified disaster.
On the ship the weapon attacks again - and Worf's attempt to counterattack it fail. With the shields collapsing under the repeated attacks, Geordi orders the ship to warp out of orbit, abandoning the Away Team. He calls Logan to the bridge, and announces his intentions; he has left because he wants to detach the Saucer Section and leave the ship's civilian population in a safe location before returning in the Engineering hull to finish the battle one way or another in a last attempt to rescue the Away Team. Logan agress to command the Saucer Section. As Geordi goes to prepare, Troi has a talk with him, assuring him that he is handling the burden of command exceptionally well but that he needs to encourage the junior officers a little more since they are feeling the pressure of the situation.
In the underground chamber, Picard discovers that there are some sort of computer systems installed. The holographic salesman reappears, expounding on the virtues of the system; it is essentially a whole weapons factory capable of designing and fabricating weapons tailored to any mission and responding to failure by simply creating superior weapons until the objective is achieved. Picard realises that the Minosians were destroyed by their own creation. The salesman announces that another weapon is about to be launched to deal with the surface targets in what it apparently believes is simply a demonstration for potential buyers. On the surface the Away Team finds the entrance to the chamber and Data jumps down to assist Picard in trying to disable the machine as Riker and Yar prepare to defend against the new weapon when it arrives. Data attempts to reprogram the system but without effect; destroying the machine is suggested, but the significant power system it uses would cause an explosion big enough to kill the Away Team anyway. Picard makes one last appeal to the salesman to deactivate the machine - and realises that the demonstration will end if the sale is made. Picard agrees to buy the weapon system, and the fourth weapon is deactivated just in time.
However, in orbit the attack on the Enterprise continues. Geordi orders the Enterprise into the planet's upper atmosphere; the weapon follows, and its position is finally revealed by the fiery atmospheric turbulence created as it ploughs into the air. With a target finally available the Enterprise destroys the weapon with a single phaser blast before pulling back up into orbit.
The Away Team is beamed aboard, and Geordi thankfully offers to relinquish command to Picard; the Captain declines, gently chidind his officer that he gave him a ship in one piece and would like it returned in the same state. Geordi smilingly orders the ship to return to pick up the Saucer Section.
I like this episode, for several reasons. Primarily, the Minosian weapon system is an interesting concept which is well thought out and well implemented. In fact it parallels the way the Borg operate in many ways, and I can't help but think that it may have been the inspiration for the Borg's method of operation. Both produce an attacker that is easy to destroy, making you think that victory against this foe can't be all that difficult. Then the next one is harder to kill... and the next one harder still... and you realise that no matter how good you are, in the end your opponent will be better. In the case of the Borg this MO was largely abandoned in the end, and they became largely conventional foes who were pretty easily defeated time after time. But as a one off threat the system in this episode suffers no such weakening.
The Enterprise side of the story is also quite well handled. Geordi does a good job against the drone, but is overmatched and comes to realise it. Leaving to deposit the saucer is an intelligent idea, and his ultimate solution to battling the drone is both happily free of technobabble and entirely believable. My only nit here is to wonder why the attack on the Enterprise didn't end when the attack on the Away team did. The salesman's talk implied that the same system was responsible for both attakcs, so one would expect Picard's agreement to buy to end both attacks. I can only assume that it was in fact a different system which attacked the ship.
One aside, I have to wonder what the computer controlling all this think about the way it ended. It made a sale... then the customers left, apparently never to return. Given the way the machine oerates, I wouldn't be surprised to see a fleet of drones turn up in the Federation one day demanding to know where their overdue payment is!
© Graham & Ian Kennedy
Page views : 58,482
Last updated : 12 Mar 2013


text:
Updated 7/17/2008
After publication of this story, the APS responded with a statement that its Physics and Society Forum is merely one unit within the APS, and its views do not reflect those of the Society at large.
The American Physical Society, an organization representing nearly 50,000 physicists, has reversed its stance on climate change and is now proclaiming that many of its members disbelieve in human-induced global warming. The APS is also sponsoring public debate on the validity of global warming science. The leadership of the society had previously called the evidence for global warming "incontrovertible."
In a posting to the APS forum, editor Jeffrey Marque explains,"There is a considerable presence within the scientific community of people who do not agree with the IPCC conclusion that anthropogenic CO2 emissions are very probably likely to be primarily responsible for global warming that has occurred since the Industrial Revolution."
The APS is opening its debate with the publication of a paper by Lord Monckton of Brenchley, which concludes that climate sensitivity — the rate of temperature change a given amount of greenhouse gas will cause — has been grossly overstated by IPCC modeling. A low sensitivity implies additional atmospheric CO2 will have little effect on global climate.
Larry Gould, Professor of Physics at the University of Hartford and Chairman of the New England Section of the APS, called Monckton's paper an "expose of the IPCC that details numerous exaggerations and "extensive errors"
In an email to DailyTech, Monckton says, "I was dismayed to discover that the IPCC's 2001 and 2007 reports did not devote chapters to the central 'climate sensitivity' question, and did not explain in proper, systematic detail the methods by which they evaluated it. When I began to investigate, it seemed that the IPCC was deliberately concealing and obscuring its method."
According to Monckton, there is substantial support for his results, "in the peer-reviewed literature, most articles on climate sensitivity conclude, as I have done, that climate sensitivity must be harmlessly low."
Monckton, who was the science advisor to Britain's Thatcher administration, says natural variability is the cause of most of the Earth's recent warming. "In the past 70 years the Sun was more active than at almost any other time in the past 11,400 years … Mars, Jupiter, Neptune's largest moon, and Pluto warmed at the same time as Earth."


text:
I saw your post about the Wrap- N-Mats and your dislike of the plastic smell. I found a solution and thought you might want to share with your readers. I made my own cloth diapers for my dd who is now 2 1/2 and potty trained. I have tons of PUL left over. This is polyurethane laminate coated fabric. After I read your post last night, I decided to wrap my sandwich in it. I made the sandwich last night, refrigerated it overnight and carried it in my insulated lunch bag. My sandwich was nice and soft at lunchtime. It didn't get stiff. I will be making more of these now for my family and my friends.
To get an idea about what the fabric looks like you can go to Diaper Shop. It's fairly soft considering it's coated, especially if the material that was coated is a knit. A little more stiff if it's a woven, but still folds up more like a thick napkin than plastic. I bought lots of "diapercuts" from Diaper Shop. You can get a nice variety of fabric choices this way, without having to buy a full yard. They run about $3 a cut. and could probably get 4 out of one 20x20 cut. Much more affordable than the Wrap-N-Mats.As you can see from Lilia's pictures, making a PUL wrap looks easy, with no layers of fabric and plastic to sew together. And the fabric selection is great, with both fun prints and plain solids. Thanks, Lilia!


text:
PayPal Targets Customer Acquisition With Purchase of Start-Up Iron Pearl
PayPal had record growth at the end of 2012, with more than 5 million new users joining in the last quarter of the year, David Marcus, PayPal's president, wrote on the company's blog yesterday. The company is further investing in expanding its customer base with a new acquisition that Marcus announced in his blog post. The company is acquiring Iron Pearl, a start-up that is focused on customer acquisition and engagement, according to Marcus' blog post.
[See Related: PayPal Introduces Mobile Point of Sale Solution For iPad]
Iron Pearl has built its tools and methodologies by using data analyiss and predictive modeling to grasp the social and cultural factors that boost the spread of new products, Marcus wrote. Iron Pearl's co-founders Stan Chudnovsky and James Currier will take up executive positions within PayPal's new growth team that will aim to increase the company's customer base by using Iron Pearl's tools and methods of data analysis.
Jonathan Camhi has been an associate editor with Bank Systems & Technology since 2012. He previously worked as a freelance journalist in New York City covering politics, health and immigration, and has a master's degree from the City University of New York's Graduate School ... View Full Bio


text:
- Jabesh-Gilead
- A town on the east of the River Jordan. Saul came to the rescue of its people (1 Sam. 11) when they were threatened by the Ammonites; their gratitude was later expressed when they removed the dead bodies of Saul and his three sons from desecration by the Philistines (1 Sam. 31:12). David praised the heroes of Jabesh-Gilead for this, at the same time pointing out that the kingship had now been assumed by himself (2 Sam. 2:4–7).
Dictionary of the Bible.


text:
PITTSBURGH – Jack Butler, who helped revolutionize the way cornerbacks played in the NFL during his Hall of Fame career with the Pittsburgh Steelers, died Saturday after a lengthy battle with a staph infection. He was 85.
Butler's son John said his father's heart stopped suddenly Saturday morning. The elder Butler had spent the last several months in the hospital dealing with a staph infection that plagued him since his career ended in 1959.
"It had been a long road," John Butler said. "It wasn't completely out of the blue."
Unlike Butler's professional career.
The Pittsburgh native played wide receiver at St. Bonaventure and was planning on returning to school to get his master's degree when he received a phone call from Steelers business manager Fran Fogarty in the summer of 1951. To be honest, Butler assumed Fogarty had the wrong number.
"I didn't know anything about professional football," Butler said.
It didn't matter. Over the next nine years, Butler became one of the NFL's top defensive backs, a 6-foot-1, 200-pound wrecking ball known for his physical play and uncanny knack for getting to the ball. Butler intercepted 52 passes during his career, including a league-high 10 in 1957. He made the Pro Bowl four times and was chosen first-team All-NFL three times before a knee injury in 1959 ended his career.
Butler remained close to the game after his retirement, becoming a prominent scout who worked closely with the Steelers for over 40 years.
During one stretch from 1969-74, Butler's insight helped Pittsburgh draft nine players that would all precede him in the Hall of Fame, including Terry Bradshaw and Joe Greene. The group became the core of a franchise for the better part of a decade, helping Pittsburgh win four Super Bowls in the span of six years.
"He was an excellent person both on and off the field, and he played an integral role in the BLESTO scouting program and our entire draft process before his retirement," Steelers chairman Dan Rooney said. "His family was very close to the entire Rooney family, and he will be missed."
Butler served as the backbone of a string of mediocre to middling teams in the 1950s and his bruising style became a precursor to the "Steel Curtain" defense that has been the team's hallmark for most of the last 40 years.
He was in his prime in 1959 when a collision with Philadelphia Eagles tight end Pete Retzlaff put an end to his playing days. The details of the play remained vivid more than 50 years later.
"He caught the ball and I was coming over to hit him, to tackle him and before I got to him, he tripped or caught his foot or something," Butler said in July, 2012. "As he was going down, his shoulder hit my (left) knee."
Butler knew the second he looked down at the smashed joint -- which appeared to be at a 90-degree angle with the rest of his leg -- he needed to think about what he was going to do with the rest of his life.
"It was just sticking out," Butler said. "I knew I was in a lot of trouble."
There was no such thing as arthroscopic knee surgery back then and given the severity of the injury, Butler's not sure he could have recovered if the injury happened today. He endured 10 surgeries and eventually had both of his knees replaced, procedures that limited his mobility later in life.
Still, he managed to make it to Canton, Ohio last summer to be inducted into the Hall of Fame after being elected by the senior committee. It was an honor Butler had given up on long ago even as a campaign to get him into the Hall built steam. He was second in NFL history in career interceptions when he retired and still ranks 26th all-time, tied with Champ Bailey among others.
More than a dozen members of his family made the two-hour trip to Canton for the ceremony when the weight of Butler's accomplishments finally seemed to set in.
"If you'd asked him five years, 10 years ago, he'd have said it was no big deal," John Butler said Saturday. "But then when it happened, he was like, `this is a big deal.' When they told him 25,000 players or so had been in the league and you're No. 268, he was like, `Wow, that's pretty good.' He kind of really figured it out."
Butler didn't have a secret for his transformation from unknown to Hall of Famer. He knew he loved football. And he knew he could get away with the kind of contact today's defensive backs only dream about.
"You could bump'em and push'em and do things," Butler said. "You could grab onto his jersey so he doesn't get far from you. You could hold on a little bit. Now they're all over you. It's hard to do anything today."
There was no method exactly to Butler's success. He was smart, sure. And he could tell by a receiver's footwork where he was heading. Yet Butler says most of the credit should go to a work ethic and a little bit of naivety. He didn't know what he was doing when the Steelers signed him to a $4,000 contract in 1951.
"I must've been given some talents," he said. "Whatever talents I had, I worked like hell to improve what I had."


text:
[imagebrowser id=2]
[nggallery template='carousel' id='2′]
A few weeks ago, Sarah from Modern Kids Photography came to our home to shoot a family photo. We just got the results back and I'm so pleased with how they turned out! I had a hard time narrowing down the images to share with you.
Something fun: instead of shooting with a digital camera, Sarah decided to use film. I asked Sarah about it and she said, "These images were shot on a Contax 645. This is a medium format film camera that makes lovely negatives — about twice the size of 35mm film. The bigger the negative the prettier the results — typically. ;) I love film because the process is slower and makes me more thoughtful when shooting. I also loves the beautiful skin tones achieved with film."
I'm pleased with the skin tones too! There is one of Baby June (2nd thumbnail, last row) where she is simply radiant and I want to eat her up.
If you're looking for a great photographer of kids, I highly recommend Sarah. My children adored her and even insisted she stay for dinner! Sarah lives in San Francisco but photographs all over the US (and sometimes Europe). If you're interested in a film shoot, reserve her quickly, because she only offers a limited number of film shoots per year. Want to see more of Sarah's work? You can find her on Pinterest and on her blog too.
P.S. — Do you like the French Greys we wore? I'll share all the sources in another post.