From a5c6f9c718cc505a4b7e6e30bff23d4ac1adc9f9 Mon Sep 17 00:00:00 2001 From: manjiamu Date: Thu, 23 Apr 2026 14:36:22 +0800 Subject: [PATCH] [Update] upgrade ncurses to 6.6 - replace upstream ncurses sources with version 6.6 - update VERSION file to 6.6 - update ncurses.spec to reference ncurses-6.6.tar.gz - update README.OpenSource with new version and URL - keep original patches for adaptation Signed-off-by: manjiamu --- Ada95/Makefile.in | 23 +- Ada95/aclocal.m4 | 873 +- Ada95/configure | 7618 ++-- Ada95/configure.in | 47 +- Ada95/doc/Makefile.in | 10 +- Ada95/gen/Makefile.in | 77 +- Ada95/gen/adacurses-config.in | 14 +- Ada95/gen/gen.c | 12 +- Ada95/include/Makefile.in | 7 +- Ada95/include/ncurses_cfg.hin | 6 +- Ada95/make-tar.sh | 49 +- Ada95/package/AdaCurses-doc.spec | 9 +- Ada95/package/AdaCurses.spec | 10 +- .../debian/adacurses.lintian-overrides | 4 + .../package/debian/adacurses.triggers | 0 Ada95/package/debian/control | 3 +- Ada95/package/debian/copyright | 131 +- Ada95/package/debian/rules | 54 +- Ada95/package/debian/watch | 2 +- Ada95/samples/Makefile.in | 14 +- Ada95/samples/sample-explanation.adb_p | 8 +- Ada95/samples/sample-menu_demo-handler.adb | 4 +- Ada95/src/Makefile.in | 23 +- Ada95/src/library.gpr.in | 6 +- Ada95/src/modules | 6 +- Ada95/src/terminal_interface-curses-forms.adb | 8 +- Ada95/src/terminal_interface-curses-menus.adb | 8 +- ...inal_interface-curses-panels-user_data.adb | 4 +- MANIFEST | 23 +- Makefile.in | 17 +- Makefile.os2 | 6 +- NEWS | 615 +- README.OpenSource | 4 +- VERSION | 2 +- aclocal.m4 | 1380 +- announce.html.in | 1157 +- c++/Makefile.in | 28 +- c++/cursesapp.cc | 22 +- c++/cursesf.cc | 133 +- c++/cursesf.h | 44 +- c++/cursesm.cc | 116 +- c++/cursesm.h | 44 +- c++/cursesp.cc | 10 +- c++/cursesp.h | 16 +- c++/cursespad.cc | 24 +- c++/cursesw.cc | 42 +- c++/cursesw.h | 10 +- c++/cursslk.cc | 15 +- c++/cursslk.h | 6 +- c++/demo.cc | 20 +- c++/edit_cfg.sh | 6 +- c++/etip.h.in | 41 +- c++/internal.h | 8 +- c++/modules | 20 +- config.guess | 26 +- config.sub | 749 +- configure | 31238 ++++++++-------- configure.in | 318 +- cross_compile_support_ohos.patch | 37 - dist.mk | 12 +- doc/html/Ada95.html | 6 +- doc/html/NCURSES-Programming-HOWTO.html | 4026 +- doc/html/ada/funcs/T.htm | 2 +- .../terminal_interface-curses-forms__adb.htm | 8 +- .../terminal_interface-curses-menus__adb.htm | 8 +- ...interface-curses-panels-user_data__adb.htm | 4 +- ...rminal_interface-curses_constants__ads.htm | 6 +- doc/html/announce.html | 1156 +- doc/html/man/adacursesw6-config.1.html | 19 +- doc/html/man/captoinfo.1m.html | 83 +- doc/html/man/clear.1.html | 24 +- doc/html/man/curs_add_wch.3x.html | 503 +- doc/html/man/curs_add_wchstr.3x.html | 99 +- doc/html/man/curs_addch.3x.html | 374 +- doc/html/man/curs_addchstr.3x.html | 90 +- doc/html/man/curs_addstr.3x.html | 73 +- doc/html/man/curs_addwstr.3x.html | 81 +- doc/html/man/curs_attr.3x.html | 316 +- doc/html/man/curs_beep.3x.html | 53 +- doc/html/man/curs_bkgd.3x.html | 142 +- doc/html/man/curs_bkgrnd.3x.html | 115 +- doc/html/man/curs_border.3x.html | 100 +- doc/html/man/curs_border_set.3x.html | 103 +- doc/html/man/curs_clear.3x.html | 46 +- doc/html/man/curs_color.3x.html | 394 +- doc/html/man/curs_delch.3x.html | 56 +- doc/html/man/curs_deleteln.3x.html | 79 +- doc/html/man/curs_extend.3x.html | 73 +- doc/html/man/curs_get_wch.3x.html | 143 +- doc/html/man/curs_get_wstr.3x.html | 219 +- doc/html/man/curs_getcchar.3x.html | 205 +- doc/html/man/curs_getch.3x.html | 308 +- doc/html/man/curs_getstr.3x.html | 290 +- doc/html/man/curs_getyx.3x.html | 78 +- doc/html/man/curs_in_wch.3x.html | 60 +- doc/html/man/curs_in_wchstr.3x.html | 90 +- doc/html/man/curs_inch.3x.html | 102 +- doc/html/man/curs_inchstr.3x.html | 106 +- doc/html/man/curs_initscr.3x.html | 354 +- doc/html/man/curs_inopts.3x.html | 437 +- doc/html/man/curs_ins_wch.3x.html | 64 +- doc/html/man/curs_ins_wstr.3x.html | 113 +- doc/html/man/curs_insch.3x.html | 50 +- doc/html/man/curs_insstr.3x.html | 113 +- doc/html/man/curs_instr.3x.html | 112 +- doc/html/man/curs_inwstr.3x.html | 124 +- doc/html/man/curs_kernel.3x.html | 247 +- doc/html/man/curs_legacy.3x.html | 34 +- doc/html/man/curs_memleaks.3x.html | 20 +- doc/html/man/curs_mouse.3x.html | 316 +- doc/html/man/curs_move.3x.html | 40 +- doc/html/man/curs_opaque.3x.html | 34 +- doc/html/man/curs_outopts.3x.html | 210 +- doc/html/man/curs_overlay.3x.html | 51 +- doc/html/man/curs_pad.3x.html | 165 +- doc/html/man/curs_print.3x.html | 67 +- doc/html/man/curs_printw.3x.html | 75 +- doc/html/man/curs_refresh.3x.html | 60 +- doc/html/man/curs_scanw.3x.html | 75 +- doc/html/man/curs_scr_dump.3x.html | 105 +- doc/html/man/curs_scroll.3x.html | 81 +- doc/html/man/curs_slk.3x.html | 111 +- doc/html/man/curs_sp_funcs.3x.html | 288 +- doc/html/man/curs_termattrs.3x.html | 122 +- doc/html/man/curs_termcap.3x.html | 284 +- doc/html/man/curs_terminfo.3x.html | 604 +- doc/html/man/curs_threads.3x.html | 55 +- doc/html/man/curs_touch.3x.html | 59 +- doc/html/man/curs_trace.3x.html | 68 +- doc/html/man/curs_util.3x.html | 312 +- doc/html/man/curs_variables.3x.html | 165 +- doc/html/man/curs_window.3x.html | 191 +- doc/html/man/default_colors.3x.html | 26 +- doc/html/man/define_key.3x.html | 57 +- doc/html/man/form.3x.html | 23 +- doc/html/man/form_cursor.3x.html | 14 +- doc/html/man/form_data.3x.html | 14 +- doc/html/man/form_driver.3x.html | 43 +- doc/html/man/form_field.3x.html | 18 +- doc/html/man/form_field_attributes.3x.html | 14 +- doc/html/man/form_field_buffer.3x.html | 28 +- doc/html/man/form_field_info.3x.html | 16 +- doc/html/man/form_field_just.3x.html | 12 +- doc/html/man/form_field_new.3x.html | 22 +- doc/html/man/form_field_opts.3x.html | 32 +- doc/html/man/form_field_userptr.3x.html | 14 +- doc/html/man/form_field_validation.3x.html | 56 +- doc/html/man/form_fieldtype.3x.html | 32 +- doc/html/man/form_hook.3x.html | 22 +- doc/html/man/form_new.3x.html | 20 +- doc/html/man/form_new_page.3x.html | 12 +- doc/html/man/form_opts.3x.html | 16 +- doc/html/man/form_page.3x.html | 14 +- doc/html/man/form_post.3x.html | 12 +- doc/html/man/form_requestname.3x.html | 24 +- doc/html/man/form_userptr.3x.html | 20 +- doc/html/man/form_variables.3x.html | 10 +- doc/html/man/form_win.3x.html | 18 +- doc/html/man/index.html | 69 +- doc/html/man/infocmp.1m.html | 303 +- doc/html/man/infotocap.1m.html | 25 +- doc/html/man/key_defined.3x.html | 41 +- doc/html/man/keybound.3x.html | 49 +- doc/html/man/keyok.3x.html | 53 +- doc/html/man/legacy_coding.3x.html | 45 +- doc/html/man/menu.3x.html | 27 +- doc/html/man/menu_attributes.3x.html | 14 +- doc/html/man/menu_cursor.3x.html | 10 +- doc/html/man/menu_driver.3x.html | 38 +- doc/html/man/menu_format.3x.html | 26 +- doc/html/man/menu_hook.3x.html | 26 +- doc/html/man/menu_items.3x.html | 18 +- doc/html/man/menu_mark.3x.html | 26 +- doc/html/man/menu_new.3x.html | 16 +- doc/html/man/menu_opts.3x.html | 16 +- doc/html/man/menu_pattern.3x.html | 16 +- doc/html/man/menu_post.3x.html | 12 +- doc/html/man/menu_requestname.3x.html | 24 +- doc/html/man/menu_spacing.3x.html | 26 +- doc/html/man/menu_userptr.3x.html | 20 +- doc/html/man/menu_win.3x.html | 18 +- doc/html/man/mitem_current.3x.html | 30 +- doc/html/man/mitem_name.3x.html | 16 +- doc/html/man/mitem_new.3x.html | 14 +- doc/html/man/mitem_opts.3x.html | 16 +- doc/html/man/mitem_userptr.3x.html | 20 +- doc/html/man/mitem_value.3x.html | 12 +- doc/html/man/mitem_visible.3x.html | 10 +- doc/html/man/ncurses.3x.html | 761 +- doc/html/man/ncursesw6-config.1.html | 14 +- doc/html/man/new_pair.3x.html | 48 +- doc/html/man/panel.3x.html | 50 +- doc/html/man/resizeterm.3x.html | 81 +- doc/html/man/scr_dump.5.html | 68 +- doc/html/man/tabs.1.html | 79 +- doc/html/man/term.5.html | 259 +- doc/html/man/term.7.html | 90 +- doc/html/man/term_variables.3x.html | 121 +- doc/html/man/terminfo.5.html | 872 +- doc/html/man/tic.1m.html | 338 +- doc/html/man/toe.1m.html | 49 +- doc/html/man/tput.1.html | 299 +- doc/html/man/tset.1.html | 126 +- doc/html/man/user_caps.5.html | 369 +- doc/html/man/wresize.3x.html | 63 +- doc/html/ncurses-intro.html | 10 +- doc/ncurses-intro.doc | 5 +- form/Makefile.in | 28 +- form/fld_arg.c | 6 +- form/fld_attr.c | 6 +- form/fld_current.c | 12 +- form/fld_def.c | 30 +- form/fld_dup.c | 6 +- form/form.priv.h | 15 +- form/frm_data.c | 8 +- form/frm_driver.c | 91 +- form/frm_post.c | 6 +- form/frm_req_name.c | 6 +- form/frm_sub.c | 15 +- form/frm_win.c | 16 +- form/fty_enum.c | 57 +- form/fty_generic.c | 17 +- form/fty_int.c | 14 +- form/fty_num.c | 16 +- form/fty_regex.c | 8 +- include/Caps | 44 +- include/Caps.aix4 | 26 +- include/Caps.hpux11 | 26 +- include/Caps.keys | 26 +- include/Caps.osf1r5 | 20 +- include/Caps.uwin | 20 +- include/MKkey_defs.sh | 8 +- include/MKterm.h.awk.in | 57 +- include/Makefile.in | 9 +- include/capdefaults.c | 6 +- include/curses.h.in | 104 +- include/curses.tail | 54 +- include/curses.wide | 7 +- include/headers | 9 +- include/nc_alloc.h | 25 +- include/nc_termios.h | 91 +- include/nc_tparm.h | 5 +- include/{nc_win32.h => nc_win32.h.in} | 131 +- include/ncurses_cfg.hin | 6 +- include/ncurses_defs | 23 +- include/ncurses_mingw.h | 82 - include/term_entry.h | 9 +- include/tic.h | 10 +- include/unctrl.h.in | 10 +- include/win32_curses.h | 75 - install-sh | 27 +- man/MKada_config.in | 8 +- man/MKncu_config.in | 4 +- man/MKterminfo.sh | 66 +- man/Makefile.in | 24 +- man/captoinfo.1m | 159 +- man/clear.1 | 12 +- man/curs_add_wch.3x | 743 +- man/curs_add_wchstr.3x | 139 +- man/curs_addch.3x | 529 +- man/curs_addchstr.3x | 122 +- man/curs_addstr.3x | 101 +- man/curs_addwstr.3x | 107 +- man/curs_attr.3x | 494 +- man/curs_beep.3x | 85 +- man/curs_bkgd.3x | 243 +- man/curs_bkgrnd.3x | 198 +- man/curs_border.3x | 239 +- man/curs_border_set.3x | 96 +- man/curs_clear.3x | 46 +- man/curs_color.3x | 510 +- man/curs_delch.3x | 56 +- man/curs_deleteln.3x | 126 +- man/curs_extend.3x | 93 +- man/curs_get_wch.3x | 175 +- man/curs_get_wstr.3x | 425 +- man/curs_getcchar.3x | 394 +- man/curs_getch.3x | 441 +- man/curs_getstr.3x | 620 +- man/curs_getyx.3x | 150 +- man/curs_in_wch.3x | 85 +- man/curs_in_wchstr.3x | 139 +- man/curs_inch.3x | 148 +- man/curs_inchstr.3x | 179 +- man/curs_initscr.3x | 675 +- man/curs_inopts.3x | 977 +- man/curs_ins_wch.3x | 110 +- man/curs_ins_wstr.3x | 181 +- man/curs_insch.3x | 71 +- man/curs_insstr.3x | 175 +- man/curs_instr.3x | 188 +- man/curs_inwstr.3x | 239 +- man/curs_kernel.3x | 461 +- man/curs_legacy.3x | 35 +- man/curs_mouse.3x | 542 +- man/curs_move.3x | 64 +- man/curs_opaque.3x | 33 +- man/curs_outopts.3x | 414 +- man/curs_overlay.3x | 53 +- man/curs_pad.3x | 250 +- man/curs_print.3x | 105 +- man/curs_printw.3x | 139 +- man/curs_refresh.3x | 33 +- man/curs_scanw.3x | 129 +- man/curs_scr_dump.3x | 200 +- man/curs_scroll.3x | 143 +- man/curs_slk.3x | 77 +- man/curs_sp_funcs.3x | 272 +- man/curs_termattrs.3x | 199 +- man/curs_termcap.3x | 446 +- man/curs_terminfo.3x | 834 +- man/curs_threads.3x | 8 +- man/curs_touch.3x | 70 +- man/curs_trace.3x | 14 +- man/curs_util.3x | 436 +- man/curs_variables.3x | 298 +- man/curs_window.3x | 318 +- man/define_key.3x | 108 +- man/form.3x | 21 +- man/form_driver.3x | 9 +- man/form_field.3x | 15 +- man/form_field_buffer.3x | 8 +- man/form_field_new.3x | 7 +- man/form_field_opts.3x | 20 +- man/form_field_userptr.3x | 7 +- man/form_field_validation.3x | 30 +- man/form_fieldtype.3x | 23 +- man/form_hook.3x | 27 +- man/form_new.3x | 11 +- man/form_opts.3x | 20 +- man/form_page.3x | 8 +- man/form_requestname.3x | 8 +- man/form_userptr.3x | 7 +- man/form_win.3x | 16 +- man/infocmp.1m | 301 +- man/infotocap.1m | 62 +- man/key_defined.3x | 60 +- man/keybound.3x | 79 +- man/keyok.3x | 88 +- man/legacy_coding.3x | 42 +- man/make_sed.sh | 10 +- man/man_db.renames.in | 28 +- man/manhtml.aliases | 29 +- man/manhtml.externs | 15 +- man/manlinks.sed | 13 +- man/menu.3x | 60 +- man/menu_driver.3x | 11 +- man/menu_hook.3x | 28 +- man/menu_items.3x | 13 +- man/menu_mark.3x | 17 +- man/menu_new.3x | 11 +- man/menu_opts.3x | 20 +- man/menu_pattern.3x | 9 +- man/menu_requestname.3x | 8 +- man/menu_spacing.3x | 8 +- man/menu_userptr.3x | 7 +- man/menu_win.3x | 16 +- man/mitem_current.3x | 10 +- man/mitem_name.3x | 7 +- man/mitem_new.3x | 8 +- man/mitem_opts.3x | 20 +- man/mitem_userptr.3x | 7 +- man/ncurses.3x | 944 +- man/new_pair.3x | 14 +- man/panel.3x | 27 +- man/resizeterm.3x | 59 +- man/scr_dump.5 | 22 +- man/tabs.1 | 73 +- man/term.5 | 431 +- man/term.7 | 16 +- man/term_variables.3x | 222 +- man/terminfo.head | 11 +- man/terminfo.tail | 387 +- man/tic.1m | 612 +- man/toe.1m | 23 +- man/tput.1 | 410 +- man/tset.1 | 22 +- man/user_caps.5 | 584 +- man/wresize.3x | 105 +- menu/Makefile.in | 28 +- menu/m_driver.c | 14 +- menu/m_global.c | 14 +- menu/m_item_new.c | 14 +- menu/m_item_vis.c | 6 +- menu/m_pattern.c | 6 +- menu/m_post.c | 42 +- menu/m_req_name.c | 6 +- menu/menu.priv.h | 7 +- menu/mf_common.h | 8 +- misc/Makefile.in | 79 +- misc/gen-pkgconfig.in | 14 +- misc/gen_edit.sh | 16 +- misc/magic | 9 +- misc/makellib | 28 +- misc/ncurses-config.in | 134 +- misc/run_tic.in | 147 +- misc/terminfo.src | 4424 ++- mk-1st.awk | 105 +- ncurses.spec | 8 +- ncurses/Makefile.in | 36 +- ncurses/base/MKkeyname.awk | 30 +- ncurses/base/MKlib_gen.sh | 77 +- ncurses/base/MKunctrl.awk | 10 +- ncurses/base/define_key.c | 12 +- ncurses/base/key_defined.c | 10 +- ncurses/base/keybound.c | 8 +- ncurses/base/keyok.c | 10 +- ncurses/base/legacy_coding.c | 6 +- ncurses/base/lib_addch.c | 12 +- ncurses/base/lib_addstr.c | 14 +- ncurses/base/lib_beep.c | 10 +- ncurses/base/lib_bkgd.c | 6 +- ncurses/base/lib_chgat.c | 7 +- ncurses/base/lib_color.c | 84 +- ncurses/base/lib_colorset.c | 6 +- ncurses/base/lib_delch.c | 8 +- ncurses/base/lib_delwin.c | 29 +- ncurses/base/lib_dft_fgbg.c | 12 +- ncurses/base/lib_driver.c | 50 +- ncurses/base/lib_echo.c | 8 +- ncurses/base/lib_endwin.c | 6 +- ncurses/base/lib_erase.c | 6 +- ncurses/base/lib_flash.c | 8 +- ncurses/base/lib_freeall.c | 18 +- ncurses/base/lib_getch.c | 51 +- ncurses/base/lib_getstr.c | 12 +- ncurses/base/lib_initscr.c | 12 +- ncurses/base/lib_insch.c | 10 +- ncurses/base/lib_insnstr.c | 8 +- ncurses/base/lib_instr.c | 16 +- ncurses/base/lib_mouse.c | 170 +- ncurses/base/lib_mvwin.c | 6 +- ncurses/base/lib_newterm.c | 47 +- ncurses/base/lib_newwin.c | 80 +- ncurses/base/lib_nl.c | 12 +- ncurses/base/lib_overlay.c | 10 +- ncurses/base/lib_pad.c | 22 +- ncurses/base/lib_printw.c | 12 +- ncurses/base/lib_redrawln.c | 6 +- ncurses/base/lib_refresh.c | 8 +- ncurses/base/lib_restart.c | 12 +- ncurses/base/lib_screen.c | 108 +- ncurses/base/lib_set_term.c | 128 +- ncurses/base/lib_slk.c | 22 +- ncurses/base/lib_slkatr_set.c | 8 +- ncurses/base/lib_slkatrof.c | 6 +- ncurses/base/lib_slkatron.c | 6 +- ncurses/base/lib_slkatrset.c | 6 +- ncurses/base/lib_slkattr.c | 6 +- ncurses/base/lib_slkclear.c | 6 +- ncurses/base/lib_slkcolor.c | 8 +- ncurses/base/lib_slklab.c | 8 +- ncurses/base/lib_slkrefr.c | 18 +- ncurses/base/lib_slkset.c | 16 +- ncurses/base/lib_slktouch.c | 6 +- ncurses/base/lib_touch.c | 12 +- ncurses/base/lib_ungetch.c | 6 +- ncurses/base/lib_wattron.c | 6 +- ncurses/base/lib_winch.c | 6 +- ncurses/base/lib_window.c | 14 +- ncurses/base/nc_panel.c | 6 +- ncurses/base/new_pair.c | 22 +- ncurses/base/resizeterm.c | 47 +- ncurses/base/safe_sprintf.c | 19 +- ncurses/base/tries.c | 20 +- ncurses/base/vsscanf.c | 8 +- ncurses/base/wresize.c | 22 +- ncurses/build.priv.h | 6 +- ncurses/curses.priv.h | 331 +- ncurses/llib-lncurses | 26 +- ncurses/llib-lncursest | 26 +- ncurses/llib-lncursestw | 40 +- ncurses/llib-lncursesw | 40 +- ncurses/llib-ltinfo | 20 +- ncurses/llib-ltinfot | 20 +- ncurses/llib-ltinfotw | 20 +- ncurses/llib-ltinfow | 20 +- ncurses/modules | 20 +- ncurses/new_pair.h | 10 +- include/nc_mingw.h => ncurses/report_ctype.c | 116 +- ncurses/report_hashing.c | 6 +- ncurses/report_offsets.c | 19 +- ncurses/term.priv.h | 8 +- ncurses/tinfo/MKcaptab.awk | 6 +- ncurses/tinfo/MKcaptab.sh | 22 +- ncurses/tinfo/MKcodes.awk | 12 +- ncurses/tinfo/MKfallback.sh | 35 +- ncurses/tinfo/MKkeys_list.sh | 26 +- ncurses/tinfo/MKnames.awk | 12 +- ncurses/tinfo/MKuserdefs.sh | 10 +- ncurses/tinfo/access.c | 188 +- ncurses/tinfo/add_tries.c | 18 +- ncurses/tinfo/alloc_entry.c | 27 +- ncurses/tinfo/alloc_ttype.c | 43 +- ncurses/tinfo/captoinfo.c | 87 +- ncurses/tinfo/comp_error.c | 16 +- ncurses/tinfo/comp_expand.c | 22 +- ncurses/tinfo/comp_hash.c | 14 +- ncurses/tinfo/comp_parse.c | 59 +- ncurses/tinfo/comp_scan.c | 68 +- ncurses/tinfo/db_iterator.c | 66 +- ncurses/tinfo/doalloc.c | 6 +- ncurses/tinfo/entries.c | 30 +- ncurses/tinfo/getenv_num.c | 14 +- ncurses/tinfo/hashed_db.c | 49 +- ncurses/tinfo/home_terminfo.c | 12 +- ncurses/tinfo/init_keytry.c | 10 +- ncurses/tinfo/lib_acs.c | 24 +- ncurses/tinfo/lib_baudrate.c | 21 +- ncurses/tinfo/lib_cur_term.c | 22 +- ncurses/tinfo/lib_data.c | 44 +- ncurses/tinfo/lib_has_cap.c | 8 +- ncurses/tinfo/lib_kernel.c | 18 +- ncurses/tinfo/lib_napms.c | 10 +- ncurses/tinfo/lib_options.c | 30 +- ncurses/tinfo/lib_print.c | 15 +- ncurses/tinfo/lib_raw.c | 39 +- ncurses/tinfo/lib_setup.c | 148 +- ncurses/tinfo/lib_termcap.c | 60 +- ncurses/tinfo/lib_termname.c | 10 +- ncurses/tinfo/lib_tgoto.c | 18 +- ncurses/tinfo/lib_ti.c | 12 +- ncurses/tinfo/lib_tparm.c | 52 +- ncurses/tinfo/lib_tputs.c | 32 +- ncurses/tinfo/lib_ttyflags.c | 46 +- ncurses/tinfo/lib_win32con.c | 414 +- ncurses/tinfo/lib_win32util.c | 11 +- ncurses/tinfo/make_hash.c | 51 +- ncurses/tinfo/make_keys.c | 25 +- ncurses/tinfo/name_match.c | 16 +- ncurses/tinfo/obsolete.c | 14 +- ncurses/tinfo/parse_entry.c | 58 +- ncurses/tinfo/read_entry.c | 42 +- ncurses/tinfo/read_termcap.c | 78 +- ncurses/tinfo/strings.c | 14 +- ncurses/tinfo/tinfo_driver.c | 125 +- ncurses/tinfo/trim_sgr0.c | 98 +- ncurses/tinfo/write_entry.c | 76 +- ncurses/trace/lib_trace.c | 22 +- ncurses/trace/lib_traceatr.c | 35 +- ncurses/trace/lib_tracebits.c | 22 +- ncurses/trace/lib_tracechr.c | 10 +- ncurses/trace/lib_tracedmp.c | 8 +- ncurses/trace/lib_tracemse.c | 10 +- ncurses/trace/trace_buf.c | 26 +- ncurses/trace/trace_tries.c | 10 +- ncurses/trace/varargs.c | 38 +- ncurses/trace/visbuf.c | 24 +- ncurses/tty/MKexpanded.sh | 11 +- ncurses/tty/hardscroll.c | 16 +- ncurses/tty/hashmap.c | 26 +- ncurses/tty/lib_mvcur.c | 84 +- ncurses/tty/lib_tstp.c | 16 +- ncurses/tty/lib_twait.c | 12 +- ncurses/tty/lib_vidattr.c | 12 +- ncurses/tty/tty_update.c | 48 +- ncurses/wcwidth.h | 966 +- ncurses/widechar/charable.c | 9 +- ncurses/widechar/lib_add_wch.c | 12 +- ncurses/widechar/lib_box_set.c | 6 +- ncurses/widechar/lib_cchar.c | 8 +- ncurses/widechar/lib_get_wch.c | 10 +- ncurses/widechar/lib_get_wstr.c | 8 +- ncurses/widechar/lib_hline_set.c | 6 +- ncurses/widechar/lib_in_wch.c | 8 +- ncurses/widechar/lib_in_wchnstr.c | 10 +- ncurses/widechar/lib_ins_wch.c | 53 +- ncurses/widechar/lib_inwstr.c | 33 +- ncurses/widechar/lib_key_name.c | 6 +- ncurses/widechar/lib_pecho_wchar.c | 6 +- ncurses/widechar/lib_slk_wset.c | 8 +- ncurses/widechar/lib_unget_wch.c | 10 +- ncurses/widechar/lib_vid_attr.c | 26 +- ncurses/widechar/lib_vline_set.c | 6 +- ncurses/widechar/lib_wacs.c | 8 +- ncurses/widechar/lib_wunctrl.c | 13 +- ncurses/widechar/widechars.c | 12 +- ncurses/win32con/gettimeofday.c | 9 +- ncurses/win32con/wcwidth.c | 13 +- ncurses/win32con/win32_driver.c | 103 +- ncurses/win32con/win_driver.c | 2282 -- package/debian-mingw/changelog | 4 +- package/debian-mingw/control | 7 +- package/debian-mingw/copyright | 185 +- .../mingw32-ncurses6.lintian-overrides | 7 - .../mingw32-ncurses6td.lintian-overrides | 7 + package/debian-mingw/rules | 6 +- package/debian-mingw/watch | 2 +- package/debian-mingw64/changelog | 4 +- package/debian-mingw64/control | 7 +- package/debian-mingw64/copyright | 185 +- .../mingw64-ncurses6.lintian-overrides | 7 - .../mingw64-ncurses6td.lintian-overrides | 7 + package/debian-mingw64/rules | 6 +- package/debian-mingw64/watch | 2 +- package/debian/changelog | 4 +- package/debian/control | 22 +- package/debian/copyright | 185 +- package/debian/ncurses6.lintian-overrides | 9 - package/debian/ncurses6td.lintian-overrides | 11 + ...ncursest6.triggers => ncurses6td.triggers} | 0 package/debian/ncursest6.lintian-overrides | 9 - package/debian/ncursest6td.lintian-overrides | 11 + package/debian/ncursest6td.triggers | 1 + package/debian/rules | 84 +- package/debian/watch | 2 +- package/mingw-ncurses.nsi | 8 +- package/mingw-ncurses.spec | 9 +- package/ncurses.map | 9 +- package/ncurses.spec | 9 +- package/ncurses.sym | 3 +- package/ncursest.map | 9 +- package/ncursest.spec | 9 +- package/ncursest.sym | 3 +- package/ncursestw.map | 9 +- package/ncursestw.sym | 3 +- package/ncursesw.map | 9 +- package/ncursesw.sym | 3 +- panel/Makefile.in | 28 +- panel/p_above.c | 16 +- panel/p_below.c | 18 +- panel/p_new.c | 6 +- panel/panel.c | 18 +- panel/panel.priv.h | 6 +- progs/Makefile.in | 65 +- progs/capconvert | 44 +- progs/clear.c | 6 +- progs/clear_cmd.c | 69 +- progs/dump_entry.c | 66 +- progs/infocmp.c | 308 +- progs/modules | 28 +- progs/progs.priv.h | 4 +- progs/reset_cmd.c | 90 +- progs/tabs.c | 51 +- progs/tic.c | 178 +- progs/toe.c | 82 +- progs/tput.c | 154 +- progs/tset.c | 70 +- test/Makefile.in | 20 +- test/aclocal.m4 | 722 +- test/back_ground.c | 35 +- test/background.c | 47 +- test/blue.c | 17 +- test/bs.6 | 75 +- test/bs.c | 29 +- test/cardfile.c | 73 +- test/chgat.c | 38 +- test/clip_printw.c | 35 +- test/color_content.c | 19 +- test/color_name.h | 12 +- test/color_set.c | 9 +- test/combine.c | 29 +- test/configure | 4721 +-- test/configure.in | 50 +- test/demo_altkeys.c | 25 +- test/demo_defkey.c | 39 +- test/demo_forms.c | 61 +- test/demo_keyok.c | 13 +- test/demo_menus.c | 101 +- test/demo_new_pair.c | 39 +- test/demo_panels.c | 72 +- test/demo_tabs.c | 15 +- test/demo_termcap.c | 94 +- test/demo_terminfo.c | 96 +- test/ditto.c | 29 +- test/dots.c | 17 +- test/dots_curses.c | 13 +- test/dots_mvcur.c | 19 +- test/dots_termcap.c | 31 +- test/dots_xcurses.c | 23 +- test/dump_window.c | 18 +- test/dup_field.c | 39 +- test/echochar.c | 15 +- test/edit_field.c | 24 +- test/extended_color.c | 9 +- test/filter.c | 35 +- test/firework.c | 9 +- test/firstlast.c | 9 +- test/foldkeys.c | 23 +- test/form_driver_w.c | 13 +- test/gdc.6 | 96 +- test/gdc.c | 86 +- test/hanoi.c | 9 +- test/hashtest.c | 27 +- test/inch_wide.c | 23 +- test/inchs.c | 25 +- test/ins_wide.c | 19 +- test/insdelln.c | 33 +- test/inserts.c | 17 +- test/key_names.c | 11 +- test/keynames.c | 11 +- test/knight.c | 12 +- test/linedata.h | 10 +- test/list_keys.c | 27 +- test/lrtest.c | 9 +- test/make-tar.sh | 38 +- test/modules | 30 +- test/move_field.c | 43 +- test/movewindow.c | 73 +- test/ncurses.c | 331 +- test/newdemo.c | 9 +- test/package/debian-mingw/copyright | 137 +- test/package/debian-mingw/rules | 2 +- test/package/debian-mingw/watch | 2 +- test/package/debian-mingw64/copyright | 137 +- test/package/debian-mingw64/rules | 2 +- test/package/debian-mingw64/watch | 2 +- test/package/debian/copyright | 137 +- .../debian/ncurses-examples.lintian-overrides | 7 + .../ncursest-examples.lintian-overrides | 7 + test/package/debian/rules | 23 +- test/package/debian/watch | 2 +- test/package/mingw-ncurses-examples.spec | 7 +- test/package/ncurses-examples.spec | 7 +- test/padview.c | 48 +- test/pair_content.c | 19 +- test/parse_rgb.h | 12 +- test/picsmap.c | 159 +- test/popup_msg.c | 17 +- test/popup_msg.h | 6 +- test/programs | 8 +- test/railroad.c | 43 +- test/rain.c | 31 +- test/redraw.c | 15 +- test/savescreen.c | 39 +- test/savescreen.sh | 17 +- test/sp_tinfo.c | 15 +- test/tclock.c | 13 +- test/test.priv.h | 105 +- test/test_add_wchstr.c | 29 +- test/test_addchstr.c | 27 +- test/test_addstr.c | 17 +- test/test_addwstr.c | 19 +- test/test_arrays.c | 39 +- test/test_delwin.c | 9 +- test/test_endwin.c | 21 +- test/test_get_wstr.c | 25 +- test/test_getstr.c | 25 +- test/test_instr.c | 57 +- test/test_inwstr.c | 58 +- test/test_mouse.c | 24 +- test/test_opaque.c | 71 +- test/test_setupterm.c | 15 +- test/test_sgr.c | 60 +- test/test_termattrs.c | 9 +- test/test_tparm.c | 66 +- test/test_unget_wch.c | 9 +- test/test_vid_puts.c | 11 +- test/test_vidputs.c | 13 +- test/testaddch.c | 9 +- test/testcurs.c | 23 +- test/testscanw.c | 11 +- test/tput-colorcube | 58 +- test/tput-initc | 21 +- test/view.c | 62 +- test/widechars.h | 4 +- test/worm.c | 73 +- test/xmas.c | 71 +- 758 files changed, 62516 insertions(+), 50350 deletions(-) create mode 100644 Ada95/package/debian/adacurses.lintian-overrides rename package/debian/ncurses6.triggers => Ada95/package/debian/adacurses.triggers (100%) delete mode 100644 cross_compile_support_ohos.patch rename include/{nc_win32.h => nc_win32.h.in} (70%) delete mode 100644 include/ncurses_mingw.h delete mode 100644 include/win32_curses.h rename include/nc_mingw.h => ncurses/report_ctype.c (59%) delete mode 100644 ncurses/win32con/win_driver.c delete mode 100644 package/debian-mingw/mingw32-ncurses6.lintian-overrides create mode 100644 package/debian-mingw/mingw32-ncurses6td.lintian-overrides delete mode 100644 package/debian-mingw64/mingw64-ncurses6.lintian-overrides create mode 100644 package/debian-mingw64/mingw64-ncurses6td.lintian-overrides delete mode 100644 package/debian/ncurses6.lintian-overrides create mode 100644 package/debian/ncurses6td.lintian-overrides rename package/debian/{ncursest6.triggers => ncurses6td.triggers} (100%) delete mode 100644 package/debian/ncursest6.lintian-overrides create mode 100644 package/debian/ncursest6td.lintian-overrides create mode 100644 package/debian/ncursest6td.triggers create mode 100644 test/package/debian/ncurses-examples.lintian-overrides create mode 100644 test/package/debian/ncursest-examples.lintian-overrides diff --git a/Ada95/Makefile.in b/Ada95/Makefile.in index 22b922e..23e59ed 100644 --- a/Ada95/Makefile.in +++ b/Ada95/Makefile.in @@ -1,6 +1,6 @@ -# $Id: Makefile.in,v 1.30 2022/12/17 23:33:33 tom Exp $ +# $Id: Makefile.in,v 1.34 2025/10/18 15:20:43 tom Exp $ ############################################################################## -# Copyright 2020-2021,2022 Thomas E. Dickey # +# Copyright 2020-2024,2025 Thomas E. Dickey # # Copyright 1998-2010,2015 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -31,7 +31,7 @@ # Author: Juergen Pfeifer, 1996 # # Version Control -# $Revision: 1.30 $ +# $Revision: 1.34 $ # SHELL = @SHELL@ VPATH = @srcdir@ @@ -47,19 +47,20 @@ libdir = @libdir@ libexecdir = @libexecdir@ includedir = @includedir@ -BINDIR = $(DESTDIR)$(bindir) -DATADIR = $(DESTDIR)$(datadir) -LIBDIR = $(DESTDIR)$(libdir) -LIBEXECDIR = $(DESTDIR)$(libexecdir) +@SET_MAKE@ +@SET_DESTDIR@ +TOP_MFLAGS = DESTDIR="$(DESTDIR)" RPATH_LIST="$(RPATH_LIST)" -SUBDIRS = @ADA_SUBDIRS@ +BINDIR = $(DESTDIR)$(bindir@MERGE_PREFIX@) +DATADIR = $(DESTDIR)$(datadir@MERGE_PREFIX@) +LIBDIR = $(DESTDIR)$(libdir@MERGE_PREFIX@) +LIBEXECDIR = $(DESTDIR)$(libexecdir@MERGE_PREFIX@) + +SUBDIRS = @ADA_SUBDIRS@ INSTALL = @INSTALL@ @INSTALL_OPT_O@ INSTALL_SCRIPT = @INSTALL@ -TOP_MFLAGS = @cf_cv_makeflags@ DESTDIR="$(DESTDIR)" RPATH_LIST="$(RPATH_LIST)" -@SET_MAKE@ - ################################################################################ @MAKE_PHONY@.PHONY : all diff --git a/Ada95/aclocal.m4 b/Ada95/aclocal.m4 index 6fe1f94..d063565 100644 --- a/Ada95/aclocal.m4 +++ b/Ada95/aclocal.m4 @@ -1,5 +1,5 @@ dnl*************************************************************************** -dnl Copyright 2018-2023,2024 Thomas E. Dickey * +dnl Copyright 2018-2024,2025 Thomas E. Dickey * dnl Copyright 2010-2017,2018 Free Software Foundation, Inc. * dnl * dnl Permission is hereby granted, free of charge, to any person obtaining a * @@ -29,7 +29,7 @@ dnl*************************************************************************** dnl dnl Author: Thomas E. Dickey dnl -dnl $Id: aclocal.m4,v 1.210 2024/03/30 22:17:13 tom Exp $ +dnl $Id: aclocal.m4,v 1.241 2025/12/25 23:45:32 tom Exp $ dnl Macros used in NCURSES Ada95 auto-configuration script. dnl dnl These macros are maintained separately from NCURSES. The copyright on @@ -189,7 +189,7 @@ AC_SUBST(EXTRA_CPPFLAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_ADD_INCDIR version: 17 updated: 2021/09/04 06:35:04 +dnl CF_ADD_INCDIR version: 18 updated: 2025/12/22 04:16:14 dnl ------------- dnl Add an include-directory to $CPPFLAGS. Don't add /usr/include, since it is dnl redundant. We don't normally need to add -I/usr/local/include for gcc, @@ -221,8 +221,8 @@ if test -n "$1" ; then then cf_save_CPPFLAGS=$CPPFLAGS CF_APPEND_TEXT(CPPFLAGS,-I$cf_add_incdir) - AC_TRY_COMPILE([#include ], - [printf("Hello")], + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ], + [printf("Hello")])], [], [cf_have_incdir=yes]) CPPFLAGS=$cf_save_CPPFLAGS @@ -381,7 +381,7 @@ dnl Allow user to enable a normally-off option. AC_DEFUN([CF_ARG_ENABLE], [CF_ARG_OPTION($1,[$2],[$3],[$4],no)])dnl dnl --------------------------------------------------------------------------- -dnl CF_ARG_OPTION version: 5 updated: 2015/05/10 19:52:14 +dnl CF_ARG_OPTION version: 6 updated: 2025/08/05 04:09:09 dnl ------------- dnl Restricted form of AC_ARG_ENABLE that ensures user doesn't give bogus dnl values. @@ -390,7 +390,7 @@ dnl Parameters: dnl $1 = option name dnl $2 = help-string dnl $3 = action to perform if option is not default -dnl $4 = action if perform if option is default +dnl $4 = action to perform if option is default dnl $5 = default option value (either 'yes' or 'no') AC_DEFUN([CF_ARG_OPTION], [AC_ARG_ENABLE([$1],[$2],[test "$enableval" != ifelse([$5],no,yes,no) && enableval=ifelse([$5],no,no,yes) @@ -404,7 +404,7 @@ ifelse([$3],,[ :]dnl ])dnl ])])dnl dnl --------------------------------------------------------------------------- -dnl CF_AR_FLAGS version: 9 updated: 2021/01/01 13:31:04 +dnl CF_AR_FLAGS version: 10 updated: 2025/12/14 20:07:31 dnl ----------- dnl Check for suitable "ar" (archiver) options for updating an archive. dnl @@ -450,8 +450,8 @@ AC_CACHE_CHECK(for options to update archives, cf_cv_ar_flags,[ int testdata[[3]] = { 123, 456, 789 }; EOF if AC_TRY_EVAL(ac_compile) ; then - echo "$AR $ARFLAGS $cf_ar_flags conftest.a conftest.$ac_cv_objext" >&AC_FD_CC - $AR $ARFLAGS "$cf_ar_flags" conftest.a "conftest.$ac_cv_objext" 2>&AC_FD_CC 1>/dev/null + echo "$AR $ARFLAGS $cf_ar_flags conftest.a conftest.$ac_cv_objext" >&AS_MESSAGE_LOG_FD + $AR $ARFLAGS "$cf_ar_flags" conftest.a "conftest.$ac_cv_objext" 2>&AS_MESSAGE_LOG_FD 1>/dev/null if test -f conftest.a ; then cf_cv_ar_flags="$cf_ar_flags" break @@ -477,7 +477,7 @@ fi AC_SUBST(ARFLAGS) ]) dnl --------------------------------------------------------------------------- -dnl CF_BUILD_CC version: 11 updated: 2022/12/04 15:40:08 +dnl CF_BUILD_CC version: 14 updated: 2024/12/14 11:58:01 dnl ----------- dnl If we're cross-compiling, allow the user to override the tools and their dnl options. The configure script is oriented toward identifying the host @@ -555,7 +555,7 @@ if test "$cross_compiling" = yes ; then AC_TRY_RUN([#include int main(int argc, char *argv[]) { - ${cf_cv_main_return:-return}(argc < 0 || argv == 0 || argv[0] == 0); + ${cf_cv_main_return:-return}(argc < 0 || argv == (void*)0 || argv[0] == (void*)0); } ], cf_ok_build_cc=yes, @@ -594,7 +594,7 @@ AC_SUBST(BUILD_EXEEXT) AC_SUBST(BUILD_OBJEXT) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_C11_NORETURN version: 4 updated: 2023/02/18 17:41:25 +dnl CF_C11_NORETURN version: 5 updated: 2025/12/14 17:40:20 dnl --------------- AC_DEFUN([CF_C11_NORETURN], [ @@ -607,12 +607,12 @@ AC_MSG_RESULT($enable_stdnoreturn) if test $enable_stdnoreturn = yes; then AC_CACHE_CHECK([for C11 _Noreturn feature], cf_cv_c11_noreturn, - [AC_TRY_COMPILE([ + [AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default #include static _Noreturn void giveup(void) { exit(0); } ], - [if (feof(stdin)) giveup()], + [if (feof(stdin)) giveup()])], cf_cv_c11_noreturn=yes, cf_cv_c11_noreturn=no) ]) @@ -696,7 +696,7 @@ case "$CC" in esac ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CFG_DEFAULTS version: 16 updated: 2021/01/04 19:33:05 +dnl CF_CFG_DEFAULTS version: 17 updated: 2025/12/24 12:27:29 dnl --------------- dnl Determine the default configuration into which we'll install ncurses. This dnl can be overridden by the user's command-line options. There's two items to @@ -726,7 +726,7 @@ AC_MSG_RESULT($prefix) if test "x$prefix" = "xNONE" ; then AC_MSG_CHECKING(for default include-directory) -test -n "$verbose" && echo 1>&AC_FD_MSG +test -n "$verbose" && echo 1>&AS_MESSAGE_FD for cf_symbol in \ "$includedir" \ "$includedir/ncurses" \ @@ -741,11 +741,11 @@ do if test -f "$cf_dir/curses.h" ; then if ( ${FGREP-fgrep} NCURSES_VERSION "$cf_dir/curses.h" >/dev/null 2>&1 ) ; then includedir="$cf_symbol" - test -n "$verbose" && echo $ECHO_N " found " 1>&AC_FD_MSG + test -n "$verbose" && echo $ECHO_N " found " 1>&AS_MESSAGE_FD break fi fi - test -n "$verbose" && echo " tested $cf_dir" 1>&AC_FD_MSG + test -n "$verbose" && echo " tested $cf_dir" 1>&AS_MESSAGE_FD done AC_MSG_RESULT($includedir) fi @@ -802,26 +802,26 @@ case "$cf_cv_gnat_version" in esac ]) dnl --------------------------------------------------------------------------- -dnl CF_CHECK_LIBSSP version: 1 updated: 2021/10/30 10:40:19 +dnl CF_CHECK_LIBSSP version: 2 updated: 2025/12/24 12:27:29 dnl --------------- dnl Check if libssp is needed, e.g., to work around misconfigured libraries dnl used in cross-compiling to MinGW. AC_DEFUN([CF_CHECK_LIBSSP],[ AC_CACHE_CHECK(if ssp library is needed,cf_cv_need_libssp,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ DIR *dp = opendir("."); -],cf_cv_need_libssp=no,[ +])],cf_cv_need_libssp=no,[ cf_save_LIBS="$LIBS" LIBS="$LIBS -lssp" - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ DIR *dp = opendir("."); - ],cf_cv_need_libssp=yes, + ])],cf_cv_need_libssp=yes, cf_cv_need_libssp=maybe) LIBS="$cf_save_LIBS" ])dnl @@ -833,7 +833,7 @@ then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CLANG_COMPILER version: 9 updated: 2023/02/18 17:41:25 +dnl CF_CLANG_COMPILER version: 11 updated: 2025/12/14 17:46:02 dnl ----------------- dnl Check if the given compiler is really clang. clang's C driver defines dnl __GNUC__ (fooling the configure script into setting $GCC to yes) but does @@ -852,12 +852,12 @@ ifelse([$2],,CLANG_COMPILER,[$2])=no if test "$ifelse([$1],,[$1],GCC)" = yes ; then AC_MSG_CHECKING(if this is really Clang ifelse([$1],GXX,C++,C) compiler) cf_save_CFLAGS="$ifelse([$3],,CFLAGS,[$3])" - AC_TRY_COMPILE([],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([],[ #ifdef __clang__ #else #error __clang__ is not defined #endif -],[ifelse([$2],,CLANG_COMPILER,[$2])=yes +])],[ifelse([$2],,CLANG_COMPILER,[$2])=yes ],[]) ifelse([$3],,CFLAGS,[$3])="$cf_save_CFLAGS" AC_MSG_RESULT($ifelse([$2],,CLANG_COMPILER,[$2])) @@ -886,9 +886,9 @@ if test "x$ifelse([$2],,CLANG_COMPILER,[$2])" = "xyes" ; then AC_MSG_CHECKING(if option $cf_clang_opt works) cf_save_CFLAGS="$CFLAGS" CFLAGS="$CFLAGS $cf_clang_opt" - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ - printf("hello!\\n");],[ + printf("hello!\\n");])],[ cf_clang_optok=yes],[ cf_clang_optok=no]) AC_MSG_RESULT($cf_clang_optok) @@ -901,7 +901,7 @@ if test "x$ifelse([$2],,CLANG_COMPILER,[$2])" = "xyes" ; then fi ]) dnl --------------------------------------------------------------------------- -dnl CF_CONST_X_STRING version: 8 updated: 2023/12/01 17:22:50 +dnl CF_CONST_X_STRING version: 10 updated: 2025/12/14 17:40:20 dnl ----------------- dnl The X11R4-X11R6 Xt specification uses an ambiguous String type for most dnl character-strings. @@ -926,22 +926,22 @@ AC_REQUIRE([AC_PATH_XTRA]) CF_SAVE_XTRA_FLAGS([CF_CONST_X_STRING]) -AC_TRY_COMPILE( +AC_COMPILE_IFELSE([AC_LANG_PROGRAM( [ -#include +$ac_includes_default #include ], -[String foo = malloc(1); free((void*)foo)],[ +[String foo = malloc(1); free((void*)foo)])],[ AC_CACHE_CHECK(for X11/Xt const-feature,cf_cv_const_x_string,[ - AC_TRY_COMPILE( + AC_COMPILE_IFELSE([AC_LANG_PROGRAM( [ #undef _CONST_X_STRING #define _CONST_X_STRING /* X11R7.8 (perhaps) */ #undef XTSTRINGDEFINES /* X11R5 and later */ -#include +$ac_includes_default #include - ],[String foo = malloc(1); *foo = 0],[ + ],[String foo = malloc(1); *foo = 0])],[ cf_cv_const_x_string=no ],[ cf_cv_const_x_string=yes @@ -962,68 +962,53 @@ esac ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CONST_X_STRING version: 8 updated: 2023/12/01 17:22:50 -dnl ----------------- -dnl The X11R4-X11R6 Xt specification uses an ambiguous String type for most -dnl character-strings. -dnl -dnl It is ambiguous because the specification accommodated the pre-ANSI -dnl compilers bundled by more than one vendor in lieu of providing a standard C -dnl compiler other than by costly add-ons. Because of this, the specification -dnl did not take into account the use of const for telling the compiler that -dnl string literals would be in readonly memory. -dnl -dnl As a workaround, one could (starting with X11R5) define XTSTRINGDEFINES, to -dnl let the compiler decide how to represent Xt's strings which were #define'd. -dnl That does not solve the problem of using the block of Xt's strings which -dnl are compiled into the library (and is less efficient than one might want). -dnl -dnl Xt specification 7 introduces the _CONST_X_STRING symbol which is used both -dnl when compiling the library and compiling using the library, to tell the -dnl compiler that String is const. -AC_DEFUN([CF_CONST_X_STRING], +dnl CF_CURSES_CONFIG version: 2 updated: 2006/10/29 11:06:27 +dnl ---------------- +dnl Tie together the configure-script macros for curses. It may be ncurses, +dnl but unless asked, we do not make a special search for ncurses. However, +dnl still check for the ncurses version number, for use in other macros. +AC_DEFUN([CF_CURSES_CONFIG], [ -AC_REQUIRE([AC_PATH_XTRA]) - -CF_SAVE_XTRA_FLAGS([CF_CONST_X_STRING]) - -AC_TRY_COMPILE( -[ -#include -#include -], -[String foo = malloc(1); free((void*)foo)],[ - -AC_CACHE_CHECK(for X11/Xt const-feature,cf_cv_const_x_string,[ - AC_TRY_COMPILE( - [ -#undef _CONST_X_STRING -#define _CONST_X_STRING /* X11R7.8 (perhaps) */ -#undef XTSTRINGDEFINES /* X11R5 and later */ -#include -#include - ],[String foo = malloc(1); *foo = 0],[ - cf_cv_const_x_string=no - ],[ - cf_cv_const_x_string=yes - ]) -]) - -CF_RESTORE_XTRA_FLAGS([CF_CONST_X_STRING]) - -case "$cf_cv_const_x_string" in -(no) - CF_APPEND_TEXT(CPPFLAGS,-DXTSTRINGDEFINES) - ;; -(*) - CF_APPEND_TEXT(CPPFLAGS,-D_CONST_X_STRING) - ;; -esac - -]) +CF_CURSES_CPPFLAGS +CF_NCURSES_VERSION +CF_CURSES_LIBS ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CURSES_HEADER version: 6 updated: 2022/12/02 20:06:52 +dnl CF_CURSES_CPPFLAGS version: 14 updated: 2021/01/02 09:31:20 +dnl ------------------ +dnl Look for the curses headers. +AC_DEFUN([CF_CURSES_CPPFLAGS],[ + +AC_CACHE_CHECK(for extra include directories,cf_cv_curses_incdir,[ +cf_cv_curses_incdir=no +case "$host_os" in +(hpux10.*) + if test "x$cf_cv_screen" = "xcurses_colr" + then + test -d /usr/include/curses_colr && \ + cf_cv_curses_incdir="-I/usr/include/curses_colr" + fi + ;; +(sunos3*|sunos4*) + if test "x$cf_cv_screen" = "xcurses_5lib" + then + test -d /usr/5lib && \ + test -d /usr/5include && \ + cf_cv_curses_incdir="-I/usr/5include" + fi + ;; +esac +]) +if test "$cf_cv_curses_incdir" != no +then + CF_APPEND_TEXT(CPPFLAGS,$cf_cv_curses_incdir) +fi + +CF_CURSES_HEADER +CF_TERM_HEADER +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_CURSES_HEADER version: 7 updated: 2025/12/22 04:16:14 dnl ---------------- dnl Find a "curses" header file, e.g,. "curses.h", or one of the more common dnl variations of ncurses' installs. @@ -1036,8 +1021,8 @@ for cf_header in \ ncurses.h ifelse($1,,,[$1/ncurses.h]) \ curses.h ifelse($1,,,[$1/curses.h]) ifelse($1,,[ncurses/ncurses.h ncurses/curses.h]) do -AC_TRY_COMPILE([#include <${cf_header}>], - [initscr(); endwin()], +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include <${cf_header}>], + [initscr(); endwin()])], [cf_cv_ncurses_header=$cf_header; break],[]) done ]) @@ -1048,6 +1033,136 @@ fi # cheat, to get the right #define's for HAVE_NCURSES_H, etc. AC_CHECK_HEADERS($cf_cv_ncurses_header) +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_CURSES_LIBS version: 46 updated: 2025/12/22 04:16:14 +dnl -------------- +dnl Look for the curses libraries. Older curses implementations may require +dnl termcap/termlib to be linked as well. Call CF_CURSES_CPPFLAGS first. +AC_DEFUN([CF_CURSES_LIBS],[ + +AC_REQUIRE([CF_CURSES_CPPFLAGS])dnl +AC_MSG_CHECKING(if we have identified curses libraries) +AC_LINK_IFELSE([AC_LANG_PROGRAM([#include <${cf_cv_ncurses_header:-curses.h}>], + [initscr(); endwin()])], + cf_result=yes, + cf_result=no) +AC_MSG_RESULT($cf_result) + +if test "$cf_result" = no ; then +case "$host_os" in +(freebsd*) + AC_CHECK_LIB(mytinfo,tgoto,[CF_ADD_LIBS(-lmytinfo)]) + ;; +(hpux10.*) + # Looking at HPUX 10.20, the Hcurses library is the oldest (1997), cur_colr + # next (1998), and xcurses "newer" (2000). There is no header file for + # Hcurses; the subdirectory curses_colr has the headers (curses.h and + # term.h) for cur_colr + if test "x$cf_cv_screen" = "xcurses_colr" + then + AC_CHECK_LIB(cur_colr,initscr,[ + CF_ADD_LIBS(-lcur_colr) + ac_cv_func_initscr=yes + ],[ + AC_CHECK_LIB(Hcurses,initscr,[ + # HP's header uses __HP_CURSES, but user claims _HP_CURSES. + CF_ADD_LIBS(-lHcurses) + CF_APPEND_TEXT(CPPFLAGS,-D__HP_CURSES -D_HP_CURSES) + ac_cv_func_initscr=yes + ])]) + fi + ;; +(linux*) + case `arch 2>/dev/null` in + (x86_64) + if test -d /lib64 + then + CF_ADD_LIBDIR(/lib64) + else + CF_ADD_LIBDIR(/lib) + fi + ;; + (*) + CF_ADD_LIBDIR(/lib) + ;; + esac + ;; +(sunos3*|sunos4*) + if test "x$cf_cv_screen" = "xcurses_5lib" + then + if test -d /usr/5lib ; then + CF_ADD_LIBDIR(/usr/5lib) + CF_ADD_LIBS(-lcurses -ltermcap) + fi + fi + ac_cv_func_initscr=yes + ;; +esac + +if test ".$ac_cv_func_initscr" != .yes ; then + cf_save_LIBS="$LIBS" + + if test ".${cf_cv_ncurses_version:-no}" != .no + then + cf_check_list="ncurses curses cursesX" + else + cf_check_list="cursesX curses ncurses" + fi + + # Check for library containing tgoto. Do this before curses library + # because it may be needed to link the test-case for initscr. + if test "x$cf_term_lib" = x + then + AC_CHECK_FUNC(tgoto,[cf_term_lib=predefined],[ + for cf_term_lib in $cf_check_list otermcap termcap tinfo termlib unknown + do + AC_CHECK_LIB($cf_term_lib,tgoto,[ + : "${cf_nculib_root:=$cf_term_lib}" + break + ]) + done + ]) + fi + + # Check for library containing initscr + test "$cf_term_lib" != predefined && test "$cf_term_lib" != unknown && LIBS="-l$cf_term_lib $cf_save_LIBS" + if test "x$cf_curs_lib" = x + then + for cf_curs_lib in $cf_check_list xcurses jcurses pdcurses unknown + do + LIBS="-l$cf_curs_lib $cf_save_LIBS" + if test "$cf_term_lib" = unknown || test "$cf_term_lib" = "$cf_curs_lib" ; then + AC_MSG_CHECKING(if we can link with $cf_curs_lib library) + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include <${cf_cv_ncurses_header:-curses.h}>], + [initscr()])], + [cf_result=yes], + [cf_result=no]) + AC_MSG_RESULT($cf_result) + test "$cf_result" = yes && break + elif test "$cf_curs_lib" = "$cf_term_lib" ; then + cf_result=no + elif test "$cf_term_lib" != predefined ; then + AC_MSG_CHECKING(if we need both $cf_curs_lib and $cf_term_lib libraries) + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include <${cf_cv_ncurses_header:-curses.h}>], + [initscr(); endwin();])], + [cf_result=no], + [ + LIBS="-l$cf_curs_lib -l$cf_term_lib $cf_save_LIBS" + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include <${cf_cv_ncurses_header:-curses.h}>], + [initscr()])], + [cf_result=yes], + [cf_result=error]) + ]) + AC_MSG_RESULT($cf_result) + test "$cf_result" != error && break + fi + done + fi + test "$cf_curs_lib" = unknown && AC_MSG_ERROR(no curses library found) +fi +fi + ])dnl dnl --------------------------------------------------------------------------- dnl CF_DIRNAME version: 5 updated: 2020/12/31 20:19:42 @@ -1155,9 +1270,9 @@ ifelse($2,yes,[CF_GCC_ATTRIBUTES]) fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_FIND_LIBRARY version: 11 updated: 2021/01/02 09:31:20 +dnl CF_FIND_LIBRARY version: 13 updated: 2025/12/22 04:16:14 dnl --------------- -dnl Look for a non-standard library, given parameters for AC_TRY_LINK. We +dnl Look for a non-standard library, given parameters for AC_LINK_IFELSE. We dnl prefer a standard location, and use -L options only if we do not find the dnl library in the standard library location(s). dnl $1 = library name @@ -1167,7 +1282,7 @@ dnl $4 = code fragment to compile/link dnl $5 = corresponding function-name dnl $6 = flag, nonnull if failure should not cause an error-exit dnl -dnl Sets the variable "$cf_libdir" as a side-effect, so we can see if we had +dnl Sets the variable "$cf_libdir" as a side effect, so we can see if we had dnl to use a -L option. AC_DEFUN([CF_FIND_LIBRARY], [ @@ -1178,7 +1293,7 @@ AC_DEFUN([CF_FIND_LIBRARY], cf_save_LIBS="$LIBS" AC_MSG_CHECKING(for $5 in -l$1) LIBS="-l$1 $LIBS" - AC_TRY_LINK([$3],[$4], + AC_LINK_IFELSE([AC_LANG_PROGRAM([$3],[$4])], [AC_MSG_RESULT(yes) eval 'cf_cv_have_lib_'"$1"'=yes' ], @@ -1188,7 +1303,7 @@ AC_DEFUN([CF_FIND_LIBRARY], do AC_MSG_CHECKING(for -l$1 in $cf_libdir) LIBS="-L$cf_libdir -l$1 $cf_save_LIBS" - AC_TRY_LINK([$3],[$4], + AC_LINK_IFELSE([AC_LANG_PROGRAM([$3],[$4])], [AC_MSG_RESULT(yes) eval 'cf_cv_have_lib_'"$1"'=yes' break], @@ -1205,7 +1320,7 @@ fi ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_FIND_LINKAGE version: 22 updated: 2020/12/31 20:19:42 +dnl CF_FIND_LINKAGE version: 23 updated: 2025/12/22 04:16:14 dnl --------------- dnl Find a library (specifically the linkage used in the code fragment), dnl searching for it if it is not already in the library path. @@ -1228,7 +1343,7 @@ dnl $cf_cv_library_file_$3 - library-file if needed, e.g., -l$3 AC_DEFUN([CF_FIND_LINKAGE],[ # If the linkage is not already in the $CPPFLAGS/$LDFLAGS configuration, these -# will be set on completion of the AC_TRY_LINK below. +# will be set on completion of the AC_LINK_IFELSE below. cf_cv_header_path_$3= cf_cv_library_path_$3= @@ -1236,7 +1351,7 @@ CF_MSG_LOG([Starting [FIND_LINKAGE]($3,$6)]) cf_save_LIBS="$LIBS" -AC_TRY_LINK([$1],[$2],[ +AC_LINK_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ cf_cv_find_linkage_$3=yes cf_cv_header_path_$3=/usr/include cf_cv_library_path_$3=/usr/lib @@ -1244,7 +1359,7 @@ AC_TRY_LINK([$1],[$2],[ LIBS="-l$3 $7 $cf_save_LIBS" -AC_TRY_LINK([$1],[$2],[ +AC_LINK_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ cf_cv_find_linkage_$3=yes cf_cv_header_path_$3=/usr/include cf_cv_library_path_$3=/usr/lib @@ -1266,7 +1381,7 @@ AC_TRY_LINK([$1],[$2],[ CF_VERBOSE(... testing $cf_cv_header_path_$3) CPPFLAGS="$cf_save_CPPFLAGS" CF_APPEND_TEXT(CPPFLAGS,-I$cf_cv_header_path_$3) - AC_TRY_COMPILE([$1],[$2],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ CF_VERBOSE(... found $3 headers in $cf_cv_header_path_$3) cf_cv_find_linkage_$3=maybe cf_test_CPPFLAGS="$CPPFLAGS" @@ -1286,7 +1401,7 @@ AC_TRY_LINK([$1],[$2],[ ifelse([$6],,,[ CPPFLAGS="$cf_test_CPPFLAGS" LIBS="-l$3 $7 $cf_save_LIBS" - AC_TRY_LINK([$1],[$2],[ + AC_LINK_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ CF_VERBOSE(... found $3 library in system) cf_cv_find_linkage_$3=yes]) CPPFLAGS="$cf_save_CPPFLAGS" @@ -1302,7 +1417,7 @@ AC_TRY_LINK([$1],[$2],[ CPPFLAGS="$cf_test_CPPFLAGS" LIBS="-l$3 $7 $cf_save_LIBS" LDFLAGS="$cf_save_LDFLAGS -L$cf_cv_library_path_$3" - AC_TRY_LINK([$1],[$2],[ + AC_LINK_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ CF_VERBOSE(... found $3 library in $cf_cv_library_path_$3) cf_cv_find_linkage_$3=yes cf_cv_library_file_$3="-l$3" @@ -1395,19 +1510,36 @@ fi AC_SUBST(EXTRA_CFLAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_FUNC_GETTIME version: 2 updated: 2023/02/25 08:45:56 +dnl CF_FUNC_GETTIME version: 4 updated: 2025/12/23 18:53:34 dnl --------------- dnl Check for gettimeofday or clock_gettime. In 2023, the former is still more dnl widely supported, but "deprecated" (2008), so we will use the latter if it dnl is available, to reduce compiler warnings. AC_DEFUN([CF_FUNC_GETTIME],[ -AC_CACHE_CHECK(for clock_gettime,cf_cv_func_clock_gettime,[ - AC_TRY_LINK([#include ], +cf_save_libs="$LIBS" +AC_CHECK_FUNC(clock_gettime, + cf_cv_test_clock_gettime=yes, + AC_CHECK_LIB(rt, clock_gettime, + [LIBS="-lrt $LIBS" + cf_cv_test_clock_gettime=yes], + cf_cv_test_clock_gettime=no)) + +if test "$cf_cv_test_clock_gettime" = yes ; then +AC_CACHE_CHECK(if clock_gettime links,cf_cv_func_clock_gettime,[ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ +$ac_includes_default +#include + ], [struct timespec ts; - int rc = clock_gettime(CLOCK_REALTIME, &ts); (void) rc; (void)ts], + int rc = clock_gettime(CLOCK_REALTIME, &ts) + + clock_gettime(CLOCK_MONOTONIC, &ts); + (void) rc; (void)ts])], [cf_cv_func_clock_gettime=yes], [cf_cv_func_clock_gettime=no]) ]) +else + cf_cv_func_clock_gettime=no +fi if test "$cf_cv_func_clock_gettime" = yes then @@ -1422,7 +1554,7 @@ AC_CHECK_LIB(bsd, gettimeofday, fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GCC_ATTRIBUTES version: 24 updated: 2021/03/20 12:00:25 +dnl CF_GCC_ATTRIBUTES version: 28 updated: 2025/12/25 18:43:31 dnl ----------------- dnl Test for availability of useful gcc __attribute__ directives to quiet dnl compiler warnings. Though useful, not all are supported -- and contrary @@ -1449,7 +1581,8 @@ cat > conftest.i < "conftest.$ac_ext" < @@ -1477,7 +1610,7 @@ EOF do CF_UPPER(cf_ATTRIBUTE,$cf_attribute) cf_directive="__attribute__(($cf_attribute))" - echo "checking for $CC $cf_directive" 1>&AC_FD_CC + echo "checking for $CC $cf_directive" 1>&AS_MESSAGE_LOG_FD case "$cf_attribute" in (printf) @@ -1552,7 +1685,7 @@ CF_INTEL_COMPILER(GCC,INTEL_COMPILER,CFLAGS) CF_CLANG_COMPILER(GCC,CLANG_COMPILER,CFLAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GCC_WARNINGS version: 41 updated: 2021/01/01 16:53:59 +dnl CF_GCC_WARNINGS version: 45 updated: 2025/12/24 09:07:25 dnl --------------- dnl Check if the compiler supports useful warning options. There's a few that dnl we don't use, simply because they're too noisy: @@ -1593,7 +1726,8 @@ then # remark #981: operands are evaluated in unspecified order # warning #279: controlling expression is constant - AC_CHECKING([for $CC warning options]) + AC_MSG_CHECKING([for $CC warning options]) + test -n "$verbose" && AC_MSG_RESULT() cf_save_CFLAGS="$CFLAGS" EXTRA_CFLAGS="$EXTRA_CFLAGS -Wall" for cf_opt in \ @@ -1616,7 +1750,8 @@ then CFLAGS="$cf_save_CFLAGS" elif test "$GCC" = yes && test "$GCC_VERSION" != "unknown" then - AC_CHECKING([for $CC warning options]) + AC_MSG_CHECKING([for $CC warning options]) + test -n "$verbose" && AC_MSG_RESULT() cf_save_CFLAGS="$CFLAGS" cf_warn_CONST="" test "$with_ext_const" = yes && cf_warn_CONST="Wwrite-strings" @@ -1666,6 +1801,26 @@ rm -rf ./conftest* AC_SUBST(EXTRA_CFLAGS) ])dnl dnl --------------------------------------------------------------------------- +dnl CF_GLOB_FULLPATH version: 2 updated: 2024/08/03 12:34:02 +dnl ---------------- +dnl Use this in case-statements to check for pathname syntax, i.e., absolute +dnl pathnames. The "x" is assumed since we provide an alternate form for DOS. +AC_DEFUN([CF_GLOB_FULLPATH],[ +AC_REQUIRE([CF_WITH_SYSTYPE])dnl +case "$cf_cv_system_name" in +(cygwin*|msys*|mingw32*|mingw64|os2*) + GLOB_FULLPATH_POSIX='/*' + GLOB_FULLPATH_OTHER='[[a-zA-Z]]:[[\\/]]*' + ;; +(*) + GLOB_FULLPATH_POSIX='/*' + GLOB_FULLPATH_OTHER=$GLOB_FULLPATH_POSIX + ;; +esac +AC_SUBST(GLOB_FULLPATH_POSIX) +AC_SUBST(GLOB_FULLPATH_OTHER) +])dnl +dnl --------------------------------------------------------------------------- dnl CF_GNATPREP_OPT_T version: 1 updated: 2014/08/02 18:37:25 dnl ----------------- AC_DEFUN([CF_GNATPREP_OPT_T],[ @@ -1707,7 +1862,7 @@ AC_SUBST(cf_compile_generics) AC_SUBST(cf_generic_objects) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GNAT_PROJECTS version: 13 updated: 2021/01/02 17:09:14 +dnl CF_GNAT_PROJECTS version: 14 updated: 2025/12/24 12:27:29 dnl ---------------- dnl GNAT projects are configured with ".gpr" project files. dnl GNAT libraries are a further development, using the project feature. @@ -1768,7 +1923,7 @@ CF_EOF -XLIBRARY_DIR="`cd ../conftest.lib;pwd`" \ -XSOURCE_DIR="`pwd`" \ -XSONAME=libConfTest.so.1 \ - -XLIB_KIND=static 1>&AC_FD_CC 2>&1 ) ; then + -XLIB_KIND=static 1>&AS_MESSAGE_LOG_FD 2>&1 ) ; then cf_gnat_projects=yes fi cd .. @@ -1872,7 +2027,7 @@ fi AC_SUBST(USE_GNAT_SIGINT) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GNAT_TRY_LINK version: 4 updated: 2021/01/01 13:31:04 +dnl CF_GNAT_TRY_LINK version: 5 updated: 2025/12/24 12:27:29 dnl ---------------- dnl Verify that a test program compiles/links with GNAT. dnl $cf_ada_make is set to the program that compiles/links @@ -1891,7 +2046,7 @@ CF_EOF cat >>conftest.adb <&AC_FD_CC 2>&1 ) ; then +if ( "$cf_ada_make" $ADAFLAGS conftest 1>&AS_MESSAGE_LOG_FD 2>&1 ) ; then ifelse($3,, :,[ $3]) ifelse($4,,,[else $4]) @@ -1899,7 +2054,7 @@ fi rm -rf ./conftest* ./*~conftest* ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GNAT_TRY_RUN version: 6 updated: 2021/01/01 13:31:04 +dnl CF_GNAT_TRY_RUN version: 7 updated: 2025/12/24 12:27:29 dnl --------------- dnl Verify that a test program compiles and runs with GNAT dnl $cf_ada_make is set to the program that compiles/links @@ -1918,8 +2073,8 @@ CF_EOF cat >>conftest.adb <&AC_FD_CC 2>&1 ) ; then - if ( ./conftest 1>&AC_FD_CC 2>&1 ) ; then +if ( "$cf_ada_make" $ADAFLAGS conftest 1>&AS_MESSAGE_LOG_FD 2>&1 ) ; then + if ( ./conftest 1>&AS_MESSAGE_LOG_FD 2>&1 ) ; then ifelse($3,, :,[ $3]) ifelse($4,,,[ else $4]) @@ -1946,7 +2101,7 @@ test -z "$cf_cv_gnat_version" && cf_cv_gnat_version=no ifelse($1,,,[eval $1=$cf_cv_gnat_version; unset cf_cv_gnat_version]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GNU_SOURCE version: 10 updated: 2018/12/10 20:09:41 +dnl CF_GNU_SOURCE version: 11 updated: 2025/12/14 17:40:20 dnl ------------- dnl Check if we must define _GNU_SOURCE to get a reasonable value for dnl _XOPEN_SOURCE, upon which many POSIX definitions depend. This is a defect @@ -1962,14 +2117,14 @@ AC_DEFUN([CF_GNU_SOURCE], cf_gnu_xopen_source=ifelse($1,,500,$1) AC_CACHE_CHECK(if this is the GNU C library,cf_cv_gnu_library,[ -AC_TRY_COMPILE([#include ],[ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if __GLIBC__ > 0 && __GLIBC_MINOR__ >= 0 return 0; #elif __NEWLIB__ > 0 && __NEWLIB_MINOR__ >= 0 return 0; #else # error not GNU C library - #endif], + #endif])], [cf_cv_gnu_library=yes], [cf_cv_gnu_library=no]) ]) @@ -1982,14 +2137,14 @@ if test x$cf_cv_gnu_library = xyes; then AC_CACHE_CHECK(if _DEFAULT_SOURCE can be used as a basis,cf_cv_gnu_library_219,[ cf_save="$CPPFLAGS" CF_APPEND_TEXT(CPPFLAGS,-D_DEFAULT_SOURCE) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 19) || (__GLIBC__ > 2) return 0; #elif (__NEWLIB__ == 2 && __NEWLIB_MINOR__ >= 4) || (__GLIBC__ > 3) return 0; #else # error GNU C library __GLIBC__.__GLIBC_MINOR__ is too old - #endif], + #endif])], [cf_cv_gnu_library_219=yes], [cf_cv_gnu_library_219=no]) CPPFLAGS="$cf_save" @@ -1999,7 +2154,7 @@ if test x$cf_cv_gnu_library = xyes; then cf_save="$CPPFLAGS" AC_CACHE_CHECK(if _XOPEN_SOURCE=$cf_gnu_xopen_source works with _DEFAULT_SOURCE,cf_cv_gnu_dftsrc_219,[ CF_ADD_CFLAGS(-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=$cf_gnu_xopen_source) - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ @@ -2007,7 +2162,7 @@ if test x$cf_cv_gnu_library = xyes; then return 0; #else # error GNU C library is too old - #endif], + #endif])], [cf_cv_gnu_dftsrc_219=yes], [cf_cv_gnu_dftsrc_219=no]) ]) @@ -2019,17 +2174,17 @@ if test x$cf_cv_gnu_library = xyes; then if test "x$cf_cv_gnu_dftsrc_219" != xyes; then AC_CACHE_CHECK(if we must define _GNU_SOURCE,cf_cv_gnu_source,[ - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef _XOPEN_SOURCE #error expected _XOPEN_SOURCE to be defined - #endif], + #endif])], [cf_cv_gnu_source=no], [cf_save="$CPPFLAGS" CF_ADD_CFLAGS(-D_GNU_SOURCE) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifdef _XOPEN_SOURCE #error expected _XOPEN_SOURCE to be undefined - #endif], + #endif])], [cf_cv_gnu_source=no], [cf_cv_gnu_source=yes]) CPPFLAGS="$cf_save" @@ -2040,10 +2195,10 @@ if test x$cf_cv_gnu_library = xyes; then then AC_CACHE_CHECK(if we should also define _DEFAULT_SOURCE,cf_cv_default_source,[ CF_APPEND_TEXT(CPPFLAGS,-D_GNU_SOURCE) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifdef _DEFAULT_SOURCE #error expected _DEFAULT_SOURCE to be undefined - #endif], + #endif])], [cf_cv_default_source=no], [cf_cv_default_source=yes]) ]) @@ -2289,7 +2444,45 @@ fi AC_SUBST(INSTALL_OPT_S) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_INTEL_COMPILER version: 9 updated: 2023/02/18 17:41:25 +dnl CF_INSTALL_PREFIX version: 2 updated: 2025/10/18 11:14:21 +dnl ----------------- +dnl Special option for use by system-builders: the install-prefix is used to +dnl adjust the location into which the actual install is done, so that an +dnl archive can be built without modifying the host system's configuration. +AC_DEFUN([CF_INSTALL_PREFIX],[ +AC_MSG_CHECKING(for an installation directory prefix) +AC_ARG_WITH(install-prefix, + [ --with-install-prefix=DESTDIR use DESTDIR as installation directory prefix], + [case "x$withval" in + (xyes|xno) + ;; + (*) DESTDIR="$withval" + ;; + esac]) +AC_MSG_RESULT([${DESTDIR:-(none)}]) +AC_SUBST(DESTDIR) + +SET_DESTDIR= +test -n "$DESTDIR" && SET_DESTDIR="DESTDIR=$DESTDIR" +AC_SUBST(SET_DESTDIR) + +AC_MSG_CHECKING(if installation directory prefix should be merged) +CF_ARG_ENABLE(install-prefix, + [ --enable-install-prefix merge DESTDIR with installation prefix], + cf_install_prefix=yes, + cf_install_prefix=no) +AC_MSG_RESULT($cf_install_prefix) + +if test "$cf_install_prefix" = yes ; then + MERGE_PREFIX=':$(prefix)%=%' +else + MERGE_PREFIX='' +fi + +AC_SUBST(MERGE_PREFIX) +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_INTEL_COMPILER version: 10 updated: 2025/12/14 17:40:20 dnl ----------------- dnl Check if the given compiler is really the Intel compiler for Linux. It dnl tries to imitate gcc, but does not return an error when it finds a mismatch @@ -2312,12 +2505,12 @@ if test "$ifelse([$1],,[$1],GCC)" = yes ; then AC_MSG_CHECKING(if this is really Intel ifelse([$1],GXX,C++,C) compiler) cf_save_CFLAGS="$ifelse([$3],,CFLAGS,[$3])" ifelse([$3],,CFLAGS,[$3])="$ifelse([$3],,CFLAGS,[$3]) -no-gcc" - AC_TRY_COMPILE([],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([],[ #ifdef __INTEL_COMPILER #else #error __INTEL_COMPILER is not defined #endif -],[ifelse([$2],,INTEL_COMPILER,[$2])=yes +])],[ifelse([$2],,INTEL_COMPILER,[$2])=yes cf_save_CFLAGS="$cf_save_CFLAGS -we147" ],[]) ifelse([$3],,CFLAGS,[$3])="$cf_save_CFLAGS" @@ -2327,7 +2520,7 @@ cf_save_CFLAGS="$cf_save_CFLAGS -we147" fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_LARGEFILE version: 13 updated: 2023/12/03 19:09:59 +dnl CF_LARGEFILE version: 14 updated: 2025/12/22 04:16:14 dnl ------------ dnl Add checks for large file support. AC_DEFUN([CF_LARGEFILE],[ @@ -2357,7 +2550,7 @@ ifdef([AC_FUNC_FSEEKO],[ fi AC_CACHE_CHECK(whether to use struct dirent64, cf_cv_struct_dirent64,[ - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #pragma GCC diagnostic error "-Wincompatible-pointer-types" #include #include @@ -2372,7 +2565,7 @@ extern struct dirent64 * readdir(DIR *); struct dirent *y = readdir(dp); int z = x - y; (void)z; - ], + ])], [cf_cv_struct_dirent64=yes], [cf_cv_struct_dirent64=no]) ]) @@ -2381,7 +2574,7 @@ extern struct dirent64 * readdir(DIR *); ]) ]) dnl --------------------------------------------------------------------------- -dnl CF_LD_RPATH_OPT version: 9 updated: 2021/01/01 13:31:04 +dnl CF_LD_RPATH_OPT version: 10 updated: 2025/12/15 04:04:20 dnl --------------- dnl For the given system and compiler, find the compiler flags to pass to the dnl loader to use the "rpath" feature. @@ -2429,7 +2622,7 @@ then AC_MSG_CHECKING(if we need a space after rpath option) cf_save_LIBS="$LIBS" CF_ADD_LIBS(${LD_RPATH_OPT}$libdir) - AC_TRY_LINK(, , cf_rpath_space=no, cf_rpath_space=yes) + AC_LINK_IFELSE([AC_LANG_PROGRAM([], [])], cf_rpath_space=no, cf_rpath_space=yes) LIBS="$cf_save_LIBS" AC_MSG_RESULT($cf_rpath_space) test "$cf_rpath_space" = yes && LD_RPATH_OPT="$LD_RPATH_OPT " @@ -2600,7 +2793,7 @@ AC_DEFUN([CF_LIB_TYPE], test -n "$LIB_SUFFIX" && $2="${LIB_SUFFIX}[$]{$2}" ])dnl dnl --------------------------------------------------------------------------- -dnl CF_LINK_DATAONLY version: 15 updated: 2023/12/03 10:03:10 +dnl CF_LINK_DATAONLY version: 17 updated: 2025/12/24 12:27:29 dnl ---------------- dnl Some systems have a non-ANSI linker that doesn't pull in modules that have dnl only data (i.e., no functions), for example NeXT. On those systems we'll @@ -2616,10 +2809,10 @@ AC_CACHE_VAL(cf_cv_link_dataonly,[ int testdata[[3]] = { 123, 456, 789 }; EOF if AC_TRY_EVAL(ac_compile) ; then - mv conftest.o data.o && \ - ( $AR $ARFLAGS conftest.a data.o ) 2>&AC_FD_CC 1>/dev/null + mv conftest.$OBJEXT data.$OBJEXT && \ + ( $AR $ARFLAGS conftest.a data.$OBJEXT ) 2>&AS_MESSAGE_LOG_FD 1>/dev/null fi - rm -f conftest.$ac_ext data.o + rm -f conftest.$ac_ext data.$OBJEXT cat >conftest.$ac_ext <&AC_FD_CC 1>/dev/null + mv conftest.$OBJEXT func.$OBJEXT && \ + ( $AR $ARFLAGS conftest.a func.$OBJEXT ) 2>&AS_MESSAGE_LOG_FD 1>/dev/null fi - rm -f conftest.$ac_ext func.o - ( eval $RANLIB conftest.a ) 2>&AC_FD_CC >/dev/null + rm -f conftest.$ac_ext func.$OBJEXT + ( eval $RANLIB conftest.a ) 2>&AS_MESSAGE_LOG_FD >/dev/null cf_saveLIBS="$LIBS" LIBS="conftest.a $LIBS" AC_TRY_RUN([ @@ -2668,50 +2861,7 @@ AC_SUBST(BROKEN_LINKER) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MAKEFLAGS version: 21 updated: 2021/09/04 06:47:34 -dnl ------------ -dnl Some 'make' programs support ${MAKEFLAGS}, some ${MFLAGS}, to pass 'make' -dnl options to lower-levels. It is very useful for "make -n" -- if we have it. -dnl (GNU 'make' does both, something POSIX 'make', which happens to make the -dnl ${MAKEFLAGS} variable incompatible because it adds the assignments :-) -AC_DEFUN([CF_MAKEFLAGS], -[AC_REQUIRE([AC_PROG_FGREP])dnl - -AC_CACHE_CHECK(for makeflags variable, cf_cv_makeflags,[ - cf_cv_makeflags='' - for cf_option in '-${MAKEFLAGS}' '${MFLAGS}' - do - cat >cf_makeflags.tmp </dev/null | ${FGREP-fgrep} -v "ing directory" | sed -e 's,[[ ]]*$,,'` - case "$cf_result" in - (.*k|.*kw) - cf_result="`${MAKE:-make} -k -f cf_makeflags.tmp CC=cc 2>/dev/null`" - case "$cf_result" in - (.*CC=*) cf_cv_makeflags= - ;; - (*) cf_cv_makeflags=$cf_option - ;; - esac - break - ;; - (.-) - ;; - (*) - CF_MSG_LOG(given option \"$cf_option\", no match \"$cf_result\") - ;; - esac - done - rm -f cf_makeflags.tmp -]) - -AC_SUBST(cf_cv_makeflags) -])dnl -dnl --------------------------------------------------------------------------- -dnl CF_MAKE_PHONY version: 3 updated: 2021/01/08 16:08:21 +dnl CF_MAKE_PHONY version: 4 updated: 2025/12/24 12:27:29 dnl ------------- dnl Check if the make-program handles a ".PHONY" target, e.g,. a target which dnl acts as a placeholder. @@ -2782,7 +2932,7 @@ CF_EOF fi break done - ) >&AC_FD_CC 2>&1 + ) >&AS_MESSAGE_LOG_FD 2>&1 cf_cv_make_PHONY="`cat conftest.tmp`" rm -rf conftest* ]) @@ -2861,7 +3011,7 @@ fi test "$cf_cv_mixedcase" = yes && AC_DEFINE(MIXEDCASE_FILENAMES,1,[Define to 1 if filesystem supports mixed-case filenames.]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MKSTEMP version: 13 updated: 2023/12/01 17:22:50 +dnl CF_MKSTEMP version: 14 updated: 2025/12/14 18:08:20 dnl ---------- dnl Check for a working mkstemp. This creates two files, checks that they are dnl successfully created and distinct (AmigaOS apparently fails on the last). @@ -2871,7 +3021,7 @@ unistd.h \ ) AC_CACHE_CHECK(for working mkstemp, cf_cv_func_mkstemp,[ rm -rf ./conftest* -AC_TRY_RUN([ +AC_RUN_IFELSE([AC_LANG_SOURCE([[ $ac_includes_default int main(void) @@ -2901,7 +3051,7 @@ int main(void) result = 1; ${cf_cv_main_return:-return}(result); } -],[cf_cv_func_mkstemp=yes +]])],[cf_cv_func_mkstemp=yes ],[cf_cv_func_mkstemp=no ],[cf_cv_func_mkstemp=maybe]) ]) @@ -2913,15 +3063,15 @@ if test "x$cf_cv_func_mkstemp" = xyes || test "x$ac_cv_func_mkstemp" = xyes ; th fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MSG_LOG version: 5 updated: 2010/10/23 15:52:32 +dnl CF_MSG_LOG version: 6 updated: 2025/12/14 17:51:46 dnl ---------- dnl Write a debug message to config.log, along with the line number in the dnl configure script. AC_DEFUN([CF_MSG_LOG],[ -echo "${as_me:-configure}:__oline__: testing $* ..." 1>&AC_FD_CC +echo "${as_me:-configure}:__oline__: testing $* ..." 1>&AS_MESSAGE_LOG_FD ])dnl dnl --------------------------------------------------------------------------- -dnl CF_NCURSES_ADDON version: 6 updated: 2021/01/04 19:33:05 +dnl CF_NCURSES_ADDON version: 9 updated: 2025/12/24 13:30:00 dnl ---------------- dnl Configure an ncurses add-on, built outside the ncurses tree. AC_DEFUN([CF_NCURSES_ADDON],[ @@ -2929,18 +3079,29 @@ AC_REQUIRE([CF_NCURSES_CONFIG]) AC_PROVIDE([CF_SUBST_NCURSES_VERSION]) -AC_MSG_CHECKING(if you want wide-character code) -AC_ARG_ENABLE(widec, - [ --enable-widec compile with wide-char/UTF-8 code], - [with_widec=$enableval], - [with_widec=no]) -AC_MSG_RESULT($with_widec) -if test "$with_widec" = yes ; then +AC_MSG_CHECKING(for specified curses library type) +AC_ARG_WITH(screen, + [ --with-screen=XXX use specified curses-libraries], + [cf_cv_screen=$withval], + [cf_cv_screen=ncurses]) + +case $cf_cv_screen in +(curses|curses_*) + CF_CURSES_CONFIG + ;; +(ncursesw*) CF_UTF8_LIB - CF_NCURSES_CONFIG(ncursesw) -else - CF_NCURSES_CONFIG(ncurses) -fi + CF_NCURSES_CONFIG($cf_cv_screen) + ;; +(ncurses*) + CF_NCURSES_CONFIG($cf_cv_screen) + ;; +(*) + AC_MSG_ERROR(unexpected screen-value: $cf_cv_screen) + ;; +esac + +AC_SUBST(cf_cv_screen) if test "$NCURSES_CONFIG_PKG" != none ; then cf_version=`$PKG_CONFIG --modversion $NCURSES_CONFIG_PKG 2>/dev/null` @@ -3004,29 +3165,32 @@ dnl We need these values in the generated makefiles AC_SUBST(cf_cv_rel_version) AC_SUBST(cf_cv_abi_version) -dnl FIXME - not needed for Ada95 -AC_SUBST(cf_cv_builtin_bool) -AC_SUBST(cf_cv_header_stdbool_h) -AC_SUBST(cf_cv_type_of_bool)dnl - +AC_CACHE_CHECK(if KEY_RESIZE is supported,cf_cv_curses_resizes,[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include <${cf_cv_ncurses_header:-curses.h}>], + [int key = KEY_RESIZE; (void)key])], + cf_cv_curses_resizes=yes, + cf_cv_curses_resizes=no)]) +cf_cv_enable_sigwinch=0 +test "$cf_cv_curses_resizes" = yes && cf_cv_enable_sigwinch=1 +AC_SUBST(cf_cv_enable_sigwinch) ]) dnl --------------------------------------------------------------------------- -dnl CF_NCURSES_CC_CHECK version: 6 updated: 2023/02/18 17:47:58 +dnl CF_NCURSES_CC_CHECK version: 7 updated: 2025/12/22 04:16:14 dnl ------------------- dnl Check if we can compile with ncurses' header file dnl $1 is the cache variable to set dnl $2 is the header-file to include dnl $3 is the root name (ncurses or ncursesw) AC_DEFUN([CF_NCURSES_CC_CHECK],[ - AC_TRY_COMPILE([ -]ifelse($3,ncursesw,[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ +]ifelse([$3],ncursesw,[ #define _XOPEN_SOURCE_EXTENDED #undef HAVE_LIBUTF8_H /* in case we used CF_UTF8_LIB */ #define HAVE_LIBUTF8_H /* to force ncurses' header file to use cchar_t */ ])[ #include <$2>],[ #ifdef NCURSES_VERSION -]ifelse($3,ncursesw,[ +]ifelse([$3],ncursesw,[ #ifndef WACS_BSSB #error WACS_BSSB is not defined #endif @@ -3039,12 +3203,12 @@ printf("old\\n"); #error __NCURSES_H is not defined #endif #endif - ] + ])]dnl ,[$1=$2] ,[$1=no]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_NCURSES_CONFIG version: 28 updated: 2021/08/28 15:20:37 +dnl CF_NCURSES_CONFIG version: 30 updated: 2025/12/22 04:16:14 dnl ----------------- dnl Tie together the configure-script macros for ncurses, preferring these in dnl order: @@ -3082,8 +3246,8 @@ if test "x${PKG_CONFIG:=none}" != xnone; then CF_ADD_CFLAGS($cf_pkg_cflags) CF_ADD_LIBS($cf_pkg_libs) - AC_TRY_LINK([#include <${cf_cv_ncurses_header:-curses.h}>], - [initscr(); mousemask(0,0); tigetstr((char *)0);], + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include <${cf_cv_ncurses_header:-curses.h}>], + [initscr(); mousemask(0,0); tigetstr((char *)0);])], [AC_TRY_RUN([#include <${cf_cv_ncurses_header:-curses.h}> int main(void) { const char *xx = curses_version(); return (xx == 0); }], @@ -3105,11 +3269,12 @@ if test "x${PKG_CONFIG:=none}" != xnone; then ;; esac + CF_REQUIRE_PKG($cf_ncuconfig_root) CF_APPEND_CFLAGS($cf_pkg_cflags) CF_ADD_LIBS($cf_pkg_libs) - AC_TRY_LINK([#include <${cf_cv_ncurses_header:-curses.h}>], - [initscr(); mousemask(0,0); tigetstr((char *)0);], + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include <${cf_cv_ncurses_header:-curses.h}>], + [initscr(); mousemask(0,0); tigetstr((char *)0);])], [AC_TRY_RUN([#include <${cf_cv_ncurses_header:-curses.h}> int main(void) { const char *xx = curses_version(); return (xx == 0); }], @@ -3225,7 +3390,7 @@ AC_DEFINE(NCURSES,1,[Define to 1 if we are using ncurses headers/libraries]) CF_NCURSES_VERSION ])dnl dnl --------------------------------------------------------------------------- -dnl CF_NCURSES_HEADER version: 7 updated: 2021/01/04 19:33:05 +dnl CF_NCURSES_HEADER version: 8 updated: 2025/12/22 04:16:14 dnl ----------------- dnl Find a "curses" header file, e.g,. "curses.h", or one of the more common dnl variations of ncurses' installs. @@ -3252,10 +3417,10 @@ AC_CACHE_CHECK(for $cf_ncuhdr_root include-path, cf_cv_ncurses_h2,[ CF_NCURSES_CC_CHECK(cf_cv_ncurses_h2,$cf_header,$1) if test "$cf_cv_ncurses_h2" != no ; then cf_cv_ncurses_h2=$cf_incdir/$cf_header - test -n "$verbose" && echo $ECHO_N " ... found $ECHO_C" 1>&AC_FD_MSG + test -n "$verbose" && echo $ECHO_N " ... found $ECHO_C" 1>&AS_MESSAGE_FD break fi - test -n "$verbose" && echo " ... tested $cf_incdir/$cf_header" 1>&AC_FD_MSG + test -n "$verbose" && echo " ... tested $cf_incdir/$cf_header" 1>&AS_MESSAGE_FD done CPPFLAGS="$cf_save2_CPPFLAGS" test "$cf_cv_ncurses_h2" != no && break @@ -3291,7 +3456,7 @@ esac ])dnl dnl --------------------------------------------------------------------------- -dnl CF_NCURSES_LIBS version: 21 updated: 2021/09/04 06:37:12 +dnl CF_NCURSES_LIBS version: 22 updated: 2025/12/22 04:16:14 dnl --------------- dnl Look for the ncurses library. This is a little complicated on Linux, dnl because it may be linked with the gpm (general purpose mouse) library. @@ -3348,8 +3513,8 @@ if test -n "$cf_ncurses_LIBS" ; then LIBS="$q" fi done - AC_TRY_LINK([#include <${cf_cv_ncurses_header:-curses.h}>], - [initscr(); mousemask(0,0); tigetstr((char *)0);], + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include <${cf_cv_ncurses_header:-curses.h}>], + [initscr(); mousemask(0,0); tigetstr((char *)0);])], [AC_MSG_RESULT(yes)], [AC_MSG_RESULT(no) LIBS="$cf_ncurses_SAVE"]) @@ -3359,7 +3524,7 @@ CF_UPPER(cf_nculib_ROOT,HAVE_LIB$cf_nculib_root) AC_DEFINE_UNQUOTED($cf_nculib_ROOT) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_NCURSES_VERSION version: 18 updated: 2024/01/07 06:34:16 +dnl CF_NCURSES_VERSION version: 19 updated: 2025/12/22 04:16:14 dnl ------------------ dnl Check for the version of ncurses, to aid in reporting bugs, etc. dnl Call CF_CURSES_CPPFLAGS first, or CF_NCURSES_CPPFLAGS. We don't use @@ -3410,7 +3575,7 @@ Autoconf "old" ; #endif EOF - cf_try="$ac_cpp conftest.$ac_ext 2>&AC_FD_CC | grep '^Autoconf ' >conftest.out" + cf_try="$ac_cpp conftest.$ac_ext 2>&AS_MESSAGE_LOG_FD | grep '^Autoconf ' >conftest.out" AC_TRY_EVAL(cf_try) if test -f conftest.out ; then cf_out=`sed -e 's%^Autoconf %%' -e 's%^[[^"]]*"%%' -e 's%".*%%' conftest.out` @@ -3459,39 +3624,39 @@ ifelse([$1],,,[$1=$PATH_SEPARATOR]) AC_MSG_RESULT($PATH_SEPARATOR) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PATH_SYNTAX version: 18 updated: 2020/12/31 18:40:20 +dnl CF_PATH_SYNTAX version: 20 updated: 2025/12/16 04:09:03 dnl -------------- dnl Check the argument to see that it looks like a pathname. Rewrite it if it dnl begins with one of the prefix/exec_prefix variables, and then again if the dnl result begins with 'NONE'. This is necessary to work around autoconf's dnl delayed evaluation of those symbols. AC_DEFUN([CF_PATH_SYNTAX],[ +AC_REQUIRE([CF_GLOB_FULLPATH])dnl + if test "x$prefix" != xNONE; then cf_path_syntax="$prefix" else cf_path_syntax="$ac_default_prefix" fi -case ".[$]$1" in -(.\[$]\(*\)*|.\'*\'*) +case "x[$]$1" in +(x\[$]\(*\)*|x\'*\'*) ;; -(..|./*|.\\*) +(x.|x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; -(.[[a-zA-Z]]:[[\\/]]*) # OS/2 EMX - ;; -(.\[$]\{*prefix\}*|.\[$]\{*dir\}*) +(x\[$]\{*prefix\}*|x\[$]\{*dir\}*) eval $1="[$]$1" - case ".[$]$1" in - (.NONE/*) + case "x[$]$1" in + (xNONE/*) $1=`echo "[$]$1" | sed -e s%NONE%$cf_path_syntax%` ;; esac ;; -(.no|.NONE/*) +(xno|xNONE/*) $1=`echo "[$]$1" | sed -e s%NONE%$cf_path_syntax%` ;; (*) - ifelse([$2],,[AC_MSG_ERROR([expected a pathname, not \"[$]$1\"])],$2) + ifelse([$2],,[AC_MSG_ERROR([expected a pathname, not "[$]$1"])],$2) ;; esac ])dnl @@ -3534,7 +3699,7 @@ fi AC_SUBST(PKG_CONFIG) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_POSIX_C_SOURCE version: 12 updated: 2023/02/18 17:41:25 +dnl CF_POSIX_C_SOURCE version: 13 updated: 2025/12/14 17:40:20 dnl ----------------- dnl Define _POSIX_C_SOURCE to the given level, and _POSIX_SOURCE if needed. dnl @@ -3563,10 +3728,10 @@ CF_REMOVE_DEFINE(cf_trim_CPPFLAGS,$cf_save_CPPFLAGS,_POSIX_C_SOURCE) AC_CACHE_CHECK(if we should define _POSIX_C_SOURCE,cf_cv_posix_c_source,[ CF_MSG_LOG(if the symbol is already defined go no further) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef _POSIX_C_SOURCE #error _POSIX_C_SOURCE is not defined -#endif], +#endif])], [cf_cv_posix_c_source=no], [cf_want_posix_source=no case .$cf_POSIX_C_SOURCE in @@ -3582,10 +3747,10 @@ AC_CACHE_CHECK(if we should define _POSIX_C_SOURCE,cf_cv_posix_c_source,[ ;; esac if test "$cf_want_posix_source" = yes ; then - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifdef _POSIX_SOURCE #error _POSIX_SOURCE is defined -#endif],[], +#endif])],[], cf_cv_posix_c_source="$cf_cv_posix_c_source -D_POSIX_SOURCE") fi CF_MSG_LOG(ifdef from value $cf_POSIX_C_SOURCE) @@ -3593,10 +3758,10 @@ AC_CACHE_CHECK(if we should define _POSIX_C_SOURCE,cf_cv_posix_c_source,[ CPPFLAGS="$cf_trim_CPPFLAGS" CF_APPEND_TEXT(CPPFLAGS,$cf_cv_posix_c_source) CF_MSG_LOG(if the second compile does not leave our definition intact error) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef _POSIX_C_SOURCE #error _POSIX_C_SOURCE is not defined -#endif],, +#endif])],, [cf_cv_posix_c_source=no]) CFLAGS="$cf_save_CFLAGS" CPPFLAGS="$cf_save_CPPFLAGS" @@ -3613,7 +3778,7 @@ fi # cf_cv_posix_visible ])dnl dnl --------------------------------------------------------------------------- -dnl CF_POSIX_VISIBLE version: 1 updated: 2018/12/31 20:46:17 +dnl CF_POSIX_VISIBLE version: 2 updated: 2025/12/14 17:40:20 dnl ---------------- dnl POSIX documents test-macros which an application may set before any system dnl headers are included to make features available. @@ -3629,14 +3794,14 @@ dnl conflicting definition. AC_DEFUN([CF_POSIX_VISIBLE], [ AC_CACHE_CHECK(if the POSIX test-macros are already defined,cf_cv_posix_visible,[ -AC_TRY_COMPILE([#include ],[ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if defined(__POSIX_VISIBLE) && ((__POSIX_VISIBLE - 0L) > 0) \ && defined(__XSI_VISIBLE) && ((__XSI_VISIBLE - 0L) > 0) \ && defined(__BSD_VISIBLE) && ((__BSD_VISIBLE - 0L) > 0) \ && defined(__ISO_C_VISIBLE) && ((__ISO_C_VISIBLE - 0L) > 0) #error conflicting symbols found #endif -],[cf_cv_posix_visible=no],[cf_cv_posix_visible=yes]) +])],[cf_cv_posix_visible=no],[cf_cv_posix_visible=yes]) ]) ])dnl dnl --------------------------------------------------------------------------- @@ -3673,7 +3838,7 @@ CF_ACVERSION_CHECK(2.52, CF_CC_ENV_FLAGS ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PROG_CC_C_O version: 6 updated: 2021/01/01 13:31:04 +dnl CF_PROG_CC_C_O version: 7 updated: 2025/12/24 12:27:29 dnl -------------- dnl Analogous to AC_PROG_CC_C_O, but more useful: tests only $CC, ensures that dnl the output file can be renamed, and allows for a shell variable that can @@ -3697,7 +3862,7 @@ int main(void) CF_EOF # We do the test twice because some compilers refuse to overwrite an # existing .o file with -o, though they will create one. -ac_try='[$]$1 $2 -c conftest.$ac_ext -o conftest2.$ac_objext >&AC_FD_CC' +ac_try='[$]$1 $2 -c conftest.$ac_ext -o conftest2.$ac_objext >&AS_MESSAGE_LOG_FD' if AC_TRY_EVAL(ac_try) && test -f conftest2.$ac_objext && AC_TRY_EVAL(ac_try); then @@ -3754,7 +3919,7 @@ AC_SUBST(PROG_EXT) test -n "$PROG_EXT" && AC_DEFINE_UNQUOTED(PROG_EXT,"$PROG_EXT",[Define to the program extension (normally blank)]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PROG_GNAT version: 12 updated: 2021/01/02 17:09:14 +dnl CF_PROG_GNAT version: 13 updated: 2025/12/24 12:27:29 dnl ------------ dnl Check for gnat/gnatmake/etc, ensure that the toolset is complete. AC_DEFUN([CF_PROG_GNAT],[ @@ -3803,12 +3968,12 @@ else "$cf_gprconfig,,,,GCC" \ "$cf_gprconfig" do - cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&AC_FD_CC | ${AWK:-awk} '/^\*/{print [$]3;}' | head -n 1` + cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&AS_MESSAGE_LOG_FD | ${AWK:-awk} '/^\*/{print [$]3;}' | head -n 1` test -n "$cf_gprconfig_value" && break done else cf_gprconfig_param=$cf_gprconfig - cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&AC_FD_CC | ${AWK:-awk} '/^\*/{print [$]3;}' | head -n 1` + cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&AS_MESSAGE_LOG_FD | ${AWK:-awk} '/^\*/{print [$]3;}' | head -n 1` fi if test -n "$cf_gprconfig_value" then @@ -3859,15 +4024,25 @@ AC_SUBST(cf_ada_config_Ada) AC_SUBST(cf_ada_config_C) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PROG_INSTALL version: 10 updated: 2021/01/04 19:33:05 +dnl CF_PROG_INSTALL version: 13 updated: 2025/10/21 16:28:49 dnl --------------- dnl Force $INSTALL to be an absolute-path. Otherwise, edit_man.sh and the dnl misc/tabset install won't work properly. Usually this happens only when dnl using the fallback mkinstalldirs script AC_DEFUN([CF_PROG_INSTALL], [AC_PROG_INSTALL -case $INSTALL in -(/*) +AC_REQUIRE([CF_GLOB_FULLPATH])dnl +if test "x$INSTALL" = "x./install-sh -c"; then + if test -f /usr/sbin/install ; then + case "$host_os" in + (linux*gnu*|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) + INSTALL=/usr/sbin/install + ;; + esac + fi +fi +case x$INSTALL in +(x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; (*) CF_DIRNAME(cf_dir,$INSTALL) @@ -3947,6 +4122,30 @@ define([CF_REMOVE_LIB], $1=`echo "$2" | sed -e 's/-l$3[[ ]]//g' -e 's/-l$3[$]//'` ])dnl dnl --------------------------------------------------------------------------- +dnl CF_REQUIRE_PKG version: 1 updated: 2025/01/10 19:55:54 +dnl -------------- +dnl Update $REQUIRE_PKG, which lists the known required packages for this +dnl program. +dnl +dnl $1 = package(s) to require, e.g., in the generated ".pc" file +define([CF_REQUIRE_PKG], +[ +for cf_required in $1 +do + # check for duplicates + for cf_require_pkg in $REQUIRE_PKG + do + if test "$cf_required" = "$cf_require_pkg" + then + cf_required= + break + fi + done + test -n "$cf_required" && REQUIRE_PKG="$REQUIRE_PKG $cf_required" +done +AC_SUBST(REQUIRE_PKG) +])dnl +dnl --------------------------------------------------------------------------- dnl CF_RESTORE_XTRA_FLAGS version: 1 updated: 2020/01/11 16:47:45 dnl --------------------- dnl Restore flags saved in CF_SAVE_XTRA_FLAGS @@ -3983,7 +4182,7 @@ do done ])dnl dnl --------------------------------------------------------------------------- -dnl CF_SHARED_OPTS version: 111 updated: 2024/03/29 20:08:49 +dnl CF_SHARED_OPTS version: 114 updated: 2025/12/15 04:04:20 dnl -------------- dnl -------------- dnl Attempt to determine the appropriate CC/LD options for creating a shared @@ -4073,7 +4272,7 @@ AC_DEFUN([CF_SHARED_OPTS], for CC_SHARED_OPTS in -fPIC -fpic '' do CFLAGS="$cf_save_CFLAGS $CC_SHARED_OPTS" - AC_TRY_COMPILE([#include ],[int x = 1; (void)x],[break],[]) + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[int x = 1; (void)x])],[break],[]) done AC_MSG_RESULT($CC_SHARED_OPTS) CFLAGS="$cf_save_CFLAGS" @@ -4148,7 +4347,7 @@ CF_EOF AC_CACHE_CHECK([if ld -search_paths_first works], cf_cv_ldflags_search_paths_first, [ cf_save_LDFLAGS=$LDFLAGS LDFLAGS="$LDFLAGS -Wl,-search_paths_first" - AC_TRY_LINK(, [int i;], cf_cv_ldflags_search_paths_first=yes, cf_cv_ldflags_search_paths_first=no) + AC_LINK_IFELSE([AC_LANG_PROGRAM([], [int i;])], cf_cv_ldflags_search_paths_first=yes, cf_cv_ldflags_search_paths_first=no) LDFLAGS=$cf_save_LDFLAGS]) if test "$cf_cv_ldflags_search_paths_first" = yes; then LDFLAGS="$LDFLAGS -Wl,-search_paths_first" @@ -4278,7 +4477,7 @@ CF_EOF -L*) ldopts+=("\`echo \"\[$]1\" | sed \"s/^-L/-LIBPATH:/\"\`") ;; - *.obj | *.o) + *.obj | *.$OBJEXT) ldopts+=("\[$]1") ;; -Wl,*) @@ -4455,7 +4654,7 @@ CF_EOF for cf_shared_opts in -xcode=pic32 -xcode=pic13 -KPIC -Kpic -O do CFLAGS="$cf_shared_opts $cf_save_CFLAGS" - AC_TRY_COMPILE([#include ],[printf("Hello\\n");],[break]) + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[printf("Hello\\n");])],[break]) done CFLAGS="$cf_save_CFLAGS" CC_SHARED_OPTS=$cf_shared_opts @@ -4499,7 +4698,7 @@ cat > conftest.$ac_ext < +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include #include <${cf_cv_ncurses_header:-curses.h}> #include <$cf_test> -],[int x = auto_left_margin; (void)x],[ +],[int x = auto_left_margin; (void)x])],[ cf_cv_term_header="$cf_test"],[ cf_cv_term_header=unknown ]) @@ -4648,17 +4847,17 @@ top_builddir=ifelse($1,,`pwd`,$1) AC_SUBST(top_builddir) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_TRY_XOPEN_SOURCE version: 4 updated: 2022/09/10 15:16:16 +dnl CF_TRY_XOPEN_SOURCE version: 5 updated: 2025/12/14 17:40:20 dnl ------------------- dnl If _XOPEN_SOURCE is not defined in the compile environment, check if we dnl can define it successfully. AC_DEFUN([CF_TRY_XOPEN_SOURCE],[ AC_CACHE_CHECK(if we should define _XOPEN_SOURCE,cf_cv_xopen_source,[ - AC_TRY_COMPILE(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY, + AC_COMPILE_IFELSE([AC_LANG_PROGRAM(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY)], [cf_cv_xopen_source=no], [cf_save="$CPPFLAGS" CF_APPEND_TEXT(CPPFLAGS,-D_XOPEN_SOURCE=$cf_XOPEN_SOURCE) - AC_TRY_COMPILE(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY, + AC_COMPILE_IFELSE([AC_LANG_PROGRAM(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY)], [cf_cv_xopen_source=no], [cf_cv_xopen_source=$cf_XOPEN_SOURCE]) CPPFLAGS="$cf_save" @@ -4682,20 +4881,20 @@ AC_DEFUN([CF_UPPER], $1=`echo "$2" | sed y%abcdefghijklmnopqrstuvwxyz./-%ABCDEFGHIJKLMNOPQRSTUVWXYZ___%` ])dnl dnl --------------------------------------------------------------------------- -dnl CF_UTF8_LIB version: 10 updated: 2023/01/11 04:05:23 +dnl CF_UTF8_LIB version: 12 updated: 2025/12/22 04:16:14 dnl ----------- dnl Check for multibyte support, and if not found, utf8 compatibility library AC_DEFUN([CF_UTF8_LIB], [ -AC_HAVE_HEADERS(wchar.h) +AC_CHECK_HEADERS(wchar.h) AC_CACHE_CHECK(for multibyte character support,cf_cv_utf8_lib,[ cf_save_LIBS="$LIBS" - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default #ifdef HAVE_WCHAR_H #include #endif -],[putwc(0,0);], +],[putwc(0,0);])], [cf_cv_utf8_lib=yes], [CF_FIND_LINKAGE([ #include ],[putwc(0,0);],utf8, @@ -4713,22 +4912,22 @@ if test "$cf_cv_utf8_lib" = "add-on" ; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_VERBOSE version: 3 updated: 2007/07/29 09:55:12 +dnl CF_VERBOSE version: 4 updated: 2025/12/14 17:51:46 dnl ---------- dnl Use AC_VERBOSE w/o the warnings AC_DEFUN([CF_VERBOSE], -[test -n "$verbose" && echo " $1" 1>&AC_FD_MSG +[test -n "$verbose" && echo " $1" 1>&AS_MESSAGE_FD CF_MSG_LOG([$1]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WEAK_SYMBOLS version: 1 updated: 2008/08/16 19:18:06 +dnl CF_WEAK_SYMBOLS version: 2 updated: 2025/12/24 12:27:29 dnl --------------- dnl Check for compiler-support for weak symbols. dnl This works with "recent" gcc. AC_DEFUN([CF_WEAK_SYMBOLS],[ AC_CACHE_CHECK(if $CC supports weak symbols,cf_cv_weak_symbols,[ -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include ], [ #if defined(__GNUC__) @@ -4743,10 +4942,60 @@ AC_TRY_COMPILE([ #endif weak_symbol(fopen); -],[cf_cv_weak_symbols=yes],[cf_cv_weak_symbols=no]) +])],[cf_cv_weak_symbols=yes],[cf_cv_weak_symbols=no]) ]) ])dnl dnl --------------------------------------------------------------------------- +dnl CF_WITH_ADA version: 2 updated: 2024/11/09 18:07:29 +dnl ----------- +dnl Check for the Ada compiler (unless requested to not do this), which causes +dnl a further check for a C compiler which can work with the Ada compiler. +AC_DEFUN([CF_WITH_ADA],[ +AC_ARG_WITH(ada, + [ --without-ada suppress check for Ada compiler], + [cf_with_ada=$withval], + [cf_with_ada=yes]) + +cf_prog_cc="gcc cc" +if test "x$cf_with_ada" = xyes +then + CF_PROG_GNAT + if test "x$cf_cv_prog_gnat_correct" = xyes; then + # gcc's developers chose to deprecate gnatgcc before making gprconfig + # work. They replaced gnatgcc in gcc 13 with a script which spits out + # a warning offering advice which could never work. + # + # Here is a workaround. + AC_PATH_PROG(cf_cv_path_gnatgcc,gnatgcc,no) + if test "$cf_cv_path_gnatgcc" != no + then + AC_MSG_CHECKING(for improvement) + cf_file_gnatgcc=`file -L "$cf_cv_path_gnatgcc" 2>/dev/null` + case "x$cf_file_gnatgcc" in + (*script*) + cf_cv_path_gnatgcc=`sh -x "$cf_cv_path_gnatgcc" --version 2>&1 | grep -w exec | sed -e 's/^[[ ]]*+[[ ]]*//' -e 's/exec[[ ]]//' -e 's/ .*//'` + ;; + (*) + cf_cv_path_gnatgcc=no + ;; + esac + AC_MSG_RESULT($cf_cv_path_gnatgcc) + test "$cf_cv_path_gnatgcc" = no && cf_cv_path_gnatgcc=gnatgcc + cf_prog_cc="$cf_cv_path_gnatgcc $cf_prog_cc" + fi + fi +fi +case "$cf_prog_cc" in +(*/*) + CC="$cf_prog_cc" + AC_SUBST(CC) + ;; +(*) + CF_PROG_CC($cf_prog_cc) + ;; +esac +])dnl +dnl --------------------------------------------------------------------------- dnl CF_WITH_ADA_COMPILER version: 3 updated: 2023/10/28 11:59:01 dnl -------------------- dnl Command-line option to specify the Ada95 compiler. @@ -4924,7 +5173,7 @@ eval $3="$withval" AC_SUBST($3)dnl ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WITH_PKG_CONFIG_LIBDIR version: 23 updated: 2023/11/22 20:48:30 +dnl CF_WITH_PKG_CONFIG_LIBDIR version: 25 updated: 2024/08/03 13:34:29 dnl ------------------------- dnl Allow the choice of the pkg-config library directory to be overridden. dnl @@ -4938,6 +5187,7 @@ dnl pkgconf (used with some systems such as FreeBSD in place of pkg-config) dnl optionally ignores $PKG_CONFIG_LIBDIR. Very old versions of pkg-config, dnl e.g., Solaris 10 also do not recognize $PKG_CONFIG_LIBDIR. AC_DEFUN([CF_WITH_PKG_CONFIG_LIBDIR],[ +AC_REQUIRE([CF_GLOB_FULLPATH])dnl case "$PKG_CONFIG" in (no|none|yes) @@ -4971,10 +5221,10 @@ case "x$cf_search_path" in ;; (x) ;; -(x/*\ *) +(x$GLOB_FULLPATH_POSIX\ *|x$GLOB_FULLPATH_OTHER\ *) PKG_CONFIG_LIBDIR= ;; -(x/*) +(x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) PKG_CONFIG_LIBDIR="$cf_search_path" AC_MSG_RESULT($PKG_CONFIG_LIBDIR) cf_search_path= @@ -4993,7 +5243,15 @@ case "x$cf_search_path" in pkg-config \ pkgconf do - cf_search_path=`"$PKG_CONFIG" --variable=pc_path "$cf_pkg_program" 2>/dev/null | tr : ' '` + cf_raw_search_path=`"$PKG_CONFIG" --variable=pc_path "$cf_pkg_program" 2>/dev/null` + case "$cf_raw_search_path" in + (*\\*) + cf_search_path=`echo "$cf_raw_search_path" | tr ';' ' ' | tr '\' '/'` + ;; + (*/*) + cf_search_path=`echo "$cf_raw_search_path" | tr : ' '` + ;; + esac test -n "$cf_search_path" && break done @@ -5066,7 +5324,7 @@ fi AC_SUBST(PKG_CONFIG_LIBDIR) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WITH_PTHREAD version: 7 updated: 2015/04/18 08:56:57 +dnl CF_WITH_PTHREAD version: 8 updated: 2025/12/24 12:27:29 dnl --------------- dnl Check for POSIX thread library. AC_DEFUN([CF_WITH_PTHREAD], @@ -5087,12 +5345,12 @@ if test "$with_pthread" != no ; then AC_MSG_CHECKING(if we can link with the $cf_lib_pthread library) cf_save_LIBS="$LIBS" CF_ADD_LIB($cf_lib_pthread) - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ int rc = pthread_create(0,0,0,0); int r2 = pthread_mutexattr_settype(0, 0); -],[with_pthread=yes],[with_pthread=no]) +])],[with_pthread=yes],[with_pthread=no]) LIBS="$cf_save_LIBS" AC_MSG_RESULT($with_pthread) test "$with_pthread" = yes && break @@ -5108,7 +5366,7 @@ if test "$with_pthread" != no ; then fi ]) dnl --------------------------------------------------------------------------- -dnl CF_WITH_SYSTYPE version: 1 updated: 2013/01/26 16:26:12 +dnl CF_WITH_SYSTYPE version: 2 updated: 2025/12/14 18:08:20 dnl --------------- dnl For testing, override the derived host system-type which is used to decide dnl things such as the linker commands used to build shared libraries. This is @@ -5119,7 +5377,7 @@ dnl This is different from the --host option: it is used only for testing parts dnl of the configure script which would not be reachable with --host since that dnl relies on the build environment being real, rather than mocked up. AC_DEFUN([CF_WITH_SYSTYPE],[ -CF_CHECK_CACHE([AC_CANONICAL_SYSTEM]) +CF_CHECK_CACHE([AC_CANONICAL_TARGET]) AC_ARG_WITH(system-type, [ --with-system-type=XXX test: override derived host system-type], [AC_MSG_WARN(overriding system type to $withval) @@ -5128,7 +5386,7 @@ AC_ARG_WITH(system-type, ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_XOPEN_SOURCE version: 67 updated: 2023/09/06 18:55:27 +dnl CF_XOPEN_SOURCE version: 71 updated: 2025/12/14 17:40:20 dnl --------------- dnl Try to get _XOPEN_SOURCE defined properly that we can use POSIX functions, dnl or adapt to the vendor's definitions to get equivalent functionality, @@ -5188,9 +5446,12 @@ case "$host_os" in cf_xopen_source="-D_SGI_SOURCE" cf_XOPEN_SOURCE= ;; -(linux*gnu|linux*gnuabi64|linux*gnuabin32|linux*gnueabi|linux*gnueabihf|linux*gnux32|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) +(linux*gnu*|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) CF_GNU_SOURCE($cf_XOPEN_SOURCE) ;; +linux*musl) + cf_xopen_source="-D_BSD_SOURCE" + ;; (minix*) cf_xopen_source="-D_NETBSD_SOURCE" # POSIX.1-2001 features are ifdef'd with this... ;; @@ -5242,7 +5503,7 @@ case "$host_os" in # Some of these niche implementations use copy/paste, double-check... if test "$cf_cv_xopen_source" = no ; then CF_VERBOSE(checking if _POSIX_C_SOURCE interferes with _XOPEN_SOURCE) - AC_TRY_COMPILE(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY,,[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY)],,[ AC_MSG_WARN(_POSIX_C_SOURCE definition is not usable) CPPFLAGS="$cf_save_xopen_cppflags"]) fi @@ -5258,19 +5519,19 @@ dnl which is still not guaranteed to provide all of the entrypoints that dnl _XOPEN_SOURCE would yield. if test -n "$cf_XOPEN_SOURCE" && test -z "$cf_cv_xopen_source" ; then AC_MSG_CHECKING(if _XOPEN_SOURCE really is set) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef _XOPEN_SOURCE #error _XOPEN_SOURCE is not defined -#endif], +#endif])], [cf_XOPEN_SOURCE_set=yes], [cf_XOPEN_SOURCE_set=no]) AC_MSG_RESULT($cf_XOPEN_SOURCE_set) if test "$cf_XOPEN_SOURCE_set" = yes then - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if (_XOPEN_SOURCE - 0) < $cf_XOPEN_SOURCE #error (_XOPEN_SOURCE - 0) < $cf_XOPEN_SOURCE -#endif], +#endif])], [cf_XOPEN_SOURCE_set_ok=yes], [cf_XOPEN_SOURCE_set_ok=no]) if test "$cf_XOPEN_SOURCE_set_ok" = no diff --git a/Ada95/configure b/Ada95/configure index 8c01a29..0b12053 100755 --- a/Ada95/configure +++ b/Ada95/configure @@ -1,7 +1,7 @@ #! /bin/sh -# From configure.in Revision: 1.91 . +# From configure.in Revision: 1.97 . # Guess values for system-dependent variables and create Makefiles. -# Generated by Autoconf 2.52.20231210. +# Generated by Autoconf 2.52.20250126. # # Copyright 2003-2022,2023 Thomas E. Dickey # Copyright 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001 @@ -481,6 +481,10 @@ do | --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*) x_libraries=$ac_optarg ;; + -*dir | -dvi* | -doc* | -html* | -local* | -pdf* | -ps* ) + echo "$as_me: WARNING: unsupported option: $ac_option" >&2 + ;; + -*) { echo "$as_me: error: unrecognized option: $ac_option Try \`$0 --help' for more information." >&2 { (exit 1); exit 1; }; } @@ -703,13 +707,15 @@ Optional Features: General Options: --with-system-type=XXX test: override derived host system-type + --without-ada suppress check for Ada compiler --disable-stripping do not strip (debug info) installed executables --with-strip-program=XX specify program to use when stripping in install --with-pkg-config[=CMD] enable/disable use of pkg-config and its name CMD --with-pkg-config-libdir[=XXX] use given directory for installing pc-files --without-tests suppress build with test-programs --enable-mixed-case tic should assume mixed-case filenames - --with-install-prefix prefixes actual install-location ($DESTDIR) + --with-install-prefix=DESTDIR use DESTDIR as installation directory prefix + --enable-install-prefix merge DESTDIR with installation prefix Build-Tools Needed to Compile Temporary Applications for Cross-compiling: --with-build-cc=XXX the build C compiler ($BUILD_CC) --with-build-cpp=XXX the build C preprocessor ($BUILD_CPP) @@ -720,7 +726,7 @@ Build-Tools Needed to Compile Temporary Applications for Cross-compiling: Options to Specify the Libraries Built/Used: --with-shared generate shared C-objects (needed for --with-ada-sharedlib) --with-curses-dir=DIR directory in which (n)curses is installed - --enable-widec compile with wide-char/UTF-8 code + --with-screen=XXX use specified curses-libraries --with-lib-prefix override library-prefix --with-shlib-version[={rel|abi}] use release or ABI version in shared library file names --enable-rpath-link link sample programs with rpath option @@ -823,7 +829,7 @@ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by $as_me, which was -generated by GNU Autoconf 2.52.20231210. Invocation command line was +generated by GNU Autoconf 2.52.20250126. Invocation command line was $ $0 $@ @@ -947,7 +953,7 @@ if test -z "$CONFIG_SITE"; then fi for ac_site_file in $CONFIG_SITE; do if test -r "$ac_site_file"; then - { echo "$as_me:950: loading site script $ac_site_file" >&5 + { echo "$as_me:956: loading site script $ac_site_file" >&5 echo "$as_me: loading site script $ac_site_file" >&6;} cat "$ac_site_file" >&5 . "$ac_site_file" @@ -958,7 +964,7 @@ if test -r "$cache_file"; then # Some versions of bash will fail to source /dev/null (special # files actually), so we avoid doing that. if test -f "$cache_file"; then - { echo "$as_me:961: loading cache $cache_file" >&5 + { echo "$as_me:967: loading cache $cache_file" >&5 echo "$as_me: loading cache $cache_file" >&6;} case $cache_file in [\\/]* | ?:[\\/]* ) . $cache_file;; @@ -966,7 +972,7 @@ echo "$as_me: loading cache $cache_file" >&6;} esac fi else - { echo "$as_me:969: creating cache $cache_file" >&5 + { echo "$as_me:975: creating cache $cache_file" >&5 echo "$as_me: creating cache $cache_file" >&6;} >$cache_file fi @@ -982,21 +988,21 @@ for ac_var in `(set) 2>&1 | eval ac_new_val="\$ac_env_${ac_var}_value" case "$ac_old_set,$ac_new_set" in set,) - { echo "$as_me:985: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 + { echo "$as_me:991: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5 echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;} ac_cache_corrupted=: ;; ,set) - { echo "$as_me:989: error: \`$ac_var' was not set in the previous run" >&5 + { echo "$as_me:995: error: \`$ac_var' was not set in the previous run" >&5 echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;} ac_cache_corrupted=: ;; ,);; *) if test "x$ac_old_val" != "x$ac_new_val"; then - { echo "$as_me:995: error: \`$ac_var' has changed since the previous run:" >&5 + { echo "$as_me:1001: error: \`$ac_var' has changed since the previous run:" >&5 echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;} - { echo "$as_me:997: former value: $ac_old_val" >&5 + { echo "$as_me:1003: former value: $ac_old_val" >&5 echo "$as_me: former value: $ac_old_val" >&2;} - { echo "$as_me:999: current value: $ac_new_val" >&5 + { echo "$as_me:1005: current value: $ac_new_val" >&5 echo "$as_me: current value: $ac_new_val" >&2;} ac_cache_corrupted=: fi;; @@ -1015,9 +1021,9 @@ echo "$as_me: current value: $ac_new_val" >&2;} fi done if "$ac_cache_corrupted"; then - { echo "$as_me:1018: error: changes in the environment can compromise the build" >&5 + { echo "$as_me:1024: error: changes in the environment can compromise the build" >&5 echo "$as_me: error: changes in the environment can compromise the build" >&2;} - { { echo "$as_me:1020: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&5 + { { echo "$as_me:1026: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&5 echo "$as_me: error: run \`make distclean' and/or \`rm $cache_file' and start over" >&2;} { (exit 1); exit 1; }; } fi @@ -1046,10 +1052,10 @@ esac echo "#! $SHELL" >conftest.sh echo "exit 0" >>conftest.sh chmod +x conftest.sh -if { (echo "$as_me:1049: PATH=\".;.\"; conftest.sh") >&5 +if { (echo "$as_me:1055: PATH=\".;.\"; conftest.sh") >&5 (PATH=".;."; conftest.sh) 2>&5 ac_status=$? - echo "$as_me:1052: \$? = $ac_status" >&5 + echo "$as_me:1058: \$? = $ac_status" >&5 (exit "$ac_status"); }; then ac_path_separator=';' else @@ -1081,7 +1087,7 @@ for ac_dir in $srcdir $srcdir/.. $srcdir/../..; do fi done if test -z "$ac_aux_dir"; then - { { echo "$as_me:1084: error: cannot find install-sh or install.sh in $srcdir $srcdir/.. $srcdir/../.." >&5 + { { echo "$as_me:1090: error: cannot find install-sh or install.sh in $srcdir $srcdir/.. $srcdir/../.." >&5 echo "$as_me: error: cannot find install-sh or install.sh in $srcdir $srcdir/.. $srcdir/../.." >&2;} { (exit 1); exit 1; }; } fi @@ -1091,11 +1097,11 @@ ac_configure="$SHELL $ac_aux_dir/configure" # This should be Cygnus configure. # Make sure we can run config.sub. $ac_config_sub sun4 >/dev/null 2>&1 || - { { echo "$as_me:1094: error: cannot run $ac_config_sub" >&5 + { { echo "$as_me:1100: error: cannot run $ac_config_sub" >&5 echo "$as_me: error: cannot run $ac_config_sub" >&2;} { (exit 1); exit 1; }; } -echo "$as_me:1098: checking build system type" >&5 +echo "$as_me:1104: checking build system type" >&5 echo $ECHO_N "checking build system type... $ECHO_C" >&6 if test "${ac_cv_build+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -1104,23 +1110,23 @@ else test -z "$ac_cv_build_alias" && ac_cv_build_alias=`$ac_config_guess` test -z "$ac_cv_build_alias" && - { { echo "$as_me:1107: error: cannot guess build type; you must specify one" >&5 + { { echo "$as_me:1113: error: cannot guess build type; you must specify one" >&5 echo "$as_me: error: cannot guess build type; you must specify one" >&2;} { (exit 1); exit 1; }; } ac_cv_build=`$ac_config_sub "$ac_cv_build_alias"` || - { { echo "$as_me:1111: error: $ac_config_sub $ac_cv_build_alias failed." >&5 + { { echo "$as_me:1117: error: $ac_config_sub $ac_cv_build_alias failed." >&5 echo "$as_me: error: $ac_config_sub $ac_cv_build_alias failed." >&2;} { (exit 1); exit 1; }; } fi -echo "$as_me:1116: result: $ac_cv_build" >&5 +echo "$as_me:1122: result: $ac_cv_build" >&5 echo "${ECHO_T}$ac_cv_build" >&6 build=$ac_cv_build build_cpu=`echo "$ac_cv_build" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'` build_vendor=`echo "$ac_cv_build" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\2/'` build_os=`echo "$ac_cv_build" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\3/'` -echo "$as_me:1123: checking host system type" >&5 +echo "$as_me:1129: checking host system type" >&5 echo $ECHO_N "checking host system type... $ECHO_C" >&6 if test "${ac_cv_host+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -1129,12 +1135,12 @@ else test -z "$ac_cv_host_alias" && ac_cv_host_alias=$ac_cv_build_alias ac_cv_host=`$ac_config_sub "$ac_cv_host_alias"` || - { { echo "$as_me:1132: error: $ac_config_sub $ac_cv_host_alias failed" >&5 + { { echo "$as_me:1138: error: $ac_config_sub $ac_cv_host_alias failed" >&5 echo "$as_me: error: $ac_config_sub $ac_cv_host_alias failed" >&2;} { (exit 1); exit 1; }; } fi -echo "$as_me:1137: result: $ac_cv_host" >&5 +echo "$as_me:1143: result: $ac_cv_host" >&5 echo "${ECHO_T}$ac_cv_host" >&6 host=$ac_cv_host host_cpu=`echo "$ac_cv_host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'` @@ -1142,7 +1148,7 @@ host_vendor=`echo "$ac_cv_host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\2/'` host_os=`echo "$ac_cv_host" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\3/'` if test -f "$srcdir/config.guess" || test -f "$ac_aux_dir/config.guess" ; then - echo "$as_me:1145: checking target system type" >&5 + echo "$as_me:1151: checking target system type" >&5 echo $ECHO_N "checking target system type... $ECHO_C" >&6 if test "${ac_cv_target+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -1151,12 +1157,12 @@ else test "x$ac_cv_target_alias" = "x" && ac_cv_target_alias=$ac_cv_host_alias ac_cv_target=`$ac_config_sub "$ac_cv_target_alias"` || - { { echo "$as_me:1154: error: $ac_config_sub $ac_cv_target_alias failed" >&5 + { { echo "$as_me:1160: error: $ac_config_sub $ac_cv_target_alias failed" >&5 echo "$as_me: error: $ac_config_sub $ac_cv_target_alias failed" >&2;} { (exit 1); exit 1; }; } fi -echo "$as_me:1159: result: $ac_cv_target" >&5 +echo "$as_me:1165: result: $ac_cv_target" >&5 echo "${ECHO_T}$ac_cv_target" >&6 target=$ac_cv_target target_cpu=`echo "$ac_cv_target" | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'` @@ -1188,13 +1194,13 @@ else fi test -z "$system_name" && system_name="$cf_cv_system_name" -test -n "$cf_cv_system_name" && echo "$as_me:1191: result: Configuring for $cf_cv_system_name" >&5 +test -n "$cf_cv_system_name" && echo "$as_me:1197: result: Configuring for $cf_cv_system_name" >&5 echo "${ECHO_T}Configuring for $cf_cv_system_name" >&6 if test ".$system_name" != ".$cf_cv_system_name" ; then - echo "$as_me:1195: result: Cached system name ($system_name) does not agree with actual ($cf_cv_system_name)" >&5 + echo "$as_me:1201: result: Cached system name ($system_name) does not agree with actual ($cf_cv_system_name)" >&5 echo "${ECHO_T}Cached system name ($system_name) does not agree with actual ($cf_cv_system_name)" >&6 - { { echo "$as_me:1197: error: \"Please remove config.cache and try again.\"" >&5 + { { echo "$as_me:1203: error: \"Please remove config.cache and try again.\"" >&5 echo "$as_me: error: \"Please remove config.cache and try again.\"" >&2;} { (exit 1); exit 1; }; } fi @@ -1202,7 +1208,7 @@ fi # Check whether --with-system-type or --without-system-type was given. if test "${with_system_type+set}" = set; then withval="$with_system_type" - { echo "$as_me:1205: WARNING: overriding system type to $withval" >&5 + { echo "$as_me:1211: WARNING: overriding system type to $withval" >&5 echo "$as_me: WARNING: overriding system type to $withval" >&2;} cf_cv_system_name=$withval host_os=$withval @@ -1217,7 +1223,7 @@ for ac_prog in ggrep grep do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:1220: checking for $ac_word" >&5 +echo "$as_me:1226: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_GREP+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -1232,7 +1238,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_GREP="$ac_prog" -echo "$as_me:1235: found $ac_dir/$ac_word" >&5 +echo "$as_me:1241: found $ac_dir/$ac_word" >&5 break done @@ -1240,10 +1246,10 @@ fi fi GREP=$ac_cv_prog_GREP if test -n "$GREP"; then - echo "$as_me:1243: result: $GREP" >&5 + echo "$as_me:1249: result: $GREP" >&5 echo "${ECHO_T}$GREP" >&6 else - echo "$as_me:1246: result: no" >&5 + echo "$as_me:1252: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -1251,7 +1257,7 @@ fi done test -n "$GREP" || GREP=": " -echo "$as_me:1254: checking for fgrep" >&5 +echo "$as_me:1260: checking for fgrep" >&5 echo $ECHO_N "checking for fgrep... $ECHO_C" >&6 if test "${ac_cv_path_FGREP+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -1263,7 +1269,7 @@ else do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:1266: checking for $ac_word" >&5 +echo "$as_me:1272: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_path_FGREP+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -1280,7 +1286,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. if $as_executable_p "$ac_dir/$ac_word"; then ac_cv_path_FGREP="$ac_dir/$ac_word" - echo "$as_me:1283: found $ac_dir/$ac_word" >&5 + echo "$as_me:1289: found $ac_dir/$ac_word" >&5 break fi done @@ -1291,10 +1297,10 @@ fi FGREP=$ac_cv_path_FGREP if test -n "$FGREP"; then - echo "$as_me:1294: result: $FGREP" >&5 + echo "$as_me:1300: result: $FGREP" >&5 echo "${ECHO_T}$FGREP" >&6 else - echo "$as_me:1297: result: no" >&5 + echo "$as_me:1303: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -1302,16 +1308,16 @@ fi done test -n "$FGREP" || FGREP=": " - test "x$ac_cv_path_FGREP" = "x:" && { { echo "$as_me:1305: error: cannot find workable fgrep" >&5 + test "x$ac_cv_path_FGREP" = "x:" && { { echo "$as_me:1311: error: cannot find workable fgrep" >&5 echo "$as_me: error: cannot find workable fgrep" >&2;} { (exit 1); exit 1; }; } fi fi -echo "$as_me:1310: result: $ac_cv_path_FGREP" >&5 +echo "$as_me:1316: result: $ac_cv_path_FGREP" >&5 echo "${ECHO_T}$ac_cv_path_FGREP" >&6 FGREP="$ac_cv_path_FGREP" -echo "$as_me:1314: checking for prefix" >&5 +echo "$as_me:1320: checking for prefix" >&5 echo $ECHO_N "checking for prefix... $ECHO_C" >&6 if test "x$prefix" = "xNONE" ; then case "$cf_cv_system_name" in @@ -1323,11 +1329,11 @@ if test "x$prefix" = "xNONE" ; then ;; esac fi -echo "$as_me:1326: result: $prefix" >&5 +echo "$as_me:1332: result: $prefix" >&5 echo "${ECHO_T}$prefix" >&6 if test "x$prefix" = "xNONE" ; then -echo "$as_me:1330: checking for default include-directory" >&5 +echo "$as_me:1336: checking for default include-directory" >&5 echo $ECHO_N "checking for default include-directory... $ECHO_C" >&6 test -n "$verbose" && echo 1>&6 for cf_symbol in \ @@ -1350,12 +1356,322 @@ do fi test -n "$verbose" && echo " tested $cf_dir" 1>&6 done -echo "$as_me:1353: result: $includedir" >&5 +echo "$as_me:1359: result: $includedir" >&5 echo "${ECHO_T}$includedir" >&6 fi ### Checks for programs. +# Check whether --with-ada or --without-ada was given. +if test "${with_ada+set}" = set; then + withval="$with_ada" + cf_with_ada=$withval +else + cf_with_ada=yes +fi; + +cf_prog_cc="gcc cc" +if test "x$cf_with_ada" = xyes +then + +for cf_prog_gnat in gnat gnatmake gprconfig gprbuild +do + +cf_upper_prog_gnat=`echo "${cf_prog_gnat}" | sed y%abcdefghijklmnopqrstuvwxyz./-%ABCDEFGHIJKLMNOPQRSTUVWXYZ___%` + + unset ac_cv_path_cf_TEMP_gnat + unset cf_TEMP_gnat + # Extract the first word of "$cf_prog_gnat", so it can be a program name with args. +set dummy $cf_prog_gnat; ac_word=$2 +echo "$as_me:1386: checking for $ac_word" >&5 +echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 +if test "${ac_cv_path_cf_TEMP_gnat+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + case $cf_TEMP_gnat in + [\\/]* | ?:[\\/]*) + ac_cv_path_cf_TEMP_gnat="$cf_TEMP_gnat" # Let the user override the test with a path. + ;; + *) + ac_save_IFS=$IFS; IFS=$ac_path_separator +ac_dummy="$PATH" +for ac_dir in $ac_dummy; do + IFS=$ac_save_IFS + test -z "$ac_dir" && ac_dir=. + if $as_executable_p "$ac_dir/$ac_word"; then + ac_cv_path_cf_TEMP_gnat="$ac_dir/$ac_word" + echo "$as_me:1403: found $ac_dir/$ac_word" >&5 + break +fi +done + + test -z "$ac_cv_path_cf_TEMP_gnat" && ac_cv_path_cf_TEMP_gnat="no" + ;; +esac +fi +cf_TEMP_gnat=$ac_cv_path_cf_TEMP_gnat + +if test -n "$cf_TEMP_gnat"; then + echo "$as_me:1415: result: $cf_TEMP_gnat" >&5 +echo "${ECHO_T}$cf_TEMP_gnat" >&6 +else + echo "$as_me:1418: result: no" >&5 +echo "${ECHO_T}no" >&6 +fi + + eval "cf_cv_PATH_$cf_upper_prog_gnat=$ac_cv_path_cf_TEMP_gnat" + + if test "x$cf_TEMP_gnat" != xno; then + unset cf_cv_gnat_version + unset cf_TEMP_gnat + +echo "$as_me:1428: checking for $cf_prog_gnat version" >&5 +echo $ECHO_N "checking for $cf_prog_gnat version... $ECHO_C" >&6 +if test "${cf_cv_gnat_version+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + +cf_cv_gnat_version=`$cf_prog_gnat --version 2>&1 | \ + grep '[0-9].[0-9][0-9]*' |\ + sed -e '2,$d' -e 's/[^0-9 \.]//g' -e 's/^[ ]*//' -e 's/ .*//'` + +fi +echo "$as_me:1439: result: $cf_cv_gnat_version" >&5 +echo "${ECHO_T}$cf_cv_gnat_version" >&6 +test -z "$cf_cv_gnat_version" && cf_cv_gnat_version=no +eval cf_TEMP_gnat=$cf_cv_gnat_version; unset cf_cv_gnat_version + + fi + eval "cf_cv_VERSION_$cf_upper_prog_gnat=$cf_TEMP_gnat" + + unset cf_TEMP_gnat + unset cf_cv_gnat_version + unset ac_cv_path_cf_TEMP_gnat +done + +if test "x$cf_cv_VERSION_GNATMAKE" = "xno"; then + cf_ada_make= + cf_cv_prog_gnat_correct=no +else + cf_ada_make=gnatmake + if test "x$cf_cv_VERSION_GPRCONFIG" = "xno"; then + # gprconfig is newer than gnatmake; we can continue... + cf_ada_config="##" + else + rm -rf ./conftest* ./*~conftest* + if mkdir conftest.src + then + cf_ada_config="" + cd conftest.src + for cf_gprconfig in Ada C + do + echo "$as_me:1468: checking for gprconfig name for $cf_gprconfig" >&5 +echo $ECHO_N "checking for gprconfig name for $cf_gprconfig... $ECHO_C" >&6 + if test "$cf_gprconfig" = C + then + for cf_gprconfig_param in \ + "$cf_gprconfig,,,,GNATGCC" \ + "$cf_gprconfig,,,,GCC" \ + "$cf_gprconfig" + do + cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&5 | ${AWK:-awk} '/^\*/{print $3;}' | head -n 1` + test -n "$cf_gprconfig_value" && break + done + else + cf_gprconfig_param=$cf_gprconfig + cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&5 | ${AWK:-awk} '/^\*/{print $3;}' | head -n 1` + fi + if test -n "$cf_gprconfig_value" + then + eval "cf_ada_config_$cf_gprconfig=$cf_gprconfig_value" + echo "$as_me:1487: result: $cf_gprconfig_value" >&5 +echo "${ECHO_T}$cf_gprconfig_value" >&6 + else + echo "$as_me:1490: result: missing" >&5 +echo "${ECHO_T}missing" >&6 + cf_ada_config="#" + break + fi + done + cd .. + rm -rf ./conftest* ./*~conftest* + fi + fi + if test "x$cf_ada_config" != "x#" + then + +echo "$as_me:1503: checking for gnat version" >&5 +echo $ECHO_N "checking for gnat version... $ECHO_C" >&6 +if test "${cf_cv_gnat_version+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + +cf_cv_gnat_version=`${cf_ada_make:-gnatmake} --version 2>&1 | \ + grep '[0-9].[0-9][0-9]*' |\ + sed -e '2,$d' -e 's/[^0-9 \.]//g' -e 's/^[ ]*//' -e 's/ .*//'` + +fi +echo "$as_me:1514: result: $cf_cv_gnat_version" >&5 +echo "${ECHO_T}$cf_cv_gnat_version" >&6 +test -z "$cf_cv_gnat_version" && cf_cv_gnat_version=no + +case "$cf_cv_gnat_version" in +(3.1[1-9]*|3.[2-9]*|[4-9].*|[1-9][0-9].[0-9]*|20[0-9][0-9]) + cf_cv_prog_gnat_correct=yes + ;; +(*) + { echo "$as_me:1523: WARNING: Unsupported GNAT version $cf_cv_gnat_version. We require 3.11 or better. Disabling Ada95 binding." >&5 +echo "$as_me: WARNING: Unsupported GNAT version $cf_cv_gnat_version. We require 3.11 or better. Disabling Ada95 binding." >&2;} + cf_cv_prog_gnat_correct=no + ;; +esac + + # Extract the first word of "m4", so it can be a program name with args. +set dummy m4; ac_word=$2 +echo "$as_me:1531: checking for $ac_word" >&5 +echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 +if test "${ac_cv_prog_M4_exists+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + if test -n "$M4_exists"; then + ac_cv_prog_M4_exists="$M4_exists" # Let the user override the test. +else + ac_save_IFS=$IFS; IFS=$ac_path_separator +ac_dummy="$PATH" +for ac_dir in $ac_dummy; do + IFS=$ac_save_IFS + test -z "$ac_dir" && ac_dir=. + $as_executable_p "$ac_dir/$ac_word" || continue +ac_cv_prog_M4_exists="yes" +echo "$as_me:1546: found $ac_dir/$ac_word" >&5 +break +done + + test -z "$ac_cv_prog_M4_exists" && ac_cv_prog_M4_exists="no" +fi +fi +M4_exists=$ac_cv_prog_M4_exists +if test -n "$M4_exists"; then + echo "$as_me:1555: result: $M4_exists" >&5 +echo "${ECHO_T}$M4_exists" >&6 +else + echo "$as_me:1558: result: no" >&5 +echo "${ECHO_T}no" >&6 +fi + + if test "$ac_cv_prog_M4_exists" = no; then + cf_cv_prog_gnat_correct=no + { echo "$as_me:1564: WARNING: Ada95 binding required program m4 not found. Ada95 binding disabled" >&5 +echo "$as_me: WARNING: Ada95 binding required program m4 not found. Ada95 binding disabled" >&2;} + fi + if test "$cf_cv_prog_gnat_correct" = yes; then + echo "$as_me:1568: checking if GNAT works" >&5 +echo $ECHO_N "checking if GNAT works... $ECHO_C" >&6 + +rm -rf ./conftest* ./*~conftest* +cat >>conftest.ads <>conftest.adb <&5 2>&1 ) ; then + if ( ./conftest 1>&5 2>&1 ) ; then + cf_cv_prog_gnat_correct=yes + else + cf_cv_prog_gnat_correct=no + fi +else + cf_cv_prog_gnat_correct=no +fi +rm -rf ./conftest* ./*~conftest* + + echo "$as_me:1596: result: $cf_cv_prog_gnat_correct" >&5 +echo "${ECHO_T}$cf_cv_prog_gnat_correct" >&6 + fi + else + cf_cv_prog_gnat_correct=no + fi +fi + + if test "x$cf_cv_prog_gnat_correct" = xyes; then + # gcc's developers chose to deprecate gnatgcc before making gprconfig + # work. They replaced gnatgcc in gcc 13 with a script which spits out + # a warning offering advice which could never work. + # + # Here is a workaround. + # Extract the first word of "gnatgcc", so it can be a program name with args. +set dummy gnatgcc; ac_word=$2 +echo "$as_me:1612: checking for $ac_word" >&5 +echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 +if test "${ac_cv_path_cf_cv_path_gnatgcc+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + case $cf_cv_path_gnatgcc in + [\\/]* | ?:[\\/]*) + ac_cv_path_cf_cv_path_gnatgcc="$cf_cv_path_gnatgcc" # Let the user override the test with a path. + ;; + *) + ac_save_IFS=$IFS; IFS=$ac_path_separator +ac_dummy="$PATH" +for ac_dir in $ac_dummy; do + IFS=$ac_save_IFS + test -z "$ac_dir" && ac_dir=. + if $as_executable_p "$ac_dir/$ac_word"; then + ac_cv_path_cf_cv_path_gnatgcc="$ac_dir/$ac_word" + echo "$as_me:1629: found $ac_dir/$ac_word" >&5 + break +fi +done + + test -z "$ac_cv_path_cf_cv_path_gnatgcc" && ac_cv_path_cf_cv_path_gnatgcc="no" + ;; +esac +fi +cf_cv_path_gnatgcc=$ac_cv_path_cf_cv_path_gnatgcc + +if test -n "$cf_cv_path_gnatgcc"; then + echo "$as_me:1641: result: $cf_cv_path_gnatgcc" >&5 +echo "${ECHO_T}$cf_cv_path_gnatgcc" >&6 +else + echo "$as_me:1644: result: no" >&5 +echo "${ECHO_T}no" >&6 +fi + + if test "$cf_cv_path_gnatgcc" != no + then + echo "$as_me:1650: checking for improvement" >&5 +echo $ECHO_N "checking for improvement... $ECHO_C" >&6 + cf_file_gnatgcc=`file -L "$cf_cv_path_gnatgcc" 2>/dev/null` + case "x$cf_file_gnatgcc" in + (*script*) + cf_cv_path_gnatgcc=`sh -x "$cf_cv_path_gnatgcc" --version 2>&1 | grep -w exec | sed -e 's/^[ ]*+[ ]*//' -e 's/exec[ ]//' -e 's/ .*//'` + ;; + (*) + cf_cv_path_gnatgcc=no + ;; + esac + echo "$as_me:1661: result: $cf_cv_path_gnatgcc" >&5 +echo "${ECHO_T}$cf_cv_path_gnatgcc" >&6 + test "$cf_cv_path_gnatgcc" = no && cf_cv_path_gnatgcc=gnatgcc + cf_prog_cc="$cf_cv_path_gnatgcc $cf_prog_cc" + fi + fi +fi +case "$cf_prog_cc" in +(*/*) + CC="$cf_prog_cc" + + ;; +(*) + ac_ext=c ac_cpp='$CPP $CPPFLAGS' ac_compile='$CC -c $CFLAGS $CPPFLAGS "conftest.$ac_ext" >&5' @@ -1363,11 +1679,11 @@ ac_link='$CC -o "conftest$ac_exeext" $CFLAGS $CPPFLAGS $LDFLAGS "conftest.$ac_ex ac_compiler_gnu=$ac_cv_c_compiler_gnu ac_main_return="return" if test -n "$ac_tool_prefix"; then - for ac_prog in gnatgcc gcc cc + for ac_prog in $cf_prog_cc do # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. set dummy $ac_tool_prefix$ac_prog; ac_word=$2 -echo "$as_me:1370: checking for $ac_word" >&5 +echo "$as_me:1686: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_CC+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -1382,7 +1698,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_CC="$ac_tool_prefix$ac_prog" -echo "$as_me:1385: found $ac_dir/$ac_word" >&5 +echo "$as_me:1701: found $ac_dir/$ac_word" >&5 break done @@ -1390,10 +1706,10 @@ fi fi CC=$ac_cv_prog_CC if test -n "$CC"; then - echo "$as_me:1393: result: $CC" >&5 + echo "$as_me:1709: result: $CC" >&5 echo "${ECHO_T}$CC" >&6 else - echo "$as_me:1396: result: no" >&5 + echo "$as_me:1712: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -1402,11 +1718,11 @@ fi fi if test -z "$CC"; then ac_ct_CC=$CC - for ac_prog in gnatgcc gcc cc + for ac_prog in $cf_prog_cc do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:1409: checking for $ac_word" >&5 +echo "$as_me:1725: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_ac_ct_CC+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -1421,7 +1737,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_ac_ct_CC="$ac_prog" -echo "$as_me:1424: found $ac_dir/$ac_word" >&5 +echo "$as_me:1740: found $ac_dir/$ac_word" >&5 break done @@ -1429,10 +1745,10 @@ fi fi ac_ct_CC=$ac_cv_prog_ac_ct_CC if test -n "$ac_ct_CC"; then - echo "$as_me:1432: result: $ac_ct_CC" >&5 + echo "$as_me:1748: result: $ac_ct_CC" >&5 echo "${ECHO_T}$ac_ct_CC" >&6 else - echo "$as_me:1435: result: no" >&5 + echo "$as_me:1751: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -1442,32 +1758,32 @@ done CC=$ac_ct_CC fi -test -z "$CC" && { { echo "$as_me:1445: error: no acceptable cc found in \$PATH" >&5 +test -z "$CC" && { { echo "$as_me:1761: error: no acceptable cc found in \$PATH" >&5 echo "$as_me: error: no acceptable cc found in \$PATH" >&2;} { (exit 1); exit 1; }; } # Provide some information about the compiler. -echo "$as_me:1450:" \ +echo "$as_me:1766:" \ "checking for C compiler version" >&5 ac_compiler=`set X $ac_compile; echo "$2"` -{ (eval echo "$as_me:1453: \"$ac_compiler --version &5\"") >&5 +{ (eval echo "$as_me:1769: \"$ac_compiler --version &5\"") >&5 (eval $ac_compiler --version &5) 2>&5 ac_status=$? - echo "$as_me:1456: \$? = $ac_status" >&5 + echo "$as_me:1772: \$? = $ac_status" >&5 (exit "$ac_status"); } -{ (eval echo "$as_me:1458: \"$ac_compiler -v &5\"") >&5 +{ (eval echo "$as_me:1774: \"$ac_compiler -v &5\"") >&5 (eval $ac_compiler -v &5) 2>&5 ac_status=$? - echo "$as_me:1461: \$? = $ac_status" >&5 + echo "$as_me:1777: \$? = $ac_status" >&5 (exit "$ac_status"); } -{ (eval echo "$as_me:1463: \"$ac_compiler -V &5\"") >&5 +{ (eval echo "$as_me:1779: \"$ac_compiler -V &5\"") >&5 (eval $ac_compiler -V &5) 2>&5 ac_status=$? - echo "$as_me:1466: \$? = $ac_status" >&5 + echo "$as_me:1782: \$? = $ac_status" >&5 (exit "$ac_status"); } cat >"conftest.$ac_ext" <<_ACEOF -#line 1470 "configure" +#line 1786 "configure" #include "confdefs.h" int @@ -1483,13 +1799,13 @@ ac_clean_files="$ac_clean_files a.out a.exe" # Try to create an executable without -o first, disregard a.out. # It will help us diagnose broken compilers, and finding out an intuition # of exeext. -echo "$as_me:1486: checking for C compiler default output" >&5 +echo "$as_me:1802: checking for C compiler default output" >&5 echo $ECHO_N "checking for C compiler default output... $ECHO_C" >&6 ac_link_default=`echo "$ac_link" | sed 's/ -o *"conftest[^"]*"//'` -if { (eval echo "$as_me:1489: \"$ac_link_default\"") >&5 +if { (eval echo "$as_me:1805: \"$ac_link_default\"") >&5 (eval $ac_link_default) 2>&5 ac_status=$? - echo "$as_me:1492: \$? = $ac_status" >&5 + echo "$as_me:1808: \$? = $ac_status" >&5 (exit "$ac_status"); }; then # Find the output, starting from the most likely. This scheme is # not robust to junk in `.', hence go to wildcards (a.*) only as a last @@ -1512,34 +1828,34 @@ done else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -{ { echo "$as_me:1515: error: C compiler cannot create executables" >&5 +{ { echo "$as_me:1831: error: C compiler cannot create executables" >&5 echo "$as_me: error: C compiler cannot create executables" >&2;} { (exit 77); exit 77; }; } fi ac_exeext=$ac_cv_exeext -echo "$as_me:1521: result: $ac_file" >&5 +echo "$as_me:1837: result: $ac_file" >&5 echo "${ECHO_T}$ac_file" >&6 # Check the compiler produces executables we can run. If not, either # the compiler is broken, or we cross compile. -echo "$as_me:1526: checking whether the C compiler works" >&5 +echo "$as_me:1842: checking whether the C compiler works" >&5 echo $ECHO_N "checking whether the C compiler works... $ECHO_C" >&6 # FIXME: These cross compiler hacks should be removed for Autoconf 3.0 # If not cross compiling, check that we can run a simple program. if test "$cross_compiling" != yes; then if { ac_try='./$ac_file' - { (eval echo "$as_me:1532: \"$ac_try\"") >&5 + { (eval echo "$as_me:1848: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:1535: \$? = $ac_status" >&5 + echo "$as_me:1851: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cross_compiling=no else if test "$cross_compiling" = maybe; then cross_compiling=yes else - { { echo "$as_me:1542: error: cannot run C compiled programs. + { { echo "$as_me:1858: error: cannot run C compiled programs. If you meant to cross compile, use \`--host'." >&5 echo "$as_me: error: cannot run C compiled programs. If you meant to cross compile, use \`--host'." >&2;} @@ -1547,24 +1863,24 @@ If you meant to cross compile, use \`--host'." >&2;} fi fi fi -echo "$as_me:1550: result: yes" >&5 +echo "$as_me:1866: result: yes" >&5 echo "${ECHO_T}yes" >&6 rm -f a.out a.exe "conftest$ac_cv_exeext" ac_clean_files=$ac_clean_files_save # Check the compiler produces executables we can run. If not, either # the compiler is broken, or we cross compile. -echo "$as_me:1557: checking whether we are cross compiling" >&5 +echo "$as_me:1873: checking whether we are cross compiling" >&5 echo $ECHO_N "checking whether we are cross compiling... $ECHO_C" >&6 -echo "$as_me:1559: result: $cross_compiling" >&5 +echo "$as_me:1875: result: $cross_compiling" >&5 echo "${ECHO_T}$cross_compiling" >&6 -echo "$as_me:1562: checking for executable suffix" >&5 +echo "$as_me:1878: checking for executable suffix" >&5 echo $ECHO_N "checking for executable suffix... $ECHO_C" >&6 -if { (eval echo "$as_me:1564: \"$ac_link\"") >&5 +if { (eval echo "$as_me:1880: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:1567: \$? = $ac_status" >&5 + echo "$as_me:1883: \$? = $ac_status" >&5 (exit "$ac_status"); }; then # If both `conftest.exe' and `conftest' are `present' (well, observable) # catch `conftest.exe'. For instance with Cygwin, `ls conftest' will @@ -1580,25 +1896,25 @@ for ac_file in `(ls conftest.exe; ls conftest; ls conftest.*) 2>/dev/null`; do esac done else - { { echo "$as_me:1583: error: cannot compute EXEEXT: cannot compile and link" >&5 + { { echo "$as_me:1899: error: cannot compute EXEEXT: cannot compile and link" >&5 echo "$as_me: error: cannot compute EXEEXT: cannot compile and link" >&2;} { (exit 1); exit 1; }; } fi rm -f "conftest$ac_cv_exeext" -echo "$as_me:1589: result: $ac_cv_exeext" >&5 +echo "$as_me:1905: result: $ac_cv_exeext" >&5 echo "${ECHO_T}$ac_cv_exeext" >&6 rm -f "conftest.$ac_ext" EXEEXT=$ac_cv_exeext ac_exeext=$EXEEXT -echo "$as_me:1595: checking for object suffix" >&5 +echo "$as_me:1911: checking for object suffix" >&5 echo $ECHO_N "checking for object suffix... $ECHO_C" >&6 if test "${ac_cv_objext+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 1601 "configure" +#line 1917 "configure" #include "confdefs.h" int @@ -1610,10 +1926,10 @@ main (void) } _ACEOF rm -f conftest.o conftest.obj -if { (eval echo "$as_me:1613: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:1929: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:1616: \$? = $ac_status" >&5 + echo "$as_me:1932: \$? = $ac_status" >&5 (exit "$ac_status"); }; then for ac_file in `(ls conftest.o conftest.obj; ls conftest.*) 2>/dev/null`; do case $ac_file in @@ -1625,24 +1941,24 @@ done else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -{ { echo "$as_me:1628: error: cannot compute OBJEXT: cannot compile" >&5 +{ { echo "$as_me:1944: error: cannot compute OBJEXT: cannot compile" >&5 echo "$as_me: error: cannot compute OBJEXT: cannot compile" >&2;} { (exit 1); exit 1; }; } fi rm -f "conftest.$ac_cv_objext" "conftest.$ac_ext" fi -echo "$as_me:1635: result: $ac_cv_objext" >&5 +echo "$as_me:1951: result: $ac_cv_objext" >&5 echo "${ECHO_T}$ac_cv_objext" >&6 OBJEXT=$ac_cv_objext ac_objext=$OBJEXT -echo "$as_me:1639: checking whether we are using the GNU C compiler" >&5 +echo "$as_me:1955: checking whether we are using the GNU C compiler" >&5 echo $ECHO_N "checking whether we are using the GNU C compiler... $ECHO_C" >&6 if test "${ac_cv_c_compiler_gnu+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 1645 "configure" +#line 1961 "configure" #include "confdefs.h" int @@ -1657,16 +1973,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:1660: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:1976: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:1663: \$? = $ac_status" >&5 + echo "$as_me:1979: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:1666: \"$ac_try\"") >&5 + { (eval echo "$as_me:1982: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:1669: \$? = $ac_status" >&5 + echo "$as_me:1985: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_compiler_gnu=yes else @@ -1678,19 +1994,19 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" ac_cv_c_compiler_gnu=$ac_compiler_gnu fi -echo "$as_me:1681: result: $ac_cv_c_compiler_gnu" >&5 +echo "$as_me:1997: result: $ac_cv_c_compiler_gnu" >&5 echo "${ECHO_T}$ac_cv_c_compiler_gnu" >&6 GCC=`test $ac_compiler_gnu = yes && echo yes` ac_test_CFLAGS=${CFLAGS+set} ac_save_CFLAGS=$CFLAGS CFLAGS="-g" -echo "$as_me:1687: checking whether $CC accepts -g" >&5 +echo "$as_me:2003: checking whether $CC accepts -g" >&5 echo $ECHO_N "checking whether $CC accepts -g... $ECHO_C" >&6 if test "${ac_cv_prog_cc_g+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 1693 "configure" +#line 2009 "configure" #include "confdefs.h" int @@ -1702,16 +2018,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:1705: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:2021: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:1708: \$? = $ac_status" >&5 + echo "$as_me:2024: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:1711: \"$ac_try\"") >&5 + { (eval echo "$as_me:2027: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:1714: \$? = $ac_status" >&5 + echo "$as_me:2030: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_prog_cc_g=yes else @@ -1721,7 +2037,7 @@ ac_cv_prog_cc_g=no fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:1724: result: $ac_cv_prog_cc_g" >&5 +echo "$as_me:2040: result: $ac_cv_prog_cc_g" >&5 echo "${ECHO_T}$ac_cv_prog_cc_g" >&6 if test "$ac_test_CFLAGS" = set; then CFLAGS=$ac_save_CFLAGS @@ -1748,16 +2064,16 @@ cat >"conftest.$ac_ext" <<_ACEOF #endif _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:1751: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:2067: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:1754: \$? = $ac_status" >&5 + echo "$as_me:2070: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:1757: \"$ac_try\"") >&5 + { (eval echo "$as_me:2073: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:1760: \$? = $ac_status" >&5 + echo "$as_me:2076: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then for ac_declaration in \ ''\ @@ -1769,7 +2085,7 @@ if { (eval echo "$as_me:1751: \"$ac_compile\"") >&5 'void exit (int);' do cat >"conftest.$ac_ext" <<_ACEOF -#line 1772 "configure" +#line 2088 "configure" #include "confdefs.h" #include $ac_declaration @@ -1782,16 +2098,16 @@ exit (42); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:1785: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:2101: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:1788: \$? = $ac_status" >&5 + echo "$as_me:2104: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:1791: \"$ac_try\"") >&5 + { (eval echo "$as_me:2107: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:1794: \$? = $ac_status" >&5 + echo "$as_me:2110: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -1801,7 +2117,7 @@ continue fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" cat >"conftest.$ac_ext" <<_ACEOF -#line 1804 "configure" +#line 2120 "configure" #include "confdefs.h" $ac_declaration int @@ -1813,16 +2129,16 @@ exit (42); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:1816: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:2132: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:1819: \$? = $ac_status" >&5 + echo "$as_me:2135: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:1822: \"$ac_try\"") >&5 + { (eval echo "$as_me:2138: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:1825: \$? = $ac_status" >&5 + echo "$as_me:2141: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then break else @@ -1852,11 +2168,11 @@ ac_main_return="return" GCC_VERSION=none if test "$GCC" = yes ; then - echo "$as_me:1855: checking version of $CC" >&5 + echo "$as_me:2171: checking version of $CC" >&5 echo $ECHO_N "checking version of $CC... $ECHO_C" >&6 GCC_VERSION="`${CC} --version 2>/dev/null | sed -e '2,$d' -e 's/^[^(]*([^)][^)]*) //' -e 's/^[^0-9.]*//' -e 's/[^0-9.].*//'`" test -z "$GCC_VERSION" && GCC_VERSION=unknown - echo "$as_me:1859: result: $GCC_VERSION" >&5 + echo "$as_me:2175: result: $GCC_VERSION" >&5 echo "${ECHO_T}$GCC_VERSION" >&6 fi @@ -1865,12 +2181,12 @@ INTEL_COMPILER=no if test "$GCC" = yes ; then case "$host_os" in (linux*|gnu*) - echo "$as_me:1868: checking if this is really Intel C compiler" >&5 + echo "$as_me:2184: checking if this is really Intel C compiler" >&5 echo $ECHO_N "checking if this is really Intel C compiler... $ECHO_C" >&6 cf_save_CFLAGS="$CFLAGS" CFLAGS="$CFLAGS -no-gcc" cat >"conftest.$ac_ext" <<_ACEOF -#line 1873 "configure" +#line 2189 "configure" #include "confdefs.h" int @@ -1887,16 +2203,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:1890: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:2206: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:1893: \$? = $ac_status" >&5 + echo "$as_me:2209: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:1896: \"$ac_try\"") >&5 + { (eval echo "$as_me:2212: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:1899: \$? = $ac_status" >&5 + echo "$as_me:2215: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then INTEL_COMPILER=yes cf_save_CFLAGS="$cf_save_CFLAGS -we147" @@ -1907,7 +2223,7 @@ cat "conftest.$ac_ext" >&5 fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" CFLAGS="$cf_save_CFLAGS" - echo "$as_me:1910: result: $INTEL_COMPILER" >&5 + echo "$as_me:2226: result: $INTEL_COMPILER" >&5 echo "${ECHO_T}$INTEL_COMPILER" >&6 ;; esac @@ -1916,11 +2232,11 @@ fi CLANG_COMPILER=no if test "$GCC" = yes ; then - echo "$as_me:1919: checking if this is really Clang C compiler" >&5 + echo "$as_me:2235: checking if this is really Clang C compiler" >&5 echo $ECHO_N "checking if this is really Clang C compiler... $ECHO_C" >&6 cf_save_CFLAGS="$CFLAGS" cat >"conftest.$ac_ext" <<_ACEOF -#line 1923 "configure" +#line 2239 "configure" #include "confdefs.h" int @@ -1937,16 +2253,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:1940: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:2256: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:1943: \$? = $ac_status" >&5 + echo "$as_me:2259: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:1946: \"$ac_try\"") >&5 + { (eval echo "$as_me:2262: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:1949: \$? = $ac_status" >&5 + echo "$as_me:2265: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then CLANG_COMPILER=yes @@ -1956,7 +2272,7 @@ cat "conftest.$ac_ext" >&5 fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" CFLAGS="$cf_save_CFLAGS" - echo "$as_me:1959: result: $CLANG_COMPILER" >&5 + echo "$as_me:2275: result: $CLANG_COMPILER" >&5 echo "${ECHO_T}$CLANG_COMPILER" >&6 fi @@ -1965,30 +2281,30 @@ CLANG_VERSION=none if test "x$CLANG_COMPILER" = "xyes" ; then case "$CC" in (c[1-9][0-9]|*/c[1-9][0-9]) - { echo "$as_me:1968: WARNING: replacing broken compiler alias $CC" >&5 + { echo "$as_me:2284: WARNING: replacing broken compiler alias $CC" >&5 echo "$as_me: WARNING: replacing broken compiler alias $CC" >&2;} CFLAGS="$CFLAGS -std=`echo "$CC" | sed -e 's%.*/%%'`" CC=clang ;; esac - echo "$as_me:1975: checking version of $CC" >&5 + echo "$as_me:2291: checking version of $CC" >&5 echo $ECHO_N "checking version of $CC... $ECHO_C" >&6 CLANG_VERSION="`$CC --version 2>/dev/null | sed -e '2,$d' -e 's/^.*(CLANG[^)]*) //' -e 's/^.*(Debian[^)]*) //' -e 's/^[^0-9.]*//' -e 's/[^0-9.].*//'`" test -z "$CLANG_VERSION" && CLANG_VERSION=unknown - echo "$as_me:1979: result: $CLANG_VERSION" >&5 + echo "$as_me:2295: result: $CLANG_VERSION" >&5 echo "${ECHO_T}$CLANG_VERSION" >&6 for cf_clang_opt in \ -Qunused-arguments \ -Wno-error=implicit-function-declaration do - echo "$as_me:1986: checking if option $cf_clang_opt works" >&5 + echo "$as_me:2302: checking if option $cf_clang_opt works" >&5 echo $ECHO_N "checking if option $cf_clang_opt works... $ECHO_C" >&6 cf_save_CFLAGS="$CFLAGS" CFLAGS="$CFLAGS $cf_clang_opt" cat >"conftest.$ac_ext" <<_ACEOF -#line 1991 "configure" +#line 2307 "configure" #include "confdefs.h" #include @@ -2002,16 +2318,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:2005: \"$ac_link\"") >&5 +if { (eval echo "$as_me:2321: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:2008: \$? = $ac_status" >&5 + echo "$as_me:2324: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:2011: \"$ac_try\"") >&5 + { (eval echo "$as_me:2327: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:2014: \$? = $ac_status" >&5 + echo "$as_me:2330: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_clang_optok=yes @@ -2022,13 +2338,13 @@ cat "conftest.$ac_ext" >&5 cf_clang_optok=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" - echo "$as_me:2025: result: $cf_clang_optok" >&5 + echo "$as_me:2341: result: $cf_clang_optok" >&5 echo "${ECHO_T}$cf_clang_optok" >&6 CFLAGS="$cf_save_CFLAGS" if test "$cf_clang_optok" = yes; then test -n "$verbose" && echo " adding option $cf_clang_opt" 1>&6 -echo "${as_me:-configure}:2031: testing adding option $cf_clang_opt ..." 1>&5 +echo "${as_me:-configure}:2347: testing adding option $cf_clang_opt ..." 1>&5 test -n "$CFLAGS" && CFLAGS="$CFLAGS " CFLAGS="${CFLAGS}$cf_clang_opt" @@ -2037,7 +2353,7 @@ echo "${as_me:-configure}:2031: testing adding option $cf_clang_opt ..." 1>&5 done fi -echo "$as_me:2040: checking for $CC option to accept ANSI C" >&5 +echo "$as_me:2356: checking for $CC option to accept ANSI C" >&5 echo $ECHO_N "checking for $CC option to accept ANSI C... $ECHO_C" >&6 if test "${ac_cv_prog_cc_stdc+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -2045,7 +2361,7 @@ else ac_cv_prog_cc_stdc=no ac_save_CC=$CC cat >"conftest.$ac_ext" <<_ACEOF -#line 2048 "configure" +#line 2364 "configure" #include "confdefs.h" #include #include @@ -2092,16 +2408,16 @@ for ac_arg in "" -qlanglvl=ansi -std1 -Ae "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIO do CC="$ac_save_CC $ac_arg" rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:2095: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:2411: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:2098: \$? = $ac_status" >&5 + echo "$as_me:2414: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:2101: \"$ac_try\"") >&5 + { (eval echo "$as_me:2417: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:2104: \$? = $ac_status" >&5 + echo "$as_me:2420: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_prog_cc_stdc=$ac_arg break @@ -2118,10 +2434,10 @@ fi case "x$ac_cv_prog_cc_stdc" in x|xno) - echo "$as_me:2121: result: none needed" >&5 + echo "$as_me:2437: result: none needed" >&5 echo "${ECHO_T}none needed" >&6 ;; *) - echo "$as_me:2124: result: $ac_cv_prog_cc_stdc" >&5 + echo "$as_me:2440: result: $ac_cv_prog_cc_stdc" >&5 echo "${ECHO_T}$ac_cv_prog_cc_stdc" >&6 CC="$CC $ac_cv_prog_cc_stdc" ;; esac @@ -2129,13 +2445,13 @@ esac # This should have been defined by AC_PROG_CC : "${CC:=cc}" -echo "$as_me:2132: checking \$CFLAGS variable" >&5 +echo "$as_me:2448: checking \$CFLAGS variable" >&5 echo $ECHO_N "checking \$CFLAGS variable... $ECHO_C" >&6 case "x$CFLAGS" in (*-[IUD]*) - echo "$as_me:2136: result: broken" >&5 + echo "$as_me:2452: result: broken" >&5 echo "${ECHO_T}broken" >&6 - { echo "$as_me:2138: WARNING: your environment uses the CFLAGS variable to hold CPPFLAGS options" >&5 + { echo "$as_me:2454: WARNING: your environment uses the CFLAGS variable to hold CPPFLAGS options" >&5 echo "$as_me: WARNING: your environment uses the CFLAGS variable to hold CPPFLAGS options" >&2;} cf_flags="$CFLAGS" CFLAGS= @@ -2243,18 +2559,18 @@ fi done ;; (*) - echo "$as_me:2246: result: ok" >&5 + echo "$as_me:2562: result: ok" >&5 echo "${ECHO_T}ok" >&6 ;; esac -echo "$as_me:2251: checking \$CC variable" >&5 +echo "$as_me:2567: checking \$CC variable" >&5 echo $ECHO_N "checking \$CC variable... $ECHO_C" >&6 case "$CC" in (*[\ \ ]-*) - echo "$as_me:2255: result: broken" >&5 + echo "$as_me:2571: result: broken" >&5 echo "${ECHO_T}broken" >&6 - { echo "$as_me:2257: WARNING: your environment uses the CC variable to hold CFLAGS/CPPFLAGS options" >&5 + { echo "$as_me:2573: WARNING: your environment uses the CC variable to hold CFLAGS/CPPFLAGS options" >&5 echo "$as_me: WARNING: your environment uses the CC variable to hold CFLAGS/CPPFLAGS options" >&2;} # humor him... cf_prog=`echo "$CC" | sed -e 's/ / /g' -e 's/[ ]* / /g' -e 's/[ ]*[ ]-[^ ].*//'` @@ -2371,24 +2687,27 @@ fi done test -n "$verbose" && echo " resulting CC: '$CC'" 1>&6 -echo "${as_me:-configure}:2374: testing resulting CC: '$CC' ..." 1>&5 +echo "${as_me:-configure}:2690: testing resulting CC: '$CC' ..." 1>&5 test -n "$verbose" && echo " resulting CFLAGS: '$CFLAGS'" 1>&6 -echo "${as_me:-configure}:2378: testing resulting CFLAGS: '$CFLAGS' ..." 1>&5 +echo "${as_me:-configure}:2694: testing resulting CFLAGS: '$CFLAGS' ..." 1>&5 test -n "$verbose" && echo " resulting CPPFLAGS: '$CPPFLAGS'" 1>&6 -echo "${as_me:-configure}:2382: testing resulting CPPFLAGS: '$CPPFLAGS' ..." 1>&5 +echo "${as_me:-configure}:2698: testing resulting CPPFLAGS: '$CPPFLAGS' ..." 1>&5 ;; (*) - echo "$as_me:2386: result: ok" >&5 + echo "$as_me:2702: result: ok" >&5 echo "${ECHO_T}ok" >&6 ;; esac -echo "$as_me:2391: checking for egrep" >&5 + ;; +esac + +echo "$as_me:2710: checking for egrep" >&5 echo $ECHO_N "checking for egrep... $ECHO_C" >&6 if test "${ac_cv_path_EGREP+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -2400,7 +2719,7 @@ else do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:2403: checking for $ac_word" >&5 +echo "$as_me:2722: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_path_EGREP+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -2417,7 +2736,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. if $as_executable_p "$ac_dir/$ac_word"; then ac_cv_path_EGREP="$ac_dir/$ac_word" - echo "$as_me:2420: found $ac_dir/$ac_word" >&5 + echo "$as_me:2739: found $ac_dir/$ac_word" >&5 break fi done @@ -2428,10 +2747,10 @@ fi EGREP=$ac_cv_path_EGREP if test -n "$EGREP"; then - echo "$as_me:2431: result: $EGREP" >&5 + echo "$as_me:2750: result: $EGREP" >&5 echo "${ECHO_T}$EGREP" >&6 else - echo "$as_me:2434: result: no" >&5 + echo "$as_me:2753: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -2439,12 +2758,12 @@ fi done test -n "$EGREP" || EGREP=": " - test "x$ac_cv_path_EGREP" = "x:" && { { echo "$as_me:2442: error: cannot find workable egrep" >&5 + test "x$ac_cv_path_EGREP" = "x:" && { { echo "$as_me:2761: error: cannot find workable egrep" >&5 echo "$as_me: error: cannot find workable egrep" >&2;} { (exit 1); exit 1; }; } fi fi -echo "$as_me:2447: result: $ac_cv_path_EGREP" >&5 +echo "$as_me:2766: result: $ac_cv_path_EGREP" >&5 echo "${ECHO_T}$ac_cv_path_EGREP" >&6 EGREP="$ac_cv_path_EGREP" @@ -2454,7 +2773,7 @@ ac_compile='$CC -c $CFLAGS $CPPFLAGS "conftest.$ac_ext" >&5' ac_link='$CC -o "conftest$ac_exeext" $CFLAGS $CPPFLAGS $LDFLAGS "conftest.$ac_ext" $LIBS >&5' ac_compiler_gnu=$ac_cv_c_compiler_gnu ac_main_return="return" -echo "$as_me:2457: checking how to run the C preprocessor" >&5 +echo "$as_me:2776: checking how to run the C preprocessor" >&5 echo $ECHO_N "checking how to run the C preprocessor... $ECHO_C" >&6 # On Suns, sometimes $CPP names a directory. if test -n "$CPP" && test -d "$CPP"; then @@ -2475,18 +2794,18 @@ do # On the NeXT, cc -E runs the code through the compiler's parser, # not just through cpp. "Syntax error" is here to catch this case. cat >"conftest.$ac_ext" <<_ACEOF -#line 2478 "configure" +#line 2797 "configure" #include "confdefs.h" #include Syntax error _ACEOF -if { (eval echo "$as_me:2483: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:2802: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:2489: \$? = $ac_status" >&5 + echo "$as_me:2808: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -2509,17 +2828,17 @@ rm -f conftest.err "conftest.$ac_ext" # OK, works on sane cases. Now check whether non-existent headers # can be detected and how. cat >"conftest.$ac_ext" <<_ACEOF -#line 2512 "configure" +#line 2831 "configure" #include "confdefs.h" #include _ACEOF -if { (eval echo "$as_me:2516: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:2835: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:2522: \$? = $ac_status" >&5 + echo "$as_me:2841: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -2556,7 +2875,7 @@ fi else ac_cv_prog_CPP=$CPP fi -echo "$as_me:2559: result: $CPP" >&5 +echo "$as_me:2878: result: $CPP" >&5 echo "${ECHO_T}$CPP" >&6 ac_preproc_ok=false for ac_c_preproc_warn_flag in '' yes @@ -2566,18 +2885,18 @@ do # On the NeXT, cc -E runs the code through the compiler's parser, # not just through cpp. "Syntax error" is here to catch this case. cat >"conftest.$ac_ext" <<_ACEOF -#line 2569 "configure" +#line 2888 "configure" #include "confdefs.h" #include Syntax error _ACEOF -if { (eval echo "$as_me:2574: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:2893: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:2580: \$? = $ac_status" >&5 + echo "$as_me:2899: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -2600,17 +2919,17 @@ rm -f conftest.err "conftest.$ac_ext" # OK, works on sane cases. Now check whether non-existent headers # can be detected and how. cat >"conftest.$ac_ext" <<_ACEOF -#line 2603 "configure" +#line 2922 "configure" #include "confdefs.h" #include _ACEOF -if { (eval echo "$as_me:2607: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:2926: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:2613: \$? = $ac_status" >&5 + echo "$as_me:2932: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -2638,7 +2957,7 @@ rm -f conftest.err "conftest.$ac_ext" if $ac_preproc_ok; then : else - { { echo "$as_me:2641: error: C preprocessor \"$CPP\" fails sanity check" >&5 + { { echo "$as_me:2960: error: C preprocessor \"$CPP\" fails sanity check" >&5 echo "$as_me: error: C preprocessor \"$CPP\" fails sanity check" >&2;} { (exit 1); exit 1; }; } fi @@ -2651,14 +2970,14 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu ac_main_return="return" if test $ac_cv_c_compiler_gnu = yes; then - echo "$as_me:2654: checking whether $CC needs -traditional" >&5 + echo "$as_me:2973: checking whether $CC needs -traditional" >&5 echo $ECHO_N "checking whether $CC needs -traditional... $ECHO_C" >&6 if test "${ac_cv_prog_gcc_traditional+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else ac_pattern="Autoconf.*'x'" cat >"conftest.$ac_ext" <<_ACEOF -#line 2661 "configure" +#line 2980 "configure" #include "confdefs.h" #include int Autoconf = TIOCGETP; @@ -2673,7 +2992,7 @@ rm -rf conftest* if test $ac_cv_prog_gcc_traditional = no; then cat >"conftest.$ac_ext" <<_ACEOF -#line 2676 "configure" +#line 2995 "configure" #include "confdefs.h" #include int Autoconf = TCGETA; @@ -2686,14 +3005,14 @@ rm -rf conftest* fi fi -echo "$as_me:2689: result: $ac_cv_prog_gcc_traditional" >&5 +echo "$as_me:3008: result: $ac_cv_prog_gcc_traditional" >&5 echo "${ECHO_T}$ac_cv_prog_gcc_traditional" >&6 if test $ac_cv_prog_gcc_traditional = yes; then CC="$CC -traditional" fi fi -echo "$as_me:2696: checking whether $CC understands -c and -o together" >&5 +echo "$as_me:3015: checking whether $CC understands -c and -o together" >&5 echo $ECHO_N "checking whether $CC understands -c and -o together... $ECHO_C" >&6 if test "${cf_cv_prog_CC_c_o+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -2708,15 +3027,15 @@ CF_EOF # We do the test twice because some compilers refuse to overwrite an # existing .o file with -o, though they will create one. ac_try='$CC $CFLAGS $CPPFLAGS -c conftest.$ac_ext -o conftest2.$ac_objext >&5' -if { (eval echo "$as_me:2711: \"$ac_try\"") >&5 +if { (eval echo "$as_me:3030: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:2714: \$? = $ac_status" >&5 + echo "$as_me:3033: \$? = $ac_status" >&5 (exit "$ac_status"); } && - test -f conftest2.$ac_objext && { (eval echo "$as_me:2716: \"$ac_try\"") >&5 + test -f conftest2.$ac_objext && { (eval echo "$as_me:3035: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:2719: \$? = $ac_status" >&5 + echo "$as_me:3038: \$? = $ac_status" >&5 (exit "$ac_status"); }; then eval cf_cv_prog_CC_c_o=yes @@ -2727,10 +3046,10 @@ rm -rf ./conftest* fi if test "$cf_cv_prog_CC_c_o" = yes; then - echo "$as_me:2730: result: yes" >&5 + echo "$as_me:3049: result: yes" >&5 echo "${ECHO_T}yes" >&6 else - echo "$as_me:2733: result: no" >&5 + echo "$as_me:3052: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -2751,7 +3070,7 @@ for ac_prog in mawk gawk nawk awk do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:2754: checking for $ac_word" >&5 +echo "$as_me:3073: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_AWK+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -2766,7 +3085,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_AWK="$ac_prog" -echo "$as_me:2769: found $ac_dir/$ac_word" >&5 +echo "$as_me:3088: found $ac_dir/$ac_word" >&5 break done @@ -2774,21 +3093,21 @@ fi fi AWK=$ac_cv_prog_AWK if test -n "$AWK"; then - echo "$as_me:2777: result: $AWK" >&5 + echo "$as_me:3096: result: $AWK" >&5 echo "${ECHO_T}$AWK" >&6 else - echo "$as_me:2780: result: no" >&5 + echo "$as_me:3099: result: no" >&5 echo "${ECHO_T}no" >&6 fi test -n "$AWK" && break done -test -z "$AWK" && { { echo "$as_me:2787: error: No awk program found" >&5 +test -z "$AWK" && { { echo "$as_me:3106: error: No awk program found" >&5 echo "$as_me: error: No awk program found" >&2;} { (exit 1); exit 1; }; } -echo "$as_me:2791: checking for egrep" >&5 +echo "$as_me:3110: checking for egrep" >&5 echo $ECHO_N "checking for egrep... $ECHO_C" >&6 if test "${ac_cv_prog_egrep+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -2798,11 +3117,11 @@ else else ac_cv_prog_egrep='egrep' fi fi -echo "$as_me:2801: result: $ac_cv_prog_egrep" >&5 +echo "$as_me:3120: result: $ac_cv_prog_egrep" >&5 echo "${ECHO_T}$ac_cv_prog_egrep" >&6 EGREP=$ac_cv_prog_egrep - test -z "$EGREP" && { { echo "$as_me:2805: error: No egrep program found" >&5 + test -z "$EGREP" && { { echo "$as_me:3124: error: No egrep program found" >&5 echo "$as_me: error: No egrep program found" >&2;} { (exit 1); exit 1; }; } @@ -2818,7 +3137,7 @@ echo "$as_me: error: No egrep program found" >&2;} # AFS /usr/afsws/bin/install, which mishandles nonexistent args # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" # ./install, which can be erroneously created by make from ./install.sh. -echo "$as_me:2821: checking for a BSD compatible install" >&5 +echo "$as_me:3140: checking for a BSD compatible install" >&5 echo $ECHO_N "checking for a BSD compatible install... $ECHO_C" >&6 if test -z "$INSTALL"; then if test "${ac_cv_path_install+set}" = set; then @@ -2867,7 +3186,7 @@ fi INSTALL=$ac_install_sh fi fi -echo "$as_me:2870: result: $INSTALL" >&5 +echo "$as_me:3189: result: $INSTALL" >&5 echo "${ECHO_T}$INSTALL" >&6 # Use test -z because SunOS4 sh mishandles braces in ${var-val}. @@ -2878,18 +3197,18 @@ test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}' test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644' -echo "$as_me:2881: checking whether ln -s works" >&5 +echo "$as_me:3200: checking whether ln -s works" >&5 echo $ECHO_N "checking whether ln -s works... $ECHO_C" >&6 LN_S=$as_ln_s if test "$LN_S" = "ln -s"; then - echo "$as_me:2885: result: yes" >&5 + echo "$as_me:3204: result: yes" >&5 echo "${ECHO_T}yes" >&6 else - echo "$as_me:2888: result: no, using $LN_S" >&5 + echo "$as_me:3207: result: no, using $LN_S" >&5 echo "${ECHO_T}no, using $LN_S" >&6 fi -echo "$as_me:2892: checking if $LN_S -f options work" >&5 +echo "$as_me:3211: checking if $LN_S -f options work" >&5 echo $ECHO_N "checking if $LN_S -f options work... $ECHO_C" >&6 rm -f conf$$.src conf$$dst @@ -2901,11 +3220,22 @@ else cf_prog_ln_sf=no fi rm -f conf$$.dst conf$$src -echo "$as_me:2904: result: $cf_prog_ln_sf" >&5 +echo "$as_me:3223: result: $cf_prog_ln_sf" >&5 echo "${ECHO_T}$cf_prog_ln_sf" >&6 test "$cf_prog_ln_sf" = yes && LN_S="$LN_S -f" +case "$cf_cv_system_name" in +(cygwin*|msys*|mingw32*|mingw64|os2*) + GLOB_FULLPATH_POSIX='/*' + GLOB_FULLPATH_OTHER='[a-zA-Z]:[\\/]*' + ;; +(*) + GLOB_FULLPATH_POSIX='/*' + GLOB_FULLPATH_OTHER=$GLOB_FULLPATH_POSIX + ;; +esac + # Find a good install program. We prefer a C program (faster), # so one script is as good as another. But avoid the broken or # incompatible versions: @@ -2918,7 +3248,7 @@ test "$cf_prog_ln_sf" = yes && LN_S="$LN_S -f" # AFS /usr/afsws/bin/install, which mishandles nonexistent args # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" # ./install, which can be erroneously created by make from ./install.sh. -echo "$as_me:2921: checking for a BSD compatible install" >&5 +echo "$as_me:3251: checking for a BSD compatible install" >&5 echo $ECHO_N "checking for a BSD compatible install... $ECHO_C" >&6 if test -z "$INSTALL"; then if test "${ac_cv_path_install+set}" = set; then @@ -2967,7 +3297,7 @@ fi INSTALL=$ac_install_sh fi fi -echo "$as_me:2970: result: $INSTALL" >&5 +echo "$as_me:3300: result: $INSTALL" >&5 echo "${ECHO_T}$INSTALL" >&6 # Use test -z because SunOS4 sh mishandles braces in ${var-val}. @@ -2978,8 +3308,17 @@ test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}' test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644' -case $INSTALL in -(/*) +if test "x$INSTALL" = "x./install-sh -c"; then + if test -f /usr/sbin/install ; then + case "$host_os" in + (linux*gnu*|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) + INSTALL=/usr/sbin/install + ;; + esac + fi +fi +case x$INSTALL in +(x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; (*) cf_dir=`echo "$INSTALL" | sed -e 's%/[^/]*$%%'` @@ -2988,7 +3327,7 @@ case $INSTALL in ;; esac -echo "$as_me:2991: checking if you want to install stripped executables" >&5 +echo "$as_me:3330: checking if you want to install stripped executables" >&5 echo $ECHO_N "checking if you want to install stripped executables... $ECHO_C" >&6 # Check whether --enable-stripping or --disable-stripping was given. @@ -3005,7 +3344,7 @@ else enable_stripping=yes fi; -echo "$as_me:3008: result: $enable_stripping" >&5 +echo "$as_me:3347: result: $enable_stripping" >&5 echo "${ECHO_T}$enable_stripping" >&6 if test "$enable_stripping" = yes @@ -3016,7 +3355,7 @@ else fi : "${INSTALL:=install}" -echo "$as_me:3019: checking if install accepts -p option" >&5 +echo "$as_me:3358: checking if install accepts -p option" >&5 echo $ECHO_N "checking if install accepts -p option... $ECHO_C" >&6 if test "${cf_cv_install_p+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3047,10 +3386,10 @@ else rm -rf ./conftest* fi -echo "$as_me:3050: result: $cf_cv_install_p" >&5 +echo "$as_me:3389: result: $cf_cv_install_p" >&5 echo "${ECHO_T}$cf_cv_install_p" >&6 -echo "$as_me:3053: checking if install needs to be told about ownership" >&5 +echo "$as_me:3392: checking if install needs to be told about ownership" >&5 echo $ECHO_N "checking if install needs to be told about ownership... $ECHO_C" >&6 case `$ac_config_guess` in (*minix) @@ -3061,7 +3400,7 @@ case `$ac_config_guess` in ;; esac -echo "$as_me:3064: result: $with_install_o" >&5 +echo "$as_me:3403: result: $with_install_o" >&5 echo "${ECHO_T}$with_install_o" >&6 if test "x$with_install_o" = xyes then @@ -3072,7 +3411,7 @@ fi if test -n "$INSTALL_OPT_S" then - echo "$as_me:3075: checking if you want to specify strip-program" >&5 + echo "$as_me:3414: checking if you want to specify strip-program" >&5 echo $ECHO_N "checking if you want to specify strip-program... $ECHO_C" >&6 # Check whether --with-strip-program or --without-strip-program was given. @@ -3082,11 +3421,11 @@ if test "${with_strip_program+set}" = set; then else with_strip_program=no fi; - echo "$as_me:3085: result: $with_strip_program" >&5 + echo "$as_me:3424: result: $with_strip_program" >&5 echo "${ECHO_T}$with_strip_program" >&6 if test "$with_strip_program" != no then - echo "$as_me:3089: checking if strip-program is supported with this installer" >&5 + echo "$as_me:3428: checking if strip-program is supported with this installer" >&5 echo $ECHO_N "checking if strip-program is supported with this installer... $ECHO_C" >&6 cf_install_program=`echo "$INSTALL" | sed -e 's%[ ]*[ ]-.%%'` check_install_strip=no @@ -3107,11 +3446,11 @@ echo $ECHO_N "checking if strip-program is supported with this installer... $ECH done fi fi - echo "$as_me:3110: result: $check_install_strip" >&5 + echo "$as_me:3449: result: $check_install_strip" >&5 echo "${ECHO_T}$check_install_strip" >&6 case "$check_install_strip" in (no) - { echo "$as_me:3114: WARNING: $cf_install_program does not support strip program option" >&5 + { echo "$as_me:3453: WARNING: $cf_install_program does not support strip program option" >&5 echo "$as_me: WARNING: $cf_install_program does not support strip program option" >&2;} with_strip_program=no ;; @@ -3126,7 +3465,7 @@ echo "$as_me: WARNING: $cf_install_program does not support strip program option chmod +x "$INSTALL" test -n "$verbose" && echo " created $INSTALL" 1>&6 -echo "${as_me:-configure}:3129: testing created $INSTALL ..." 1>&5 +echo "${as_me:-configure}:3468: testing created $INSTALL ..." 1>&5 ;; (option) @@ -3136,7 +3475,7 @@ echo "${as_me:-configure}:3129: testing created $INSTALL ..." 1>&5 fi fi -echo "$as_me:3139: checking for long file names" >&5 +echo "$as_me:3478: checking for long file names" >&5 echo $ECHO_N "checking for long file names... $ECHO_C" >&6 if test "${ac_cv_sys_long_file_names+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3175,7 +3514,7 @@ for ac_dir in . $ac_tmpdirs `eval echo "$prefix/lib" "$exec_prefix/lib"` ; do rm -rf "$ac_xdir" 2>/dev/null done fi -echo "$as_me:3178: result: $ac_cv_sys_long_file_names" >&5 +echo "$as_me:3517: result: $ac_cv_sys_long_file_names" >&5 echo "${ECHO_T}$ac_cv_sys_long_file_names" >&6 if test "$ac_cv_sys_long_file_names" = yes; then @@ -3187,7 +3526,7 @@ fi # if we find pkg-config, check if we should install the ".pc" files. -echo "$as_me:3190: checking if you want to use pkg-config" >&5 +echo "$as_me:3529: checking if you want to use pkg-config" >&5 echo $ECHO_N "checking if you want to use pkg-config... $ECHO_C" >&6 # Check whether --with-pkg-config or --without-pkg-config was given. @@ -3197,7 +3536,7 @@ if test "${with_pkg_config+set}" = set; then else cf_pkg_config=yes fi; -echo "$as_me:3200: result: $cf_pkg_config" >&5 +echo "$as_me:3539: result: $cf_pkg_config" >&5 echo "${ECHO_T}$cf_pkg_config" >&6 case "$cf_pkg_config" in @@ -3209,7 +3548,7 @@ case "$cf_pkg_config" in if test -n "$ac_tool_prefix"; then # Extract the first word of "${ac_tool_prefix}pkg-config", so it can be a program name with args. set dummy ${ac_tool_prefix}pkg-config; ac_word=$2 -echo "$as_me:3212: checking for $ac_word" >&5 +echo "$as_me:3551: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_path_PKG_CONFIG+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3226,7 +3565,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. if $as_executable_p "$ac_dir/$ac_word"; then ac_cv_path_PKG_CONFIG="$ac_dir/$ac_word" - echo "$as_me:3229: found $ac_dir/$ac_word" >&5 + echo "$as_me:3568: found $ac_dir/$ac_word" >&5 break fi done @@ -3237,10 +3576,10 @@ fi PKG_CONFIG=$ac_cv_path_PKG_CONFIG if test -n "$PKG_CONFIG"; then - echo "$as_me:3240: result: $PKG_CONFIG" >&5 + echo "$as_me:3579: result: $PKG_CONFIG" >&5 echo "${ECHO_T}$PKG_CONFIG" >&6 else - echo "$as_me:3243: result: no" >&5 + echo "$as_me:3582: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3249,7 +3588,7 @@ if test -z "$ac_cv_path_PKG_CONFIG"; then ac_pt_PKG_CONFIG=$PKG_CONFIG # Extract the first word of "pkg-config", so it can be a program name with args. set dummy pkg-config; ac_word=$2 -echo "$as_me:3252: checking for $ac_word" >&5 +echo "$as_me:3591: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_path_ac_pt_PKG_CONFIG+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3266,7 +3605,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. if $as_executable_p "$ac_dir/$ac_word"; then ac_cv_path_ac_pt_PKG_CONFIG="$ac_dir/$ac_word" - echo "$as_me:3269: found $ac_dir/$ac_word" >&5 + echo "$as_me:3608: found $ac_dir/$ac_word" >&5 break fi done @@ -3278,10 +3617,10 @@ fi ac_pt_PKG_CONFIG=$ac_cv_path_ac_pt_PKG_CONFIG if test -n "$ac_pt_PKG_CONFIG"; then - echo "$as_me:3281: result: $ac_pt_PKG_CONFIG" >&5 + echo "$as_me:3620: result: $ac_pt_PKG_CONFIG" >&5 echo "${ECHO_T}$ac_pt_PKG_CONFIG" >&6 else - echo "$as_me:3284: result: no" >&5 + echo "$as_me:3623: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3305,43 +3644,41 @@ else cf_path_syntax="$ac_default_prefix" fi -case ".$PKG_CONFIG" in -(.\$\(*\)*|.\'*\'*) +case "x$PKG_CONFIG" in +(x\$\(*\)*|x\'*\'*) ;; -(..|./*|.\\*) +(x.|x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; -(.[a-zA-Z]:[\\/]*) # OS/2 EMX - ;; -(.\$\{*prefix\}*|.\$\{*dir\}*) +(x\$\{*prefix\}*|x\$\{*dir\}*) eval PKG_CONFIG="$PKG_CONFIG" - case ".$PKG_CONFIG" in - (.NONE/*) + case "x$PKG_CONFIG" in + (xNONE/*) PKG_CONFIG=`echo "$PKG_CONFIG" | sed -e s%NONE%$cf_path_syntax%` ;; esac ;; -(.no|.NONE/*) +(xno|xNONE/*) PKG_CONFIG=`echo "$PKG_CONFIG" | sed -e s%NONE%$cf_path_syntax%` ;; (*) - { { echo "$as_me:3327: error: expected a pathname, not \"$PKG_CONFIG\"" >&5 + { { echo "$as_me:3664: error: expected a pathname, not \"$PKG_CONFIG\"" >&5 echo "$as_me: error: expected a pathname, not \"$PKG_CONFIG\"" >&2;} { (exit 1); exit 1; }; } ;; esac elif test "x$cf_pkg_config" != xno ; then - { echo "$as_me:3334: WARNING: pkg-config is not installed" >&5 + { echo "$as_me:3671: WARNING: pkg-config is not installed" >&5 echo "$as_me: WARNING: pkg-config is not installed" >&2;} fi case "$PKG_CONFIG" in (no|none|yes) - echo "$as_me:3340: checking for pkg-config library directory" >&5 + echo "$as_me:3677: checking for pkg-config library directory" >&5 echo $ECHO_N "checking for pkg-config library directory... $ECHO_C" >&6 ;; (*) - echo "$as_me:3344: checking for $PKG_CONFIG library directory" >&5 + echo "$as_me:3681: checking for $PKG_CONFIG library directory" >&5 echo $ECHO_N "checking for $PKG_CONFIG library directory... $ECHO_C" >&6 ;; esac @@ -3368,27 +3705,27 @@ fi; case "x$cf_search_path" in (xlibdir) PKG_CONFIG_LIBDIR='${libdir}/pkgconfig' - echo "$as_me:3371: result: $PKG_CONFIG_LIBDIR" >&5 + echo "$as_me:3708: result: $PKG_CONFIG_LIBDIR" >&5 echo "${ECHO_T}$PKG_CONFIG_LIBDIR" >&6 cf_search_path= ;; (x) ;; -(x/*\ *) +(x$GLOB_FULLPATH_POSIX\ *|x$GLOB_FULLPATH_OTHER\ *) PKG_CONFIG_LIBDIR= ;; -(x/*) +(x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) PKG_CONFIG_LIBDIR="$cf_search_path" - echo "$as_me:3382: result: $PKG_CONFIG_LIBDIR" >&5 + echo "$as_me:3719: result: $PKG_CONFIG_LIBDIR" >&5 echo "${ECHO_T}$PKG_CONFIG_LIBDIR" >&6 cf_search_path= ;; (xyes|xauto) - echo "$as_me:3387: result: auto" >&5 + echo "$as_me:3724: result: auto" >&5 echo "${ECHO_T}auto" >&6 cf_search_path= # Look for the library directory using the same prefix as the executable - echo "$as_me:3391: checking for search-list" >&5 + echo "$as_me:3728: checking for search-list" >&5 echo $ECHO_N "checking for search-list... $ECHO_C" >&6 if test "x$PKG_CONFIG" != xnone then @@ -3399,7 +3736,15 @@ echo $ECHO_N "checking for search-list... $ECHO_C" >&6 pkg-config \ pkgconf do - cf_search_path=`"$PKG_CONFIG" --variable=pc_path "$cf_pkg_program" 2>/dev/null | tr : ' '` + cf_raw_search_path=`"$PKG_CONFIG" --variable=pc_path "$cf_pkg_program" 2>/dev/null` + case "$cf_raw_search_path" in + (*\\*) + cf_search_path=`echo "$cf_raw_search_path" | tr ';' ' ' | tr '\' '/'` + ;; + (*/*) + cf_search_path=`echo "$cf_raw_search_path" | tr : ' '` + ;; + esac test -n "$cf_search_path" && break done @@ -3415,11 +3760,11 @@ echo $ECHO_N "checking for search-list... $ECHO_C" >&6 "` fi - echo "$as_me:3418: result: $cf_search_path" >&5 + echo "$as_me:3763: result: $cf_search_path" >&5 echo "${ECHO_T}$cf_search_path" >&6 ;; (*) - { { echo "$as_me:3422: error: Unexpected option value: $cf_search_path" >&5 + { { echo "$as_me:3767: error: Unexpected option value: $cf_search_path" >&5 echo "$as_me: error: Unexpected option value: $cf_search_path" >&2;} { (exit 1); exit 1; }; } ;; @@ -3427,7 +3772,7 @@ esac if test -n "$cf_search_path" then - echo "$as_me:3430: checking for first directory" >&5 + echo "$as_me:3775: checking for first directory" >&5 echo $ECHO_N "checking for first directory... $ECHO_C" >&6 cf_pkg_config_path=none for cf_config in $cf_search_path @@ -3438,7 +3783,7 @@ echo $ECHO_N "checking for first directory... $ECHO_C" >&6 break fi done - echo "$as_me:3441: result: $cf_pkg_config_path" >&5 + echo "$as_me:3786: result: $cf_pkg_config_path" >&5 echo "${ECHO_T}$cf_pkg_config_path" >&6 if test "x$cf_pkg_config_path" != xnone ; then @@ -3448,7 +3793,7 @@ echo "${ECHO_T}$cf_pkg_config_path" >&6 if test -z "$PKG_CONFIG_LIBDIR" && test -n "$cf_search_path" then - echo "$as_me:3451: checking for workaround" >&5 + echo "$as_me:3796: checking for workaround" >&5 echo $ECHO_N "checking for workaround... $ECHO_C" >&6 if test "$prefix" = "NONE" ; then cf_prefix="$ac_default_prefix" @@ -3471,12 +3816,12 @@ echo $ECHO_N "checking for workaround... $ECHO_C" >&6 esac done test -z "$PKG_CONFIG_LIBDIR" && PKG_CONFIG_LIBDIR=$cf_backup - echo "$as_me:3474: result: $PKG_CONFIG_LIBDIR" >&5 + echo "$as_me:3819: result: $PKG_CONFIG_LIBDIR" >&5 echo "${ECHO_T}$PKG_CONFIG_LIBDIR" >&6 fi fi -echo "$as_me:3479: checking if you want to build test-programs" >&5 +echo "$as_me:3824: checking if you want to build test-programs" >&5 echo $ECHO_N "checking if you want to build test-programs... $ECHO_C" >&6 # Check whether --with-tests or --without-tests was given. @@ -3486,10 +3831,10 @@ if test "${with_tests+set}" = set; then else cf_with_tests=yes fi; -echo "$as_me:3489: result: $cf_with_tests" >&5 +echo "$as_me:3834: result: $cf_with_tests" >&5 echo "${ECHO_T}$cf_with_tests" >&6 -echo "$as_me:3492: checking if we should assume mixed-case filenames" >&5 +echo "$as_me:3837: checking if we should assume mixed-case filenames" >&5 echo $ECHO_N "checking if we should assume mixed-case filenames... $ECHO_C" >&6 # Check whether --enable-mixed-case or --disable-mixed-case was given. @@ -3499,11 +3844,11 @@ if test "${enable_mixed_case+set}" = set; then else enable_mixedcase=auto fi; -echo "$as_me:3502: result: $enable_mixedcase" >&5 +echo "$as_me:3847: result: $enable_mixedcase" >&5 echo "${ECHO_T}$enable_mixedcase" >&6 if test "$enable_mixedcase" = "auto" ; then -echo "$as_me:3506: checking if filesystem supports mixed-case filenames" >&5 +echo "$as_me:3851: checking if filesystem supports mixed-case filenames" >&5 echo $ECHO_N "checking if filesystem supports mixed-case filenames... $ECHO_C" >&6 if test "${cf_cv_mixedcase+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3530,7 +3875,7 @@ else fi fi -echo "$as_me:3533: result: $cf_cv_mixedcase" >&5 +echo "$as_me:3878: result: $cf_cv_mixedcase" >&5 echo "${ECHO_T}$cf_cv_mixedcase" >&6 test "$cf_cv_mixedcase" = yes && cat >>confdefs.h <<\EOF @@ -3548,7 +3893,7 @@ EOF fi # do this after mixed-case option (tags/TAGS is not as important as tic). -echo "$as_me:3551: checking whether ${MAKE-make} sets \${MAKE}" >&5 +echo "$as_me:3896: checking whether ${MAKE-make} sets \${MAKE}" >&5 echo $ECHO_N "checking whether ${MAKE-make} sets \${MAKE}... $ECHO_C" >&6 set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y,./+-,__p_,'` if eval "test \"\${ac_cv_prog_make_${ac_make}_set+set}\" = set"; then @@ -3568,16 +3913,16 @@ fi rm -f conftest.make fi if eval "test \"`echo '$ac_cv_prog_make_'${ac_make}_set`\" = yes"; then - echo "$as_me:3571: result: yes" >&5 + echo "$as_me:3916: result: yes" >&5 echo "${ECHO_T}yes" >&6 SET_MAKE= else - echo "$as_me:3575: result: no" >&5 + echo "$as_me:3920: result: no" >&5 echo "${ECHO_T}no" >&6 SET_MAKE="MAKE=${MAKE-make}" fi -echo "$as_me:3580: checking for \".PHONY\" make-support" >&5 +echo "$as_me:3925: checking for \".PHONY\" make-support" >&5 echo $ECHO_N "checking for \".PHONY\" make-support... $ECHO_C" >&6 if test "${cf_cv_make_PHONY+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3632,7 +3977,7 @@ CF_EOF rm -rf conftest* fi -echo "$as_me:3635: result: $cf_cv_make_PHONY" >&5 +echo "$as_me:3980: result: $cf_cv_make_PHONY" >&5 echo "${ECHO_T}$cf_cv_make_PHONY" >&6 MAKE_NO_PHONY="#" MAKE_PHONY="#" @@ -3643,7 +3988,7 @@ for ac_prog in exctags ctags do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:3646: checking for $ac_word" >&5 +echo "$as_me:3991: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_CTAGS+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3658,7 +4003,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_CTAGS="$ac_prog" -echo "$as_me:3661: found $ac_dir/$ac_word" >&5 +echo "$as_me:4006: found $ac_dir/$ac_word" >&5 break done @@ -3666,10 +4011,10 @@ fi fi CTAGS=$ac_cv_prog_CTAGS if test -n "$CTAGS"; then - echo "$as_me:3669: result: $CTAGS" >&5 + echo "$as_me:4014: result: $CTAGS" >&5 echo "${ECHO_T}$CTAGS" >&6 else - echo "$as_me:3672: result: no" >&5 + echo "$as_me:4017: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3680,7 +4025,7 @@ for ac_prog in exetags etags do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:3683: checking for $ac_word" >&5 +echo "$as_me:4028: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_ETAGS+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3695,7 +4040,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_ETAGS="$ac_prog" -echo "$as_me:3698: found $ac_dir/$ac_word" >&5 +echo "$as_me:4043: found $ac_dir/$ac_word" >&5 break done @@ -3703,10 +4048,10 @@ fi fi ETAGS=$ac_cv_prog_ETAGS if test -n "$ETAGS"; then - echo "$as_me:3706: result: $ETAGS" >&5 + echo "$as_me:4051: result: $ETAGS" >&5 echo "${ECHO_T}$ETAGS" >&6 else - echo "$as_me:3709: result: no" >&5 + echo "$as_me:4054: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3715,7 +4060,7 @@ done # Extract the first word of "${CTAGS:-ctags}", so it can be a program name with args. set dummy ${CTAGS:-ctags}; ac_word=$2 -echo "$as_me:3718: checking for $ac_word" >&5 +echo "$as_me:4063: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_MAKE_LOWER_TAGS+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3730,7 +4075,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_MAKE_LOWER_TAGS="yes" -echo "$as_me:3733: found $ac_dir/$ac_word" >&5 +echo "$as_me:4078: found $ac_dir/$ac_word" >&5 break done @@ -3739,17 +4084,17 @@ fi fi MAKE_LOWER_TAGS=$ac_cv_prog_MAKE_LOWER_TAGS if test -n "$MAKE_LOWER_TAGS"; then - echo "$as_me:3742: result: $MAKE_LOWER_TAGS" >&5 + echo "$as_me:4087: result: $MAKE_LOWER_TAGS" >&5 echo "${ECHO_T}$MAKE_LOWER_TAGS" >&6 else - echo "$as_me:3745: result: no" >&5 + echo "$as_me:4090: result: no" >&5 echo "${ECHO_T}no" >&6 fi if test "$cf_cv_mixedcase" = yes ; then # Extract the first word of "${ETAGS:-etags}", so it can be a program name with args. set dummy ${ETAGS:-etags}; ac_word=$2 -echo "$as_me:3752: checking for $ac_word" >&5 +echo "$as_me:4097: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_MAKE_UPPER_TAGS+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3764,7 +4109,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_MAKE_UPPER_TAGS="yes" -echo "$as_me:3767: found $ac_dir/$ac_word" >&5 +echo "$as_me:4112: found $ac_dir/$ac_word" >&5 break done @@ -3773,10 +4118,10 @@ fi fi MAKE_UPPER_TAGS=$ac_cv_prog_MAKE_UPPER_TAGS if test -n "$MAKE_UPPER_TAGS"; then - echo "$as_me:3776: result: $MAKE_UPPER_TAGS" >&5 + echo "$as_me:4121: result: $MAKE_UPPER_TAGS" >&5 echo "${ECHO_T}$MAKE_UPPER_TAGS" >&6 else - echo "$as_me:3779: result: no" >&5 + echo "$as_me:4124: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3796,51 +4141,10 @@ else MAKE_LOWER_TAGS="#" fi -echo "$as_me:3799: checking for makeflags variable" >&5 -echo $ECHO_N "checking for makeflags variable... $ECHO_C" >&6 -if test "${cf_cv_makeflags+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - - cf_cv_makeflags='' - for cf_option in '-${MAKEFLAGS}' '${MFLAGS}' - do - cat >cf_makeflags.tmp </dev/null | ${FGREP-fgrep} -v "ing directory" | sed -e 's,[ ]*$,,'` - case "$cf_result" in - (.*k|.*kw) - cf_result="`${MAKE:-make} -k -f cf_makeflags.tmp CC=cc 2>/dev/null`" - case "$cf_result" in - (.*CC=*) cf_cv_makeflags= - ;; - (*) cf_cv_makeflags=$cf_option - ;; - esac - break - ;; - (.-) - ;; - (*) - -echo "${as_me:-configure}:3829: testing given option \"$cf_option\",no match \"$cf_result\" ..." 1>&5 - - ;; - esac - done - rm -f cf_makeflags.tmp - -fi -echo "$as_me:3837: result: $cf_cv_makeflags" >&5 -echo "${ECHO_T}$cf_cv_makeflags" >&6 - if test -n "$ac_tool_prefix"; then # Extract the first word of "${ac_tool_prefix}ranlib", so it can be a program name with args. set dummy ${ac_tool_prefix}ranlib; ac_word=$2 -echo "$as_me:3843: checking for $ac_word" >&5 +echo "$as_me:4147: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_RANLIB+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3855,7 +4159,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_RANLIB="${ac_tool_prefix}ranlib" -echo "$as_me:3858: found $ac_dir/$ac_word" >&5 +echo "$as_me:4162: found $ac_dir/$ac_word" >&5 break done @@ -3863,10 +4167,10 @@ fi fi RANLIB=$ac_cv_prog_RANLIB if test -n "$RANLIB"; then - echo "$as_me:3866: result: $RANLIB" >&5 + echo "$as_me:4170: result: $RANLIB" >&5 echo "${ECHO_T}$RANLIB" >&6 else - echo "$as_me:3869: result: no" >&5 + echo "$as_me:4173: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3875,7 +4179,7 @@ if test -z "$ac_cv_prog_RANLIB"; then ac_ct_RANLIB=$RANLIB # Extract the first word of "ranlib", so it can be a program name with args. set dummy ranlib; ac_word=$2 -echo "$as_me:3878: checking for $ac_word" >&5 +echo "$as_me:4182: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_ac_ct_RANLIB+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3890,7 +4194,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_ac_ct_RANLIB="ranlib" -echo "$as_me:3893: found $ac_dir/$ac_word" >&5 +echo "$as_me:4197: found $ac_dir/$ac_word" >&5 break done @@ -3899,10 +4203,10 @@ fi fi ac_ct_RANLIB=$ac_cv_prog_ac_ct_RANLIB if test -n "$ac_ct_RANLIB"; then - echo "$as_me:3902: result: $ac_ct_RANLIB" >&5 + echo "$as_me:4206: result: $ac_ct_RANLIB" >&5 echo "${ECHO_T}$ac_ct_RANLIB" >&6 else - echo "$as_me:3905: result: no" >&5 + echo "$as_me:4209: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3914,7 +4218,7 @@ fi if test -n "$ac_tool_prefix"; then # Extract the first word of "${ac_tool_prefix}ld", so it can be a program name with args. set dummy ${ac_tool_prefix}ld; ac_word=$2 -echo "$as_me:3917: checking for $ac_word" >&5 +echo "$as_me:4221: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_LD+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3929,7 +4233,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_LD="${ac_tool_prefix}ld" -echo "$as_me:3932: found $ac_dir/$ac_word" >&5 +echo "$as_me:4236: found $ac_dir/$ac_word" >&5 break done @@ -3937,10 +4241,10 @@ fi fi LD=$ac_cv_prog_LD if test -n "$LD"; then - echo "$as_me:3940: result: $LD" >&5 + echo "$as_me:4244: result: $LD" >&5 echo "${ECHO_T}$LD" >&6 else - echo "$as_me:3943: result: no" >&5 + echo "$as_me:4247: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3949,7 +4253,7 @@ if test -z "$ac_cv_prog_LD"; then ac_ct_LD=$LD # Extract the first word of "ld", so it can be a program name with args. set dummy ld; ac_word=$2 -echo "$as_me:3952: checking for $ac_word" >&5 +echo "$as_me:4256: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_ac_ct_LD+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -3964,7 +4268,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_ac_ct_LD="ld" -echo "$as_me:3967: found $ac_dir/$ac_word" >&5 +echo "$as_me:4271: found $ac_dir/$ac_word" >&5 break done @@ -3973,10 +4277,10 @@ fi fi ac_ct_LD=$ac_cv_prog_ac_ct_LD if test -n "$ac_ct_LD"; then - echo "$as_me:3976: result: $ac_ct_LD" >&5 + echo "$as_me:4280: result: $ac_ct_LD" >&5 echo "${ECHO_T}$ac_ct_LD" >&6 else - echo "$as_me:3979: result: no" >&5 + echo "$as_me:4283: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -3988,7 +4292,7 @@ fi if test -n "$ac_tool_prefix"; then # Extract the first word of "${ac_tool_prefix}ar", so it can be a program name with args. set dummy ${ac_tool_prefix}ar; ac_word=$2 -echo "$as_me:3991: checking for $ac_word" >&5 +echo "$as_me:4295: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_AR+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -4003,7 +4307,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_AR="${ac_tool_prefix}ar" -echo "$as_me:4006: found $ac_dir/$ac_word" >&5 +echo "$as_me:4310: found $ac_dir/$ac_word" >&5 break done @@ -4011,10 +4315,10 @@ fi fi AR=$ac_cv_prog_AR if test -n "$AR"; then - echo "$as_me:4014: result: $AR" >&5 + echo "$as_me:4318: result: $AR" >&5 echo "${ECHO_T}$AR" >&6 else - echo "$as_me:4017: result: no" >&5 + echo "$as_me:4321: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -4023,7 +4327,7 @@ if test -z "$ac_cv_prog_AR"; then ac_ct_AR=$AR # Extract the first word of "ar", so it can be a program name with args. set dummy ar; ac_word=$2 -echo "$as_me:4026: checking for $ac_word" >&5 +echo "$as_me:4330: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_ac_ct_AR+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -4038,7 +4342,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_ac_ct_AR="ar" -echo "$as_me:4041: found $ac_dir/$ac_word" >&5 +echo "$as_me:4345: found $ac_dir/$ac_word" >&5 break done @@ -4047,10 +4351,10 @@ fi fi ac_ct_AR=$ac_cv_prog_ac_ct_AR if test -n "$ac_ct_AR"; then - echo "$as_me:4050: result: $ac_ct_AR" >&5 + echo "$as_me:4354: result: $ac_ct_AR" >&5 echo "${ECHO_T}$ac_ct_AR" >&6 else - echo "$as_me:4053: result: no" >&5 + echo "$as_me:4357: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -4062,7 +4366,7 @@ fi if test -n "$ac_tool_prefix"; then # Extract the first word of "${ac_tool_prefix}ar", so it can be a program name with args. set dummy ${ac_tool_prefix}ar; ac_word=$2 -echo "$as_me:4065: checking for $ac_word" >&5 +echo "$as_me:4369: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_AR+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -4077,7 +4381,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_AR="${ac_tool_prefix}ar" -echo "$as_me:4080: found $ac_dir/$ac_word" >&5 +echo "$as_me:4384: found $ac_dir/$ac_word" >&5 break done @@ -4085,10 +4389,10 @@ fi fi AR=$ac_cv_prog_AR if test -n "$AR"; then - echo "$as_me:4088: result: $AR" >&5 + echo "$as_me:4392: result: $AR" >&5 echo "${ECHO_T}$AR" >&6 else - echo "$as_me:4091: result: no" >&5 + echo "$as_me:4395: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -4097,7 +4401,7 @@ if test -z "$ac_cv_prog_AR"; then ac_ct_AR=$AR # Extract the first word of "ar", so it can be a program name with args. set dummy ar; ac_word=$2 -echo "$as_me:4100: checking for $ac_word" >&5 +echo "$as_me:4404: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_ac_ct_AR+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -4112,7 +4416,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_ac_ct_AR="ar" -echo "$as_me:4115: found $ac_dir/$ac_word" >&5 +echo "$as_me:4419: found $ac_dir/$ac_word" >&5 break done @@ -4121,10 +4425,10 @@ fi fi ac_ct_AR=$ac_cv_prog_ac_ct_AR if test -n "$ac_ct_AR"; then - echo "$as_me:4124: result: $ac_ct_AR" >&5 + echo "$as_me:4428: result: $ac_ct_AR" >&5 echo "${ECHO_T}$ac_ct_AR" >&6 else - echo "$as_me:4127: result: no" >&5 + echo "$as_me:4431: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -4133,7 +4437,7 @@ else AR="$ac_cv_prog_AR" fi -echo "$as_me:4136: checking for options to update archives" >&5 +echo "$as_me:4440: checking for options to update archives" >&5 echo $ECHO_N "checking for options to update archives... $ECHO_C" >&6 if test "${cf_cv_ar_flags+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -4170,13 +4474,13 @@ else rm -f conftest.a cat >"conftest.$ac_ext" <&5 + if { (eval echo "$as_me:4480: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:4179: \$? = $ac_status" >&5 + echo "$as_me:4483: \$? = $ac_status" >&5 (exit "$ac_status"); } ; then echo "$AR $ARFLAGS $cf_ar_flags conftest.a conftest.$ac_cv_objext" >&5 $AR $ARFLAGS "$cf_ar_flags" conftest.a "conftest.$ac_cv_objext" 2>&5 1>/dev/null @@ -4187,7 +4491,7 @@ EOF else test -n "$verbose" && echo " cannot compile test-program" 1>&6 -echo "${as_me:-configure}:4190: testing cannot compile test-program ..." 1>&5 +echo "${as_me:-configure}:4494: testing cannot compile test-program ..." 1>&5 break fi @@ -4197,7 +4501,7 @@ echo "${as_me:-configure}:4190: testing cannot compile test-program ..." 1>&5 esac fi -echo "$as_me:4200: result: $cf_cv_ar_flags" >&5 +echo "$as_me:4504: result: $cf_cv_ar_flags" >&5 echo "${ECHO_T}$cf_cv_ar_flags" >&6 if test -n "$ARFLAGS" ; then @@ -4208,31 +4512,60 @@ else ARFLAGS=$cf_cv_ar_flags fi - echo "$as_me:4211: checking for PATH separator" >&5 + echo "$as_me:4515: checking for PATH separator" >&5 echo $ECHO_N "checking for PATH separator... $ECHO_C" >&6 case "$cf_cv_system_name" in (os2*) PATH_SEPARATOR=';' ;; (*) ${PATH_SEPARATOR:=':'} ;; esac - echo "$as_me:4218: result: $PATH_SEPARATOR" >&5 + echo "$as_me:4522: result: $PATH_SEPARATOR" >&5 echo "${ECHO_T}$PATH_SEPARATOR" >&6 -echo "$as_me:4221: checking if you have specified an install-prefix" >&5 -echo $ECHO_N "checking if you have specified an install-prefix... $ECHO_C" >&6 +echo "$as_me:4525: checking for an installation directory prefix" >&5 +echo $ECHO_N "checking for an installation directory prefix... $ECHO_C" >&6 # Check whether --with-install-prefix or --without-install-prefix was given. if test "${with_install_prefix+set}" = set; then withval="$with_install_prefix" - case "$withval" in - (yes|no) + case "x$withval" in + (xyes|xno) ;; (*) DESTDIR="$withval" ;; esac fi; -echo "$as_me:4234: result: $DESTDIR" >&5 -echo "${ECHO_T}$DESTDIR" >&6 +echo "$as_me:4538: result: ${DESTDIR:-(none)}" >&5 +echo "${ECHO_T}${DESTDIR:-(none)}" >&6 + +SET_DESTDIR= +test -n "$DESTDIR" && SET_DESTDIR="DESTDIR=$DESTDIR" + +echo "$as_me:4544: checking if installation directory prefix should be merged" >&5 +echo $ECHO_N "checking if installation directory prefix should be merged... $ECHO_C" >&6 + +# Check whether --enable-install-prefix or --disable-install-prefix was given. +if test "${enable_install_prefix+set}" = set; then + enableval="$enable_install_prefix" + test "$enableval" != yes && enableval=no + if test "$enableval" != "no" ; then + cf_install_prefix=yes + else + cf_install_prefix=no + fi +else + enableval=no + cf_install_prefix=no + +fi; +echo "$as_me:4561: result: $cf_install_prefix" >&5 +echo "${ECHO_T}$cf_install_prefix" >&6 + +if test "$cf_install_prefix" = yes ; then + MERGE_PREFIX=':$(prefix)%=%' +else + MERGE_PREFIX='' +fi ############################################################################### @@ -4259,7 +4592,7 @@ else do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:4262: checking for $ac_word" >&5 +echo "$as_me:4595: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_BUILD_CC+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -4274,7 +4607,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_BUILD_CC="$ac_prog" -echo "$as_me:4277: found $ac_dir/$ac_word" >&5 +echo "$as_me:4610: found $ac_dir/$ac_word" >&5 break done @@ -4282,10 +4615,10 @@ fi fi BUILD_CC=$ac_cv_prog_BUILD_CC if test -n "$BUILD_CC"; then - echo "$as_me:4285: result: $BUILD_CC" >&5 + echo "$as_me:4618: result: $BUILD_CC" >&5 echo "${ECHO_T}$BUILD_CC" >&6 else - echo "$as_me:4288: result: no" >&5 + echo "$as_me:4621: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -4294,12 +4627,12 @@ done test -n "$BUILD_CC" || BUILD_CC="none" fi; - echo "$as_me:4297: checking for native build C compiler" >&5 + echo "$as_me:4630: checking for native build C compiler" >&5 echo $ECHO_N "checking for native build C compiler... $ECHO_C" >&6 - echo "$as_me:4299: result: $BUILD_CC" >&5 + echo "$as_me:4632: result: $BUILD_CC" >&5 echo "${ECHO_T}$BUILD_CC" >&6 - echo "$as_me:4302: checking for native build C preprocessor" >&5 + echo "$as_me:4635: checking for native build C preprocessor" >&5 echo $ECHO_N "checking for native build C preprocessor... $ECHO_C" >&6 # Check whether --with-build-cpp or --without-build-cpp was given. @@ -4309,10 +4642,10 @@ if test "${with_build_cpp+set}" = set; then else BUILD_CPP='${BUILD_CC} -E' fi; - echo "$as_me:4312: result: $BUILD_CPP" >&5 + echo "$as_me:4645: result: $BUILD_CPP" >&5 echo "${ECHO_T}$BUILD_CPP" >&6 - echo "$as_me:4315: checking for native build C flags" >&5 + echo "$as_me:4648: checking for native build C flags" >&5 echo $ECHO_N "checking for native build C flags... $ECHO_C" >&6 # Check whether --with-build-cflags or --without-build-cflags was given. @@ -4320,10 +4653,10 @@ if test "${with_build_cflags+set}" = set; then withval="$with_build_cflags" BUILD_CFLAGS="$withval" fi; - echo "$as_me:4323: result: $BUILD_CFLAGS" >&5 + echo "$as_me:4656: result: $BUILD_CFLAGS" >&5 echo "${ECHO_T}$BUILD_CFLAGS" >&6 - echo "$as_me:4326: checking for native build C preprocessor-flags" >&5 + echo "$as_me:4659: checking for native build C preprocessor-flags" >&5 echo $ECHO_N "checking for native build C preprocessor-flags... $ECHO_C" >&6 # Check whether --with-build-cppflags or --without-build-cppflags was given. @@ -4331,10 +4664,10 @@ if test "${with_build_cppflags+set}" = set; then withval="$with_build_cppflags" BUILD_CPPFLAGS="$withval" fi; - echo "$as_me:4334: result: $BUILD_CPPFLAGS" >&5 + echo "$as_me:4667: result: $BUILD_CPPFLAGS" >&5 echo "${ECHO_T}$BUILD_CPPFLAGS" >&6 - echo "$as_me:4337: checking for native build linker-flags" >&5 + echo "$as_me:4670: checking for native build linker-flags" >&5 echo $ECHO_N "checking for native build linker-flags... $ECHO_C" >&6 # Check whether --with-build-ldflags or --without-build-ldflags was given. @@ -4342,10 +4675,10 @@ if test "${with_build_ldflags+set}" = set; then withval="$with_build_ldflags" BUILD_LDFLAGS="$withval" fi; - echo "$as_me:4345: result: $BUILD_LDFLAGS" >&5 + echo "$as_me:4678: result: $BUILD_LDFLAGS" >&5 echo "${ECHO_T}$BUILD_LDFLAGS" >&6 - echo "$as_me:4348: checking for native build linker-libraries" >&5 + echo "$as_me:4681: checking for native build linker-libraries" >&5 echo $ECHO_N "checking for native build linker-libraries... $ECHO_C" >&6 # Check whether --with-build-libs or --without-build-libs was given. @@ -4353,7 +4686,7 @@ if test "${with_build_libs+set}" = set; then withval="$with_build_libs" BUILD_LIBS="$withval" fi; - echo "$as_me:4356: result: $BUILD_LIBS" >&5 + echo "$as_me:4689: result: $BUILD_LIBS" >&5 echo "${ECHO_T}$BUILD_LIBS" >&6 # this assumes we're on Unix. @@ -4362,7 +4695,7 @@ echo "${ECHO_T}$BUILD_LIBS" >&6 : ${BUILD_CC:='${CC}'} - echo "$as_me:4365: checking if the build-compiler \"$BUILD_CC\" works" >&5 + echo "$as_me:4698: checking if the build-compiler \"$BUILD_CC\" works" >&5 echo $ECHO_N "checking if the build-compiler \"$BUILD_CC\" works... $ECHO_C" >&6 cf_save_crossed=$cross_compiling @@ -4376,25 +4709,25 @@ echo $ECHO_N "checking if the build-compiler \"$BUILD_CC\" works... $ECHO_C" >&6 cf_ok_build_cc=unknown else cat >"conftest.$ac_ext" <<_ACEOF -#line 4379 "configure" +#line 4712 "configure" #include "confdefs.h" #include int main(int argc, char *argv[]) { - ${cf_cv_main_return:-return}(argc < 0 || argv == 0 || argv[0] == 0); + ${cf_cv_main_return:-return}(argc < 0 || argv == (void*)0 || argv[0] == (void*)0); } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:4389: \"$ac_link\"") >&5 +if { (eval echo "$as_me:4722: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:4392: \$? = $ac_status" >&5 + echo "$as_me:4725: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:4394: \"$ac_try\"") >&5 + { (eval echo "$as_me:4727: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:4397: \$? = $ac_status" >&5 + echo "$as_me:4730: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_ok_build_cc=yes else @@ -4409,12 +4742,12 @@ fi cross_compiling=$cf_save_crossed ac_link=$cf_save_ac_link - echo "$as_me:4412: result: $cf_ok_build_cc" >&5 + echo "$as_me:4745: result: $cf_ok_build_cc" >&5 echo "${ECHO_T}$cf_ok_build_cc" >&6 if test "$cf_ok_build_cc" != yes then - { { echo "$as_me:4417: error: Cross-build requires two compilers. + { { echo "$as_me:4750: error: Cross-build requires two compilers. Use --with-build-cc to specify the native compiler." >&5 echo "$as_me: error: Cross-build requires two compilers. Use --with-build-cc to specify the native compiler." >&2;} @@ -4439,7 +4772,7 @@ fi ### shared, for example. cf_list_models="" -echo "$as_me:4442: checking if you want to build shared C-objects" >&5 +echo "$as_me:4775: checking if you want to build shared C-objects" >&5 echo $ECHO_N "checking if you want to build shared C-objects... $ECHO_C" >&6 # Check whether --with-shared or --without-shared was given. @@ -4449,27 +4782,27 @@ if test "${with_shared+set}" = set; then else with_shared=no fi; -echo "$as_me:4452: result: $with_shared" >&5 +echo "$as_me:4785: result: $with_shared" >&5 echo "${ECHO_T}$with_shared" >&6 test "$with_shared" = "yes" && cf_list_models="$cf_list_models shared" -echo "$as_me:4456: checking for specified models" >&5 +echo "$as_me:4789: checking for specified models" >&5 echo $ECHO_N "checking for specified models... $ECHO_C" >&6 test -z "$cf_list_models" && cf_list_models=normal -echo "$as_me:4459: result: $cf_list_models" >&5 +echo "$as_me:4792: result: $cf_list_models" >&5 echo "${ECHO_T}$cf_list_models" >&6 ### Use the first model as the default, and save its suffix for use in building ### up test-applications. -echo "$as_me:4464: checking for default model" >&5 +echo "$as_me:4797: checking for default model" >&5 echo $ECHO_N "checking for default model... $ECHO_C" >&6 DFT_LWR_MODEL=`echo "$cf_list_models" | $AWK '{print $1}'` -echo "$as_me:4467: result: $DFT_LWR_MODEL" >&5 +echo "$as_me:4800: result: $DFT_LWR_MODEL" >&5 echo "${ECHO_T}$DFT_LWR_MODEL" >&6 DFT_UPR_MODEL=`echo "$DFT_LWR_MODEL" | sed y%abcdefghijklmnopqrstuvwxyz./-%ABCDEFGHIJKLMNOPQRSTUVWXYZ___%` -echo "$as_me:4472: checking for specific curses-directory" >&5 +echo "$as_me:4805: checking for specific curses-directory" >&5 echo $ECHO_N "checking for specific curses-directory... $ECHO_C" >&6 # Check whether --with-curses-dir or --without-curses-dir was given. @@ -4479,7 +4812,7 @@ if test "${with_curses_dir+set}" = set; then else cf_cv_curses_dir=no fi; -echo "$as_me:4482: result: $cf_cv_curses_dir" >&5 +echo "$as_me:4815: result: $cf_cv_curses_dir" >&5 echo "${ECHO_T}$cf_cv_curses_dir" >&6 if test -n "$cf_cv_curses_dir" && test "$cf_cv_curses_dir" != "no" @@ -4491,26 +4824,24 @@ else cf_path_syntax="$ac_default_prefix" fi -case ".$withval" in -(.\$\(*\)*|.\'*\'*) +case "x$withval" in +(x\$\(*\)*|x\'*\'*) ;; -(..|./*|.\\*) +(x.|x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; -(.[a-zA-Z]:[\\/]*) # OS/2 EMX - ;; -(.\$\{*prefix\}*|.\$\{*dir\}*) +(x\$\{*prefix\}*|x\$\{*dir\}*) eval withval="$withval" - case ".$withval" in - (.NONE/*) + case "x$withval" in + (xNONE/*) withval=`echo "$withval" | sed -e s%NONE%$cf_path_syntax%` ;; esac ;; -(.no|.NONE/*) +(xno|xNONE/*) withval=`echo "$withval" | sed -e s%NONE%$cf_path_syntax%` ;; (*) - { { echo "$as_me:4513: error: expected a pathname, not \"$withval\"" >&5 + { { echo "$as_me:4844: error: expected a pathname, not \"$withval\"" >&5 echo "$as_me: error: expected a pathname, not \"$withval\"" >&2;} { (exit 1); exit 1; }; } ;; @@ -4546,7 +4877,7 @@ if test -n "$cf_cv_curses_dir/include" ; then CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" cat >"conftest.$ac_ext" <<_ACEOF -#line 4549 "configure" +#line 4880 "configure" #include "confdefs.h" #include int @@ -4558,16 +4889,16 @@ printf("Hello") } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:4561: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:4892: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:4564: \$? = $ac_status" >&5 + echo "$as_me:4895: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:4567: \"$ac_try\"") >&5 + { (eval echo "$as_me:4898: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:4570: \$? = $ac_status" >&5 + echo "$as_me:4901: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -4584,7 +4915,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_have_incdir" = no ; then test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 -echo "${as_me:-configure}:4587: testing adding $cf_add_incdir to include-path ..." 1>&5 +echo "${as_me:-configure}:4918: testing adding $cf_add_incdir to include-path ..." 1>&5 CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" @@ -4620,7 +4951,7 @@ if test -n "$cf_cv_curses_dir/lib" ; then if test "$cf_have_libdir" = no ; then test -n "$verbose" && echo " adding $cf_add_libdir to library-path" 1>&6 -echo "${as_me:-configure}:4623: testing adding $cf_add_libdir to library-path ..." 1>&5 +echo "${as_me:-configure}:4954: testing adding $cf_add_libdir to library-path ..." 1>&5 LDFLAGS="-L$cf_add_libdir $LDFLAGS" fi @@ -4635,13 +4966,13 @@ cf_ncuconfig_root=ncurses cf_have_ncuconfig=no if test "x${PKG_CONFIG:=none}" != xnone; then - echo "$as_me:4638: checking pkg-config for $cf_ncuconfig_root" >&5 + echo "$as_me:4969: checking pkg-config for $cf_ncuconfig_root" >&5 echo $ECHO_N "checking pkg-config for $cf_ncuconfig_root... $ECHO_C" >&6 if "$PKG_CONFIG" --exists $cf_ncuconfig_root ; then - echo "$as_me:4641: result: yes" >&5 + echo "$as_me:4972: result: yes" >&5 echo "${ECHO_T}yes" >&6 - echo "$as_me:4644: checking if the $cf_ncuconfig_root package files work" >&5 + echo "$as_me:4975: checking if the $cf_ncuconfig_root package files work" >&5 echo $ECHO_N "checking if the $cf_ncuconfig_root package files work... $ECHO_C" >&6 cf_have_ncuconfig=unknown @@ -4774,7 +5105,7 @@ done LIBS="$cf_add_libs" cat >"conftest.$ac_ext" <<_ACEOF -#line 4777 "configure" +#line 5108 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -4786,37 +5117,37 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:4789: \"$ac_link\"") >&5 +if { (eval echo "$as_me:5120: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:4792: \$? = $ac_status" >&5 + echo "$as_me:5123: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:4795: \"$ac_try\"") >&5 + { (eval echo "$as_me:5126: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:4798: \$? = $ac_status" >&5 + echo "$as_me:5129: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then if test "$cross_compiling" = yes; then cf_test_ncuconfig=maybe else cat >"conftest.$ac_ext" <<_ACEOF -#line 4804 "configure" +#line 5135 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int main(void) { const char *xx = curses_version(); return (xx == 0); } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:4811: \"$ac_link\"") >&5 +if { (eval echo "$as_me:5142: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:4814: \$? = $ac_status" >&5 + echo "$as_me:5145: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:4816: \"$ac_try\"") >&5 + { (eval echo "$as_me:5147: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:4819: \$? = $ac_status" >&5 + echo "$as_me:5150: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_test_ncuconfig=yes else @@ -4847,6 +5178,20 @@ rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" ;; esac +for cf_required in $cf_ncuconfig_root +do + # check for duplicates + for cf_require_pkg in $REQUIRE_PKG + do + if test "$cf_required" = "$cf_require_pkg" + then + cf_required= + break + fi + done + test -n "$cf_required" && REQUIRE_PKG="$REQUIRE_PKG $cf_required" +done + for cf_add_cflags in $cf_pkg_cflags do case "x$cf_add_cflags" in @@ -4990,7 +5335,7 @@ done LIBS="$cf_add_libs" cat >"conftest.$ac_ext" <<_ACEOF -#line 4993 "configure" +#line 5338 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -5002,37 +5347,37 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:5005: \"$ac_link\"") >&5 +if { (eval echo "$as_me:5350: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:5008: \$? = $ac_status" >&5 + echo "$as_me:5353: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:5011: \"$ac_try\"") >&5 + { (eval echo "$as_me:5356: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5014: \$? = $ac_status" >&5 + echo "$as_me:5359: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then if test "$cross_compiling" = yes; then cf_have_ncuconfig=maybe else cat >"conftest.$ac_ext" <<_ACEOF -#line 5020 "configure" +#line 5365 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int main(void) { const char *xx = curses_version(); return (xx == 0); } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:5027: \"$ac_link\"") >&5 +if { (eval echo "$as_me:5372: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:5030: \$? = $ac_status" >&5 + echo "$as_me:5375: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:5032: \"$ac_try\"") >&5 + { (eval echo "$as_me:5377: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5035: \$? = $ac_status" >&5 + echo "$as_me:5380: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_have_ncuconfig=yes else @@ -5049,7 +5394,7 @@ cat "conftest.$ac_ext" >&5 cf_have_ncuconfig=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" - echo "$as_me:5052: result: $cf_have_ncuconfig" >&5 + echo "$as_me:5397: result: $cf_have_ncuconfig" >&5 echo "${ECHO_T}$cf_have_ncuconfig" >&6 test "$cf_have_ncuconfig" = maybe && cf_have_ncuconfig=yes if test "$cf_have_ncuconfig" != "yes" @@ -5065,7 +5410,7 @@ EOF NCURSES_CONFIG_PKG=$cf_ncuconfig_root -echo "$as_me:5068: checking for terminfo header" >&5 +echo "$as_me:5413: checking for terminfo header" >&5 echo $ECHO_N "checking for terminfo header... $ECHO_C" >&6 if test "${cf_cv_term_header+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -5083,7 +5428,7 @@ esac for cf_test in $cf_term_header "ncurses/term.h" "ncursesw/term.h" do cat >"conftest.$ac_ext" <<_ACEOF -#line 5086 "configure" +#line 5431 "configure" #include "confdefs.h" #include #include <${cf_cv_ncurses_header:-curses.h}> @@ -5098,16 +5443,16 @@ int x = auto_left_margin; (void)x } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:5101: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:5446: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:5104: \$? = $ac_status" >&5 + echo "$as_me:5449: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:5107: \"$ac_try\"") >&5 + { (eval echo "$as_me:5452: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5110: \$? = $ac_status" >&5 + echo "$as_me:5455: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_term_header="$cf_test" @@ -5123,7 +5468,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" done fi -echo "$as_me:5126: result: $cf_cv_term_header" >&5 +echo "$as_me:5471: result: $cf_cv_term_header" >&5 echo "${ECHO_T}$cf_cv_term_header" >&6 # Set definitions to allow ifdef'ing to accommodate subdirectories @@ -5158,7 +5503,7 @@ esac fi else - echo "$as_me:5161: result: no" >&5 + echo "$as_me:5506: result: no" >&5 echo "${ECHO_T}no" >&6 NCURSES_CONFIG_PKG=none fi @@ -5174,7 +5519,7 @@ if test -n "$ac_tool_prefix"; then do # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. set dummy $ac_tool_prefix$ac_prog; ac_word=$2 -echo "$as_me:5177: checking for $ac_word" >&5 +echo "$as_me:5522: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_NCURSES_CONFIG+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -5189,7 +5534,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_NCURSES_CONFIG="$ac_tool_prefix$ac_prog" -echo "$as_me:5192: found $ac_dir/$ac_word" >&5 +echo "$as_me:5537: found $ac_dir/$ac_word" >&5 break done @@ -5197,10 +5542,10 @@ fi fi NCURSES_CONFIG=$ac_cv_prog_NCURSES_CONFIG if test -n "$NCURSES_CONFIG"; then - echo "$as_me:5200: result: $NCURSES_CONFIG" >&5 + echo "$as_me:5545: result: $NCURSES_CONFIG" >&5 echo "${ECHO_T}$NCURSES_CONFIG" >&6 else - echo "$as_me:5203: result: no" >&5 + echo "$as_me:5548: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -5213,7 +5558,7 @@ if test -z "$NCURSES_CONFIG"; then do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:5216: checking for $ac_word" >&5 +echo "$as_me:5561: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_ac_ct_NCURSES_CONFIG+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -5228,7 +5573,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_ac_ct_NCURSES_CONFIG="$ac_prog" -echo "$as_me:5231: found $ac_dir/$ac_word" >&5 +echo "$as_me:5576: found $ac_dir/$ac_word" >&5 break done @@ -5236,10 +5581,10 @@ fi fi ac_ct_NCURSES_CONFIG=$ac_cv_prog_ac_ct_NCURSES_CONFIG if test -n "$ac_ct_NCURSES_CONFIG"; then - echo "$as_me:5239: result: $ac_ct_NCURSES_CONFIG" >&5 + echo "$as_me:5584: result: $ac_ct_NCURSES_CONFIG" >&5 echo "${ECHO_T}$ac_ct_NCURSES_CONFIG" >&6 else - echo "$as_me:5242: result: no" >&5 + echo "$as_me:5587: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -5396,7 +5741,7 @@ LIBS="$cf_add_libs" # even with config script, some packages use no-override for curses.h -echo "$as_me:5399: checking if we have identified curses headers" >&5 +echo "$as_me:5744: checking if we have identified curses headers" >&5 echo $ECHO_N "checking if we have identified curses headers... $ECHO_C" >&6 if test "${cf_cv_ncurses_header+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -5408,7 +5753,7 @@ for cf_header in \ curses.h ncurses/curses.h do cat >"conftest.$ac_ext" <<_ACEOF -#line 5411 "configure" +#line 5756 "configure" #include "confdefs.h" #include <${cf_header}> int @@ -5420,16 +5765,16 @@ initscr(); endwin() } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:5423: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:5768: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:5426: \$? = $ac_status" >&5 + echo "$as_me:5771: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:5429: \"$ac_try\"") >&5 + { (eval echo "$as_me:5774: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5432: \$? = $ac_status" >&5 + echo "$as_me:5777: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ncurses_header=$cf_header; break else @@ -5440,11 +5785,11 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" done fi -echo "$as_me:5443: result: $cf_cv_ncurses_header" >&5 +echo "$as_me:5788: result: $cf_cv_ncurses_header" >&5 echo "${ECHO_T}$cf_cv_ncurses_header" >&6 if test "$cf_cv_ncurses_header" = none ; then - { { echo "$as_me:5447: error: No curses header-files found" >&5 + { { echo "$as_me:5792: error: No curses header-files found" >&5 echo "$as_me: error: No curses header-files found" >&2;} { (exit 1); exit 1; }; } fi @@ -5454,23 +5799,23 @@ fi for ac_header in $cf_cv_ncurses_header do as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` -echo "$as_me:5457: checking for $ac_header" >&5 +echo "$as_me:5802: checking for $ac_header" >&5 echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 if eval "test \"\${$as_ac_Header+set}\" = set"; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 5463 "configure" +#line 5808 "configure" #include "confdefs.h" #include <$ac_header> _ACEOF -if { (eval echo "$as_me:5467: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:5812: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:5473: \$? = $ac_status" >&5 + echo "$as_me:5818: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -5489,7 +5834,7 @@ else fi rm -f conftest.err "conftest.$ac_ext" fi -echo "$as_me:5492: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 +echo "$as_me:5837: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then cat >>confdefs.h <"conftest.$ac_ext" <<_ACEOF -#line 5548 "configure" +#line 5893 "configure" #include "confdefs.h" #include int @@ -5557,16 +5902,16 @@ printf("Hello") } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:5560: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:5905: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:5563: \$? = $ac_status" >&5 + echo "$as_me:5908: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:5566: \"$ac_try\"") >&5 + { (eval echo "$as_me:5911: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5569: \$? = $ac_status" >&5 + echo "$as_me:5914: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -5583,7 +5928,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_have_incdir" = no ; then test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 -echo "${as_me:-configure}:5586: testing adding $cf_add_incdir to include-path ..." 1>&5 +echo "${as_me:-configure}:5931: testing adding $cf_add_incdir to include-path ..." 1>&5 CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" @@ -5602,7 +5947,7 @@ fi } -echo "$as_me:5605: checking for $cf_ncuhdr_root header in include-path" >&5 +echo "$as_me:5950: checking for $cf_ncuhdr_root header in include-path" >&5 echo $ECHO_N "checking for $cf_ncuhdr_root header in include-path... $ECHO_C" >&6 if test "${cf_cv_ncurses_h+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -5614,7 +5959,7 @@ else do cat >"conftest.$ac_ext" <<_ACEOF -#line 5617 "configure" +#line 5962 "configure" #include "confdefs.h" #include <$cf_header> @@ -5638,16 +5983,16 @@ printf("old\\n"); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:5641: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:5986: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:5644: \$? = $ac_status" >&5 + echo "$as_me:5989: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:5647: \"$ac_try\"") >&5 + { (eval echo "$as_me:5992: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5650: \$? = $ac_status" >&5 + echo "$as_me:5995: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ncurses_h=$cf_header @@ -5662,14 +6007,14 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" done fi -echo "$as_me:5665: result: $cf_cv_ncurses_h" >&5 +echo "$as_me:6010: result: $cf_cv_ncurses_h" >&5 echo "${ECHO_T}$cf_cv_ncurses_h" >&6 if test "$cf_cv_ncurses_h" != no ; then cf_cv_ncurses_header=$cf_cv_ncurses_h else -echo "$as_me:5672: checking for $cf_ncuhdr_root include-path" >&5 +echo "$as_me:6017: checking for $cf_ncuhdr_root include-path" >&5 echo $ECHO_N "checking for $cf_ncuhdr_root include-path... $ECHO_C" >&6 if test "${cf_cv_ncurses_h2+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -5790,7 +6135,7 @@ if test -n "$cf_incdir" ; then CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" cat >"conftest.$ac_ext" <<_ACEOF -#line 5793 "configure" +#line 6138 "configure" #include "confdefs.h" #include int @@ -5802,16 +6147,16 @@ printf("Hello") } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:5805: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:6150: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:5808: \$? = $ac_status" >&5 + echo "$as_me:6153: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:5811: \"$ac_try\"") >&5 + { (eval echo "$as_me:6156: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5814: \$? = $ac_status" >&5 + echo "$as_me:6159: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -5828,7 +6173,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_have_incdir" = no ; then test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 -echo "${as_me:-configure}:5831: testing adding $cf_add_incdir to include-path ..." 1>&5 +echo "${as_me:-configure}:6176: testing adding $cf_add_incdir to include-path ..." 1>&5 CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" @@ -5851,7 +6196,7 @@ fi do cat >"conftest.$ac_ext" <<_ACEOF -#line 5854 "configure" +#line 6199 "configure" #include "confdefs.h" #include <$cf_header> @@ -5875,16 +6220,16 @@ printf("old\\n"); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:5878: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:6223: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:5881: \$? = $ac_status" >&5 + echo "$as_me:6226: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:5884: \"$ac_try\"") >&5 + { (eval echo "$as_me:6229: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5887: \$? = $ac_status" >&5 + echo "$as_me:6232: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ncurses_h2=$cf_header @@ -5905,12 +6250,12 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" CPPFLAGS="$cf_save2_CPPFLAGS" test "$cf_cv_ncurses_h2" != no && break done - test "$cf_cv_ncurses_h2" = no && { { echo "$as_me:5908: error: not found" >&5 + test "$cf_cv_ncurses_h2" = no && { { echo "$as_me:6253: error: not found" >&5 echo "$as_me: error: not found" >&2;} { (exit 1); exit 1; }; } fi -echo "$as_me:5913: result: $cf_cv_ncurses_h2" >&5 +echo "$as_me:6258: result: $cf_cv_ncurses_h2" >&5 echo "${ECHO_T}$cf_cv_ncurses_h2" >&6 cf_1st_incdir=`echo "$cf_cv_ncurses_h2" | sed -e 's%/[^/]*$%%'` @@ -5946,7 +6291,7 @@ if test -n "$cf_1st_incdir" ; then CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" cat >"conftest.$ac_ext" <<_ACEOF -#line 5949 "configure" +#line 6294 "configure" #include "confdefs.h" #include int @@ -5958,16 +6303,16 @@ printf("Hello") } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:5961: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:6306: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:5964: \$? = $ac_status" >&5 + echo "$as_me:6309: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:5967: \"$ac_try\"") >&5 + { (eval echo "$as_me:6312: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:5970: \$? = $ac_status" >&5 + echo "$as_me:6315: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -5984,7 +6329,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_have_incdir" = no ; then test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 -echo "${as_me:-configure}:5987: testing adding $cf_add_incdir to include-path ..." 1>&5 +echo "${as_me:-configure}:6332: testing adding $cf_add_incdir to include-path ..." 1>&5 CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" @@ -6032,7 +6377,7 @@ EOF ;; esac -echo "$as_me:6035: checking for terminfo header" >&5 +echo "$as_me:6380: checking for terminfo header" >&5 echo $ECHO_N "checking for terminfo header... $ECHO_C" >&6 if test "${cf_cv_term_header+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -6050,7 +6395,7 @@ esac for cf_test in $cf_term_header "ncurses/term.h" "ncursesw/term.h" do cat >"conftest.$ac_ext" <<_ACEOF -#line 6053 "configure" +#line 6398 "configure" #include "confdefs.h" #include #include <${cf_cv_ncurses_header:-curses.h}> @@ -6065,16 +6410,16 @@ int x = auto_left_margin; (void)x } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:6068: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:6413: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:6071: \$? = $ac_status" >&5 + echo "$as_me:6416: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:6074: \"$ac_try\"") >&5 + { (eval echo "$as_me:6419: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6077: \$? = $ac_status" >&5 + echo "$as_me:6422: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_term_header="$cf_test" @@ -6090,7 +6435,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" done fi -echo "$as_me:6093: result: $cf_cv_term_header" >&5 +echo "$as_me:6438: result: $cf_cv_term_header" >&5 echo "${ECHO_T}$cf_cv_term_header" >&6 # Set definitions to allow ifdef'ing to accommodate subdirectories @@ -6128,7 +6473,7 @@ cat >>confdefs.h <<\EOF #define NCURSES 1 EOF -echo "$as_me:6131: checking for ncurses version" >&5 +echo "$as_me:6476: checking for ncurses version" >&5 echo $ECHO_N "checking for ncurses version... $ECHO_C" >&6 if test "${cf_cv_ncurses_version+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -6154,10 +6499,10 @@ Autoconf "old" #endif EOF cf_try="$ac_cpp conftest.$ac_ext 2>&5 | grep '^Autoconf ' >conftest.out" - { (eval echo "$as_me:6157: \"$cf_try\"") >&5 + { (eval echo "$as_me:6502: \"$cf_try\"") >&5 (eval $cf_try) 2>&5 ac_status=$? - echo "$as_me:6160: \$? = $ac_status" >&5 + echo "$as_me:6505: \$? = $ac_status" >&5 (exit "$ac_status"); } if test -f conftest.out ; then cf_out=`sed -e 's%^Autoconf %%' -e 's%^[^"]*"%%' -e 's%".*%%' conftest.out` @@ -6167,7 +6512,7 @@ EOF else cat >"conftest.$ac_ext" <<_ACEOF -#line 6170 "configure" +#line 6515 "configure" #include "confdefs.h" $ac_includes_default @@ -6194,15 +6539,15 @@ int main(void) } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:6197: \"$ac_link\"") >&5 +if { (eval echo "$as_me:6542: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6200: \$? = $ac_status" >&5 + echo "$as_me:6545: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:6202: \"$ac_try\"") >&5 + { (eval echo "$as_me:6547: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6205: \$? = $ac_status" >&5 + echo "$as_me:6550: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ncurses_version=`cat $cf_tempfile` @@ -6216,7 +6561,7 @@ fi rm -f "$cf_tempfile" fi -echo "$as_me:6219: result: $cf_cv_ncurses_version" >&5 +echo "$as_me:6564: result: $cf_cv_ncurses_version" >&5 echo "${ECHO_T}$cf_cv_ncurses_version" >&6 test "$cf_cv_ncurses_version" = no || cat >>confdefs.h <<\EOF @@ -6229,7 +6574,7 @@ cf_nculib_root=ncurses # to link gpm. cf_ncurses_LIBS="" cf_ncurses_SAVE="$LIBS" -echo "$as_me:6232: checking for Gpm_Open in -lgpm" >&5 +echo "$as_me:6577: checking for Gpm_Open in -lgpm" >&5 echo $ECHO_N "checking for Gpm_Open in -lgpm... $ECHO_C" >&6 if test "${ac_cv_lib_gpm_Gpm_Open+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -6237,7 +6582,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-lgpm $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 6240 "configure" +#line 6585 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -6256,16 +6601,16 @@ Gpm_Open (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6259: \"$ac_link\"") >&5 +if { (eval echo "$as_me:6604: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6262: \$? = $ac_status" >&5 + echo "$as_me:6607: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6265: \"$ac_try\"") >&5 + { (eval echo "$as_me:6610: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6268: \$? = $ac_status" >&5 + echo "$as_me:6613: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_gpm_Gpm_Open=yes else @@ -6276,10 +6621,10 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:6279: result: $ac_cv_lib_gpm_Gpm_Open" >&5 +echo "$as_me:6624: result: $ac_cv_lib_gpm_Gpm_Open" >&5 echo "${ECHO_T}$ac_cv_lib_gpm_Gpm_Open" >&6 if test "$ac_cv_lib_gpm_Gpm_Open" = yes; then - echo "$as_me:6282: checking for initscr in -lgpm" >&5 + echo "$as_me:6627: checking for initscr in -lgpm" >&5 echo $ECHO_N "checking for initscr in -lgpm... $ECHO_C" >&6 if test "${ac_cv_lib_gpm_initscr+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -6287,7 +6632,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-lgpm $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 6290 "configure" +#line 6635 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -6306,16 +6651,16 @@ initscr (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6309: \"$ac_link\"") >&5 +if { (eval echo "$as_me:6654: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6312: \$? = $ac_status" >&5 + echo "$as_me:6657: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6315: \"$ac_try\"") >&5 + { (eval echo "$as_me:6660: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6318: \$? = $ac_status" >&5 + echo "$as_me:6663: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_gpm_initscr=yes else @@ -6326,7 +6671,7 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:6329: result: $ac_cv_lib_gpm_initscr" >&5 +echo "$as_me:6674: result: $ac_cv_lib_gpm_initscr" >&5 echo "${ECHO_T}$ac_cv_lib_gpm_initscr" >&6 if test "$ac_cv_lib_gpm_initscr" = yes; then LIBS="$cf_ncurses_SAVE" @@ -6341,7 +6686,7 @@ case "$host_os" in # This is only necessary if you are linking against an obsolete # version of ncurses (but it should do no harm, since it is static). if test "$cf_nculib_root" = ncurses ; then - echo "$as_me:6344: checking for tgoto in -lmytinfo" >&5 + echo "$as_me:6689: checking for tgoto in -lmytinfo" >&5 echo $ECHO_N "checking for tgoto in -lmytinfo... $ECHO_C" >&6 if test "${ac_cv_lib_mytinfo_tgoto+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -6349,7 +6694,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-lmytinfo $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 6352 "configure" +#line 6697 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -6368,16 +6713,16 @@ tgoto (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6371: \"$ac_link\"") >&5 +if { (eval echo "$as_me:6716: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6374: \$? = $ac_status" >&5 + echo "$as_me:6719: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6377: \"$ac_try\"") >&5 + { (eval echo "$as_me:6722: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6380: \$? = $ac_status" >&5 + echo "$as_me:6725: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_mytinfo_tgoto=yes else @@ -6388,7 +6733,7 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:6391: result: $ac_cv_lib_mytinfo_tgoto" >&5 +echo "$as_me:6736: result: $ac_cv_lib_mytinfo_tgoto" >&5 echo "${ECHO_T}$ac_cv_lib_mytinfo_tgoto" >&6 if test "$ac_cv_lib_mytinfo_tgoto" = yes; then cf_ncurses_LIBS="-lmytinfo $cf_ncurses_LIBS" @@ -6437,13 +6782,13 @@ else eval 'cf_cv_have_lib_'"$cf_nculib_root"'=no' cf_libdir="" - echo "$as_me:6440: checking for initscr" >&5 + echo "$as_me:6785: checking for initscr" >&5 echo $ECHO_N "checking for initscr... $ECHO_C" >&6 if test "${ac_cv_func_initscr+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 6446 "configure" +#line 6791 "configure" #include "confdefs.h" #define initscr autoconf_temporary #include /* least-intrusive standard header which defines gcc2 __stub macros */ @@ -6474,16 +6819,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6477: \"$ac_link\"") >&5 +if { (eval echo "$as_me:6822: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6480: \$? = $ac_status" >&5 + echo "$as_me:6825: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6483: \"$ac_try\"") >&5 + { (eval echo "$as_me:6828: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6486: \$? = $ac_status" >&5 + echo "$as_me:6831: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_func_initscr=yes else @@ -6493,18 +6838,18 @@ ac_cv_func_initscr=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:6496: result: $ac_cv_func_initscr" >&5 +echo "$as_me:6841: result: $ac_cv_func_initscr" >&5 echo "${ECHO_T}$ac_cv_func_initscr" >&6 if test "$ac_cv_func_initscr" = yes; then eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' else cf_save_LIBS="$LIBS" - echo "$as_me:6503: checking for initscr in -l$cf_nculib_root" >&5 + echo "$as_me:6848: checking for initscr in -l$cf_nculib_root" >&5 echo $ECHO_N "checking for initscr in -l$cf_nculib_root... $ECHO_C" >&6 LIBS="-l$cf_nculib_root $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 6507 "configure" +#line 6852 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -6516,25 +6861,25 @@ initscr() } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6519: \"$ac_link\"") >&5 +if { (eval echo "$as_me:6864: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6522: \$? = $ac_status" >&5 + echo "$as_me:6867: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6525: \"$ac_try\"") >&5 + { (eval echo "$as_me:6870: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6528: \$? = $ac_status" >&5 + echo "$as_me:6873: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:6530: result: yes" >&5 + echo "$as_me:6875: result: yes" >&5 echo "${ECHO_T}yes" >&6 eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:6537: result: no" >&5 +echo "$as_me:6882: result: no" >&5 echo "${ECHO_T}no" >&6 cf_search= @@ -6602,11 +6947,11 @@ cf_search="$cf_library_path_list $cf_search" for cf_libdir in $cf_search do - echo "$as_me:6605: checking for -l$cf_nculib_root in $cf_libdir" >&5 + echo "$as_me:6950: checking for -l$cf_nculib_root in $cf_libdir" >&5 echo $ECHO_N "checking for -l$cf_nculib_root in $cf_libdir... $ECHO_C" >&6 LIBS="-L$cf_libdir -l$cf_nculib_root $cf_save_LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 6609 "configure" +#line 6954 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -6618,25 +6963,25 @@ initscr() } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6621: \"$ac_link\"") >&5 +if { (eval echo "$as_me:6966: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6624: \$? = $ac_status" >&5 + echo "$as_me:6969: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6627: \"$ac_try\"") >&5 + { (eval echo "$as_me:6972: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6630: \$? = $ac_status" >&5 + echo "$as_me:6975: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:6632: result: yes" >&5 + echo "$as_me:6977: result: yes" >&5 echo "${ECHO_T}yes" >&6 eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' break else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:6639: result: no" >&5 +echo "$as_me:6984: result: no" >&5 echo "${ECHO_T}no" >&6 LIBS="$cf_save_LIBS" fi @@ -6651,7 +6996,7 @@ fi eval 'cf_found_library="$cf_cv_have_lib_'"$cf_nculib_root"\" if test "$cf_found_library" = no ; then - { { echo "$as_me:6654: error: Cannot link $cf_nculib_root library" >&5 + { { echo "$as_me:6999: error: Cannot link $cf_nculib_root library" >&5 echo "$as_me: error: Cannot link $cf_nculib_root library" >&2;} { (exit 1); exit 1; }; } fi @@ -6659,7 +7004,7 @@ fi fi if test -n "$cf_ncurses_LIBS" ; then - echo "$as_me:6662: checking if we can link $cf_nculib_root without $cf_ncurses_LIBS" >&5 + echo "$as_me:7007: checking if we can link $cf_nculib_root without $cf_ncurses_LIBS" >&5 echo $ECHO_N "checking if we can link $cf_nculib_root without $cf_ncurses_LIBS... $ECHO_C" >&6 cf_ncurses_SAVE="$LIBS" for p in $cf_ncurses_LIBS ; do @@ -6669,7 +7014,7 @@ echo $ECHO_N "checking if we can link $cf_nculib_root without $cf_ncurses_LIBS.. fi done cat >"conftest.$ac_ext" <<_ACEOF -#line 6672 "configure" +#line 7017 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -6681,23 +7026,23 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6684: \"$ac_link\"") >&5 +if { (eval echo "$as_me:7029: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6687: \$? = $ac_status" >&5 + echo "$as_me:7032: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6690: \"$ac_try\"") >&5 + { (eval echo "$as_me:7035: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6693: \$? = $ac_status" >&5 + echo "$as_me:7038: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:6695: result: yes" >&5 + echo "$as_me:7040: result: yes" >&5 echo "${ECHO_T}yes" >&6 else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:6700: result: no" >&5 +echo "$as_me:7045: result: no" >&5 echo "${ECHO_T}no" >&6 LIBS="$cf_ncurses_SAVE" fi @@ -6715,40 +7060,131 @@ else NCURSES_CONFIG=none fi -echo "$as_me:6718: checking if you want wide-character code" >&5 -echo $ECHO_N "checking if you want wide-character code... $ECHO_C" >&6 +echo "$as_me:7063: checking for specified curses library type" >&5 +echo $ECHO_N "checking for specified curses library type... $ECHO_C" >&6 -# Check whether --enable-widec or --disable-widec was given. -if test "${enable_widec+set}" = set; then - enableval="$enable_widec" - with_widec=$enableval +# Check whether --with-screen or --without-screen was given. +if test "${with_screen+set}" = set; then + withval="$with_screen" + cf_cv_screen=$withval else - with_widec=no + cf_cv_screen=ncurses fi; -echo "$as_me:6728: result: $with_widec" >&5 -echo "${ECHO_T}$with_widec" >&6 -if test "$with_widec" = yes ; then -for ac_header in wchar.h +case $cf_cv_screen in +(curses|curses_*) + +echo "$as_me:7077: checking for extra include directories" >&5 +echo $ECHO_N "checking for extra include directories... $ECHO_C" >&6 +if test "${cf_cv_curses_incdir+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + +cf_cv_curses_incdir=no +case "$host_os" in +(hpux10.*) + if test "x$cf_cv_screen" = "xcurses_colr" + then + test -d /usr/include/curses_colr && \ + cf_cv_curses_incdir="-I/usr/include/curses_colr" + fi + ;; +(sunos3*|sunos4*) + if test "x$cf_cv_screen" = "xcurses_5lib" + then + test -d /usr/5lib && \ + test -d /usr/5include && \ + cf_cv_curses_incdir="-I/usr/5include" + fi + ;; +esac + +fi +echo "$as_me:7103: result: $cf_cv_curses_incdir" >&5 +echo "${ECHO_T}$cf_cv_curses_incdir" >&6 +if test "$cf_cv_curses_incdir" != no +then + + test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " + CPPFLAGS="${CPPFLAGS}$cf_cv_curses_incdir" + +fi + +echo "$as_me:7113: checking if we have identified curses headers" >&5 +echo $ECHO_N "checking if we have identified curses headers... $ECHO_C" >&6 +if test "${cf_cv_ncurses_header+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + +cf_cv_ncurses_header=none +for cf_header in \ + ncurses.h \ + curses.h ncurses/ncurses.h ncurses/curses.h +do +cat >"conftest.$ac_ext" <<_ACEOF +#line 7125 "configure" +#include "confdefs.h" +#include <${cf_header}> +int +main (void) +{ +initscr(); endwin() + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:7137: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:7140: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:7143: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7146: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_cv_ncurses_header=$cf_header; break +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" +done + +fi +echo "$as_me:7157: result: $cf_cv_ncurses_header" >&5 +echo "${ECHO_T}$cf_cv_ncurses_header" >&6 + +if test "$cf_cv_ncurses_header" = none ; then + { { echo "$as_me:7161: error: No curses header-files found" >&5 +echo "$as_me: error: No curses header-files found" >&2;} + { (exit 1); exit 1; }; } +fi + +# cheat, to get the right #define's for HAVE_NCURSES_H, etc. + +for ac_header in $cf_cv_ncurses_header do as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` -echo "$as_me:6735: checking for $ac_header" >&5 +echo "$as_me:7171: checking for $ac_header" >&5 echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 if eval "test \"\${$as_ac_Header+set}\" = set"; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 6741 "configure" +#line 7177 "configure" #include "confdefs.h" #include <$ac_header> _ACEOF -if { (eval echo "$as_me:6745: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:7181: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:6751: \$? = $ac_status" >&5 + echo "$as_me:7187: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -6767,7 +7203,7 @@ else fi rm -f conftest.err "conftest.$ac_ext" fi -echo "$as_me:6770: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 +echo "$as_me:7206: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then cat >>confdefs.h <&5 +echo "$as_me:7216: checking for terminfo header" >&5 +echo $ECHO_N "checking for terminfo header... $ECHO_C" >&6 +if test "${cf_cv_term_header+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + +case "${cf_cv_ncurses_header}" in +(*/ncurses.h|*/ncursesw.h) + cf_term_header=`echo "$cf_cv_ncurses_header" | sed -e 's%ncurses[^.]*\.h$%term.h%'` + ;; +(*) + cf_term_header=term.h + ;; +esac + +for cf_test in $cf_term_header "ncurses/term.h" "ncursesw/term.h" +do +cat >"conftest.$ac_ext" <<_ACEOF +#line 7234 "configure" +#include "confdefs.h" +#include +#include <${cf_cv_ncurses_header:-curses.h}> +#include <$cf_test> + +int +main (void) +{ +int x = auto_left_margin; (void)x + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:7249: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:7252: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:7255: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7258: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + + cf_cv_term_header="$cf_test" +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 + + cf_cv_term_header=unknown + +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" + test "$cf_cv_term_header" != unknown && break +done + +fi +echo "$as_me:7274: result: $cf_cv_term_header" >&5 +echo "${ECHO_T}$cf_cv_term_header" >&6 + +# Set definitions to allow ifdef'ing to accommodate subdirectories + +case "$cf_cv_term_header" in +(*term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_TERM_H 1 +EOF + + ;; +esac + +case "$cf_cv_term_header" in +(ncurses/term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSES_TERM_H 1 +EOF + + ;; +(ncursesw/term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSESW_TERM_H 1 +EOF + + ;; +esac + +echo "$as_me:7306: checking for ncurses version" >&5 +echo $ECHO_N "checking for ncurses version... $ECHO_C" >&6 +if test "${cf_cv_ncurses_version+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + + cf_cv_ncurses_version=no + cf_tempfile=out$$ + rm -f "$cf_tempfile" + if test "$cross_compiling" = yes; then + + # This will not work if the preprocessor splits the line after the + # Autoconf token. The 'unproto' program does that. + cat > "conftest.$ac_ext" < +#undef Autoconf +#ifdef NCURSES_VERSION +Autoconf NCURSES_VERSION +#else +#ifdef __NCURSES_H +Autoconf "old" +#endif +; +#endif +EOF + cf_try="$ac_cpp conftest.$ac_ext 2>&5 | grep '^Autoconf ' >conftest.out" + { (eval echo "$as_me:7332: \"$cf_try\"") >&5 + (eval $cf_try) 2>&5 + ac_status=$? + echo "$as_me:7335: \$? = $ac_status" >&5 + (exit "$ac_status"); } + if test -f conftest.out ; then + cf_out=`sed -e 's%^Autoconf %%' -e 's%^[^"]*"%%' -e 's%".*%%' conftest.out` + test -n "$cf_out" && cf_cv_ncurses_version="$cf_out" + rm -f conftest.out + fi + +else + cat >"conftest.$ac_ext" <<_ACEOF +#line 7345 "configure" +#include "confdefs.h" + +$ac_includes_default + +#include <${cf_cv_ncurses_header:-curses.h}> + +int main(void) +{ + FILE *fp = fopen("$cf_tempfile", "w"); +#ifdef NCURSES_VERSION +# ifdef NCURSES_VERSION_PATCH + fprintf(fp, "%s.%d\\n", NCURSES_VERSION, NCURSES_VERSION_PATCH); +# else + fprintf(fp, "%s\\n", NCURSES_VERSION); +# endif +#else +# ifdef __NCURSES_H + fprintf(fp, "old\\n"); +# else + #error expected ncurses header to define __NCURSES_H +# endif +#endif + ${cf_cv_main_return:-return}(0); +} +_ACEOF +rm -f "conftest$ac_exeext" +if { (eval echo "$as_me:7372: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:7375: \$? = $ac_status" >&5 + (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' + { (eval echo "$as_me:7377: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7380: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + + cf_cv_ncurses_version=`cat $cf_tempfile` +else + echo "$as_me: program exited with status $ac_status" >&5 +echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +fi +rm -f core ./core.* ./*.core "conftest$ac_exeext" "conftest.$ac_objext" "conftest.$ac_ext" +fi + rm -f "$cf_tempfile" + +fi +echo "$as_me:7394: result: $cf_cv_ncurses_version" >&5 +echo "${ECHO_T}$cf_cv_ncurses_version" >&6 +test "$cf_cv_ncurses_version" = no || +cat >>confdefs.h <<\EOF +#define NCURSES 1 +EOF + +echo "$as_me:7401: checking if we have identified curses libraries" >&5 +echo $ECHO_N "checking if we have identified curses libraries... $ECHO_C" >&6 +cat >"conftest.$ac_ext" <<_ACEOF +#line 7404 "configure" +#include "confdefs.h" +#include <${cf_cv_ncurses_header:-curses.h}> +int +main (void) +{ +initscr(); endwin() + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:7416: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:7419: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:7422: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7425: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_result=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_result=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +echo "$as_me:7434: result: $cf_result" >&5 +echo "${ECHO_T}$cf_result" >&6 + +if test "$cf_result" = no ; then +case "$host_os" in +(freebsd*) + echo "$as_me:7440: checking for tgoto in -lmytinfo" >&5 +echo $ECHO_N "checking for tgoto in -lmytinfo... $ECHO_C" >&6 +if test "${ac_cv_lib_mytinfo_tgoto+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-lmytinfo $LIBS" +cat >"conftest.$ac_ext" <<_ACEOF +#line 7448 "configure" +#include "confdefs.h" + +/* Override any gcc2 internal prototype to avoid an error. */ +#ifdef __cplusplus +extern "C" +#endif +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char tgoto (void); +int +main (void) +{ +tgoto (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:7467: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:7470: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:7473: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7476: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_lib_mytinfo_tgoto=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_lib_mytinfo_tgoto=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +LIBS=$ac_check_lib_save_LIBS +fi +echo "$as_me:7487: result: $ac_cv_lib_mytinfo_tgoto" >&5 +echo "${ECHO_T}$ac_cv_lib_mytinfo_tgoto" >&6 +if test "$ac_cv_lib_mytinfo_tgoto" = yes; then + +cf_add_libs="$LIBS" +# reverse order +cf_add_0lib= +for cf_add_1lib in -lmytinfo; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done +# filter duplicates +for cf_add_1lib in $cf_add_0lib; do + for cf_add_2lib in $cf_add_libs; do + if test "x$cf_add_1lib" = "x$cf_add_2lib"; then + cf_add_1lib= + break + fi + done + test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" +done +LIBS="$cf_add_libs" + +fi + + ;; +(hpux10.*) + # Looking at HPUX 10.20, the Hcurses library is the oldest (1997), cur_colr + # next (1998), and xcurses "newer" (2000). There is no header file for + # Hcurses; the subdirectory curses_colr has the headers (curses.h and + # term.h) for cur_colr + if test "x$cf_cv_screen" = "xcurses_colr" + then + echo "$as_me:7517: checking for initscr in -lcur_colr" >&5 +echo $ECHO_N "checking for initscr in -lcur_colr... $ECHO_C" >&6 +if test "${ac_cv_lib_cur_colr_initscr+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-lcur_colr $LIBS" +cat >"conftest.$ac_ext" <<_ACEOF +#line 7525 "configure" +#include "confdefs.h" + +/* Override any gcc2 internal prototype to avoid an error. */ +#ifdef __cplusplus +extern "C" +#endif +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char initscr (void); +int +main (void) +{ +initscr (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:7544: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:7547: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:7550: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7553: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_lib_cur_colr_initscr=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_lib_cur_colr_initscr=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +LIBS=$ac_check_lib_save_LIBS +fi +echo "$as_me:7564: result: $ac_cv_lib_cur_colr_initscr" >&5 +echo "${ECHO_T}$ac_cv_lib_cur_colr_initscr" >&6 +if test "$ac_cv_lib_cur_colr_initscr" = yes; then + +cf_add_libs="$LIBS" +# reverse order +cf_add_0lib= +for cf_add_1lib in -lcur_colr; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done +# filter duplicates +for cf_add_1lib in $cf_add_0lib; do + for cf_add_2lib in $cf_add_libs; do + if test "x$cf_add_1lib" = "x$cf_add_2lib"; then + cf_add_1lib= + break + fi + done + test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" +done +LIBS="$cf_add_libs" + + ac_cv_func_initscr=yes + +else + + echo "$as_me:7588: checking for initscr in -lHcurses" >&5 +echo $ECHO_N "checking for initscr in -lHcurses... $ECHO_C" >&6 +if test "${ac_cv_lib_Hcurses_initscr+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-lHcurses $LIBS" +cat >"conftest.$ac_ext" <<_ACEOF +#line 7596 "configure" +#include "confdefs.h" + +/* Override any gcc2 internal prototype to avoid an error. */ +#ifdef __cplusplus +extern "C" +#endif +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char initscr (void); +int +main (void) +{ +initscr (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:7615: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:7618: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:7621: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7624: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_lib_Hcurses_initscr=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_lib_Hcurses_initscr=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +LIBS=$ac_check_lib_save_LIBS +fi +echo "$as_me:7635: result: $ac_cv_lib_Hcurses_initscr" >&5 +echo "${ECHO_T}$ac_cv_lib_Hcurses_initscr" >&6 +if test "$ac_cv_lib_Hcurses_initscr" = yes; then + + # HP's header uses __HP_CURSES, but user claims _HP_CURSES. + +cf_add_libs="$LIBS" +# reverse order +cf_add_0lib= +for cf_add_1lib in -lHcurses; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done +# filter duplicates +for cf_add_1lib in $cf_add_0lib; do + for cf_add_2lib in $cf_add_libs; do + if test "x$cf_add_1lib" = "x$cf_add_2lib"; then + cf_add_1lib= + break + fi + done + test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" +done +LIBS="$cf_add_libs" + + test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " + CPPFLAGS="${CPPFLAGS}-D__HP_CURSES -D_HP_CURSES" + + ac_cv_func_initscr=yes + +fi + +fi + + fi + ;; +(linux*) + case `arch 2>/dev/null` in + (x86_64) + if test -d /lib64 + then + +if test -n "/lib64" ; then + for cf_add_libdir in /lib64 + do + if test "$cf_add_libdir" = /usr/lib ; then + : + elif test -d "$cf_add_libdir" + then + cf_have_libdir=no + if test -n "$LDFLAGS$LIBS" ; then + # a loop is needed to ensure we can add subdirs of existing dirs + for cf_test_libdir in $LDFLAGS $LIBS ; do + if test ".$cf_test_libdir" = ".-L$cf_add_libdir" ; then + cf_have_libdir=yes; break + fi + done + fi + if test "$cf_have_libdir" = no ; then + test -n "$verbose" && echo " adding $cf_add_libdir to library-path" 1>&6 + +echo "${as_me:-configure}:7693: testing adding $cf_add_libdir to library-path ..." 1>&5 + + LDFLAGS="-L$cf_add_libdir $LDFLAGS" + fi + fi + done +fi + + else + +if test -n "/lib" ; then + for cf_add_libdir in /lib + do + if test "$cf_add_libdir" = /usr/lib ; then + : + elif test -d "$cf_add_libdir" + then + cf_have_libdir=no + if test -n "$LDFLAGS$LIBS" ; then + # a loop is needed to ensure we can add subdirs of existing dirs + for cf_test_libdir in $LDFLAGS $LIBS ; do + if test ".$cf_test_libdir" = ".-L$cf_add_libdir" ; then + cf_have_libdir=yes; break + fi + done + fi + if test "$cf_have_libdir" = no ; then + test -n "$verbose" && echo " adding $cf_add_libdir to library-path" 1>&6 + +echo "${as_me:-configure}:7722: testing adding $cf_add_libdir to library-path ..." 1>&5 + + LDFLAGS="-L$cf_add_libdir $LDFLAGS" + fi + fi + done +fi + + fi + ;; + (*) + +if test -n "/lib" ; then + for cf_add_libdir in /lib + do + if test "$cf_add_libdir" = /usr/lib ; then + : + elif test -d "$cf_add_libdir" + then + cf_have_libdir=no + if test -n "$LDFLAGS$LIBS" ; then + # a loop is needed to ensure we can add subdirs of existing dirs + for cf_test_libdir in $LDFLAGS $LIBS ; do + if test ".$cf_test_libdir" = ".-L$cf_add_libdir" ; then + cf_have_libdir=yes; break + fi + done + fi + if test "$cf_have_libdir" = no ; then + test -n "$verbose" && echo " adding $cf_add_libdir to library-path" 1>&6 + +echo "${as_me:-configure}:7753: testing adding $cf_add_libdir to library-path ..." 1>&5 + + LDFLAGS="-L$cf_add_libdir $LDFLAGS" + fi + fi + done +fi + + ;; + esac + ;; +(sunos3*|sunos4*) + if test "x$cf_cv_screen" = "xcurses_5lib" + then + if test -d /usr/5lib ; then + +if test -n "/usr/5lib" ; then + for cf_add_libdir in /usr/5lib + do + if test "$cf_add_libdir" = /usr/lib ; then + : + elif test -d "$cf_add_libdir" + then + cf_have_libdir=no + if test -n "$LDFLAGS$LIBS" ; then + # a loop is needed to ensure we can add subdirs of existing dirs + for cf_test_libdir in $LDFLAGS $LIBS ; do + if test ".$cf_test_libdir" = ".-L$cf_add_libdir" ; then + cf_have_libdir=yes; break + fi + done + fi + if test "$cf_have_libdir" = no ; then + test -n "$verbose" && echo " adding $cf_add_libdir to library-path" 1>&6 + +echo "${as_me:-configure}:7788: testing adding $cf_add_libdir to library-path ..." 1>&5 + + LDFLAGS="-L$cf_add_libdir $LDFLAGS" + fi + fi + done +fi + +cf_add_libs="$LIBS" +# reverse order +cf_add_0lib= +for cf_add_1lib in -lcurses -ltermcap; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done +# filter duplicates +for cf_add_1lib in $cf_add_0lib; do + for cf_add_2lib in $cf_add_libs; do + if test "x$cf_add_1lib" = "x$cf_add_2lib"; then + cf_add_1lib= + break + fi + done + test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" +done +LIBS="$cf_add_libs" + + fi + fi + ac_cv_func_initscr=yes + ;; +esac + +if test ".$ac_cv_func_initscr" != .yes ; then + cf_save_LIBS="$LIBS" + + if test ".${cf_cv_ncurses_version:-no}" != .no + then + cf_check_list="ncurses curses cursesX" + else + cf_check_list="cursesX curses ncurses" + fi + + # Check for library containing tgoto. Do this before curses library + # because it may be needed to link the test-case for initscr. + if test "x$cf_term_lib" = x + then + echo "$as_me:7832: checking for tgoto" >&5 +echo $ECHO_N "checking for tgoto... $ECHO_C" >&6 +if test "${ac_cv_func_tgoto+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + cat >"conftest.$ac_ext" <<_ACEOF +#line 7838 "configure" +#include "confdefs.h" +#define tgoto autoconf_temporary +#include /* least-intrusive standard header which defines gcc2 __stub macros */ +#undef tgoto + +#ifdef __cplusplus +extern "C" +#endif + +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char tgoto (void); + +int +main (void) +{ + +/* The GNU C library defines stubs for functions which it implements + to always fail with ENOSYS. Some functions are actually named + something starting with __ and the normal name is an alias. */ +#if defined (__stub_tgoto) || defined (__stub___tgoto) +#error found stub for tgoto +#endif + + return tgoto (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:7869: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:7872: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:7875: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7878: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_func_tgoto=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_func_tgoto=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +fi +echo "$as_me:7888: result: $ac_cv_func_tgoto" >&5 +echo "${ECHO_T}$ac_cv_func_tgoto" >&6 +if test "$ac_cv_func_tgoto" = yes; then + cf_term_lib=predefined +else + + for cf_term_lib in $cf_check_list otermcap termcap tinfo termlib unknown + do + as_ac_Lib=`echo "ac_cv_lib_$cf_term_lib''_tgoto" | $as_tr_sh` +echo "$as_me:7897: checking for tgoto in -l$cf_term_lib" >&5 +echo $ECHO_N "checking for tgoto in -l$cf_term_lib... $ECHO_C" >&6 +if eval "test \"\${$as_ac_Lib+set}\" = set"; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-l$cf_term_lib $LIBS" +cat >"conftest.$ac_ext" <<_ACEOF +#line 7905 "configure" +#include "confdefs.h" + +/* Override any gcc2 internal prototype to avoid an error. */ +#ifdef __cplusplus +extern "C" +#endif +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char tgoto (void); +int +main (void) +{ +tgoto (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:7924: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:7927: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:7930: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7933: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + eval "$as_ac_Lib=yes" +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +eval "$as_ac_Lib=no" +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +LIBS=$ac_check_lib_save_LIBS +fi +echo "$as_me:7944: result: `eval echo '${'"$as_ac_Lib"'}'`" >&5 +echo "${ECHO_T}`eval echo '${'"$as_ac_Lib"'}'`" >&6 +if test "`eval echo '${'"$as_ac_Lib"'}'`" = yes; then + + : "${cf_nculib_root:=$cf_term_lib}" + break + +fi + + done + +fi + + fi + + # Check for library containing initscr + test "$cf_term_lib" != predefined && test "$cf_term_lib" != unknown && LIBS="-l$cf_term_lib $cf_save_LIBS" + if test "x$cf_curs_lib" = x + then + for cf_curs_lib in $cf_check_list xcurses jcurses pdcurses unknown + do + LIBS="-l$cf_curs_lib $cf_save_LIBS" + if test "$cf_term_lib" = unknown || test "$cf_term_lib" = "$cf_curs_lib" ; then + echo "$as_me:7967: checking if we can link with $cf_curs_lib library" >&5 +echo $ECHO_N "checking if we can link with $cf_curs_lib library... $ECHO_C" >&6 + cat >"conftest.$ac_ext" <<_ACEOF +#line 7970 "configure" +#include "confdefs.h" +#include <${cf_cv_ncurses_header:-curses.h}> +int +main (void) +{ +initscr() + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:7982: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:7985: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:7988: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:7991: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_result=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_result=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" + echo "$as_me:8000: result: $cf_result" >&5 +echo "${ECHO_T}$cf_result" >&6 + test "$cf_result" = yes && break + elif test "$cf_curs_lib" = "$cf_term_lib" ; then + cf_result=no + elif test "$cf_term_lib" != predefined ; then + echo "$as_me:8006: checking if we need both $cf_curs_lib and $cf_term_lib libraries" >&5 +echo $ECHO_N "checking if we need both $cf_curs_lib and $cf_term_lib libraries... $ECHO_C" >&6 + cat >"conftest.$ac_ext" <<_ACEOF +#line 8009 "configure" +#include "confdefs.h" +#include <${cf_cv_ncurses_header:-curses.h}> +int +main (void) +{ +initscr(); endwin(); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:8021: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:8024: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:8027: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:8030: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_result=no +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 + + LIBS="-l$cf_curs_lib -l$cf_term_lib $cf_save_LIBS" + cat >"conftest.$ac_ext" <<_ACEOF +#line 8039 "configure" +#include "confdefs.h" +#include <${cf_cv_ncurses_header:-curses.h}> +int +main (void) +{ +initscr() + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:8051: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:8054: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:8057: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:8060: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_result=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_result=error +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" + +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" + echo "$as_me:8072: result: $cf_result" >&5 +echo "${ECHO_T}$cf_result" >&6 + test "$cf_result" != error && break + fi + done + fi + test "$cf_curs_lib" = unknown && { { echo "$as_me:8078: error: no curses library found" >&5 +echo "$as_me: error: no curses library found" >&2;} + { (exit 1); exit 1; }; } +fi +fi + + ;; +(ncursesw*) + +for ac_header in wchar.h +do +as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +echo "$as_me:8090: checking for $ac_header" >&5 +echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 +if eval "test \"\${$as_ac_Header+set}\" = set"; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + cat >"conftest.$ac_ext" <<_ACEOF +#line 8096 "configure" +#include "confdefs.h" +#include <$ac_header> +_ACEOF +if { (eval echo "$as_me:8100: \"$ac_cpp "conftest.$ac_ext"\"") >&5 + (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 + ac_status=$? + $EGREP -v '^ *\+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + echo "$as_me:8106: \$? = $ac_status" >&5 + (exit "$ac_status"); } >/dev/null; then + if test -s conftest.err; then + ac_cpp_err=$ac_c_preproc_warn_flag + else + ac_cpp_err= + fi +else + ac_cpp_err=yes +fi +if test -z "$ac_cpp_err"; then + eval "$as_ac_Header=yes" +else + echo "$as_me: failed program was:" >&5 + cat "conftest.$ac_ext" >&5 + eval "$as_ac_Header=no" +fi +rm -f conftest.err "conftest.$ac_ext" +fi +echo "$as_me:8125: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 +echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 +if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then + cat >>confdefs.h <&5 echo $ECHO_N "checking for multibyte character support... $ECHO_C" >&6 if test "${cf_cv_utf8_lib+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -6785,7 +8140,7 @@ else cf_save_LIBS="$LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 6788 "configure" +#line 8143 "configure" #include "confdefs.h" $ac_includes_default @@ -6802,16 +8157,16 @@ putwc(0,0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6805: \"$ac_link\"") >&5 +if { (eval echo "$as_me:8160: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6808: \$? = $ac_status" >&5 + echo "$as_me:8163: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6811: \"$ac_try\"") >&5 + { (eval echo "$as_me:8166: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6814: \$? = $ac_status" >&5 + echo "$as_me:8169: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_utf8_lib=yes else @@ -6819,16 +8174,16 @@ else cat "conftest.$ac_ext" >&5 # If the linkage is not already in the $CPPFLAGS/$LDFLAGS configuration, these -# will be set on completion of the AC_TRY_LINK below. +# will be set on completion of the AC_LINK_IFELSE below. cf_cv_header_path_utf8= cf_cv_library_path_utf8= -echo "${as_me:-configure}:6826: testing Starting FIND_LINKAGE(utf8,) ..." 1>&5 +echo "${as_me:-configure}:8181: testing Starting FIND_LINKAGE(utf8,) ..." 1>&5 cf_save_LIBS="$LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 6831 "configure" +#line 8186 "configure" #include "confdefs.h" #include @@ -6841,16 +8196,16 @@ putwc(0,0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6844: \"$ac_link\"") >&5 +if { (eval echo "$as_me:8199: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6847: \$? = $ac_status" >&5 + echo "$as_me:8202: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6850: \"$ac_try\"") >&5 + { (eval echo "$as_me:8205: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6853: \$? = $ac_status" >&5 + echo "$as_me:8208: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_find_linkage_utf8=yes @@ -6864,7 +8219,7 @@ cat "conftest.$ac_ext" >&5 LIBS="-lutf8 $cf_save_LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 6867 "configure" +#line 8222 "configure" #include "confdefs.h" #include @@ -6877,16 +8232,16 @@ putwc(0,0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:6880: \"$ac_link\"") >&5 +if { (eval echo "$as_me:8235: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:6883: \$? = $ac_status" >&5 + echo "$as_me:8238: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:6886: \"$ac_try\"") >&5 + { (eval echo "$as_me:8241: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:6889: \$? = $ac_status" >&5 + echo "$as_me:8244: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_find_linkage_utf8=yes @@ -6903,9 +8258,9 @@ cat "conftest.$ac_ext" >&5 test -n "$verbose" && echo " find linkage for utf8 library" 1>&6 -echo "${as_me:-configure}:6906: testing find linkage for utf8 library ..." 1>&5 +echo "${as_me:-configure}:8261: testing find linkage for utf8 library ..." 1>&5 -echo "${as_me:-configure}:6908: testing Searching for headers in FIND_LINKAGE(utf8,) ..." 1>&5 +echo "${as_me:-configure}:8263: testing Searching for headers in FIND_LINKAGE(utf8,) ..." 1>&5 cf_save_CPPFLAGS="$CPPFLAGS" cf_test_CPPFLAGS="$CPPFLAGS" @@ -6996,7 +8351,7 @@ cf_search="$cf_search $cf_header_path_list" if test -d "$cf_cv_header_path_utf8" ; then test -n "$verbose" && echo " ... testing $cf_cv_header_path_utf8" 1>&6 -echo "${as_me:-configure}:6999: testing ... testing $cf_cv_header_path_utf8 ..." 1>&5 +echo "${as_me:-configure}:8354: testing ... testing $cf_cv_header_path_utf8 ..." 1>&5 CPPFLAGS="$cf_save_CPPFLAGS" @@ -7004,7 +8359,7 @@ echo "${as_me:-configure}:6999: testing ... testing $cf_cv_header_path_utf8 ..." CPPFLAGS="${CPPFLAGS}-I$cf_cv_header_path_utf8" cat >"conftest.$ac_ext" <<_ACEOF -#line 7007 "configure" +#line 8362 "configure" #include "confdefs.h" #include @@ -7017,21 +8372,21 @@ putwc(0,0); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:7020: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:8375: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:7023: \$? = $ac_status" >&5 + echo "$as_me:8378: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:7026: \"$ac_try\"") >&5 + { (eval echo "$as_me:8381: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:7029: \$? = $ac_status" >&5 + echo "$as_me:8384: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then test -n "$verbose" && echo " ... found utf8 headers in $cf_cv_header_path_utf8" 1>&6 -echo "${as_me:-configure}:7034: testing ... found utf8 headers in $cf_cv_header_path_utf8 ..." 1>&5 +echo "${as_me:-configure}:8389: testing ... found utf8 headers in $cf_cv_header_path_utf8 ..." 1>&5 cf_cv_find_linkage_utf8=maybe cf_test_CPPFLAGS="$CPPFLAGS" @@ -7049,7 +8404,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_cv_find_linkage_utf8" = maybe ; then -echo "${as_me:-configure}:7052: testing Searching for utf8 library in FIND_LINKAGE(utf8,) ..." 1>&5 +echo "${as_me:-configure}:8407: testing Searching for utf8 library in FIND_LINKAGE(utf8,) ..." 1>&5 cf_save_LIBS="$LIBS" cf_save_LDFLAGS="$LDFLAGS" @@ -7124,13 +8479,13 @@ cf_search="$cf_library_path_list $cf_search" if test -d "$cf_cv_library_path_utf8" ; then test -n "$verbose" && echo " ... testing $cf_cv_library_path_utf8" 1>&6 -echo "${as_me:-configure}:7127: testing ... testing $cf_cv_library_path_utf8 ..." 1>&5 +echo "${as_me:-configure}:8482: testing ... testing $cf_cv_library_path_utf8 ..." 1>&5 CPPFLAGS="$cf_test_CPPFLAGS" LIBS="-lutf8 $cf_save_LIBS" LDFLAGS="$cf_save_LDFLAGS -L$cf_cv_library_path_utf8" cat >"conftest.$ac_ext" <<_ACEOF -#line 7133 "configure" +#line 8488 "configure" #include "confdefs.h" #include @@ -7143,21 +8498,21 @@ putwc(0,0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:7146: \"$ac_link\"") >&5 +if { (eval echo "$as_me:8501: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:7149: \$? = $ac_status" >&5 + echo "$as_me:8504: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:7152: \"$ac_try\"") >&5 + { (eval echo "$as_me:8507: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:7155: \$? = $ac_status" >&5 + echo "$as_me:8510: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then test -n "$verbose" && echo " ... found utf8 library in $cf_cv_library_path_utf8" 1>&6 -echo "${as_me:-configure}:7160: testing ... found utf8 library in $cf_cv_library_path_utf8 ..." 1>&5 +echo "${as_me:-configure}:8515: testing ... found utf8 library in $cf_cv_library_path_utf8 ..." 1>&5 cf_cv_find_linkage_utf8=yes cf_cv_library_file_utf8="-lutf8" @@ -7199,7 +8554,7 @@ fi fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:7202: result: $cf_cv_utf8_lib" >&5 +echo "$as_me:8557: result: $cf_cv_utf8_lib" >&5 echo "${ECHO_T}$cf_cv_utf8_lib" >&6 # HAVE_LIBUTF8_H is used by ncurses if curses.h is shared between @@ -7237,7 +8592,7 @@ if test -n "$cf_cv_header_path_utf8" ; then CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" cat >"conftest.$ac_ext" <<_ACEOF -#line 7240 "configure" +#line 8595 "configure" #include "confdefs.h" #include int @@ -7249,16 +8604,16 @@ printf("Hello") } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:7252: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:8607: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:7255: \$? = $ac_status" >&5 + echo "$as_me:8610: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:7258: \"$ac_try\"") >&5 + { (eval echo "$as_me:8613: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:7261: \$? = $ac_status" >&5 + echo "$as_me:8616: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -7275,7 +8630,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_have_incdir" = no ; then test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 -echo "${as_me:-configure}:7278: testing adding $cf_add_incdir to include-path ..." 1>&5 +echo "${as_me:-configure}:8633: testing adding $cf_add_incdir to include-path ..." 1>&5 CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" @@ -7311,7 +8666,7 @@ if test -n "$cf_cv_library_path_utf8" ; then if test "$cf_have_libdir" = no ; then test -n "$verbose" && echo " adding $cf_add_libdir to library-path" 1>&6 -echo "${as_me:-configure}:7314: testing adding $cf_add_libdir to library-path ..." 1>&5 +echo "${as_me:-configure}:8669: testing adding $cf_add_libdir to library-path ..." 1>&5 LDFLAGS="-L$cf_add_libdir $LDFLAGS" fi @@ -7337,17 +8692,17 @@ LIBS="$cf_add_libs" fi -cf_ncuconfig_root=ncursesw +cf_ncuconfig_root=$cf_cv_screen cf_have_ncuconfig=no if test "x${PKG_CONFIG:=none}" != xnone; then - echo "$as_me:7344: checking pkg-config for $cf_ncuconfig_root" >&5 + echo "$as_me:8699: checking pkg-config for $cf_ncuconfig_root" >&5 echo $ECHO_N "checking pkg-config for $cf_ncuconfig_root... $ECHO_C" >&6 if "$PKG_CONFIG" --exists $cf_ncuconfig_root ; then - echo "$as_me:7347: result: yes" >&5 + echo "$as_me:8702: result: yes" >&5 echo "${ECHO_T}yes" >&6 - echo "$as_me:7350: checking if the $cf_ncuconfig_root package files work" >&5 + echo "$as_me:8705: checking if the $cf_ncuconfig_root package files work" >&5 echo $ECHO_N "checking if the $cf_ncuconfig_root package files work... $ECHO_C" >&6 cf_have_ncuconfig=unknown @@ -7480,7 +8835,7 @@ done LIBS="$cf_add_libs" cat >"conftest.$ac_ext" <<_ACEOF -#line 7483 "configure" +#line 8838 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -7492,37 +8847,37 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:7495: \"$ac_link\"") >&5 +if { (eval echo "$as_me:8850: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:7498: \$? = $ac_status" >&5 + echo "$as_me:8853: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:7501: \"$ac_try\"") >&5 + { (eval echo "$as_me:8856: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:7504: \$? = $ac_status" >&5 + echo "$as_me:8859: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then if test "$cross_compiling" = yes; then cf_test_ncuconfig=maybe else cat >"conftest.$ac_ext" <<_ACEOF -#line 7510 "configure" +#line 8865 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int main(void) { const char *xx = curses_version(); return (xx == 0); } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:7517: \"$ac_link\"") >&5 +if { (eval echo "$as_me:8872: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:7520: \$? = $ac_status" >&5 + echo "$as_me:8875: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:7522: \"$ac_try\"") >&5 + { (eval echo "$as_me:8877: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:7525: \$? = $ac_status" >&5 + echo "$as_me:8880: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_test_ncuconfig=yes else @@ -7553,6 +8908,20 @@ rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" ;; esac +for cf_required in $cf_ncuconfig_root +do + # check for duplicates + for cf_require_pkg in $REQUIRE_PKG + do + if test "$cf_required" = "$cf_require_pkg" + then + cf_required= + break + fi + done + test -n "$cf_required" && REQUIRE_PKG="$REQUIRE_PKG $cf_required" +done + for cf_add_cflags in $cf_pkg_cflags do case "x$cf_add_cflags" in @@ -7696,7 +9065,7 @@ done LIBS="$cf_add_libs" cat >"conftest.$ac_ext" <<_ACEOF -#line 7699 "configure" +#line 9068 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -7708,37 +9077,37 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:7711: \"$ac_link\"") >&5 +if { (eval echo "$as_me:9080: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:7714: \$? = $ac_status" >&5 + echo "$as_me:9083: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:7717: \"$ac_try\"") >&5 + { (eval echo "$as_me:9086: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:7720: \$? = $ac_status" >&5 + echo "$as_me:9089: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then if test "$cross_compiling" = yes; then cf_have_ncuconfig=maybe else cat >"conftest.$ac_ext" <<_ACEOF -#line 7726 "configure" +#line 9095 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int main(void) { const char *xx = curses_version(); return (xx == 0); } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:7733: \"$ac_link\"") >&5 +if { (eval echo "$as_me:9102: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:7736: \$? = $ac_status" >&5 + echo "$as_me:9105: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:7738: \"$ac_try\"") >&5 + { (eval echo "$as_me:9107: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:7741: \$? = $ac_status" >&5 + echo "$as_me:9110: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_have_ncuconfig=yes else @@ -7755,7 +9124,7 @@ cat "conftest.$ac_ext" >&5 cf_have_ncuconfig=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" - echo "$as_me:7758: result: $cf_have_ncuconfig" >&5 + echo "$as_me:9127: result: $cf_have_ncuconfig" >&5 echo "${ECHO_T}$cf_have_ncuconfig" >&6 test "$cf_have_ncuconfig" = maybe && cf_have_ncuconfig=yes if test "$cf_have_ncuconfig" != "yes" @@ -7771,7 +9140,7 @@ EOF NCURSES_CONFIG_PKG=$cf_ncuconfig_root -echo "$as_me:7774: checking for terminfo header" >&5 +echo "$as_me:9143: checking for terminfo header" >&5 echo $ECHO_N "checking for terminfo header... $ECHO_C" >&6 if test "${cf_cv_term_header+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -7789,7 +9158,7 @@ esac for cf_test in $cf_term_header "ncurses/term.h" "ncursesw/term.h" do cat >"conftest.$ac_ext" <<_ACEOF -#line 7792 "configure" +#line 9161 "configure" #include "confdefs.h" #include #include <${cf_cv_ncurses_header:-curses.h}> @@ -7804,16 +9173,16 @@ int x = auto_left_margin; (void)x } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:7807: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:9176: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:7810: \$? = $ac_status" >&5 + echo "$as_me:9179: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:7813: \"$ac_try\"") >&5 + { (eval echo "$as_me:9182: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:7816: \$? = $ac_status" >&5 + echo "$as_me:9185: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_term_header="$cf_test" @@ -7829,7 +9198,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" done fi -echo "$as_me:7832: result: $cf_cv_term_header" >&5 +echo "$as_me:9201: result: $cf_cv_term_header" >&5 echo "${ECHO_T}$cf_cv_term_header" >&6 # Set definitions to allow ifdef'ing to accommodate subdirectories @@ -7864,7 +9233,7 @@ esac fi else - echo "$as_me:7867: result: no" >&5 + echo "$as_me:9236: result: no" >&5 echo "${ECHO_T}no" >&6 NCURSES_CONFIG_PKG=none fi @@ -7880,7 +9249,7 @@ if test -n "$ac_tool_prefix"; then do # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. set dummy $ac_tool_prefix$ac_prog; ac_word=$2 -echo "$as_me:7883: checking for $ac_word" >&5 +echo "$as_me:9252: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_NCURSES_CONFIG+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -7895,7 +9264,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_NCURSES_CONFIG="$ac_tool_prefix$ac_prog" -echo "$as_me:7898: found $ac_dir/$ac_word" >&5 +echo "$as_me:9267: found $ac_dir/$ac_word" >&5 break done @@ -7903,10 +9272,10 @@ fi fi NCURSES_CONFIG=$ac_cv_prog_NCURSES_CONFIG if test -n "$NCURSES_CONFIG"; then - echo "$as_me:7906: result: $NCURSES_CONFIG" >&5 + echo "$as_me:9275: result: $NCURSES_CONFIG" >&5 echo "${ECHO_T}$NCURSES_CONFIG" >&6 else - echo "$as_me:7909: result: no" >&5 + echo "$as_me:9278: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -7919,7 +9288,7 @@ if test -z "$NCURSES_CONFIG"; then do # Extract the first word of "$ac_prog", so it can be a program name with args. set dummy $ac_prog; ac_word=$2 -echo "$as_me:7922: checking for $ac_word" >&5 +echo "$as_me:9291: checking for $ac_word" >&5 echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 if test "${ac_cv_prog_ac_ct_NCURSES_CONFIG+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -7934,7 +9303,7 @@ for ac_dir in $ac_dummy; do test -z "$ac_dir" && ac_dir=. $as_executable_p "$ac_dir/$ac_word" || continue ac_cv_prog_ac_ct_NCURSES_CONFIG="$ac_prog" -echo "$as_me:7937: found $ac_dir/$ac_word" >&5 +echo "$as_me:9306: found $ac_dir/$ac_word" >&5 break done @@ -7942,10 +9311,10 @@ fi fi ac_ct_NCURSES_CONFIG=$ac_cv_prog_ac_ct_NCURSES_CONFIG if test -n "$ac_ct_NCURSES_CONFIG"; then - echo "$as_me:7945: result: $ac_ct_NCURSES_CONFIG" >&5 + echo "$as_me:9314: result: $ac_ct_NCURSES_CONFIG" >&5 echo "${ECHO_T}$ac_ct_NCURSES_CONFIG" >&6 else - echo "$as_me:7948: result: no" >&5 + echo "$as_me:9317: result: no" >&5 echo "${ECHO_T}no" >&6 fi @@ -8102,7 +9471,7 @@ LIBS="$cf_add_libs" # even with config script, some packages use no-override for curses.h -echo "$as_me:8105: checking if we have identified curses headers" >&5 +echo "$as_me:9474: checking if we have identified curses headers" >&5 echo $ECHO_N "checking if we have identified curses headers... $ECHO_C" >&6 if test "${cf_cv_ncurses_header+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -8110,11 +9479,11 @@ else cf_cv_ncurses_header=none for cf_header in \ - ncurses.h ncursesw/ncurses.h \ - curses.h ncursesw/curses.h + ncurses.h $cf_cv_screen/ncurses.h \ + curses.h $cf_cv_screen/curses.h do cat >"conftest.$ac_ext" <<_ACEOF -#line 8117 "configure" +#line 9486 "configure" #include "confdefs.h" #include <${cf_header}> int @@ -8126,16 +9495,16 @@ initscr(); endwin() } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:8129: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:9498: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:8132: \$? = $ac_status" >&5 + echo "$as_me:9501: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:8135: \"$ac_try\"") >&5 + { (eval echo "$as_me:9504: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8138: \$? = $ac_status" >&5 + echo "$as_me:9507: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ncurses_header=$cf_header; break else @@ -8146,11 +9515,11 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" done fi -echo "$as_me:8149: result: $cf_cv_ncurses_header" >&5 +echo "$as_me:9518: result: $cf_cv_ncurses_header" >&5 echo "${ECHO_T}$cf_cv_ncurses_header" >&6 if test "$cf_cv_ncurses_header" = none ; then - { { echo "$as_me:8153: error: No curses header-files found" >&5 + { { echo "$as_me:9522: error: No curses header-files found" >&5 echo "$as_me: error: No curses header-files found" >&2;} { (exit 1); exit 1; }; } fi @@ -8160,23 +9529,23 @@ fi for ac_header in $cf_cv_ncurses_header do as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` -echo "$as_me:8163: checking for $ac_header" >&5 +echo "$as_me:9532: checking for $ac_header" >&5 echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 if eval "test \"\${$as_ac_Header+set}\" = set"; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 8169 "configure" +#line 9538 "configure" #include "confdefs.h" #include <$ac_header> _ACEOF -if { (eval echo "$as_me:8173: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:9542: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:8179: \$? = $ac_status" >&5 + echo "$as_me:9548: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -8195,7 +9564,7 @@ else fi rm -f conftest.err "conftest.$ac_ext" fi -echo "$as_me:8198: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 +echo "$as_me:9567: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then cat >>confdefs.h <"conftest.$ac_ext" <<_ACEOF -#line 8254 "configure" +#line 9623 "configure" #include "confdefs.h" #include int @@ -8263,16 +9632,16 @@ printf("Hello") } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:8266: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:9635: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:8269: \$? = $ac_status" >&5 + echo "$as_me:9638: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:8272: \"$ac_try\"") >&5 + { (eval echo "$as_me:9641: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8275: \$? = $ac_status" >&5 + echo "$as_me:9644: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -8289,7 +9658,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_have_incdir" = no ; then test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 -echo "${as_me:-configure}:8292: testing adding $cf_add_incdir to include-path ..." 1>&5 +echo "${as_me:-configure}:9661: testing adding $cf_add_incdir to include-path ..." 1>&5 CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" @@ -8308,7 +9677,7 @@ fi } -echo "$as_me:8311: checking for $cf_ncuhdr_root header in include-path" >&5 +echo "$as_me:9680: checking for $cf_ncuhdr_root header in include-path" >&5 echo $ECHO_N "checking for $cf_ncuhdr_root header in include-path... $ECHO_C" >&6 if test "${cf_cv_ncurses_h+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -8320,13 +9689,9 @@ else do cat >"conftest.$ac_ext" <<_ACEOF -#line 8323 "configure" +#line 9692 "configure" #include "confdefs.h" -#define _XOPEN_SOURCE_EXTENDED -#undef HAVE_LIBUTF8_H /* in case we used CF_UTF8_LIB */ -#define HAVE_LIBUTF8_H /* to force ncurses' header file to use cchar_t */ - #include <$cf_header> int main (void) @@ -8334,10 +9699,6 @@ main (void) #ifdef NCURSES_VERSION -#ifndef WACS_BSSB - #error WACS_BSSB is not defined -#endif - printf("%s\\n", NCURSES_VERSION); #else #ifdef __NCURSES_H @@ -8352,16 +9713,16 @@ printf("old\\n"); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:8355: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:9716: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:8358: \$? = $ac_status" >&5 + echo "$as_me:9719: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:8361: \"$ac_try\"") >&5 + { (eval echo "$as_me:9722: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8364: \$? = $ac_status" >&5 + echo "$as_me:9725: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ncurses_h=$cf_header @@ -8376,14 +9737,14 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" done fi -echo "$as_me:8379: result: $cf_cv_ncurses_h" >&5 +echo "$as_me:9740: result: $cf_cv_ncurses_h" >&5 echo "${ECHO_T}$cf_cv_ncurses_h" >&6 if test "$cf_cv_ncurses_h" != no ; then cf_cv_ncurses_header=$cf_cv_ncurses_h else -echo "$as_me:8386: checking for $cf_ncuhdr_root include-path" >&5 +echo "$as_me:9747: checking for $cf_ncuhdr_root include-path" >&5 echo $ECHO_N "checking for $cf_ncuhdr_root include-path... $ECHO_C" >&6 if test "${cf_cv_ncurses_h2+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -8504,7 +9865,7 @@ if test -n "$cf_incdir" ; then CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" cat >"conftest.$ac_ext" <<_ACEOF -#line 8507 "configure" +#line 9868 "configure" #include "confdefs.h" #include int @@ -8516,16 +9877,16 @@ printf("Hello") } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:8519: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:9880: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:8522: \$? = $ac_status" >&5 + echo "$as_me:9883: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:8525: \"$ac_try\"") >&5 + { (eval echo "$as_me:9886: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8528: \$? = $ac_status" >&5 + echo "$as_me:9889: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -8542,7 +9903,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_have_incdir" = no ; then test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 -echo "${as_me:-configure}:8545: testing adding $cf_add_incdir to include-path ..." 1>&5 +echo "${as_me:-configure}:9906: testing adding $cf_add_incdir to include-path ..." 1>&5 CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" @@ -8565,7 +9926,7 @@ fi do cat >"conftest.$ac_ext" <<_ACEOF -#line 8568 "configure" +#line 9929 "configure" #include "confdefs.h" #include <$cf_header> @@ -8589,16 +9950,16 @@ printf("old\\n"); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:8592: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:9953: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:8595: \$? = $ac_status" >&5 + echo "$as_me:9956: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:8598: \"$ac_try\"") >&5 + { (eval echo "$as_me:9959: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8601: \$? = $ac_status" >&5 + echo "$as_me:9962: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ncurses_h2=$cf_header @@ -8619,12 +9980,12 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" CPPFLAGS="$cf_save2_CPPFLAGS" test "$cf_cv_ncurses_h2" != no && break done - test "$cf_cv_ncurses_h2" = no && { { echo "$as_me:8622: error: not found" >&5 + test "$cf_cv_ncurses_h2" = no && { { echo "$as_me:9983: error: not found" >&5 echo "$as_me: error: not found" >&2;} { (exit 1); exit 1; }; } fi -echo "$as_me:8627: result: $cf_cv_ncurses_h2" >&5 +echo "$as_me:9988: result: $cf_cv_ncurses_h2" >&5 echo "${ECHO_T}$cf_cv_ncurses_h2" >&6 cf_1st_incdir=`echo "$cf_cv_ncurses_h2" | sed -e 's%/[^/]*$%%'` @@ -8660,7 +10021,7 @@ if test -n "$cf_1st_incdir" ; then CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" cat >"conftest.$ac_ext" <<_ACEOF -#line 8663 "configure" +#line 10024 "configure" #include "confdefs.h" #include int @@ -8672,16 +10033,16 @@ printf("Hello") } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:8675: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:10036: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:8678: \$? = $ac_status" >&5 + echo "$as_me:10039: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:8681: \"$ac_try\"") >&5 + { (eval echo "$as_me:10042: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8684: \$? = $ac_status" >&5 + echo "$as_me:10045: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -8698,7 +10059,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_have_incdir" = no ; then test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 -echo "${as_me:-configure}:8701: testing adding $cf_add_incdir to include-path ..." 1>&5 +echo "${as_me:-configure}:10062: testing adding $cf_add_incdir to include-path ..." 1>&5 CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" @@ -8746,7 +10107,7 @@ EOF ;; esac -echo "$as_me:8749: checking for terminfo header" >&5 +echo "$as_me:10110: checking for terminfo header" >&5 echo $ECHO_N "checking for terminfo header... $ECHO_C" >&6 if test "${cf_cv_term_header+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -8764,7 +10125,7 @@ esac for cf_test in $cf_term_header "ncurses/term.h" "ncursesw/term.h" do cat >"conftest.$ac_ext" <<_ACEOF -#line 8767 "configure" +#line 10128 "configure" #include "confdefs.h" #include #include <${cf_cv_ncurses_header:-curses.h}> @@ -8779,16 +10140,16 @@ int x = auto_left_margin; (void)x } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:8782: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:10143: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:8785: \$? = $ac_status" >&5 + echo "$as_me:10146: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:8788: \"$ac_try\"") >&5 + { (eval echo "$as_me:10149: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8791: \$? = $ac_status" >&5 + echo "$as_me:10152: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_term_header="$cf_test" @@ -8804,7 +10165,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" done fi -echo "$as_me:8807: result: $cf_cv_term_header" >&5 +echo "$as_me:10168: result: $cf_cv_term_header" >&5 echo "${ECHO_T}$cf_cv_term_header" >&6 # Set definitions to allow ifdef'ing to accommodate subdirectories @@ -8842,7 +10203,7 @@ cat >>confdefs.h <<\EOF #define NCURSES 1 EOF -echo "$as_me:8845: checking for ncurses version" >&5 +echo "$as_me:10206: checking for ncurses version" >&5 echo $ECHO_N "checking for ncurses version... $ECHO_C" >&6 if test "${cf_cv_ncurses_version+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -8868,10 +10229,10 @@ Autoconf "old" #endif EOF cf_try="$ac_cpp conftest.$ac_ext 2>&5 | grep '^Autoconf ' >conftest.out" - { (eval echo "$as_me:8871: \"$cf_try\"") >&5 + { (eval echo "$as_me:10232: \"$cf_try\"") >&5 (eval $cf_try) 2>&5 ac_status=$? - echo "$as_me:8874: \$? = $ac_status" >&5 + echo "$as_me:10235: \$? = $ac_status" >&5 (exit "$ac_status"); } if test -f conftest.out ; then cf_out=`sed -e 's%^Autoconf %%' -e 's%^[^"]*"%%' -e 's%".*%%' conftest.out` @@ -8881,7 +10242,7 @@ EOF else cat >"conftest.$ac_ext" <<_ACEOF -#line 8884 "configure" +#line 10245 "configure" #include "confdefs.h" $ac_includes_default @@ -8908,15 +10269,15 @@ int main(void) } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:8911: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10272: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:8914: \$? = $ac_status" >&5 + echo "$as_me:10275: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:8916: \"$ac_try\"") >&5 + { (eval echo "$as_me:10277: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8919: \$? = $ac_status" >&5 + echo "$as_me:10280: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ncurses_version=`cat $cf_tempfile` @@ -8930,20 +10291,20 @@ fi rm -f "$cf_tempfile" fi -echo "$as_me:8933: result: $cf_cv_ncurses_version" >&5 +echo "$as_me:10294: result: $cf_cv_ncurses_version" >&5 echo "${ECHO_T}$cf_cv_ncurses_version" >&6 test "$cf_cv_ncurses_version" = no || cat >>confdefs.h <<\EOF #define NCURSES 1 EOF -cf_nculib_root=ncursesw +cf_nculib_root=$cf_cv_screen # This works, except for the special case where we find gpm, but # ncurses is in a nonstandard location via $LIBS, and we really want # to link gpm. cf_ncurses_LIBS="" cf_ncurses_SAVE="$LIBS" -echo "$as_me:8946: checking for Gpm_Open in -lgpm" >&5 +echo "$as_me:10307: checking for Gpm_Open in -lgpm" >&5 echo $ECHO_N "checking for Gpm_Open in -lgpm... $ECHO_C" >&6 if test "${ac_cv_lib_gpm_Gpm_Open+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -8951,7 +10312,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-lgpm $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 8954 "configure" +#line 10315 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -8970,16 +10331,16 @@ Gpm_Open (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:8973: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10334: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:8976: \$? = $ac_status" >&5 + echo "$as_me:10337: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:8979: \"$ac_try\"") >&5 + { (eval echo "$as_me:10340: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:8982: \$? = $ac_status" >&5 + echo "$as_me:10343: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_gpm_Gpm_Open=yes else @@ -8990,10 +10351,10 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:8993: result: $ac_cv_lib_gpm_Gpm_Open" >&5 +echo "$as_me:10354: result: $ac_cv_lib_gpm_Gpm_Open" >&5 echo "${ECHO_T}$ac_cv_lib_gpm_Gpm_Open" >&6 if test "$ac_cv_lib_gpm_Gpm_Open" = yes; then - echo "$as_me:8996: checking for initscr in -lgpm" >&5 + echo "$as_me:10357: checking for initscr in -lgpm" >&5 echo $ECHO_N "checking for initscr in -lgpm... $ECHO_C" >&6 if test "${ac_cv_lib_gpm_initscr+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -9001,7 +10362,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-lgpm $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 9004 "configure" +#line 10365 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -9020,16 +10381,16 @@ initscr (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:9023: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10384: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9026: \$? = $ac_status" >&5 + echo "$as_me:10387: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:9029: \"$ac_try\"") >&5 + { (eval echo "$as_me:10390: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9032: \$? = $ac_status" >&5 + echo "$as_me:10393: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_gpm_initscr=yes else @@ -9040,7 +10401,7 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:9043: result: $ac_cv_lib_gpm_initscr" >&5 +echo "$as_me:10404: result: $ac_cv_lib_gpm_initscr" >&5 echo "${ECHO_T}$ac_cv_lib_gpm_initscr" >&6 if test "$ac_cv_lib_gpm_initscr" = yes; then LIBS="$cf_ncurses_SAVE" @@ -9055,7 +10416,7 @@ case "$host_os" in # This is only necessary if you are linking against an obsolete # version of ncurses (but it should do no harm, since it is static). if test "$cf_nculib_root" = ncurses ; then - echo "$as_me:9058: checking for tgoto in -lmytinfo" >&5 + echo "$as_me:10419: checking for tgoto in -lmytinfo" >&5 echo $ECHO_N "checking for tgoto in -lmytinfo... $ECHO_C" >&6 if test "${ac_cv_lib_mytinfo_tgoto+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -9063,7 +10424,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-lmytinfo $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 9066 "configure" +#line 10427 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -9082,16 +10443,16 @@ tgoto (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:9085: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10446: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9088: \$? = $ac_status" >&5 + echo "$as_me:10449: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:9091: \"$ac_try\"") >&5 + { (eval echo "$as_me:10452: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9094: \$? = $ac_status" >&5 + echo "$as_me:10455: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_mytinfo_tgoto=yes else @@ -9102,7 +10463,7 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:9105: result: $ac_cv_lib_mytinfo_tgoto" >&5 +echo "$as_me:10466: result: $ac_cv_lib_mytinfo_tgoto" >&5 echo "${ECHO_T}$ac_cv_lib_mytinfo_tgoto" >&6 if test "$ac_cv_lib_mytinfo_tgoto" = yes; then cf_ncurses_LIBS="-lmytinfo $cf_ncurses_LIBS" @@ -9151,13 +10512,13 @@ else eval 'cf_cv_have_lib_'"$cf_nculib_root"'=no' cf_libdir="" - echo "$as_me:9154: checking for initscr" >&5 + echo "$as_me:10515: checking for initscr" >&5 echo $ECHO_N "checking for initscr... $ECHO_C" >&6 if test "${ac_cv_func_initscr+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 9160 "configure" +#line 10521 "configure" #include "confdefs.h" #define initscr autoconf_temporary #include /* least-intrusive standard header which defines gcc2 __stub macros */ @@ -9188,16 +10549,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:9191: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10552: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9194: \$? = $ac_status" >&5 + echo "$as_me:10555: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:9197: \"$ac_try\"") >&5 + { (eval echo "$as_me:10558: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9200: \$? = $ac_status" >&5 + echo "$as_me:10561: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_func_initscr=yes else @@ -9207,18 +10568,18 @@ ac_cv_func_initscr=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:9210: result: $ac_cv_func_initscr" >&5 +echo "$as_me:10571: result: $ac_cv_func_initscr" >&5 echo "${ECHO_T}$ac_cv_func_initscr" >&6 if test "$ac_cv_func_initscr" = yes; then eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' else cf_save_LIBS="$LIBS" - echo "$as_me:9217: checking for initscr in -l$cf_nculib_root" >&5 + echo "$as_me:10578: checking for initscr in -l$cf_nculib_root" >&5 echo $ECHO_N "checking for initscr in -l$cf_nculib_root... $ECHO_C" >&6 LIBS="-l$cf_nculib_root $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 9221 "configure" +#line 10582 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -9230,25 +10591,25 @@ initscr() } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:9233: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10594: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9236: \$? = $ac_status" >&5 + echo "$as_me:10597: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:9239: \"$ac_try\"") >&5 + { (eval echo "$as_me:10600: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9242: \$? = $ac_status" >&5 + echo "$as_me:10603: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:9244: result: yes" >&5 + echo "$as_me:10605: result: yes" >&5 echo "${ECHO_T}yes" >&6 eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:9251: result: no" >&5 +echo "$as_me:10612: result: no" >&5 echo "${ECHO_T}no" >&6 cf_search= @@ -9316,11 +10677,11 @@ cf_search="$cf_library_path_list $cf_search" for cf_libdir in $cf_search do - echo "$as_me:9319: checking for -l$cf_nculib_root in $cf_libdir" >&5 + echo "$as_me:10680: checking for -l$cf_nculib_root in $cf_libdir" >&5 echo $ECHO_N "checking for -l$cf_nculib_root in $cf_libdir... $ECHO_C" >&6 LIBS="-L$cf_libdir -l$cf_nculib_root $cf_save_LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 9323 "configure" +#line 10684 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -9332,25 +10693,25 @@ initscr() } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:9335: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10696: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9338: \$? = $ac_status" >&5 + echo "$as_me:10699: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:9341: \"$ac_try\"") >&5 + { (eval echo "$as_me:10702: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9344: \$? = $ac_status" >&5 + echo "$as_me:10705: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:9346: result: yes" >&5 + echo "$as_me:10707: result: yes" >&5 echo "${ECHO_T}yes" >&6 eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' break else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:9353: result: no" >&5 +echo "$as_me:10714: result: no" >&5 echo "${ECHO_T}no" >&6 LIBS="$cf_save_LIBS" fi @@ -9365,7 +10726,7 @@ fi eval 'cf_found_library="$cf_cv_have_lib_'"$cf_nculib_root"\" if test "$cf_found_library" = no ; then - { { echo "$as_me:9368: error: Cannot link $cf_nculib_root library" >&5 + { { echo "$as_me:10729: error: Cannot link $cf_nculib_root library" >&5 echo "$as_me: error: Cannot link $cf_nculib_root library" >&2;} { (exit 1); exit 1; }; } fi @@ -9373,7 +10734,7 @@ fi fi if test -n "$cf_ncurses_LIBS" ; then - echo "$as_me:9376: checking if we can link $cf_nculib_root without $cf_ncurses_LIBS" >&5 + echo "$as_me:10737: checking if we can link $cf_nculib_root without $cf_ncurses_LIBS" >&5 echo $ECHO_N "checking if we can link $cf_nculib_root without $cf_ncurses_LIBS... $ECHO_C" >&6 cf_ncurses_SAVE="$LIBS" for p in $cf_ncurses_LIBS ; do @@ -9383,7 +10744,7 @@ echo $ECHO_N "checking if we can link $cf_nculib_root without $cf_ncurses_LIBS.. fi done cat >"conftest.$ac_ext" <<_ACEOF -#line 9386 "configure" +#line 10747 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -9395,23 +10756,23 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:9398: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10759: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9401: \$? = $ac_status" >&5 + echo "$as_me:10762: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:9404: \"$ac_try\"") >&5 + { (eval echo "$as_me:10765: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9407: \$? = $ac_status" >&5 + echo "$as_me:10768: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:9409: result: yes" >&5 + echo "$as_me:10770: result: yes" >&5 echo "${ECHO_T}yes" >&6 else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:9414: result: no" >&5 +echo "$as_me:10775: result: no" >&5 echo "${ECHO_T}no" >&6 LIBS="$cf_ncurses_SAVE" fi @@ -9429,19 +10790,20 @@ else NCURSES_CONFIG=none fi -else + ;; +(ncurses*) -cf_ncuconfig_root=ncurses +cf_ncuconfig_root=$cf_cv_screen cf_have_ncuconfig=no if test "x${PKG_CONFIG:=none}" != xnone; then - echo "$as_me:9438: checking pkg-config for $cf_ncuconfig_root" >&5 + echo "$as_me:10800: checking pkg-config for $cf_ncuconfig_root" >&5 echo $ECHO_N "checking pkg-config for $cf_ncuconfig_root... $ECHO_C" >&6 if "$PKG_CONFIG" --exists $cf_ncuconfig_root ; then - echo "$as_me:9441: result: yes" >&5 + echo "$as_me:10803: result: yes" >&5 echo "${ECHO_T}yes" >&6 - echo "$as_me:9444: checking if the $cf_ncuconfig_root package files work" >&5 + echo "$as_me:10806: checking if the $cf_ncuconfig_root package files work" >&5 echo $ECHO_N "checking if the $cf_ncuconfig_root package files work... $ECHO_C" >&6 cf_have_ncuconfig=unknown @@ -9574,7 +10936,7 @@ done LIBS="$cf_add_libs" cat >"conftest.$ac_ext" <<_ACEOF -#line 9577 "configure" +#line 10939 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -9586,37 +10948,37 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:9589: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10951: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9592: \$? = $ac_status" >&5 + echo "$as_me:10954: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:9595: \"$ac_try\"") >&5 + { (eval echo "$as_me:10957: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9598: \$? = $ac_status" >&5 + echo "$as_me:10960: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then if test "$cross_compiling" = yes; then cf_test_ncuconfig=maybe else cat >"conftest.$ac_ext" <<_ACEOF -#line 9604 "configure" +#line 10966 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int main(void) { const char *xx = curses_version(); return (xx == 0); } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:9611: \"$ac_link\"") >&5 +if { (eval echo "$as_me:10973: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9614: \$? = $ac_status" >&5 + echo "$as_me:10976: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:9616: \"$ac_try\"") >&5 + { (eval echo "$as_me:10978: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9619: \$? = $ac_status" >&5 + echo "$as_me:10981: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_test_ncuconfig=yes else @@ -9647,6 +11009,20 @@ rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" ;; esac +for cf_required in $cf_ncuconfig_root +do + # check for duplicates + for cf_require_pkg in $REQUIRE_PKG + do + if test "$cf_required" = "$cf_require_pkg" + then + cf_required= + break + fi + done + test -n "$cf_required" && REQUIRE_PKG="$REQUIRE_PKG $cf_required" +done + for cf_add_cflags in $cf_pkg_cflags do case "x$cf_add_cflags" in @@ -9790,7 +11166,7 @@ done LIBS="$cf_add_libs" cat >"conftest.$ac_ext" <<_ACEOF -#line 9793 "configure" +#line 11169 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -9802,37 +11178,37 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:9805: \"$ac_link\"") >&5 +if { (eval echo "$as_me:11181: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9808: \$? = $ac_status" >&5 + echo "$as_me:11184: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:9811: \"$ac_try\"") >&5 + { (eval echo "$as_me:11187: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9814: \$? = $ac_status" >&5 + echo "$as_me:11190: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then if test "$cross_compiling" = yes; then cf_have_ncuconfig=maybe else cat >"conftest.$ac_ext" <<_ACEOF -#line 9820 "configure" +#line 11196 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int main(void) { const char *xx = curses_version(); return (xx == 0); } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:9827: \"$ac_link\"") >&5 +if { (eval echo "$as_me:11203: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:9830: \$? = $ac_status" >&5 + echo "$as_me:11206: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:9832: \"$ac_try\"") >&5 + { (eval echo "$as_me:11208: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:9835: \$? = $ac_status" >&5 + echo "$as_me:11211: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_have_ncuconfig=yes else @@ -9849,7 +11225,7 @@ cat "conftest.$ac_ext" >&5 cf_have_ncuconfig=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" - echo "$as_me:9852: result: $cf_have_ncuconfig" >&5 + echo "$as_me:11228: result: $cf_have_ncuconfig" >&5 echo "${ECHO_T}$cf_have_ncuconfig" >&6 test "$cf_have_ncuconfig" = maybe && cf_have_ncuconfig=yes if test "$cf_have_ncuconfig" != "yes" @@ -9865,7 +11241,7 @@ EOF NCURSES_CONFIG_PKG=$cf_ncuconfig_root -echo "$as_me:9868: checking for terminfo header" >&5 +echo "$as_me:11244: checking for terminfo header" >&5 echo $ECHO_N "checking for terminfo header... $ECHO_C" >&6 if test "${cf_cv_term_header+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -9883,7 +11259,7 @@ esac for cf_test in $cf_term_header "ncurses/term.h" "ncursesw/term.h" do cat >"conftest.$ac_ext" <<_ACEOF -#line 9886 "configure" +#line 11262 "configure" #include "confdefs.h" #include #include <${cf_cv_ncurses_header:-curses.h}> @@ -9898,1392 +11274,1392 @@ int x = auto_left_margin; (void)x } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:9901: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:11277: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:9904: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:9907: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:9910: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - - cf_cv_term_header="$cf_test" -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 - - cf_cv_term_header=unknown - -fi -rm -f "conftest.$ac_objext" "conftest.$ac_ext" - test "$cf_cv_term_header" != unknown && break -done - -fi -echo "$as_me:9926: result: $cf_cv_term_header" >&5 -echo "${ECHO_T}$cf_cv_term_header" >&6 - -# Set definitions to allow ifdef'ing to accommodate subdirectories - -case "$cf_cv_term_header" in -(*term.h) - -cat >>confdefs.h <<\EOF -#define HAVE_TERM_H 1 -EOF - - ;; -esac - -case "$cf_cv_term_header" in -(ncurses/term.h) - -cat >>confdefs.h <<\EOF -#define HAVE_NCURSES_TERM_H 1 -EOF - - ;; -(ncursesw/term.h) - -cat >>confdefs.h <<\EOF -#define HAVE_NCURSESW_TERM_H 1 -EOF - - ;; -esac - - fi - - else - echo "$as_me:9961: result: no" >&5 -echo "${ECHO_T}no" >&6 - NCURSES_CONFIG_PKG=none - fi -else - NCURSES_CONFIG_PKG=none -fi - -if test "x$cf_have_ncuconfig" = "xno"; then - cf_ncurses_config="${cf_ncuconfig_root}${NCURSES_CONFIG_SUFFIX}-config"; echo "Looking for ${cf_ncurses_config}" - -if test -n "$ac_tool_prefix"; then - for ac_prog in ${cf_ncurses_config} ${cf_ncuconfig_root}6-config ${cf_ncuconfig_root}6-config ${cf_ncuconfig_root}5-config - do - # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. -set dummy $ac_tool_prefix$ac_prog; ac_word=$2 -echo "$as_me:9977: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 -if test "${ac_cv_prog_NCURSES_CONFIG+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - if test -n "$NCURSES_CONFIG"; then - ac_cv_prog_NCURSES_CONFIG="$NCURSES_CONFIG" # Let the user override the test. -else - ac_save_IFS=$IFS; IFS=$ac_path_separator -ac_dummy="$PATH" -for ac_dir in $ac_dummy; do - IFS=$ac_save_IFS - test -z "$ac_dir" && ac_dir=. - $as_executable_p "$ac_dir/$ac_word" || continue -ac_cv_prog_NCURSES_CONFIG="$ac_tool_prefix$ac_prog" -echo "$as_me:9992: found $ac_dir/$ac_word" >&5 -break -done - -fi -fi -NCURSES_CONFIG=$ac_cv_prog_NCURSES_CONFIG -if test -n "$NCURSES_CONFIG"; then - echo "$as_me:10000: result: $NCURSES_CONFIG" >&5 -echo "${ECHO_T}$NCURSES_CONFIG" >&6 -else - echo "$as_me:10003: result: no" >&5 -echo "${ECHO_T}no" >&6 -fi - - test -n "$NCURSES_CONFIG" && break - done -fi -if test -z "$NCURSES_CONFIG"; then - ac_ct_NCURSES_CONFIG=$NCURSES_CONFIG - for ac_prog in ${cf_ncurses_config} ${cf_ncuconfig_root}6-config ${cf_ncuconfig_root}6-config ${cf_ncuconfig_root}5-config -do - # Extract the first word of "$ac_prog", so it can be a program name with args. -set dummy $ac_prog; ac_word=$2 -echo "$as_me:10016: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 -if test "${ac_cv_prog_ac_ct_NCURSES_CONFIG+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - if test -n "$ac_ct_NCURSES_CONFIG"; then - ac_cv_prog_ac_ct_NCURSES_CONFIG="$ac_ct_NCURSES_CONFIG" # Let the user override the test. -else - ac_save_IFS=$IFS; IFS=$ac_path_separator -ac_dummy="$PATH" -for ac_dir in $ac_dummy; do - IFS=$ac_save_IFS - test -z "$ac_dir" && ac_dir=. - $as_executable_p "$ac_dir/$ac_word" || continue -ac_cv_prog_ac_ct_NCURSES_CONFIG="$ac_prog" -echo "$as_me:10031: found $ac_dir/$ac_word" >&5 -break -done - -fi -fi -ac_ct_NCURSES_CONFIG=$ac_cv_prog_ac_ct_NCURSES_CONFIG -if test -n "$ac_ct_NCURSES_CONFIG"; then - echo "$as_me:10039: result: $ac_ct_NCURSES_CONFIG" >&5 -echo "${ECHO_T}$ac_ct_NCURSES_CONFIG" >&6 -else - echo "$as_me:10042: result: no" >&5 -echo "${ECHO_T}no" >&6 -fi - - test -n "$ac_ct_NCURSES_CONFIG" && break -done -test -n "$ac_ct_NCURSES_CONFIG" || ac_ct_NCURSES_CONFIG="none" - - NCURSES_CONFIG=$ac_ct_NCURSES_CONFIG -fi - - if test "$NCURSES_CONFIG" != none ; then - -for cf_add_cflags in `$NCURSES_CONFIG --cflags` -do - case "x$cf_add_cflags" in - (x-[DU]*) - -cf_tmp_cflag=`echo "x$cf_add_cflags" | sed -e 's/^.//' -e 's/=.*//'` -while true -do - cf_old_cflag=`echo "x$CFLAGS" | sed -e 's/^.//' -e 's/[ ][ ]*-/ -/g' -e "s%$cf_tmp_cflag\\(=[^ ][^ ]*\\)\?%%" -e 's/^[ ]*//' -e 's%[ ][ ]*-D% -D%g' -e 's%[ ][ ]*-I% -I%g'` - test "$CFLAGS" != "$cf_old_cflag" || break - - CFLAGS="$cf_old_cflag" -done - -cf_tmp_cflag=`echo "x$cf_add_cflags" | sed -e 's/^.//' -e 's/=.*//'` -while true -do - cf_old_cflag=`echo "x$CPPFLAGS" | sed -e 's/^.//' -e 's/[ ][ ]*-/ -/g' -e "s%$cf_tmp_cflag\\(=[^ ][^ ]*\\)\?%%" -e 's/^[ ]*//' -e 's%[ ][ ]*-D% -D%g' -e 's%[ ][ ]*-I% -I%g'` - test "$CPPFLAGS" != "$cf_old_cflag" || break - - CPPFLAGS="$cf_old_cflag" -done - - ;; - esac - -cf_fix_cppflags=no -cf_new_cflags= -cf_new_cppflags= -cf_new_extra_cppflags= - -for cf_add_cflags in $cf_add_cflags -do -case "$cf_fix_cppflags" in -(no) - case "$cf_add_cflags" in - (-undef|-nostdinc*|-I*|-D*|-U*|-E|-P|-C) - case "$cf_add_cflags" in - (-D*) - cf_tst_cflags=`echo "${cf_add_cflags}" |sed -e 's/^-D[^=]*='\''\"[^"]*//'` - - test "x${cf_add_cflags}" != "x${cf_tst_cflags}" \ - && test -z "${cf_tst_cflags}" \ - && cf_fix_cppflags=yes - - if test "$cf_fix_cppflags" = yes ; then - - test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " - cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" - - continue - elif test "${cf_tst_cflags}" = "\"'" ; then - - test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " - cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" - - continue - fi - ;; - esac - case "$CPPFLAGS" in - (*$cf_add_cflags) - ;; - (*) - case "$cf_add_cflags" in - (-D*) - cf_tst_cppflags=`echo "x$cf_add_cflags" | sed -e 's/^...//' -e 's/=.*//'` - -CPPFLAGS=`echo "$CPPFLAGS" | \ - sed -e 's/-[UD]'"$cf_tst_cppflags"'\(=[^ ]*\)\?[ ]/ /g' \ - -e 's/-[UD]'"$cf_tst_cppflags"'\(=[^ ]*\)\?$//g'` - - ;; - esac - - test -n "$cf_new_cppflags" && cf_new_cppflags="$cf_new_cppflags " - cf_new_cppflags="${cf_new_cppflags}$cf_add_cflags" - - ;; - esac - ;; - (*) - - test -n "$cf_new_cflags" && cf_new_cflags="$cf_new_cflags " - cf_new_cflags="${cf_new_cflags}$cf_add_cflags" - - ;; - esac - ;; -(yes) - - test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " - cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" - - cf_tst_cflags=`echo "${cf_add_cflags}" |sed -e 's/^[^"]*"'\''//'` - - test "x${cf_add_cflags}" != "x${cf_tst_cflags}" \ - && test -z "${cf_tst_cflags}" \ - && cf_fix_cppflags=no - ;; -esac -done - -if test -n "$cf_new_cflags" ; then - - test -n "$CFLAGS" && CFLAGS="$CFLAGS " - CFLAGS="${CFLAGS}$cf_new_cflags" - -fi - -if test -n "$cf_new_cppflags" ; then - - test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " - CPPFLAGS="${CPPFLAGS}$cf_new_cppflags" - -fi - -if test -n "$cf_new_extra_cppflags" ; then - - test -n "$EXTRA_CPPFLAGS" && EXTRA_CPPFLAGS="$EXTRA_CPPFLAGS " - EXTRA_CPPFLAGS="${EXTRA_CPPFLAGS}$cf_new_extra_cppflags" - -fi - -done - -cf_add_libs="$LIBS" -# reverse order -cf_add_0lib= -for cf_add_1lib in `$NCURSES_CONFIG --libs`; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done -# filter duplicates -for cf_add_1lib in $cf_add_0lib; do - for cf_add_2lib in $cf_add_libs; do - if test "x$cf_add_1lib" = "x$cf_add_2lib"; then - cf_add_1lib= - break - fi - done - test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" -done -LIBS="$cf_add_libs" - - # even with config script, some packages use no-override for curses.h - -echo "$as_me:10199: checking if we have identified curses headers" >&5 -echo $ECHO_N "checking if we have identified curses headers... $ECHO_C" >&6 -if test "${cf_cv_ncurses_header+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - -cf_cv_ncurses_header=none -for cf_header in \ - ncurses.h ncurses/ncurses.h \ - curses.h ncurses/curses.h -do -cat >"conftest.$ac_ext" <<_ACEOF -#line 10211 "configure" -#include "confdefs.h" -#include <${cf_header}> -int -main (void) -{ -initscr(); endwin() - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:10223: \"$ac_compile\"") >&5 - (eval $ac_compile) 2>&5 - ac_status=$? - echo "$as_me:10226: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:10229: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:10232: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - cf_cv_ncurses_header=$cf_header; break -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -fi -rm -f "conftest.$ac_objext" "conftest.$ac_ext" -done - -fi -echo "$as_me:10243: result: $cf_cv_ncurses_header" >&5 -echo "${ECHO_T}$cf_cv_ncurses_header" >&6 - -if test "$cf_cv_ncurses_header" = none ; then - { { echo "$as_me:10247: error: No curses header-files found" >&5 -echo "$as_me: error: No curses header-files found" >&2;} - { (exit 1); exit 1; }; } -fi - -# cheat, to get the right #define's for HAVE_NCURSES_H, etc. - -for ac_header in $cf_cv_ncurses_header -do -as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` -echo "$as_me:10257: checking for $ac_header" >&5 -echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 -if eval "test \"\${$as_ac_Header+set}\" = set"; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - cat >"conftest.$ac_ext" <<_ACEOF -#line 10263 "configure" -#include "confdefs.h" -#include <$ac_header> -_ACEOF -if { (eval echo "$as_me:10267: \"$ac_cpp "conftest.$ac_ext"\"") >&5 - (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 - ac_status=$? - $EGREP -v '^ *\+' conftest.er1 >conftest.err - rm -f conftest.er1 - cat conftest.err >&5 - echo "$as_me:10273: \$? = $ac_status" >&5 - (exit "$ac_status"); } >/dev/null; then - if test -s conftest.err; then - ac_cpp_err=$ac_c_preproc_warn_flag - else - ac_cpp_err= - fi -else - ac_cpp_err=yes -fi -if test -z "$ac_cpp_err"; then - eval "$as_ac_Header=yes" -else - echo "$as_me: failed program was:" >&5 - cat "conftest.$ac_ext" >&5 - eval "$as_ac_Header=no" -fi -rm -f conftest.err "conftest.$ac_ext" -fi -echo "$as_me:10292: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 -echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 -if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then - cat >>confdefs.h <>confdefs.h <<\EOF -#define NCURSES 1 -EOF - -cf_nculib_ROOT=`echo "HAVE_LIB$cf_ncuconfig_root" | sed y%abcdefghijklmnopqrstuvwxyz./-%ABCDEFGHIJKLMNOPQRSTUVWXYZ___%` - - cat >>confdefs.h <"conftest.$ac_ext" <<_ACEOF -#line 10348 "configure" -#include "confdefs.h" -#include -int -main (void) -{ -printf("Hello") - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:10360: \"$ac_compile\"") >&5 - (eval $ac_compile) 2>&5 - ac_status=$? - echo "$as_me:10363: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:10366: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:10369: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - : -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -cf_have_incdir=yes -fi -rm -f "conftest.$ac_objext" "conftest.$ac_ext" - CPPFLAGS=$cf_save_CPPFLAGS - fi - fi - fi - - if test "$cf_have_incdir" = no ; then - test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 - -echo "${as_me:-configure}:10386: testing adding $cf_add_incdir to include-path ..." 1>&5 - - CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" - - cf_top_incdir=`echo "$cf_add_incdir" | sed -e 's%/include/.*$%/include%'` - test "$cf_top_incdir" = "$cf_add_incdir" && break - cf_add_incdir="$cf_top_incdir" - else - break - fi - else - break - fi - done - done -fi - -} - -echo "$as_me:10405: checking for $cf_ncuhdr_root header in include-path" >&5 -echo $ECHO_N "checking for $cf_ncuhdr_root header in include-path... $ECHO_C" >&6 -if test "${cf_cv_ncurses_h+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - - cf_header_list="$cf_ncuhdr_root/curses.h $cf_ncuhdr_root/ncurses.h" - { test "$cf_ncuhdr_root" = ncurses || test "$cf_ncuhdr_root" = ncursesw; } && cf_header_list="$cf_header_list curses.h ncurses.h" - for cf_header in $cf_header_list - do - - cat >"conftest.$ac_ext" <<_ACEOF -#line 10417 "configure" -#include "confdefs.h" - -#include <$cf_header> -int -main (void) -{ - -#ifdef NCURSES_VERSION - -printf("%s\\n", NCURSES_VERSION); -#else -#ifdef __NCURSES_H -printf("old\\n"); -#else - #error __NCURSES_H is not defined -#endif -#endif - - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:10441: \"$ac_compile\"") >&5 - (eval $ac_compile) 2>&5 - ac_status=$? - echo "$as_me:10444: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:10447: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:10450: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - cf_cv_ncurses_h=$cf_header - -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -cf_cv_ncurses_h=no -fi -rm -f "conftest.$ac_objext" "conftest.$ac_ext" - - test "$cf_cv_ncurses_h" != no && break - done - -fi -echo "$as_me:10465: result: $cf_cv_ncurses_h" >&5 -echo "${ECHO_T}$cf_cv_ncurses_h" >&6 - -if test "$cf_cv_ncurses_h" != no ; then - cf_cv_ncurses_header=$cf_cv_ncurses_h -else - -echo "$as_me:10472: checking for $cf_ncuhdr_root include-path" >&5 -echo $ECHO_N "checking for $cf_ncuhdr_root include-path... $ECHO_C" >&6 -if test "${cf_cv_ncurses_h2+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - - test -n "$verbose" && echo - -cf_search= - -# collect the current set of include-directories from compiler flags -cf_header_path_list="" -if test -n "${CFLAGS}${CPPFLAGS}" ; then - for cf_header_path in $CPPFLAGS $CFLAGS - do - case "$cf_header_path" in - (-I*) - cf_header_path=`echo ".$cf_header_path" |sed -e 's/^...//' -e 's,/include$,,'` - -test "x$cf_header_path" != "xNONE" && \ -test -d "$cf_header_path" && \ - { - test -n "$verbose" && echo " ... testing for include-directories under $cf_header_path" - test -d "$cf_header_path/include" && cf_search="$cf_search $cf_header_path/include" - test -d "$cf_header_path/include/$cf_ncuhdr_root" && cf_search="$cf_search $cf_header_path/include/$cf_ncuhdr_root" - test -d "$cf_header_path/include/$cf_ncuhdr_root/include" && cf_search="$cf_search $cf_header_path/include/$cf_ncuhdr_root/include" - test -d "$cf_header_path/$cf_ncuhdr_root/include" && cf_search="$cf_search $cf_header_path/$cf_ncuhdr_root/include" - test -d "$cf_header_path/$cf_ncuhdr_root/include/$cf_ncuhdr_root" && cf_search="$cf_search $cf_header_path/$cf_ncuhdr_root/include/$cf_ncuhdr_root" -} - - cf_header_path_list="$cf_header_path_list $cf_search" - ;; - esac - done -fi - -# add the variations for the package we are looking for - -cf_search= - -test "x$prefix" != "xNONE" && \ -test -d "$prefix" && \ - { - test -n "$verbose" && echo " ... testing for include-directories under $prefix" - test -d "$prefix/include" && cf_search="$cf_search $prefix/include" - test -d "$prefix/include/$cf_ncuhdr_root" && cf_search="$cf_search $prefix/include/$cf_ncuhdr_root" - test -d "$prefix/include/$cf_ncuhdr_root/include" && cf_search="$cf_search $prefix/include/$cf_ncuhdr_root/include" - test -d "$prefix/$cf_ncuhdr_root/include" && cf_search="$cf_search $prefix/$cf_ncuhdr_root/include" - test -d "$prefix/$cf_ncuhdr_root/include/$cf_ncuhdr_root" && cf_search="$cf_search $prefix/$cf_ncuhdr_root/include/$cf_ncuhdr_root" -} - -for cf_subdir_prefix in \ - /usr \ - /usr/local \ - /usr/pkg \ - /opt \ - /opt/local \ - $HOME -do - -test "x$cf_subdir_prefix" != "x$prefix" && \ -test -d "$cf_subdir_prefix" && \ -{ test -z "$prefix" || test "x$prefix" = xNONE || test "x$cf_subdir_prefix" != "x$prefix"; } && { - test -n "$verbose" && echo " ... testing for include-directories under $cf_subdir_prefix" - test -d "$cf_subdir_prefix/include" && cf_search="$cf_search $cf_subdir_prefix/include" - test -d "$cf_subdir_prefix/include/$cf_ncuhdr_root" && cf_search="$cf_search $cf_subdir_prefix/include/$cf_ncuhdr_root" - test -d "$cf_subdir_prefix/include/$cf_ncuhdr_root/include" && cf_search="$cf_search $cf_subdir_prefix/include/$cf_ncuhdr_root/include" - test -d "$cf_subdir_prefix/$cf_ncuhdr_root/include" && cf_search="$cf_search $cf_subdir_prefix/$cf_ncuhdr_root/include" - test -d "$cf_subdir_prefix/$cf_ncuhdr_root/include/$cf_ncuhdr_root" && cf_search="$cf_search $cf_subdir_prefix/$cf_ncuhdr_root/include/$cf_ncuhdr_root" -} - -done - -test "$includedir" != NONE && \ -test "$includedir" != "/usr/include" && \ -test -d "$includedir" && { - test -d "$includedir" && cf_search="$cf_search $includedir" - test -d "$includedir/$cf_ncuhdr_root" && cf_search="$cf_search $includedir/$cf_ncuhdr_root" -} - -test "$oldincludedir" != NONE && \ -test "$oldincludedir" != "/usr/include" && \ -test -d "$oldincludedir" && { - test -d "$oldincludedir" && cf_search="$cf_search $oldincludedir" - test -d "$oldincludedir/$cf_ncuhdr_root" && cf_search="$cf_search $oldincludedir/$cf_ncuhdr_root" -} - -cf_search="$cf_search $cf_header_path_list" - - test -n "$verbose" && echo "search path $cf_search" - cf_save2_CPPFLAGS="$CPPFLAGS" - for cf_incdir in $cf_search - do - -if test -n "$cf_incdir" ; then - for cf_add_incdir in $cf_incdir - do - while test "$cf_add_incdir" != /usr/include - do - if test -d "$cf_add_incdir" - then - cf_have_incdir=no - if test -n "$CFLAGS$CPPFLAGS" ; then - # a loop is needed to ensure we can add subdirs of existing dirs - for cf_test_incdir in $CFLAGS $CPPFLAGS ; do - if test ".$cf_test_incdir" = ".-I$cf_add_incdir" ; then - cf_have_incdir=yes; break - fi - done - fi - - if test "$cf_have_incdir" = no ; then - if test "$cf_add_incdir" = /usr/local/include ; then - if test "$GCC" = yes - then - cf_save_CPPFLAGS=$CPPFLAGS - - test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " - CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" - - cat >"conftest.$ac_ext" <<_ACEOF -#line 10593 "configure" -#include "confdefs.h" -#include -int -main (void) -{ -printf("Hello") - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:10605: \"$ac_compile\"") >&5 - (eval $ac_compile) 2>&5 - ac_status=$? - echo "$as_me:10608: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:10611: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:10614: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - : -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -cf_have_incdir=yes -fi -rm -f "conftest.$ac_objext" "conftest.$ac_ext" - CPPFLAGS=$cf_save_CPPFLAGS - fi - fi - fi - - if test "$cf_have_incdir" = no ; then - test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 - -echo "${as_me:-configure}:10631: testing adding $cf_add_incdir to include-path ..." 1>&5 - - CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" - - cf_top_incdir=`echo "$cf_add_incdir" | sed -e 's%/include/.*$%/include%'` - test "$cf_top_incdir" = "$cf_add_incdir" && break - cf_add_incdir="$cf_top_incdir" - else - break - fi - else - break - fi - done - done -fi - - for cf_header in \ - ncurses.h \ - curses.h - do - - cat >"conftest.$ac_ext" <<_ACEOF -#line 10654 "configure" -#include "confdefs.h" - -#include <$cf_header> -int -main (void) -{ - -#ifdef NCURSES_VERSION - -printf("%s\\n", NCURSES_VERSION); -#else -#ifdef __NCURSES_H -printf("old\\n"); -#else - #error __NCURSES_H is not defined -#endif -#endif - - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:10678: \"$ac_compile\"") >&5 - (eval $ac_compile) 2>&5 - ac_status=$? - echo "$as_me:10681: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:10684: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:10687: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - cf_cv_ncurses_h2=$cf_header - -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -cf_cv_ncurses_h2=no -fi -rm -f "conftest.$ac_objext" "conftest.$ac_ext" - - if test "$cf_cv_ncurses_h2" != no ; then - cf_cv_ncurses_h2=$cf_incdir/$cf_header - test -n "$verbose" && echo $ECHO_N " ... found $ECHO_C" 1>&6 - break - fi - test -n "$verbose" && echo " ... tested $cf_incdir/$cf_header" 1>&6 - done - CPPFLAGS="$cf_save2_CPPFLAGS" - test "$cf_cv_ncurses_h2" != no && break - done - test "$cf_cv_ncurses_h2" = no && { { echo "$as_me:10708: error: not found" >&5 -echo "$as_me: error: not found" >&2;} - { (exit 1); exit 1; }; } - -fi -echo "$as_me:10713: result: $cf_cv_ncurses_h2" >&5 -echo "${ECHO_T}$cf_cv_ncurses_h2" >&6 - - cf_1st_incdir=`echo "$cf_cv_ncurses_h2" | sed -e 's%/[^/]*$%%'` - cf_cv_ncurses_header="`basename "$cf_cv_ncurses_h2"`" - if test "`basename "$cf_1st_incdir"`" = "$cf_ncuhdr_root" ; then - cf_cv_ncurses_header="$cf_ncuhdr_root/$cf_cv_ncurses_header" - fi - -if test -n "$cf_1st_incdir" ; then - for cf_add_incdir in $cf_1st_incdir - do - while test "$cf_add_incdir" != /usr/include - do - if test -d "$cf_add_incdir" - then - cf_have_incdir=no - if test -n "$CFLAGS$CPPFLAGS" ; then - # a loop is needed to ensure we can add subdirs of existing dirs - for cf_test_incdir in $CFLAGS $CPPFLAGS ; do - if test ".$cf_test_incdir" = ".-I$cf_add_incdir" ; then - cf_have_incdir=yes; break - fi - done - fi - - if test "$cf_have_incdir" = no ; then - if test "$cf_add_incdir" = /usr/local/include ; then - if test "$GCC" = yes - then - cf_save_CPPFLAGS=$CPPFLAGS - - test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " - CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" - - cat >"conftest.$ac_ext" <<_ACEOF -#line 10749 "configure" -#include "confdefs.h" -#include -int -main (void) -{ -printf("Hello") - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:10761: \"$ac_compile\"") >&5 - (eval $ac_compile) 2>&5 - ac_status=$? - echo "$as_me:10764: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:10767: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:10770: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - : -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -cf_have_incdir=yes -fi -rm -f "conftest.$ac_objext" "conftest.$ac_ext" - CPPFLAGS=$cf_save_CPPFLAGS - fi - fi - fi - - if test "$cf_have_incdir" = no ; then - test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 - -echo "${as_me:-configure}:10787: testing adding $cf_add_incdir to include-path ..." 1>&5 - - CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" - - cf_top_incdir=`echo "$cf_add_incdir" | sed -e 's%/include/.*$%/include%'` - test "$cf_top_incdir" = "$cf_add_incdir" && break - cf_add_incdir="$cf_top_incdir" - else - break - fi - else - break - fi - done - done -fi - -fi - -# Set definitions to allow ifdef'ing for ncurses.h - -case "$cf_cv_ncurses_header" in -(*ncurses.h) - -cat >>confdefs.h <<\EOF -#define HAVE_NCURSES_H 1 -EOF - - ;; -esac - -case "$cf_cv_ncurses_header" in -(ncurses/curses.h|ncurses/ncurses.h) - -cat >>confdefs.h <<\EOF -#define HAVE_NCURSES_NCURSES_H 1 -EOF - - ;; -(ncursesw/curses.h|ncursesw/ncurses.h) - -cat >>confdefs.h <<\EOF -#define HAVE_NCURSESW_NCURSES_H 1 -EOF - - ;; -esac - -echo "$as_me:10835: checking for terminfo header" >&5 -echo $ECHO_N "checking for terminfo header... $ECHO_C" >&6 -if test "${cf_cv_term_header+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - -case "${cf_cv_ncurses_header}" in -(*/ncurses.h|*/ncursesw.h) - cf_term_header=`echo "$cf_cv_ncurses_header" | sed -e 's%ncurses[^.]*\.h$%term.h%'` - ;; -(*) - cf_term_header=term.h - ;; -esac - -for cf_test in $cf_term_header "ncurses/term.h" "ncursesw/term.h" -do -cat >"conftest.$ac_ext" <<_ACEOF -#line 10853 "configure" -#include "confdefs.h" -#include -#include <${cf_cv_ncurses_header:-curses.h}> -#include <$cf_test> - -int -main (void) -{ -int x = auto_left_margin; (void)x - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:10868: \"$ac_compile\"") >&5 - (eval $ac_compile) 2>&5 - ac_status=$? - echo "$as_me:10871: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:10874: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:10877: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - - cf_cv_term_header="$cf_test" -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 - - cf_cv_term_header=unknown - -fi -rm -f "conftest.$ac_objext" "conftest.$ac_ext" - test "$cf_cv_term_header" != unknown && break -done - -fi -echo "$as_me:10893: result: $cf_cv_term_header" >&5 -echo "${ECHO_T}$cf_cv_term_header" >&6 - -# Set definitions to allow ifdef'ing to accommodate subdirectories - -case "$cf_cv_term_header" in -(*term.h) - -cat >>confdefs.h <<\EOF -#define HAVE_TERM_H 1 -EOF - - ;; -esac - -case "$cf_cv_term_header" in -(ncurses/term.h) - -cat >>confdefs.h <<\EOF -#define HAVE_NCURSES_TERM_H 1 -EOF - - ;; -(ncursesw/term.h) - -cat >>confdefs.h <<\EOF -#define HAVE_NCURSESW_TERM_H 1 -EOF - - ;; -esac - -# some applications need this, but should check for NCURSES_VERSION - -cat >>confdefs.h <<\EOF -#define NCURSES 1 -EOF - -echo "$as_me:10931: checking for ncurses version" >&5 -echo $ECHO_N "checking for ncurses version... $ECHO_C" >&6 -if test "${cf_cv_ncurses_version+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - - cf_cv_ncurses_version=no - cf_tempfile=out$$ - rm -f "$cf_tempfile" - if test "$cross_compiling" = yes; then - - # This will not work if the preprocessor splits the line after the - # Autoconf token. The 'unproto' program does that. - cat > "conftest.$ac_ext" < -#undef Autoconf -#ifdef NCURSES_VERSION -Autoconf NCURSES_VERSION -#else -#ifdef __NCURSES_H -Autoconf "old" -#endif -; -#endif -EOF - cf_try="$ac_cpp conftest.$ac_ext 2>&5 | grep '^Autoconf ' >conftest.out" - { (eval echo "$as_me:10957: \"$cf_try\"") >&5 - (eval $cf_try) 2>&5 - ac_status=$? - echo "$as_me:10960: \$? = $ac_status" >&5 - (exit "$ac_status"); } - if test -f conftest.out ; then - cf_out=`sed -e 's%^Autoconf %%' -e 's%^[^"]*"%%' -e 's%".*%%' conftest.out` - test -n "$cf_out" && cf_cv_ncurses_version="$cf_out" - rm -f conftest.out - fi - -else - cat >"conftest.$ac_ext" <<_ACEOF -#line 10970 "configure" -#include "confdefs.h" - -$ac_includes_default - -#include <${cf_cv_ncurses_header:-curses.h}> - -int main(void) -{ - FILE *fp = fopen("$cf_tempfile", "w"); -#ifdef NCURSES_VERSION -# ifdef NCURSES_VERSION_PATCH - fprintf(fp, "%s.%d\\n", NCURSES_VERSION, NCURSES_VERSION_PATCH); -# else - fprintf(fp, "%s\\n", NCURSES_VERSION); -# endif -#else -# ifdef __NCURSES_H - fprintf(fp, "old\\n"); -# else - #error expected ncurses header to define __NCURSES_H -# endif -#endif - ${cf_cv_main_return:-return}(0); -} -_ACEOF -rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:10997: \"$ac_link\"") >&5 - (eval $ac_link) 2>&5 - ac_status=$? - echo "$as_me:11000: \$? = $ac_status" >&5 - (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:11002: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:11005: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - - cf_cv_ncurses_version=`cat $cf_tempfile` -else - echo "$as_me: program exited with status $ac_status" >&5 -echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -fi -rm -f core ./core.* ./*.core "conftest$ac_exeext" "conftest.$ac_objext" "conftest.$ac_ext" -fi - rm -f "$cf_tempfile" - -fi -echo "$as_me:11019: result: $cf_cv_ncurses_version" >&5 -echo "${ECHO_T}$cf_cv_ncurses_version" >&6 -test "$cf_cv_ncurses_version" = no || -cat >>confdefs.h <<\EOF -#define NCURSES 1 -EOF - -cf_nculib_root=ncurses - # This works, except for the special case where we find gpm, but - # ncurses is in a nonstandard location via $LIBS, and we really want - # to link gpm. -cf_ncurses_LIBS="" -cf_ncurses_SAVE="$LIBS" -echo "$as_me:11032: checking for Gpm_Open in -lgpm" >&5 -echo $ECHO_N "checking for Gpm_Open in -lgpm... $ECHO_C" >&6 -if test "${ac_cv_lib_gpm_Gpm_Open+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - ac_check_lib_save_LIBS=$LIBS -LIBS="-lgpm $LIBS" -cat >"conftest.$ac_ext" <<_ACEOF -#line 11040 "configure" -#include "confdefs.h" - -/* Override any gcc2 internal prototype to avoid an error. */ -#ifdef __cplusplus -extern "C" -#endif -/* We use char because int might match the return type of a gcc2 - builtin and then its argument prototype would still apply. */ -char Gpm_Open (void); -int -main (void) -{ -Gpm_Open (); - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11059: \"$ac_link\"") >&5 - (eval $ac_link) 2>&5 - ac_status=$? - echo "$as_me:11062: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:11065: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:11068: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - ac_cv_lib_gpm_Gpm_Open=yes -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -ac_cv_lib_gpm_Gpm_Open=no -fi -rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" -LIBS=$ac_check_lib_save_LIBS -fi -echo "$as_me:11079: result: $ac_cv_lib_gpm_Gpm_Open" >&5 -echo "${ECHO_T}$ac_cv_lib_gpm_Gpm_Open" >&6 -if test "$ac_cv_lib_gpm_Gpm_Open" = yes; then - echo "$as_me:11082: checking for initscr in -lgpm" >&5 -echo $ECHO_N "checking for initscr in -lgpm... $ECHO_C" >&6 -if test "${ac_cv_lib_gpm_initscr+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - ac_check_lib_save_LIBS=$LIBS -LIBS="-lgpm $LIBS" -cat >"conftest.$ac_ext" <<_ACEOF -#line 11090 "configure" -#include "confdefs.h" - -/* Override any gcc2 internal prototype to avoid an error. */ -#ifdef __cplusplus -extern "C" -#endif -/* We use char because int might match the return type of a gcc2 - builtin and then its argument prototype would still apply. */ -char initscr (void); -int -main (void) -{ -initscr (); - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11109: \"$ac_link\"") >&5 - (eval $ac_link) 2>&5 - ac_status=$? - echo "$as_me:11112: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:11115: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:11118: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - ac_cv_lib_gpm_initscr=yes -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -ac_cv_lib_gpm_initscr=no -fi -rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" -LIBS=$ac_check_lib_save_LIBS -fi -echo "$as_me:11129: result: $ac_cv_lib_gpm_initscr" >&5 -echo "${ECHO_T}$ac_cv_lib_gpm_initscr" >&6 -if test "$ac_cv_lib_gpm_initscr" = yes; then - LIBS="$cf_ncurses_SAVE" -else - cf_ncurses_LIBS="-lgpm" -fi - -fi - -case "$host_os" in -(freebsd*) - # This is only necessary if you are linking against an obsolete - # version of ncurses (but it should do no harm, since it is static). - if test "$cf_nculib_root" = ncurses ; then - echo "$as_me:11144: checking for tgoto in -lmytinfo" >&5 -echo $ECHO_N "checking for tgoto in -lmytinfo... $ECHO_C" >&6 -if test "${ac_cv_lib_mytinfo_tgoto+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - ac_check_lib_save_LIBS=$LIBS -LIBS="-lmytinfo $LIBS" -cat >"conftest.$ac_ext" <<_ACEOF -#line 11152 "configure" -#include "confdefs.h" - -/* Override any gcc2 internal prototype to avoid an error. */ -#ifdef __cplusplus -extern "C" -#endif -/* We use char because int might match the return type of a gcc2 - builtin and then its argument prototype would still apply. */ -char tgoto (void); -int -main (void) -{ -tgoto (); - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11171: \"$ac_link\"") >&5 - (eval $ac_link) 2>&5 - ac_status=$? - echo "$as_me:11174: \$? = $ac_status" >&5 - (exit "$ac_status"); } && - { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:11177: \"$ac_try\"") >&5 - (eval $ac_try) 2>&5 - ac_status=$? - echo "$as_me:11180: \$? = $ac_status" >&5 - (exit "$ac_status"); }; }; then - ac_cv_lib_mytinfo_tgoto=yes -else - echo "$as_me: failed program was:" >&5 -cat "conftest.$ac_ext" >&5 -ac_cv_lib_mytinfo_tgoto=no -fi -rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" -LIBS=$ac_check_lib_save_LIBS -fi -echo "$as_me:11191: result: $ac_cv_lib_mytinfo_tgoto" >&5 -echo "${ECHO_T}$ac_cv_lib_mytinfo_tgoto" >&6 -if test "$ac_cv_lib_mytinfo_tgoto" = yes; then - cf_ncurses_LIBS="-lmytinfo $cf_ncurses_LIBS" -fi - - fi - ;; -esac - -cf_add_libs="$LIBS" -# reverse order -cf_add_0lib= -for cf_add_1lib in $cf_ncurses_LIBS; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done -# filter duplicates -for cf_add_1lib in $cf_add_0lib; do - for cf_add_2lib in $cf_add_libs; do - if test "x$cf_add_1lib" = "x$cf_add_2lib"; then - cf_add_1lib= - break - fi - done - test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" -done -LIBS="$cf_add_libs" - -if test -n "$cf_cv_curses_dir" && test "$cf_cv_curses_dir" != "no" -then - -cf_add_libs="$LIBS" -# reverse order -cf_add_0lib= -for cf_add_1lib in -l$cf_nculib_root; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done -# filter duplicates -for cf_add_1lib in $cf_add_0lib; do - for cf_add_2lib in $cf_add_libs; do - if test "x$cf_add_1lib" = "x$cf_add_2lib"; then - cf_add_1lib= - break - fi - done - test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" -done -LIBS="$cf_add_libs" - -else - - eval 'cf_cv_have_lib_'"$cf_nculib_root"'=no' - cf_libdir="" - echo "$as_me:11240: checking for initscr" >&5 -echo $ECHO_N "checking for initscr... $ECHO_C" >&6 -if test "${ac_cv_func_initscr+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - cat >"conftest.$ac_ext" <<_ACEOF -#line 11246 "configure" -#include "confdefs.h" -#define initscr autoconf_temporary -#include /* least-intrusive standard header which defines gcc2 __stub macros */ -#undef initscr - -#ifdef __cplusplus -extern "C" -#endif - -/* We use char because int might match the return type of a gcc2 - builtin and then its argument prototype would still apply. */ -char initscr (void); - -int -main (void) -{ - -/* The GNU C library defines stubs for functions which it implements - to always fail with ENOSYS. Some functions are actually named - something starting with __ and the normal name is an alias. */ -#if defined (__stub_initscr) || defined (__stub___initscr) -#error found stub for initscr -#endif - - return initscr (); - ; - return 0; -} -_ACEOF -rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11277: \"$ac_link\"") >&5 - (eval $ac_link) 2>&5 - ac_status=$? echo "$as_me:11280: \$? = $ac_status" >&5 (exit "$ac_status"); } && - { ac_try='test -s "conftest$ac_exeext"' + { ac_try='test -s "conftest.$ac_objext"' { (eval echo "$as_me:11283: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? echo "$as_me:11286: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + + cf_cv_term_header="$cf_test" +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 + + cf_cv_term_header=unknown + +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" + test "$cf_cv_term_header" != unknown && break +done + +fi +echo "$as_me:11302: result: $cf_cv_term_header" >&5 +echo "${ECHO_T}$cf_cv_term_header" >&6 + +# Set definitions to allow ifdef'ing to accommodate subdirectories + +case "$cf_cv_term_header" in +(*term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_TERM_H 1 +EOF + + ;; +esac + +case "$cf_cv_term_header" in +(ncurses/term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSES_TERM_H 1 +EOF + + ;; +(ncursesw/term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSESW_TERM_H 1 +EOF + + ;; +esac + + fi + + else + echo "$as_me:11337: result: no" >&5 +echo "${ECHO_T}no" >&6 + NCURSES_CONFIG_PKG=none + fi +else + NCURSES_CONFIG_PKG=none +fi + +if test "x$cf_have_ncuconfig" = "xno"; then + cf_ncurses_config="${cf_ncuconfig_root}${NCURSES_CONFIG_SUFFIX}-config"; echo "Looking for ${cf_ncurses_config}" + +if test -n "$ac_tool_prefix"; then + for ac_prog in ${cf_ncurses_config} ${cf_ncuconfig_root}6-config ${cf_ncuconfig_root}6-config ${cf_ncuconfig_root}5-config + do + # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args. +set dummy $ac_tool_prefix$ac_prog; ac_word=$2 +echo "$as_me:11353: checking for $ac_word" >&5 +echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 +if test "${ac_cv_prog_NCURSES_CONFIG+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + if test -n "$NCURSES_CONFIG"; then + ac_cv_prog_NCURSES_CONFIG="$NCURSES_CONFIG" # Let the user override the test. +else + ac_save_IFS=$IFS; IFS=$ac_path_separator +ac_dummy="$PATH" +for ac_dir in $ac_dummy; do + IFS=$ac_save_IFS + test -z "$ac_dir" && ac_dir=. + $as_executable_p "$ac_dir/$ac_word" || continue +ac_cv_prog_NCURSES_CONFIG="$ac_tool_prefix$ac_prog" +echo "$as_me:11368: found $ac_dir/$ac_word" >&5 +break +done + +fi +fi +NCURSES_CONFIG=$ac_cv_prog_NCURSES_CONFIG +if test -n "$NCURSES_CONFIG"; then + echo "$as_me:11376: result: $NCURSES_CONFIG" >&5 +echo "${ECHO_T}$NCURSES_CONFIG" >&6 +else + echo "$as_me:11379: result: no" >&5 +echo "${ECHO_T}no" >&6 +fi + + test -n "$NCURSES_CONFIG" && break + done +fi +if test -z "$NCURSES_CONFIG"; then + ac_ct_NCURSES_CONFIG=$NCURSES_CONFIG + for ac_prog in ${cf_ncurses_config} ${cf_ncuconfig_root}6-config ${cf_ncuconfig_root}6-config ${cf_ncuconfig_root}5-config +do + # Extract the first word of "$ac_prog", so it can be a program name with args. +set dummy $ac_prog; ac_word=$2 +echo "$as_me:11392: checking for $ac_word" >&5 +echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 +if test "${ac_cv_prog_ac_ct_NCURSES_CONFIG+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + if test -n "$ac_ct_NCURSES_CONFIG"; then + ac_cv_prog_ac_ct_NCURSES_CONFIG="$ac_ct_NCURSES_CONFIG" # Let the user override the test. +else + ac_save_IFS=$IFS; IFS=$ac_path_separator +ac_dummy="$PATH" +for ac_dir in $ac_dummy; do + IFS=$ac_save_IFS + test -z "$ac_dir" && ac_dir=. + $as_executable_p "$ac_dir/$ac_word" || continue +ac_cv_prog_ac_ct_NCURSES_CONFIG="$ac_prog" +echo "$as_me:11407: found $ac_dir/$ac_word" >&5 +break +done + +fi +fi +ac_ct_NCURSES_CONFIG=$ac_cv_prog_ac_ct_NCURSES_CONFIG +if test -n "$ac_ct_NCURSES_CONFIG"; then + echo "$as_me:11415: result: $ac_ct_NCURSES_CONFIG" >&5 +echo "${ECHO_T}$ac_ct_NCURSES_CONFIG" >&6 +else + echo "$as_me:11418: result: no" >&5 +echo "${ECHO_T}no" >&6 +fi + + test -n "$ac_ct_NCURSES_CONFIG" && break +done +test -n "$ac_ct_NCURSES_CONFIG" || ac_ct_NCURSES_CONFIG="none" + + NCURSES_CONFIG=$ac_ct_NCURSES_CONFIG +fi + + if test "$NCURSES_CONFIG" != none ; then + +for cf_add_cflags in `$NCURSES_CONFIG --cflags` +do + case "x$cf_add_cflags" in + (x-[DU]*) + +cf_tmp_cflag=`echo "x$cf_add_cflags" | sed -e 's/^.//' -e 's/=.*//'` +while true +do + cf_old_cflag=`echo "x$CFLAGS" | sed -e 's/^.//' -e 's/[ ][ ]*-/ -/g' -e "s%$cf_tmp_cflag\\(=[^ ][^ ]*\\)\?%%" -e 's/^[ ]*//' -e 's%[ ][ ]*-D% -D%g' -e 's%[ ][ ]*-I% -I%g'` + test "$CFLAGS" != "$cf_old_cflag" || break + + CFLAGS="$cf_old_cflag" +done + +cf_tmp_cflag=`echo "x$cf_add_cflags" | sed -e 's/^.//' -e 's/=.*//'` +while true +do + cf_old_cflag=`echo "x$CPPFLAGS" | sed -e 's/^.//' -e 's/[ ][ ]*-/ -/g' -e "s%$cf_tmp_cflag\\(=[^ ][^ ]*\\)\?%%" -e 's/^[ ]*//' -e 's%[ ][ ]*-D% -D%g' -e 's%[ ][ ]*-I% -I%g'` + test "$CPPFLAGS" != "$cf_old_cflag" || break + + CPPFLAGS="$cf_old_cflag" +done + + ;; + esac + +cf_fix_cppflags=no +cf_new_cflags= +cf_new_cppflags= +cf_new_extra_cppflags= + +for cf_add_cflags in $cf_add_cflags +do +case "$cf_fix_cppflags" in +(no) + case "$cf_add_cflags" in + (-undef|-nostdinc*|-I*|-D*|-U*|-E|-P|-C) + case "$cf_add_cflags" in + (-D*) + cf_tst_cflags=`echo "${cf_add_cflags}" |sed -e 's/^-D[^=]*='\''\"[^"]*//'` + + test "x${cf_add_cflags}" != "x${cf_tst_cflags}" \ + && test -z "${cf_tst_cflags}" \ + && cf_fix_cppflags=yes + + if test "$cf_fix_cppflags" = yes ; then + + test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " + cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" + + continue + elif test "${cf_tst_cflags}" = "\"'" ; then + + test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " + cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" + + continue + fi + ;; + esac + case "$CPPFLAGS" in + (*$cf_add_cflags) + ;; + (*) + case "$cf_add_cflags" in + (-D*) + cf_tst_cppflags=`echo "x$cf_add_cflags" | sed -e 's/^...//' -e 's/=.*//'` + +CPPFLAGS=`echo "$CPPFLAGS" | \ + sed -e 's/-[UD]'"$cf_tst_cppflags"'\(=[^ ]*\)\?[ ]/ /g' \ + -e 's/-[UD]'"$cf_tst_cppflags"'\(=[^ ]*\)\?$//g'` + + ;; + esac + + test -n "$cf_new_cppflags" && cf_new_cppflags="$cf_new_cppflags " + cf_new_cppflags="${cf_new_cppflags}$cf_add_cflags" + + ;; + esac + ;; + (*) + + test -n "$cf_new_cflags" && cf_new_cflags="$cf_new_cflags " + cf_new_cflags="${cf_new_cflags}$cf_add_cflags" + + ;; + esac + ;; +(yes) + + test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " + cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" + + cf_tst_cflags=`echo "${cf_add_cflags}" |sed -e 's/^[^"]*"'\''//'` + + test "x${cf_add_cflags}" != "x${cf_tst_cflags}" \ + && test -z "${cf_tst_cflags}" \ + && cf_fix_cppflags=no + ;; +esac +done + +if test -n "$cf_new_cflags" ; then + + test -n "$CFLAGS" && CFLAGS="$CFLAGS " + CFLAGS="${CFLAGS}$cf_new_cflags" + +fi + +if test -n "$cf_new_cppflags" ; then + + test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " + CPPFLAGS="${CPPFLAGS}$cf_new_cppflags" + +fi + +if test -n "$cf_new_extra_cppflags" ; then + + test -n "$EXTRA_CPPFLAGS" && EXTRA_CPPFLAGS="$EXTRA_CPPFLAGS " + EXTRA_CPPFLAGS="${EXTRA_CPPFLAGS}$cf_new_extra_cppflags" + +fi + +done + +cf_add_libs="$LIBS" +# reverse order +cf_add_0lib= +for cf_add_1lib in `$NCURSES_CONFIG --libs`; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done +# filter duplicates +for cf_add_1lib in $cf_add_0lib; do + for cf_add_2lib in $cf_add_libs; do + if test "x$cf_add_1lib" = "x$cf_add_2lib"; then + cf_add_1lib= + break + fi + done + test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" +done +LIBS="$cf_add_libs" + + # even with config script, some packages use no-override for curses.h + +echo "$as_me:11575: checking if we have identified curses headers" >&5 +echo $ECHO_N "checking if we have identified curses headers... $ECHO_C" >&6 +if test "${cf_cv_ncurses_header+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + +cf_cv_ncurses_header=none +for cf_header in \ + ncurses.h $cf_cv_screen/ncurses.h \ + curses.h $cf_cv_screen/curses.h +do +cat >"conftest.$ac_ext" <<_ACEOF +#line 11587 "configure" +#include "confdefs.h" +#include <${cf_header}> +int +main (void) +{ +initscr(); endwin() + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:11599: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:11602: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:11605: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:11608: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_cv_ncurses_header=$cf_header; break +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" +done + +fi +echo "$as_me:11619: result: $cf_cv_ncurses_header" >&5 +echo "${ECHO_T}$cf_cv_ncurses_header" >&6 + +if test "$cf_cv_ncurses_header" = none ; then + { { echo "$as_me:11623: error: No curses header-files found" >&5 +echo "$as_me: error: No curses header-files found" >&2;} + { (exit 1); exit 1; }; } +fi + +# cheat, to get the right #define's for HAVE_NCURSES_H, etc. + +for ac_header in $cf_cv_ncurses_header +do +as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` +echo "$as_me:11633: checking for $ac_header" >&5 +echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 +if eval "test \"\${$as_ac_Header+set}\" = set"; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + cat >"conftest.$ac_ext" <<_ACEOF +#line 11639 "configure" +#include "confdefs.h" +#include <$ac_header> +_ACEOF +if { (eval echo "$as_me:11643: \"$ac_cpp "conftest.$ac_ext"\"") >&5 + (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 + ac_status=$? + $EGREP -v '^ *\+' conftest.er1 >conftest.err + rm -f conftest.er1 + cat conftest.err >&5 + echo "$as_me:11649: \$? = $ac_status" >&5 + (exit "$ac_status"); } >/dev/null; then + if test -s conftest.err; then + ac_cpp_err=$ac_c_preproc_warn_flag + else + ac_cpp_err= + fi +else + ac_cpp_err=yes +fi +if test -z "$ac_cpp_err"; then + eval "$as_ac_Header=yes" +else + echo "$as_me: failed program was:" >&5 + cat "conftest.$ac_ext" >&5 + eval "$as_ac_Header=no" +fi +rm -f conftest.err "conftest.$ac_ext" +fi +echo "$as_me:11668: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 +echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 +if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then + cat >>confdefs.h <>confdefs.h <<\EOF +#define NCURSES 1 +EOF + +cf_nculib_ROOT=`echo "HAVE_LIB$cf_ncuconfig_root" | sed y%abcdefghijklmnopqrstuvwxyz./-%ABCDEFGHIJKLMNOPQRSTUVWXYZ___%` + + cat >>confdefs.h <"conftest.$ac_ext" <<_ACEOF +#line 11724 "configure" +#include "confdefs.h" +#include +int +main (void) +{ +printf("Hello") + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:11736: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:11739: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:11742: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:11745: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + : +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_have_incdir=yes +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" + CPPFLAGS=$cf_save_CPPFLAGS + fi + fi + fi + + if test "$cf_have_incdir" = no ; then + test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 + +echo "${as_me:-configure}:11762: testing adding $cf_add_incdir to include-path ..." 1>&5 + + CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" + + cf_top_incdir=`echo "$cf_add_incdir" | sed -e 's%/include/.*$%/include%'` + test "$cf_top_incdir" = "$cf_add_incdir" && break + cf_add_incdir="$cf_top_incdir" + else + break + fi + else + break + fi + done + done +fi + +} + +echo "$as_me:11781: checking for $cf_ncuhdr_root header in include-path" >&5 +echo $ECHO_N "checking for $cf_ncuhdr_root header in include-path... $ECHO_C" >&6 +if test "${cf_cv_ncurses_h+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + + cf_header_list="$cf_ncuhdr_root/curses.h $cf_ncuhdr_root/ncurses.h" + { test "$cf_ncuhdr_root" = ncurses || test "$cf_ncuhdr_root" = ncursesw; } && cf_header_list="$cf_header_list curses.h ncurses.h" + for cf_header in $cf_header_list + do + + cat >"conftest.$ac_ext" <<_ACEOF +#line 11793 "configure" +#include "confdefs.h" + +#include <$cf_header> +int +main (void) +{ + +#ifdef NCURSES_VERSION + +printf("%s\\n", NCURSES_VERSION); +#else +#ifdef __NCURSES_H +printf("old\\n"); +#else + #error __NCURSES_H is not defined +#endif +#endif + + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:11817: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:11820: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:11823: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:11826: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_cv_ncurses_h=$cf_header + +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_cv_ncurses_h=no +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" + + test "$cf_cv_ncurses_h" != no && break + done + +fi +echo "$as_me:11841: result: $cf_cv_ncurses_h" >&5 +echo "${ECHO_T}$cf_cv_ncurses_h" >&6 + +if test "$cf_cv_ncurses_h" != no ; then + cf_cv_ncurses_header=$cf_cv_ncurses_h +else + +echo "$as_me:11848: checking for $cf_ncuhdr_root include-path" >&5 +echo $ECHO_N "checking for $cf_ncuhdr_root include-path... $ECHO_C" >&6 +if test "${cf_cv_ncurses_h2+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + + test -n "$verbose" && echo + +cf_search= + +# collect the current set of include-directories from compiler flags +cf_header_path_list="" +if test -n "${CFLAGS}${CPPFLAGS}" ; then + for cf_header_path in $CPPFLAGS $CFLAGS + do + case "$cf_header_path" in + (-I*) + cf_header_path=`echo ".$cf_header_path" |sed -e 's/^...//' -e 's,/include$,,'` + +test "x$cf_header_path" != "xNONE" && \ +test -d "$cf_header_path" && \ + { + test -n "$verbose" && echo " ... testing for include-directories under $cf_header_path" + test -d "$cf_header_path/include" && cf_search="$cf_search $cf_header_path/include" + test -d "$cf_header_path/include/$cf_ncuhdr_root" && cf_search="$cf_search $cf_header_path/include/$cf_ncuhdr_root" + test -d "$cf_header_path/include/$cf_ncuhdr_root/include" && cf_search="$cf_search $cf_header_path/include/$cf_ncuhdr_root/include" + test -d "$cf_header_path/$cf_ncuhdr_root/include" && cf_search="$cf_search $cf_header_path/$cf_ncuhdr_root/include" + test -d "$cf_header_path/$cf_ncuhdr_root/include/$cf_ncuhdr_root" && cf_search="$cf_search $cf_header_path/$cf_ncuhdr_root/include/$cf_ncuhdr_root" +} + + cf_header_path_list="$cf_header_path_list $cf_search" + ;; + esac + done +fi + +# add the variations for the package we are looking for + +cf_search= + +test "x$prefix" != "xNONE" && \ +test -d "$prefix" && \ + { + test -n "$verbose" && echo " ... testing for include-directories under $prefix" + test -d "$prefix/include" && cf_search="$cf_search $prefix/include" + test -d "$prefix/include/$cf_ncuhdr_root" && cf_search="$cf_search $prefix/include/$cf_ncuhdr_root" + test -d "$prefix/include/$cf_ncuhdr_root/include" && cf_search="$cf_search $prefix/include/$cf_ncuhdr_root/include" + test -d "$prefix/$cf_ncuhdr_root/include" && cf_search="$cf_search $prefix/$cf_ncuhdr_root/include" + test -d "$prefix/$cf_ncuhdr_root/include/$cf_ncuhdr_root" && cf_search="$cf_search $prefix/$cf_ncuhdr_root/include/$cf_ncuhdr_root" +} + +for cf_subdir_prefix in \ + /usr \ + /usr/local \ + /usr/pkg \ + /opt \ + /opt/local \ + $HOME +do + +test "x$cf_subdir_prefix" != "x$prefix" && \ +test -d "$cf_subdir_prefix" && \ +{ test -z "$prefix" || test "x$prefix" = xNONE || test "x$cf_subdir_prefix" != "x$prefix"; } && { + test -n "$verbose" && echo " ... testing for include-directories under $cf_subdir_prefix" + test -d "$cf_subdir_prefix/include" && cf_search="$cf_search $cf_subdir_prefix/include" + test -d "$cf_subdir_prefix/include/$cf_ncuhdr_root" && cf_search="$cf_search $cf_subdir_prefix/include/$cf_ncuhdr_root" + test -d "$cf_subdir_prefix/include/$cf_ncuhdr_root/include" && cf_search="$cf_search $cf_subdir_prefix/include/$cf_ncuhdr_root/include" + test -d "$cf_subdir_prefix/$cf_ncuhdr_root/include" && cf_search="$cf_search $cf_subdir_prefix/$cf_ncuhdr_root/include" + test -d "$cf_subdir_prefix/$cf_ncuhdr_root/include/$cf_ncuhdr_root" && cf_search="$cf_search $cf_subdir_prefix/$cf_ncuhdr_root/include/$cf_ncuhdr_root" +} + +done + +test "$includedir" != NONE && \ +test "$includedir" != "/usr/include" && \ +test -d "$includedir" && { + test -d "$includedir" && cf_search="$cf_search $includedir" + test -d "$includedir/$cf_ncuhdr_root" && cf_search="$cf_search $includedir/$cf_ncuhdr_root" +} + +test "$oldincludedir" != NONE && \ +test "$oldincludedir" != "/usr/include" && \ +test -d "$oldincludedir" && { + test -d "$oldincludedir" && cf_search="$cf_search $oldincludedir" + test -d "$oldincludedir/$cf_ncuhdr_root" && cf_search="$cf_search $oldincludedir/$cf_ncuhdr_root" +} + +cf_search="$cf_search $cf_header_path_list" + + test -n "$verbose" && echo "search path $cf_search" + cf_save2_CPPFLAGS="$CPPFLAGS" + for cf_incdir in $cf_search + do + +if test -n "$cf_incdir" ; then + for cf_add_incdir in $cf_incdir + do + while test "$cf_add_incdir" != /usr/include + do + if test -d "$cf_add_incdir" + then + cf_have_incdir=no + if test -n "$CFLAGS$CPPFLAGS" ; then + # a loop is needed to ensure we can add subdirs of existing dirs + for cf_test_incdir in $CFLAGS $CPPFLAGS ; do + if test ".$cf_test_incdir" = ".-I$cf_add_incdir" ; then + cf_have_incdir=yes; break + fi + done + fi + + if test "$cf_have_incdir" = no ; then + if test "$cf_add_incdir" = /usr/local/include ; then + if test "$GCC" = yes + then + cf_save_CPPFLAGS=$CPPFLAGS + + test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " + CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" + + cat >"conftest.$ac_ext" <<_ACEOF +#line 11969 "configure" +#include "confdefs.h" +#include +int +main (void) +{ +printf("Hello") + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:11981: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:11984: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:11987: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:11990: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + : +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_have_incdir=yes +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" + CPPFLAGS=$cf_save_CPPFLAGS + fi + fi + fi + + if test "$cf_have_incdir" = no ; then + test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 + +echo "${as_me:-configure}:12007: testing adding $cf_add_incdir to include-path ..." 1>&5 + + CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" + + cf_top_incdir=`echo "$cf_add_incdir" | sed -e 's%/include/.*$%/include%'` + test "$cf_top_incdir" = "$cf_add_incdir" && break + cf_add_incdir="$cf_top_incdir" + else + break + fi + else + break + fi + done + done +fi + + for cf_header in \ + ncurses.h \ + curses.h + do + + cat >"conftest.$ac_ext" <<_ACEOF +#line 12030 "configure" +#include "confdefs.h" + +#include <$cf_header> +int +main (void) +{ + +#ifdef NCURSES_VERSION + +printf("%s\\n", NCURSES_VERSION); +#else +#ifdef __NCURSES_H +printf("old\\n"); +#else + #error __NCURSES_H is not defined +#endif +#endif + + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:12054: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:12057: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:12060: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12063: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_cv_ncurses_h2=$cf_header + +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_cv_ncurses_h2=no +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" + + if test "$cf_cv_ncurses_h2" != no ; then + cf_cv_ncurses_h2=$cf_incdir/$cf_header + test -n "$verbose" && echo $ECHO_N " ... found $ECHO_C" 1>&6 + break + fi + test -n "$verbose" && echo " ... tested $cf_incdir/$cf_header" 1>&6 + done + CPPFLAGS="$cf_save2_CPPFLAGS" + test "$cf_cv_ncurses_h2" != no && break + done + test "$cf_cv_ncurses_h2" = no && { { echo "$as_me:12084: error: not found" >&5 +echo "$as_me: error: not found" >&2;} + { (exit 1); exit 1; }; } + +fi +echo "$as_me:12089: result: $cf_cv_ncurses_h2" >&5 +echo "${ECHO_T}$cf_cv_ncurses_h2" >&6 + + cf_1st_incdir=`echo "$cf_cv_ncurses_h2" | sed -e 's%/[^/]*$%%'` + cf_cv_ncurses_header="`basename "$cf_cv_ncurses_h2"`" + if test "`basename "$cf_1st_incdir"`" = "$cf_ncuhdr_root" ; then + cf_cv_ncurses_header="$cf_ncuhdr_root/$cf_cv_ncurses_header" + fi + +if test -n "$cf_1st_incdir" ; then + for cf_add_incdir in $cf_1st_incdir + do + while test "$cf_add_incdir" != /usr/include + do + if test -d "$cf_add_incdir" + then + cf_have_incdir=no + if test -n "$CFLAGS$CPPFLAGS" ; then + # a loop is needed to ensure we can add subdirs of existing dirs + for cf_test_incdir in $CFLAGS $CPPFLAGS ; do + if test ".$cf_test_incdir" = ".-I$cf_add_incdir" ; then + cf_have_incdir=yes; break + fi + done + fi + + if test "$cf_have_incdir" = no ; then + if test "$cf_add_incdir" = /usr/local/include ; then + if test "$GCC" = yes + then + cf_save_CPPFLAGS=$CPPFLAGS + + test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " + CPPFLAGS="${CPPFLAGS}-I$cf_add_incdir" + + cat >"conftest.$ac_ext" <<_ACEOF +#line 12125 "configure" +#include "confdefs.h" +#include +int +main (void) +{ +printf("Hello") + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:12137: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:12140: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:12143: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12146: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + : +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_have_incdir=yes +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" + CPPFLAGS=$cf_save_CPPFLAGS + fi + fi + fi + + if test "$cf_have_incdir" = no ; then + test -n "$verbose" && echo " adding $cf_add_incdir to include-path" 1>&6 + +echo "${as_me:-configure}:12163: testing adding $cf_add_incdir to include-path ..." 1>&5 + + CPPFLAGS="$CPPFLAGS -I$cf_add_incdir" + + cf_top_incdir=`echo "$cf_add_incdir" | sed -e 's%/include/.*$%/include%'` + test "$cf_top_incdir" = "$cf_add_incdir" && break + cf_add_incdir="$cf_top_incdir" + else + break + fi + else + break + fi + done + done +fi + +fi + +# Set definitions to allow ifdef'ing for ncurses.h + +case "$cf_cv_ncurses_header" in +(*ncurses.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSES_H 1 +EOF + + ;; +esac + +case "$cf_cv_ncurses_header" in +(ncurses/curses.h|ncurses/ncurses.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSES_NCURSES_H 1 +EOF + + ;; +(ncursesw/curses.h|ncursesw/ncurses.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSESW_NCURSES_H 1 +EOF + + ;; +esac + +echo "$as_me:12211: checking for terminfo header" >&5 +echo $ECHO_N "checking for terminfo header... $ECHO_C" >&6 +if test "${cf_cv_term_header+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + +case "${cf_cv_ncurses_header}" in +(*/ncurses.h|*/ncursesw.h) + cf_term_header=`echo "$cf_cv_ncurses_header" | sed -e 's%ncurses[^.]*\.h$%term.h%'` + ;; +(*) + cf_term_header=term.h + ;; +esac + +for cf_test in $cf_term_header "ncurses/term.h" "ncursesw/term.h" +do +cat >"conftest.$ac_ext" <<_ACEOF +#line 12229 "configure" +#include "confdefs.h" +#include +#include <${cf_cv_ncurses_header:-curses.h}> +#include <$cf_test> + +int +main (void) +{ +int x = auto_left_margin; (void)x + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:12244: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:12247: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:12250: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12253: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + + cf_cv_term_header="$cf_test" +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 + + cf_cv_term_header=unknown + +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" + test "$cf_cv_term_header" != unknown && break +done + +fi +echo "$as_me:12269: result: $cf_cv_term_header" >&5 +echo "${ECHO_T}$cf_cv_term_header" >&6 + +# Set definitions to allow ifdef'ing to accommodate subdirectories + +case "$cf_cv_term_header" in +(*term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_TERM_H 1 +EOF + + ;; +esac + +case "$cf_cv_term_header" in +(ncurses/term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSES_TERM_H 1 +EOF + + ;; +(ncursesw/term.h) + +cat >>confdefs.h <<\EOF +#define HAVE_NCURSESW_TERM_H 1 +EOF + + ;; +esac + +# some applications need this, but should check for NCURSES_VERSION + +cat >>confdefs.h <<\EOF +#define NCURSES 1 +EOF + +echo "$as_me:12307: checking for ncurses version" >&5 +echo $ECHO_N "checking for ncurses version... $ECHO_C" >&6 +if test "${cf_cv_ncurses_version+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + + cf_cv_ncurses_version=no + cf_tempfile=out$$ + rm -f "$cf_tempfile" + if test "$cross_compiling" = yes; then + + # This will not work if the preprocessor splits the line after the + # Autoconf token. The 'unproto' program does that. + cat > "conftest.$ac_ext" < +#undef Autoconf +#ifdef NCURSES_VERSION +Autoconf NCURSES_VERSION +#else +#ifdef __NCURSES_H +Autoconf "old" +#endif +; +#endif +EOF + cf_try="$ac_cpp conftest.$ac_ext 2>&5 | grep '^Autoconf ' >conftest.out" + { (eval echo "$as_me:12333: \"$cf_try\"") >&5 + (eval $cf_try) 2>&5 + ac_status=$? + echo "$as_me:12336: \$? = $ac_status" >&5 + (exit "$ac_status"); } + if test -f conftest.out ; then + cf_out=`sed -e 's%^Autoconf %%' -e 's%^[^"]*"%%' -e 's%".*%%' conftest.out` + test -n "$cf_out" && cf_cv_ncurses_version="$cf_out" + rm -f conftest.out + fi + +else + cat >"conftest.$ac_ext" <<_ACEOF +#line 12346 "configure" +#include "confdefs.h" + +$ac_includes_default + +#include <${cf_cv_ncurses_header:-curses.h}> + +int main(void) +{ + FILE *fp = fopen("$cf_tempfile", "w"); +#ifdef NCURSES_VERSION +# ifdef NCURSES_VERSION_PATCH + fprintf(fp, "%s.%d\\n", NCURSES_VERSION, NCURSES_VERSION_PATCH); +# else + fprintf(fp, "%s\\n", NCURSES_VERSION); +# endif +#else +# ifdef __NCURSES_H + fprintf(fp, "old\\n"); +# else + #error expected ncurses header to define __NCURSES_H +# endif +#endif + ${cf_cv_main_return:-return}(0); +} +_ACEOF +rm -f "conftest$ac_exeext" +if { (eval echo "$as_me:12373: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:12376: \$? = $ac_status" >&5 + (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' + { (eval echo "$as_me:12378: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12381: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + + cf_cv_ncurses_version=`cat $cf_tempfile` +else + echo "$as_me: program exited with status $ac_status" >&5 +echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +fi +rm -f core ./core.* ./*.core "conftest$ac_exeext" "conftest.$ac_objext" "conftest.$ac_ext" +fi + rm -f "$cf_tempfile" + +fi +echo "$as_me:12395: result: $cf_cv_ncurses_version" >&5 +echo "${ECHO_T}$cf_cv_ncurses_version" >&6 +test "$cf_cv_ncurses_version" = no || +cat >>confdefs.h <<\EOF +#define NCURSES 1 +EOF + +cf_nculib_root=$cf_cv_screen + # This works, except for the special case where we find gpm, but + # ncurses is in a nonstandard location via $LIBS, and we really want + # to link gpm. +cf_ncurses_LIBS="" +cf_ncurses_SAVE="$LIBS" +echo "$as_me:12408: checking for Gpm_Open in -lgpm" >&5 +echo $ECHO_N "checking for Gpm_Open in -lgpm... $ECHO_C" >&6 +if test "${ac_cv_lib_gpm_Gpm_Open+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-lgpm $LIBS" +cat >"conftest.$ac_ext" <<_ACEOF +#line 12416 "configure" +#include "confdefs.h" + +/* Override any gcc2 internal prototype to avoid an error. */ +#ifdef __cplusplus +extern "C" +#endif +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char Gpm_Open (void); +int +main (void) +{ +Gpm_Open (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:12435: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:12438: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:12441: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12444: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_lib_gpm_Gpm_Open=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_lib_gpm_Gpm_Open=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +LIBS=$ac_check_lib_save_LIBS +fi +echo "$as_me:12455: result: $ac_cv_lib_gpm_Gpm_Open" >&5 +echo "${ECHO_T}$ac_cv_lib_gpm_Gpm_Open" >&6 +if test "$ac_cv_lib_gpm_Gpm_Open" = yes; then + echo "$as_me:12458: checking for initscr in -lgpm" >&5 +echo $ECHO_N "checking for initscr in -lgpm... $ECHO_C" >&6 +if test "${ac_cv_lib_gpm_initscr+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-lgpm $LIBS" +cat >"conftest.$ac_ext" <<_ACEOF +#line 12466 "configure" +#include "confdefs.h" + +/* Override any gcc2 internal prototype to avoid an error. */ +#ifdef __cplusplus +extern "C" +#endif +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char initscr (void); +int +main (void) +{ +initscr (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:12485: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:12488: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:12491: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12494: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_lib_gpm_initscr=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_lib_gpm_initscr=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +LIBS=$ac_check_lib_save_LIBS +fi +echo "$as_me:12505: result: $ac_cv_lib_gpm_initscr" >&5 +echo "${ECHO_T}$ac_cv_lib_gpm_initscr" >&6 +if test "$ac_cv_lib_gpm_initscr" = yes; then + LIBS="$cf_ncurses_SAVE" +else + cf_ncurses_LIBS="-lgpm" +fi + +fi + +case "$host_os" in +(freebsd*) + # This is only necessary if you are linking against an obsolete + # version of ncurses (but it should do no harm, since it is static). + if test "$cf_nculib_root" = ncurses ; then + echo "$as_me:12520: checking for tgoto in -lmytinfo" >&5 +echo $ECHO_N "checking for tgoto in -lmytinfo... $ECHO_C" >&6 +if test "${ac_cv_lib_mytinfo_tgoto+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-lmytinfo $LIBS" +cat >"conftest.$ac_ext" <<_ACEOF +#line 12528 "configure" +#include "confdefs.h" + +/* Override any gcc2 internal prototype to avoid an error. */ +#ifdef __cplusplus +extern "C" +#endif +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char tgoto (void); +int +main (void) +{ +tgoto (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:12547: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:12550: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:12553: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12556: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_lib_mytinfo_tgoto=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_lib_mytinfo_tgoto=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +LIBS=$ac_check_lib_save_LIBS +fi +echo "$as_me:12567: result: $ac_cv_lib_mytinfo_tgoto" >&5 +echo "${ECHO_T}$ac_cv_lib_mytinfo_tgoto" >&6 +if test "$ac_cv_lib_mytinfo_tgoto" = yes; then + cf_ncurses_LIBS="-lmytinfo $cf_ncurses_LIBS" +fi + + fi + ;; +esac + +cf_add_libs="$LIBS" +# reverse order +cf_add_0lib= +for cf_add_1lib in $cf_ncurses_LIBS; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done +# filter duplicates +for cf_add_1lib in $cf_add_0lib; do + for cf_add_2lib in $cf_add_libs; do + if test "x$cf_add_1lib" = "x$cf_add_2lib"; then + cf_add_1lib= + break + fi + done + test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" +done +LIBS="$cf_add_libs" + +if test -n "$cf_cv_curses_dir" && test "$cf_cv_curses_dir" != "no" +then + +cf_add_libs="$LIBS" +# reverse order +cf_add_0lib= +for cf_add_1lib in -l$cf_nculib_root; do cf_add_0lib="$cf_add_1lib $cf_add_0lib"; done +# filter duplicates +for cf_add_1lib in $cf_add_0lib; do + for cf_add_2lib in $cf_add_libs; do + if test "x$cf_add_1lib" = "x$cf_add_2lib"; then + cf_add_1lib= + break + fi + done + test -n "$cf_add_1lib" && cf_add_libs="$cf_add_1lib $cf_add_libs" +done +LIBS="$cf_add_libs" + +else + + eval 'cf_cv_have_lib_'"$cf_nculib_root"'=no' + cf_libdir="" + echo "$as_me:12616: checking for initscr" >&5 +echo $ECHO_N "checking for initscr... $ECHO_C" >&6 +if test "${ac_cv_func_initscr+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + cat >"conftest.$ac_ext" <<_ACEOF +#line 12622 "configure" +#include "confdefs.h" +#define initscr autoconf_temporary +#include /* least-intrusive standard header which defines gcc2 __stub macros */ +#undef initscr + +#ifdef __cplusplus +extern "C" +#endif + +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char initscr (void); + +int +main (void) +{ + +/* The GNU C library defines stubs for functions which it implements + to always fail with ENOSYS. Some functions are actually named + something starting with __ and the normal name is an alias. */ +#if defined (__stub_initscr) || defined (__stub___initscr) +#error found stub for initscr +#endif + + return initscr (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:12653: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:12656: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:12659: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12662: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_func_initscr=yes else @@ -11293,18 +12669,18 @@ ac_cv_func_initscr=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:11296: result: $ac_cv_func_initscr" >&5 +echo "$as_me:12672: result: $ac_cv_func_initscr" >&5 echo "${ECHO_T}$ac_cv_func_initscr" >&6 if test "$ac_cv_func_initscr" = yes; then eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' else cf_save_LIBS="$LIBS" - echo "$as_me:11303: checking for initscr in -l$cf_nculib_root" >&5 + echo "$as_me:12679: checking for initscr in -l$cf_nculib_root" >&5 echo $ECHO_N "checking for initscr in -l$cf_nculib_root... $ECHO_C" >&6 LIBS="-l$cf_nculib_root $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 11307 "configure" +#line 12683 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -11316,25 +12692,25 @@ initscr() } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11319: \"$ac_link\"") >&5 +if { (eval echo "$as_me:12695: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:11322: \$? = $ac_status" >&5 + echo "$as_me:12698: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:11325: \"$ac_try\"") >&5 + { (eval echo "$as_me:12701: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:11328: \$? = $ac_status" >&5 + echo "$as_me:12704: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:11330: result: yes" >&5 + echo "$as_me:12706: result: yes" >&5 echo "${ECHO_T}yes" >&6 eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:11337: result: no" >&5 +echo "$as_me:12713: result: no" >&5 echo "${ECHO_T}no" >&6 cf_search= @@ -11402,11 +12778,11 @@ cf_search="$cf_library_path_list $cf_search" for cf_libdir in $cf_search do - echo "$as_me:11405: checking for -l$cf_nculib_root in $cf_libdir" >&5 + echo "$as_me:12781: checking for -l$cf_nculib_root in $cf_libdir" >&5 echo $ECHO_N "checking for -l$cf_nculib_root in $cf_libdir... $ECHO_C" >&6 LIBS="-L$cf_libdir -l$cf_nculib_root $cf_save_LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 11409 "configure" +#line 12785 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -11418,25 +12794,25 @@ initscr() } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11421: \"$ac_link\"") >&5 +if { (eval echo "$as_me:12797: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:11424: \$? = $ac_status" >&5 + echo "$as_me:12800: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:11427: \"$ac_try\"") >&5 + { (eval echo "$as_me:12803: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:11430: \$? = $ac_status" >&5 + echo "$as_me:12806: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:11432: result: yes" >&5 + echo "$as_me:12808: result: yes" >&5 echo "${ECHO_T}yes" >&6 eval 'cf_cv_have_lib_'"$cf_nculib_root"'=yes' break else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:11439: result: no" >&5 +echo "$as_me:12815: result: no" >&5 echo "${ECHO_T}no" >&6 LIBS="$cf_save_LIBS" fi @@ -11451,7 +12827,7 @@ fi eval 'cf_found_library="$cf_cv_have_lib_'"$cf_nculib_root"\" if test "$cf_found_library" = no ; then - { { echo "$as_me:11454: error: Cannot link $cf_nculib_root library" >&5 + { { echo "$as_me:12830: error: Cannot link $cf_nculib_root library" >&5 echo "$as_me: error: Cannot link $cf_nculib_root library" >&2;} { (exit 1); exit 1; }; } fi @@ -11459,7 +12835,7 @@ fi fi if test -n "$cf_ncurses_LIBS" ; then - echo "$as_me:11462: checking if we can link $cf_nculib_root without $cf_ncurses_LIBS" >&5 + echo "$as_me:12838: checking if we can link $cf_nculib_root without $cf_ncurses_LIBS" >&5 echo $ECHO_N "checking if we can link $cf_nculib_root without $cf_ncurses_LIBS... $ECHO_C" >&6 cf_ncurses_SAVE="$LIBS" for p in $cf_ncurses_LIBS ; do @@ -11469,7 +12845,7 @@ echo $ECHO_N "checking if we can link $cf_nculib_root without $cf_ncurses_LIBS.. fi done cat >"conftest.$ac_ext" <<_ACEOF -#line 11472 "configure" +#line 12848 "configure" #include "confdefs.h" #include <${cf_cv_ncurses_header:-curses.h}> int @@ -11481,23 +12857,23 @@ initscr(); mousemask(0,0); tigetstr((char *)0); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11484: \"$ac_link\"") >&5 +if { (eval echo "$as_me:12860: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:11487: \$? = $ac_status" >&5 + echo "$as_me:12863: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:11490: \"$ac_try\"") >&5 + { (eval echo "$as_me:12866: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:11493: \$? = $ac_status" >&5 + echo "$as_me:12869: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then - echo "$as_me:11495: result: yes" >&5 + echo "$as_me:12871: result: yes" >&5 echo "${ECHO_T}yes" >&6 else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 -echo "$as_me:11500: result: no" >&5 +echo "$as_me:12876: result: no" >&5 echo "${ECHO_T}no" >&6 LIBS="$cf_ncurses_SAVE" fi @@ -11515,7 +12891,13 @@ else NCURSES_CONFIG=none fi -fi + ;; +(*) + { { echo "$as_me:12896: error: unexpected screen-value: $cf_cv_screen" >&5 +echo "$as_me: error: unexpected screen-value: $cf_cv_screen" >&2;} + { (exit 1); exit 1; }; } + ;; +esac if test "$NCURSES_CONFIG_PKG" != none ; then cf_version=`$PKG_CONFIG --modversion $NCURSES_CONFIG_PKG 2>/dev/null` @@ -11550,10 +12932,10 @@ else AUTOCONF_$cf_name NCURSES_VERSION_$cf_name CF_EOF cf_try="$ac_cpp conftest.$ac_ext 2>&5 | fgrep AUTOCONF_$cf_name >conftest.out" - { (eval echo "$as_me:11553: \"$cf_try\"") >&5 + { (eval echo "$as_me:12935: \"$cf_try\"") >&5 (eval $cf_try) 2>&5 ac_status=$? - echo "$as_me:11556: \$? = $ac_status" >&5 + echo "$as_me:12938: \$? = $ac_status" >&5 (exit "$ac_status"); } if test -f conftest.out ; then cf_result=`sed -e "s/^.*AUTOCONF_${cf_name}[ ][ ]*//" conftest.out` @@ -11571,10 +12953,53 @@ cf_cv_rel_version=${NCURSES_MAJOR}.${NCURSES_MINOR} cf_cv_timestamp=`date` -echo "$as_me:11574: result: Configuring NCURSES $cf_cv_rel_version ABI $cf_cv_abi_version ($cf_cv_timestamp)" >&5 +echo "$as_me:12956: result: Configuring NCURSES $cf_cv_rel_version ABI $cf_cv_abi_version ($cf_cv_timestamp)" >&5 echo "${ECHO_T}Configuring NCURSES $cf_cv_rel_version ABI $cf_cv_abi_version ($cf_cv_timestamp)" >&6 -echo "$as_me:11577: checking if you want to have a library-prefix" >&5 +echo "$as_me:12959: checking if KEY_RESIZE is supported" >&5 +echo $ECHO_N "checking if KEY_RESIZE is supported... $ECHO_C" >&6 +if test "${cf_cv_curses_resizes+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + + cat >"conftest.$ac_ext" <<_ACEOF +#line 12966 "configure" +#include "confdefs.h" +#include <${cf_cv_ncurses_header:-curses.h}> +int +main (void) +{ +int key = KEY_RESIZE; (void)key + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" +if { (eval echo "$as_me:12978: \"$ac_compile\"") >&5 + (eval $ac_compile) 2>&5 + ac_status=$? + echo "$as_me:12981: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest.$ac_objext"' + { (eval echo "$as_me:12984: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:12987: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + cf_cv_curses_resizes=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +cf_cv_curses_resizes=no +fi +rm -f "conftest.$ac_objext" "conftest.$ac_ext" +fi +echo "$as_me:12997: result: $cf_cv_curses_resizes" >&5 +echo "${ECHO_T}$cf_cv_curses_resizes" >&6 +cf_cv_enable_sigwinch=0 +test "$cf_cv_curses_resizes" = yes && cf_cv_enable_sigwinch=1 + +echo "$as_me:13002: checking if you want to have a library-prefix" >&5 echo $ECHO_N "checking if you want to have a library-prefix... $ECHO_C" >&6 # Check whether --with-lib-prefix or --without-lib-prefix was given. @@ -11584,7 +13009,7 @@ if test "${with_lib_prefix+set}" = set; then else with_lib_prefix=auto fi; -echo "$as_me:11587: result: $with_lib_prefix" >&5 +echo "$as_me:13012: result: $with_lib_prefix" >&5 echo "${ECHO_T}$with_lib_prefix" >&6 if test "$with_lib_prefix" = auto @@ -11622,7 +13047,7 @@ if test X"$CC_G_OPT" = X"" ; then test -n "$GCC" && test "${ac_cv_prog_cc_g}" != yes && CC_G_OPT='' fi -echo "$as_me:11625: checking for default loader flags" >&5 +echo "$as_me:13050: checking for default loader flags" >&5 echo $ECHO_N "checking for default loader flags... $ECHO_C" >&6 case $DFT_LWR_MODEL in (normal) LD_MODEL='' ;; @@ -11630,13 +13055,13 @@ case $DFT_LWR_MODEL in (profile) LD_MODEL='-pg';; (shared) LD_MODEL='' ;; esac -echo "$as_me:11633: result: $LD_MODEL" >&5 +echo "$as_me:13058: result: $LD_MODEL" >&5 echo "${ECHO_T}$LD_MODEL" >&6 LD_RPATH_OPT= if test "x$cf_cv_enable_rpath" != xno then - echo "$as_me:11639: checking for an rpath option" >&5 + echo "$as_me:13064: checking for an rpath option" >&5 echo $ECHO_N "checking for an rpath option... $ECHO_C" >&6 case "$cf_cv_system_name" in (irix*) @@ -11667,12 +13092,12 @@ echo $ECHO_N "checking for an rpath option... $ECHO_C" >&6 (*) ;; esac - echo "$as_me:11670: result: $LD_RPATH_OPT" >&5 + echo "$as_me:13095: result: $LD_RPATH_OPT" >&5 echo "${ECHO_T}$LD_RPATH_OPT" >&6 case "x$LD_RPATH_OPT" in (x-R*) - echo "$as_me:11675: checking if we need a space after rpath option" >&5 + echo "$as_me:13100: checking if we need a space after rpath option" >&5 echo $ECHO_N "checking if we need a space after rpath option... $ECHO_C" >&6 cf_save_LIBS="$LIBS" @@ -11693,7 +13118,7 @@ done LIBS="$cf_add_libs" cat >"conftest.$ac_ext" <<_ACEOF -#line 11696 "configure" +#line 13121 "configure" #include "confdefs.h" int @@ -11705,16 +13130,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11708: \"$ac_link\"") >&5 +if { (eval echo "$as_me:13133: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:11711: \$? = $ac_status" >&5 + echo "$as_me:13136: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:11714: \"$ac_try\"") >&5 + { (eval echo "$as_me:13139: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:11717: \$? = $ac_status" >&5 + echo "$as_me:13142: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_rpath_space=no else @@ -11724,7 +13149,7 @@ cf_rpath_space=yes fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS="$cf_save_LIBS" - echo "$as_me:11727: result: $cf_rpath_space" >&5 + echo "$as_me:13152: result: $cf_rpath_space" >&5 echo "${ECHO_T}$cf_rpath_space" >&6 test "$cf_rpath_space" = yes && LD_RPATH_OPT="$LD_RPATH_OPT " ;; @@ -11746,7 +13171,7 @@ fi cf_ld_rpath_opt= test "$cf_cv_enable_rpath" = yes && cf_ld_rpath_opt="$LD_RPATH_OPT" - echo "$as_me:11749: checking whether to use release or ABI version in shared library file names" >&5 + echo "$as_me:13174: checking whether to use release or ABI version in shared library file names" >&5 echo $ECHO_N "checking whether to use release or ABI version in shared library file names... $ECHO_C" >&6 # Check whether --with-shlib-version or --without-shlib-version was given. @@ -11761,9 +13186,9 @@ if test "${with_shlib_version+set}" = set; then cf_cv_shlib_version=$withval ;; (*) - echo "$as_me:11764: result: $withval" >&5 + echo "$as_me:13189: result: $withval" >&5 echo "${ECHO_T}$withval" >&6 - { { echo "$as_me:11766: error: option value must be one of: rel, abi, or auto" >&5 + { { echo "$as_me:13191: error: option value must be one of: rel, abi, or auto" >&5 echo "$as_me: error: option value must be one of: rel, abi, or auto" >&2;} { (exit 1); exit 1; }; } ;; @@ -11772,7 +13197,7 @@ echo "$as_me: error: option value must be one of: rel, abi, or auto" >&2;} else cf_cv_shlib_version=auto fi; - echo "$as_me:11775: result: $cf_cv_shlib_version" >&5 + echo "$as_me:13200: result: $cf_cv_shlib_version" >&5 echo "${ECHO_T}$cf_cv_shlib_version" >&6 cf_cv_rm_so_locs=no @@ -11795,14 +13220,14 @@ echo "${ECHO_T}$cf_cv_shlib_version" >&6 if test "$cf_try_fPIC" = yes then - echo "$as_me:11798: checking which $CC option to use" >&5 + echo "$as_me:13223: checking which $CC option to use" >&5 echo $ECHO_N "checking which $CC option to use... $ECHO_C" >&6 cf_save_CFLAGS="$CFLAGS" for CC_SHARED_OPTS in -fPIC -fpic '' do CFLAGS="$cf_save_CFLAGS $CC_SHARED_OPTS" cat >"conftest.$ac_ext" <<_ACEOF -#line 11805 "configure" +#line 13230 "configure" #include "confdefs.h" #include int @@ -11814,16 +13239,16 @@ int x = 1; (void)x } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:11817: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:13242: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:11820: \$? = $ac_status" >&5 + echo "$as_me:13245: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:11823: \"$ac_try\"") >&5 + { (eval echo "$as_me:13248: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:11826: \$? = $ac_status" >&5 + echo "$as_me:13251: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then break else @@ -11832,7 +13257,7 @@ cat "conftest.$ac_ext" >&5 fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" done - echo "$as_me:11835: result: $CC_SHARED_OPTS" >&5 + echo "$as_me:13260: result: $CC_SHARED_OPTS" >&5 echo "${ECHO_T}$CC_SHARED_OPTS" >&6 CFLAGS="$cf_save_CFLAGS" fi @@ -11903,7 +13328,7 @@ CF_EOF MK_SHARED_LIB='${CC} ${LDFLAGS} ${CFLAGS} -dynamiclib -install_name ${libdir}/`basename $@` -compatibility_version ${ABI_VERSION} -current_version ${ABI_VERSION} -o $@' test "$cf_cv_shlib_version" = auto && cf_cv_shlib_version=abi cf_cv_shlib_version_infix=yes - echo "$as_me:11906: checking if ld -search_paths_first works" >&5 + echo "$as_me:13331: checking if ld -search_paths_first works" >&5 echo $ECHO_N "checking if ld -search_paths_first works... $ECHO_C" >&6 if test "${cf_cv_ldflags_search_paths_first+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -11912,7 +13337,7 @@ else cf_save_LDFLAGS=$LDFLAGS LDFLAGS="$LDFLAGS -Wl,-search_paths_first" cat >"conftest.$ac_ext" <<_ACEOF -#line 11915 "configure" +#line 13340 "configure" #include "confdefs.h" int @@ -11924,16 +13349,16 @@ int i; } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:11927: \"$ac_link\"") >&5 +if { (eval echo "$as_me:13352: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:11930: \$? = $ac_status" >&5 + echo "$as_me:13355: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:11933: \"$ac_try\"") >&5 + { (eval echo "$as_me:13358: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:11936: \$? = $ac_status" >&5 + echo "$as_me:13361: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_ldflags_search_paths_first=yes else @@ -11944,7 +13369,7 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LDFLAGS=$cf_save_LDFLAGS fi -echo "$as_me:11947: result: $cf_cv_ldflags_search_paths_first" >&5 +echo "$as_me:13372: result: $cf_cv_ldflags_search_paths_first" >&5 echo "${ECHO_T}$cf_cv_ldflags_search_paths_first" >&6 if test "$cf_cv_ldflags_search_paths_first" = yes; then LDFLAGS="$LDFLAGS -Wl,-search_paths_first" @@ -12088,7 +13513,7 @@ CF_EOF -L*) ldopts+=("\`echo \"\$1\" | sed \"s/^-L/-LIBPATH:/\"\`") ;; - *.obj | *.o) + *.obj | *.$OBJEXT) ldopts+=("\$1") ;; -Wl,*) @@ -12294,7 +13719,7 @@ CF_EOF do CFLAGS="$cf_shared_opts $cf_save_CFLAGS" cat >"conftest.$ac_ext" <<_ACEOF -#line 12297 "configure" +#line 13722 "configure" #include "confdefs.h" #include int @@ -12306,16 +13731,16 @@ printf("Hello\\n"); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:12309: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:13734: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:12312: \$? = $ac_status" >&5 + echo "$as_me:13737: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:12315: \"$ac_try\"") >&5 + { (eval echo "$as_me:13740: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:12318: \$? = $ac_status" >&5 + echo "$as_me:13743: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then break else @@ -12352,7 +13777,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" test "$cf_cv_do_symlinks" = no && cf_cv_do_symlinks=yes ;; (*) - { echo "$as_me:12355: WARNING: ignored --with-shlib-version" >&5 + { echo "$as_me:13780: WARNING: ignored --with-shlib-version" >&5 echo "$as_me: WARNING: ignored --with-shlib-version" >&2;} ;; esac @@ -12362,30 +13787,30 @@ echo "$as_me: WARNING: ignored --with-shlib-version" >&2;} if test -n "$cf_try_cflags" then cat > conftest.$ac_ext < int main(int argc, char *argv[]) { printf("hello\\n"); - return (argv[argc-1] == 0) ; + return (argv[argc-1] == NULL) ; } EOF cf_save_CFLAGS="$CFLAGS" for cf_opt in $cf_try_cflags do CFLAGS="$cf_save_CFLAGS -$cf_opt" - echo "$as_me:12377: checking if CFLAGS option -$cf_opt works" >&5 + echo "$as_me:13802: checking if CFLAGS option -$cf_opt works" >&5 echo $ECHO_N "checking if CFLAGS option -$cf_opt works... $ECHO_C" >&6 - if { (eval echo "$as_me:12379: \"$ac_compile\"") >&5 + if { (eval echo "$as_me:13804: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:12382: \$? = $ac_status" >&5 + echo "$as_me:13807: \$? = $ac_status" >&5 (exit "$ac_status"); }; then - echo "$as_me:12384: result: yes" >&5 + echo "$as_me:13809: result: yes" >&5 echo "${ECHO_T}yes" >&6 cf_save_CFLAGS="$CFLAGS" else - echo "$as_me:12388: result: no" >&5 + echo "$as_me:13813: result: no" >&5 echo "${ECHO_T}no" >&6 fi done @@ -12400,17 +13825,17 @@ echo "${ECHO_T}no" >&6 test -n "$verbose" && echo " CC_SHARED_OPTS: $CC_SHARED_OPTS" 1>&6 -echo "${as_me:-configure}:12403: testing CC_SHARED_OPTS: $CC_SHARED_OPTS ..." 1>&5 +echo "${as_me:-configure}:13828: testing CC_SHARED_OPTS: $CC_SHARED_OPTS ..." 1>&5 test -n "$verbose" && echo " MK_SHARED_LIB: $MK_SHARED_LIB" 1>&6 -echo "${as_me:-configure}:12407: testing MK_SHARED_LIB: $MK_SHARED_LIB ..." 1>&5 +echo "${as_me:-configure}:13832: testing MK_SHARED_LIB: $MK_SHARED_LIB ..." 1>&5 # The test/sample programs in the original tree link using rpath option. # Make it optional for packagers. if test -n "$LOCAL_LDFLAGS" then - echo "$as_me:12413: checking if you want to link sample programs with rpath option" >&5 + echo "$as_me:13838: checking if you want to link sample programs with rpath option" >&5 echo $ECHO_N "checking if you want to link sample programs with rpath option... $ECHO_C" >&6 # Check whether --enable-rpath-link or --disable-rpath-link was given. @@ -12420,7 +13845,7 @@ if test "${enable_rpath_link+set}" = set; then else with_rpath_link=yes fi; - echo "$as_me:12423: result: $with_rpath_link" >&5 + echo "$as_me:13848: result: $with_rpath_link" >&5 echo "${ECHO_T}$with_rpath_link" >&6 if test "$with_rpath_link" = no then @@ -12433,7 +13858,7 @@ fi ### use option --enable-broken-linker to force on use of broken-linker support -echo "$as_me:12436: checking if you want broken-linker support code" >&5 +echo "$as_me:13861: checking if you want broken-linker support code" >&5 echo $ECHO_N "checking if you want broken-linker support code... $ECHO_C" >&6 # Check whether --enable-broken_linker or --disable-broken_linker was given. @@ -12443,7 +13868,7 @@ if test "${enable_broken_linker+set}" = set; then else with_broken_linker=no fi; -echo "$as_me:12446: result: $with_broken_linker" >&5 +echo "$as_me:13871: result: $with_broken_linker" >&5 echo "${ECHO_T}$with_broken_linker" >&6 : "${BROKEN_LINKER:=0}" @@ -12458,14 +13883,14 @@ fi # Check to define _XOPEN_SOURCE "automatically" -echo "$as_me:12461: checking if the POSIX test-macros are already defined" >&5 +echo "$as_me:13886: checking if the POSIX test-macros are already defined" >&5 echo $ECHO_N "checking if the POSIX test-macros are already defined... $ECHO_C" >&6 if test "${cf_cv_posix_visible+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 12468 "configure" +#line 13893 "configure" #include "confdefs.h" #include int @@ -12484,16 +13909,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:12487: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:13912: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:12490: \$? = $ac_status" >&5 + echo "$as_me:13915: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:12493: \"$ac_try\"") >&5 + { (eval echo "$as_me:13918: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:12496: \$? = $ac_status" >&5 + echo "$as_me:13921: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_posix_visible=no else @@ -12504,7 +13929,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:12507: result: $cf_cv_posix_visible" >&5 +echo "$as_me:13932: result: $cf_cv_posix_visible" >&5 echo "${ECHO_T}$cf_cv_posix_visible" >&6 if test "$cf_cv_posix_visible" = no; then @@ -12542,18 +13967,18 @@ case "$host_os" in cf_xopen_source="-D_SGI_SOURCE" cf_XOPEN_SOURCE= ;; -(linux*gnu|linux*gnuabi64|linux*gnuabin32|linux*gnueabi|linux*gnueabihf|linux*gnux32|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) +(linux*gnu*|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) cf_gnu_xopen_source=$cf_XOPEN_SOURCE -echo "$as_me:12549: checking if this is the GNU C library" >&5 +echo "$as_me:13974: checking if this is the GNU C library" >&5 echo $ECHO_N "checking if this is the GNU C library... $ECHO_C" >&6 if test "${cf_cv_gnu_library+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 12556 "configure" +#line 13981 "configure" #include "confdefs.h" #include int @@ -12572,16 +13997,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:12575: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14000: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:12578: \$? = $ac_status" >&5 + echo "$as_me:14003: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:12581: \"$ac_try\"") >&5 + { (eval echo "$as_me:14006: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:12584: \$? = $ac_status" >&5 + echo "$as_me:14009: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_gnu_library=yes else @@ -12592,7 +14017,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:12595: result: $cf_cv_gnu_library" >&5 +echo "$as_me:14020: result: $cf_cv_gnu_library" >&5 echo "${ECHO_T}$cf_cv_gnu_library" >&6 if test x$cf_cv_gnu_library = xyes; then @@ -12600,7 +14025,7 @@ if test x$cf_cv_gnu_library = xyes; then # With glibc 2.19 (13 years after this check was begun), _DEFAULT_SOURCE # was changed to help a little. newlib incorporated the change about 4 # years later. - echo "$as_me:12603: checking if _DEFAULT_SOURCE can be used as a basis" >&5 + echo "$as_me:14028: checking if _DEFAULT_SOURCE can be used as a basis" >&5 echo $ECHO_N "checking if _DEFAULT_SOURCE can be used as a basis... $ECHO_C" >&6 if test "${cf_cv_gnu_library_219+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -12612,7 +14037,7 @@ else CPPFLAGS="${CPPFLAGS}-D_DEFAULT_SOURCE" cat >"conftest.$ac_ext" <<_ACEOF -#line 12615 "configure" +#line 14040 "configure" #include "confdefs.h" #include int @@ -12631,16 +14056,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:12634: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14059: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:12637: \$? = $ac_status" >&5 + echo "$as_me:14062: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:12640: \"$ac_try\"") >&5 + { (eval echo "$as_me:14065: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:12643: \$? = $ac_status" >&5 + echo "$as_me:14068: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_gnu_library_219=yes else @@ -12652,12 +14077,12 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" CPPFLAGS="$cf_save" fi -echo "$as_me:12655: result: $cf_cv_gnu_library_219" >&5 +echo "$as_me:14080: result: $cf_cv_gnu_library_219" >&5 echo "${ECHO_T}$cf_cv_gnu_library_219" >&6 if test "x$cf_cv_gnu_library_219" = xyes; then cf_save="$CPPFLAGS" - echo "$as_me:12660: checking if _XOPEN_SOURCE=$cf_gnu_xopen_source works with _DEFAULT_SOURCE" >&5 + echo "$as_me:14085: checking if _XOPEN_SOURCE=$cf_gnu_xopen_source works with _DEFAULT_SOURCE" >&5 echo $ECHO_N "checking if _XOPEN_SOURCE=$cf_gnu_xopen_source works with _DEFAULT_SOURCE... $ECHO_C" >&6 if test "${cf_cv_gnu_dftsrc_219+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -12762,7 +14187,7 @@ if test -n "$cf_new_extra_cppflags" ; then fi cat >"conftest.$ac_ext" <<_ACEOF -#line 12765 "configure" +#line 14190 "configure" #include "confdefs.h" #include @@ -12782,16 +14207,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:12785: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14210: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:12788: \$? = $ac_status" >&5 + echo "$as_me:14213: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:12791: \"$ac_try\"") >&5 + { (eval echo "$as_me:14216: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:12794: \$? = $ac_status" >&5 + echo "$as_me:14219: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_gnu_dftsrc_219=yes else @@ -12802,7 +14227,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:12805: result: $cf_cv_gnu_dftsrc_219" >&5 +echo "$as_me:14230: result: $cf_cv_gnu_dftsrc_219" >&5 echo "${ECHO_T}$cf_cv_gnu_dftsrc_219" >&6 test "x$cf_cv_gnu_dftsrc_219" = "xyes" || CPPFLAGS="$cf_save" else @@ -12811,14 +14236,14 @@ echo "${ECHO_T}$cf_cv_gnu_dftsrc_219" >&6 if test "x$cf_cv_gnu_dftsrc_219" != xyes; then - echo "$as_me:12814: checking if we must define _GNU_SOURCE" >&5 + echo "$as_me:14239: checking if we must define _GNU_SOURCE" >&5 echo $ECHO_N "checking if we must define _GNU_SOURCE... $ECHO_C" >&6 if test "${cf_cv_gnu_source+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 12821 "configure" +#line 14246 "configure" #include "confdefs.h" #include int @@ -12833,16 +14258,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:12836: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14261: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:12839: \$? = $ac_status" >&5 + echo "$as_me:14264: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:12842: \"$ac_try\"") >&5 + { (eval echo "$as_me:14267: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:12845: \$? = $ac_status" >&5 + echo "$as_me:14270: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_gnu_source=no else @@ -12949,7 +14374,7 @@ if test -n "$cf_new_extra_cppflags" ; then fi cat >"conftest.$ac_ext" <<_ACEOF -#line 12952 "configure" +#line 14377 "configure" #include "confdefs.h" #include int @@ -12964,16 +14389,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:12967: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14392: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:12970: \$? = $ac_status" >&5 + echo "$as_me:14395: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:12973: \"$ac_try\"") >&5 + { (eval echo "$as_me:14398: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:12976: \$? = $ac_status" >&5 + echo "$as_me:14401: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_gnu_source=no else @@ -12988,12 +14413,12 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:12991: result: $cf_cv_gnu_source" >&5 +echo "$as_me:14416: result: $cf_cv_gnu_source" >&5 echo "${ECHO_T}$cf_cv_gnu_source" >&6 if test "$cf_cv_gnu_source" = yes then - echo "$as_me:12996: checking if we should also define _DEFAULT_SOURCE" >&5 + echo "$as_me:14421: checking if we should also define _DEFAULT_SOURCE" >&5 echo $ECHO_N "checking if we should also define _DEFAULT_SOURCE... $ECHO_C" >&6 if test "${cf_cv_default_source+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -13003,7 +14428,7 @@ else CPPFLAGS="${CPPFLAGS}-D_GNU_SOURCE" cat >"conftest.$ac_ext" <<_ACEOF -#line 13006 "configure" +#line 14431 "configure" #include "confdefs.h" #include int @@ -13018,16 +14443,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13021: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14446: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13024: \$? = $ac_status" >&5 + echo "$as_me:14449: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13027: \"$ac_try\"") >&5 + { (eval echo "$as_me:14452: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13030: \$? = $ac_status" >&5 + echo "$as_me:14455: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_default_source=no else @@ -13038,7 +14463,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:13041: result: $cf_cv_default_source" >&5 +echo "$as_me:14466: result: $cf_cv_default_source" >&5 echo "${ECHO_T}$cf_cv_default_source" >&6 if test "$cf_cv_default_source" = yes then @@ -13052,6 +14477,9 @@ echo "${ECHO_T}$cf_cv_default_source" >&6 fi + ;; +linux*musl) + cf_xopen_source="-D_BSD_SOURCE" ;; (minix*) cf_xopen_source="-D_NETBSD_SOURCE" # POSIX.1-2001 features are ifdef'd with this... @@ -13075,16 +14503,16 @@ cf_trim_CPPFLAGS=`echo "$cf_save_CPPFLAGS" | \ sed -e 's/-[UD]'"_POSIX_C_SOURCE"'\(=[^ ]*\)\?[ ]/ /g' \ -e 's/-[UD]'"_POSIX_C_SOURCE"'\(=[^ ]*\)\?$//g'` -echo "$as_me:13078: checking if we should define _POSIX_C_SOURCE" >&5 +echo "$as_me:14506: checking if we should define _POSIX_C_SOURCE" >&5 echo $ECHO_N "checking if we should define _POSIX_C_SOURCE... $ECHO_C" >&6 if test "${cf_cv_posix_c_source+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else -echo "${as_me:-configure}:13084: testing if the symbol is already defined go no further ..." 1>&5 +echo "${as_me:-configure}:14512: testing if the symbol is already defined go no further ..." 1>&5 cat >"conftest.$ac_ext" <<_ACEOF -#line 13087 "configure" +#line 14515 "configure" #include "confdefs.h" #include int @@ -13099,16 +14527,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13102: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14530: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13105: \$? = $ac_status" >&5 + echo "$as_me:14533: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13108: \"$ac_try\"") >&5 + { (eval echo "$as_me:14536: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13111: \$? = $ac_status" >&5 + echo "$as_me:14539: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_posix_c_source=no else @@ -13129,7 +14557,7 @@ cf_want_posix_source=no esac if test "$cf_want_posix_source" = yes ; then cat >"conftest.$ac_ext" <<_ACEOF -#line 13132 "configure" +#line 14560 "configure" #include "confdefs.h" #include int @@ -13144,16 +14572,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13147: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14575: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13150: \$? = $ac_status" >&5 + echo "$as_me:14578: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13153: \"$ac_try\"") >&5 + { (eval echo "$as_me:14581: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13156: \$? = $ac_status" >&5 + echo "$as_me:14584: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -13164,7 +14592,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "${as_me:-configure}:13167: testing ifdef from value $cf_POSIX_C_SOURCE ..." 1>&5 +echo "${as_me:-configure}:14595: testing ifdef from value $cf_POSIX_C_SOURCE ..." 1>&5 CFLAGS="$cf_trim_CFLAGS" CPPFLAGS="$cf_trim_CPPFLAGS" @@ -13172,10 +14600,10 @@ echo "${as_me:-configure}:13167: testing ifdef from value $cf_POSIX_C_SOURCE ... test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " CPPFLAGS="${CPPFLAGS}$cf_cv_posix_c_source" -echo "${as_me:-configure}:13175: testing if the second compile does not leave our definition intact error ..." 1>&5 +echo "${as_me:-configure}:14603: testing if the second compile does not leave our definition intact error ..." 1>&5 cat >"conftest.$ac_ext" <<_ACEOF -#line 13178 "configure" +#line 14606 "configure" #include "confdefs.h" #include int @@ -13190,16 +14618,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13193: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14621: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13196: \$? = $ac_status" >&5 + echo "$as_me:14624: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13199: \"$ac_try\"") >&5 + { (eval echo "$as_me:14627: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13202: \$? = $ac_status" >&5 + echo "$as_me:14630: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -13215,7 +14643,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:13218: result: $cf_cv_posix_c_source" >&5 +echo "$as_me:14646: result: $cf_cv_posix_c_source" >&5 echo "${ECHO_T}$cf_cv_posix_c_source" >&6 if test "$cf_cv_posix_c_source" != no ; then @@ -13332,7 +14760,7 @@ fi # cf_cv_posix_visible # OpenBSD 6.x has broken locale support, both compile-time and runtime. # see https://www.mail-archive.com/bugs@openbsd.org/msg13200.html # Abusing the conformance level is a workaround. - { echo "$as_me:13335: WARNING: this system does not provide usable locale support" >&5 + { echo "$as_me:14763: WARNING: this system does not provide usable locale support" >&5 echo "$as_me: WARNING: this system does not provide usable locale support" >&2;} cf_xopen_source="-D_BSD_SOURCE" cf_XOPEN_SOURCE=700 @@ -13364,14 +14792,14 @@ echo "$as_me: WARNING: this system does not provide usable locale support" >&2;} ;; (*) -echo "$as_me:13367: checking if we should define _XOPEN_SOURCE" >&5 +echo "$as_me:14795: checking if we should define _XOPEN_SOURCE" >&5 echo $ECHO_N "checking if we should define _XOPEN_SOURCE... $ECHO_C" >&6 if test "${cf_cv_xopen_source+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 13374 "configure" +#line 14802 "configure" #include "confdefs.h" $ac_includes_default @@ -13389,16 +14817,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13392: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14820: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13395: \$? = $ac_status" >&5 + echo "$as_me:14823: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13398: \"$ac_try\"") >&5 + { (eval echo "$as_me:14826: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13401: \$? = $ac_status" >&5 + echo "$as_me:14829: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_xopen_source=no else @@ -13410,7 +14838,7 @@ cf_save="$CPPFLAGS" CPPFLAGS="${CPPFLAGS}-D_XOPEN_SOURCE=$cf_XOPEN_SOURCE" cat >"conftest.$ac_ext" <<_ACEOF -#line 13413 "configure" +#line 14841 "configure" #include "confdefs.h" $ac_includes_default @@ -13428,16 +14856,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13431: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:14859: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13434: \$? = $ac_status" >&5 + echo "$as_me:14862: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13437: \"$ac_try\"") >&5 + { (eval echo "$as_me:14865: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13440: \$? = $ac_status" >&5 + echo "$as_me:14868: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_xopen_source=no else @@ -13452,7 +14880,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:13455: result: $cf_cv_xopen_source" >&5 +echo "$as_me:14883: result: $cf_cv_xopen_source" >&5 echo "${ECHO_T}$cf_cv_xopen_source" >&6 if test "$cf_cv_xopen_source" != no ; then @@ -13612,16 +15040,16 @@ cf_trim_CPPFLAGS=`echo "$cf_save_CPPFLAGS" | \ sed -e 's/-[UD]'"_POSIX_C_SOURCE"'\(=[^ ]*\)\?[ ]/ /g' \ -e 's/-[UD]'"_POSIX_C_SOURCE"'\(=[^ ]*\)\?$//g'` -echo "$as_me:13615: checking if we should define _POSIX_C_SOURCE" >&5 +echo "$as_me:15043: checking if we should define _POSIX_C_SOURCE" >&5 echo $ECHO_N "checking if we should define _POSIX_C_SOURCE... $ECHO_C" >&6 if test "${cf_cv_posix_c_source+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else -echo "${as_me:-configure}:13621: testing if the symbol is already defined go no further ..." 1>&5 +echo "${as_me:-configure}:15049: testing if the symbol is already defined go no further ..." 1>&5 cat >"conftest.$ac_ext" <<_ACEOF -#line 13624 "configure" +#line 15052 "configure" #include "confdefs.h" #include int @@ -13636,16 +15064,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13639: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15067: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13642: \$? = $ac_status" >&5 + echo "$as_me:15070: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13645: \"$ac_try\"") >&5 + { (eval echo "$as_me:15073: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13648: \$? = $ac_status" >&5 + echo "$as_me:15076: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_posix_c_source=no else @@ -13666,7 +15094,7 @@ cf_want_posix_source=no esac if test "$cf_want_posix_source" = yes ; then cat >"conftest.$ac_ext" <<_ACEOF -#line 13669 "configure" +#line 15097 "configure" #include "confdefs.h" #include int @@ -13681,16 +15109,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13684: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15112: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13687: \$? = $ac_status" >&5 + echo "$as_me:15115: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13690: \"$ac_try\"") >&5 + { (eval echo "$as_me:15118: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13693: \$? = $ac_status" >&5 + echo "$as_me:15121: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -13701,7 +15129,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "${as_me:-configure}:13704: testing ifdef from value $cf_POSIX_C_SOURCE ..." 1>&5 +echo "${as_me:-configure}:15132: testing ifdef from value $cf_POSIX_C_SOURCE ..." 1>&5 CFLAGS="$cf_trim_CFLAGS" CPPFLAGS="$cf_trim_CPPFLAGS" @@ -13709,10 +15137,10 @@ echo "${as_me:-configure}:13704: testing ifdef from value $cf_POSIX_C_SOURCE ... test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " CPPFLAGS="${CPPFLAGS}$cf_cv_posix_c_source" -echo "${as_me:-configure}:13712: testing if the second compile does not leave our definition intact error ..." 1>&5 +echo "${as_me:-configure}:15140: testing if the second compile does not leave our definition intact error ..." 1>&5 cat >"conftest.$ac_ext" <<_ACEOF -#line 13715 "configure" +#line 15143 "configure" #include "confdefs.h" #include int @@ -13727,16 +15155,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13730: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15158: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13733: \$? = $ac_status" >&5 + echo "$as_me:15161: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13736: \"$ac_try\"") >&5 + { (eval echo "$as_me:15164: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13739: \$? = $ac_status" >&5 + echo "$as_me:15167: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -13752,7 +15180,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:13755: result: $cf_cv_posix_c_source" >&5 +echo "$as_me:15183: result: $cf_cv_posix_c_source" >&5 echo "${ECHO_T}$cf_cv_posix_c_source" >&6 if test "$cf_cv_posix_c_source" != no ; then @@ -13865,10 +15293,10 @@ fi # cf_cv_posix_visible if test "$cf_cv_xopen_source" = no ; then test -n "$verbose" && echo " checking if _POSIX_C_SOURCE interferes with _XOPEN_SOURCE" 1>&6 -echo "${as_me:-configure}:13868: testing checking if _POSIX_C_SOURCE interferes with _XOPEN_SOURCE ..." 1>&5 +echo "${as_me:-configure}:15296: testing checking if _POSIX_C_SOURCE interferes with _XOPEN_SOURCE ..." 1>&5 cat >"conftest.$ac_ext" <<_ACEOF -#line 13871 "configure" +#line 15299 "configure" #include "confdefs.h" $ac_includes_default @@ -13886,23 +15314,23 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:13889: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15317: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:13892: \$? = $ac_status" >&5 + echo "$as_me:15320: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:13895: \"$ac_try\"") >&5 + { (eval echo "$as_me:15323: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:13898: \$? = $ac_status" >&5 + echo "$as_me:15326: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else echo "$as_me: failed program was:" >&5 cat "conftest.$ac_ext" >&5 - { echo "$as_me:13905: WARNING: _POSIX_C_SOURCE definition is not usable" >&5 + { echo "$as_me:15333: WARNING: _POSIX_C_SOURCE definition is not usable" >&5 echo "$as_me: WARNING: _POSIX_C_SOURCE definition is not usable" >&2;} CPPFLAGS="$cf_save_xopen_cppflags" fi @@ -13925,7 +15353,7 @@ do test "$CFLAGS" != "$cf_old_cflag" || break test -n "$verbose" && echo " removing old option $cf_add_cflags from CFLAGS" 1>&6 -echo "${as_me:-configure}:13928: testing removing old option $cf_add_cflags from CFLAGS ..." 1>&5 +echo "${as_me:-configure}:15356: testing removing old option $cf_add_cflags from CFLAGS ..." 1>&5 CFLAGS="$cf_old_cflag" done @@ -13937,7 +15365,7 @@ do test "$CPPFLAGS" != "$cf_old_cflag" || break test -n "$verbose" && echo " removing old option $cf_add_cflags from CPPFLAGS" 1>&6 -echo "${as_me:-configure}:13940: testing removing old option $cf_add_cflags from CPPFLAGS ..." 1>&5 +echo "${as_me:-configure}:15368: testing removing old option $cf_add_cflags from CPPFLAGS ..." 1>&5 CPPFLAGS="$cf_old_cflag" done @@ -14025,7 +15453,7 @@ done if test -n "$cf_new_cflags" ; then test -n "$verbose" && echo " add to \$CFLAGS $cf_new_cflags" 1>&6 -echo "${as_me:-configure}:14028: testing add to \$CFLAGS $cf_new_cflags ..." 1>&5 +echo "${as_me:-configure}:15456: testing add to \$CFLAGS $cf_new_cflags ..." 1>&5 test -n "$CFLAGS" && CFLAGS="$CFLAGS " CFLAGS="${CFLAGS}$cf_new_cflags" @@ -14035,7 +15463,7 @@ fi if test -n "$cf_new_cppflags" ; then test -n "$verbose" && echo " add to \$CPPFLAGS $cf_new_cppflags" 1>&6 -echo "${as_me:-configure}:14038: testing add to \$CPPFLAGS $cf_new_cppflags ..." 1>&5 +echo "${as_me:-configure}:15466: testing add to \$CPPFLAGS $cf_new_cppflags ..." 1>&5 test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " CPPFLAGS="${CPPFLAGS}$cf_new_cppflags" @@ -14045,7 +15473,7 @@ fi if test -n "$cf_new_extra_cppflags" ; then test -n "$verbose" && echo " add to \$EXTRA_CPPFLAGS $cf_new_extra_cppflags" 1>&6 -echo "${as_me:-configure}:14048: testing add to \$EXTRA_CPPFLAGS $cf_new_extra_cppflags ..." 1>&5 +echo "${as_me:-configure}:15476: testing add to \$EXTRA_CPPFLAGS $cf_new_extra_cppflags ..." 1>&5 test -n "$EXTRA_CPPFLAGS" && EXTRA_CPPFLAGS="$EXTRA_CPPFLAGS " EXTRA_CPPFLAGS="${EXTRA_CPPFLAGS}$cf_new_extra_cppflags" @@ -14057,10 +15485,10 @@ done fi if test -n "$cf_XOPEN_SOURCE" && test -z "$cf_cv_xopen_source" ; then - echo "$as_me:14060: checking if _XOPEN_SOURCE really is set" >&5 + echo "$as_me:15488: checking if _XOPEN_SOURCE really is set" >&5 echo $ECHO_N "checking if _XOPEN_SOURCE really is set... $ECHO_C" >&6 cat >"conftest.$ac_ext" <<_ACEOF -#line 14063 "configure" +#line 15491 "configure" #include "confdefs.h" #include int @@ -14075,16 +15503,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14078: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15506: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14081: \$? = $ac_status" >&5 + echo "$as_me:15509: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14084: \"$ac_try\"") >&5 + { (eval echo "$as_me:15512: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14087: \$? = $ac_status" >&5 + echo "$as_me:15515: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_XOPEN_SOURCE_set=yes else @@ -14093,12 +15521,12 @@ cat "conftest.$ac_ext" >&5 cf_XOPEN_SOURCE_set=no fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" - echo "$as_me:14096: result: $cf_XOPEN_SOURCE_set" >&5 + echo "$as_me:15524: result: $cf_XOPEN_SOURCE_set" >&5 echo "${ECHO_T}$cf_XOPEN_SOURCE_set" >&6 if test "$cf_XOPEN_SOURCE_set" = yes then cat >"conftest.$ac_ext" <<_ACEOF -#line 14101 "configure" +#line 15529 "configure" #include "confdefs.h" #include int @@ -14113,16 +15541,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14116: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15544: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14119: \$? = $ac_status" >&5 + echo "$as_me:15547: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14122: \"$ac_try\"") >&5 + { (eval echo "$as_me:15550: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14125: \$? = $ac_status" >&5 + echo "$as_me:15553: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_XOPEN_SOURCE_set_ok=yes else @@ -14133,19 +15561,19 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" if test "$cf_XOPEN_SOURCE_set_ok" = no then - { echo "$as_me:14136: WARNING: _XOPEN_SOURCE is lower than requested" >&5 + { echo "$as_me:15564: WARNING: _XOPEN_SOURCE is lower than requested" >&5 echo "$as_me: WARNING: _XOPEN_SOURCE is lower than requested" >&2;} fi else -echo "$as_me:14141: checking if we should define _XOPEN_SOURCE" >&5 +echo "$as_me:15569: checking if we should define _XOPEN_SOURCE" >&5 echo $ECHO_N "checking if we should define _XOPEN_SOURCE... $ECHO_C" >&6 if test "${cf_cv_xopen_source+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 14148 "configure" +#line 15576 "configure" #include "confdefs.h" $ac_includes_default @@ -14163,16 +15591,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14166: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15594: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14169: \$? = $ac_status" >&5 + echo "$as_me:15597: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14172: \"$ac_try\"") >&5 + { (eval echo "$as_me:15600: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14175: \$? = $ac_status" >&5 + echo "$as_me:15603: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_xopen_source=no else @@ -14184,7 +15612,7 @@ cf_save="$CPPFLAGS" CPPFLAGS="${CPPFLAGS}-D_XOPEN_SOURCE=$cf_XOPEN_SOURCE" cat >"conftest.$ac_ext" <<_ACEOF -#line 14187 "configure" +#line 15615 "configure" #include "confdefs.h" $ac_includes_default @@ -14202,16 +15630,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14205: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15633: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14208: \$? = $ac_status" >&5 + echo "$as_me:15636: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14211: \"$ac_try\"") >&5 + { (eval echo "$as_me:15639: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14214: \$? = $ac_status" >&5 + echo "$as_me:15642: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_xopen_source=no else @@ -14226,7 +15654,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:14229: result: $cf_cv_xopen_source" >&5 +echo "$as_me:15657: result: $cf_cv_xopen_source" >&5 echo "${ECHO_T}$cf_cv_xopen_source" >&6 if test "$cf_cv_xopen_source" != no ; then @@ -14373,13 +15801,13 @@ fi fi fi # cf_cv_posix_visible -echo "$as_me:14376: checking for ANSI C header files" >&5 +echo "$as_me:15804: checking for ANSI C header files" >&5 echo $ECHO_N "checking for ANSI C header files... $ECHO_C" >&6 if test "${ac_cv_header_stdc+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 14382 "configure" +#line 15810 "configure" #include "confdefs.h" #include #include @@ -14387,13 +15815,13 @@ else #include _ACEOF -if { (eval echo "$as_me:14390: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:15818: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:14396: \$? = $ac_status" >&5 + echo "$as_me:15824: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -14415,7 +15843,7 @@ rm -f conftest.err "conftest.$ac_ext" if test $ac_cv_header_stdc = yes; then # SunOS 4.x string.h does not declare mem*, contrary to ANSI. cat >"conftest.$ac_ext" <<_ACEOF -#line 14418 "configure" +#line 15846 "configure" #include "confdefs.h" #include @@ -14433,7 +15861,7 @@ fi if test $ac_cv_header_stdc = yes; then # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI. cat >"conftest.$ac_ext" <<_ACEOF -#line 14436 "configure" +#line 15864 "configure" #include "confdefs.h" #include @@ -14454,7 +15882,7 @@ if test $ac_cv_header_stdc = yes; then : else cat >"conftest.$ac_ext" <<_ACEOF -#line 14457 "configure" +#line 15885 "configure" #include "confdefs.h" #include #if ((' ' & 0x0FF) == 0x020) @@ -14480,15 +15908,15 @@ main (void) } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:14483: \"$ac_link\"") >&5 +if { (eval echo "$as_me:15911: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:14486: \$? = $ac_status" >&5 + echo "$as_me:15914: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:14488: \"$ac_try\"") >&5 + { (eval echo "$as_me:15916: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14491: \$? = $ac_status" >&5 + echo "$as_me:15919: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then : else @@ -14501,7 +15929,7 @@ rm -f core ./core.* ./*.core "conftest$ac_exeext" "conftest.$ac_objext" "conftes fi fi fi -echo "$as_me:14504: result: $ac_cv_header_stdc" >&5 +echo "$as_me:15932: result: $ac_cv_header_stdc" >&5 echo "${ECHO_T}$ac_cv_header_stdc" >&6 if test $ac_cv_header_stdc = yes; then @@ -14517,28 +15945,28 @@ for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \ inttypes.h stdint.h unistd.h do as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` -echo "$as_me:14520: checking for $ac_header" >&5 +echo "$as_me:15948: checking for $ac_header" >&5 echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 if eval "test \"\${$as_ac_Header+set}\" = set"; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 14526 "configure" +#line 15954 "configure" #include "confdefs.h" $ac_includes_default #include <$ac_header> _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14532: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:15960: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14535: \$? = $ac_status" >&5 + echo "$as_me:15963: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14538: \"$ac_try\"") >&5 + { (eval echo "$as_me:15966: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14541: \$? = $ac_status" >&5 + echo "$as_me:15969: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then eval "$as_ac_Header=yes" else @@ -14548,7 +15976,7 @@ eval "$as_ac_Header=no" fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:14551: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 +echo "$as_me:15979: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then cat >>confdefs.h <&5 +echo "$as_me:15989: checking whether exit is declared" >&5 echo $ECHO_N "checking whether exit is declared... $ECHO_C" >&6 if test "${ac_cv_have_decl_exit+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 14567 "configure" +#line 15995 "configure" #include "confdefs.h" $ac_includes_default int @@ -14579,16 +16007,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14582: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16010: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14585: \$? = $ac_status" >&5 + echo "$as_me:16013: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14588: \"$ac_try\"") >&5 + { (eval echo "$as_me:16016: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14591: \$? = $ac_status" >&5 + echo "$as_me:16019: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_have_decl_exit=yes else @@ -14598,7 +16026,7 @@ ac_cv_have_decl_exit=no fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:14601: result: $ac_cv_have_decl_exit" >&5 +echo "$as_me:16029: result: $ac_cv_have_decl_exit" >&5 echo "${ECHO_T}$ac_cv_have_decl_exit" >&6 # Check whether --enable-largefile or --disable-largefile was given. @@ -14608,7 +16036,7 @@ if test "${enable_largefile+set}" = set; then fi; if test "$enable_largefile" != no; then - echo "$as_me:14611: checking for special C compiler options needed for large files" >&5 + echo "$as_me:16039: checking for special C compiler options needed for large files" >&5 echo $ECHO_N "checking for special C compiler options needed for large files... $ECHO_C" >&6 if test "${ac_cv_sys_largefile_CC+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -14620,7 +16048,7 @@ else # IRIX 6.2 and later do not support large files by default, # so use the C compiler's -n32 option if that helps. cat >"conftest.$ac_ext" <<_ACEOF -#line 14623 "configure" +#line 16051 "configure" #include "confdefs.h" #include /* Check that off_t can represent 2**63 - 1 correctly. @@ -14640,16 +16068,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14643: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16071: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14646: \$? = $ac_status" >&5 + echo "$as_me:16074: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14649: \"$ac_try\"") >&5 + { (eval echo "$as_me:16077: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14652: \$? = $ac_status" >&5 + echo "$as_me:16080: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then break else @@ -14659,16 +16087,16 @@ fi rm -f "conftest.$ac_objext" CC="$CC -n32" rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14662: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16090: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14665: \$? = $ac_status" >&5 + echo "$as_me:16093: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14668: \"$ac_try\"") >&5 + { (eval echo "$as_me:16096: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14671: \$? = $ac_status" >&5 + echo "$as_me:16099: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_sys_largefile_CC=' -n32'; break else @@ -14682,13 +16110,13 @@ rm -f "conftest.$ac_objext" rm -f "conftest.$ac_ext" fi fi -echo "$as_me:14685: result: $ac_cv_sys_largefile_CC" >&5 +echo "$as_me:16113: result: $ac_cv_sys_largefile_CC" >&5 echo "${ECHO_T}$ac_cv_sys_largefile_CC" >&6 if test "$ac_cv_sys_largefile_CC" != no; then CC=$CC$ac_cv_sys_largefile_CC fi - echo "$as_me:14691: checking for _FILE_OFFSET_BITS value needed for large files" >&5 + echo "$as_me:16119: checking for _FILE_OFFSET_BITS value needed for large files" >&5 echo $ECHO_N "checking for _FILE_OFFSET_BITS value needed for large files... $ECHO_C" >&6 if test "${ac_cv_sys_file_offset_bits+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -14696,7 +16124,7 @@ else while :; do ac_cv_sys_file_offset_bits=no cat >"conftest.$ac_ext" <<_ACEOF -#line 14699 "configure" +#line 16127 "configure" #include "confdefs.h" #include /* Check that off_t can represent 2**63 - 1 correctly. @@ -14716,16 +16144,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14719: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16147: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14722: \$? = $ac_status" >&5 + echo "$as_me:16150: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14725: \"$ac_try\"") >&5 + { (eval echo "$as_me:16153: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14728: \$? = $ac_status" >&5 + echo "$as_me:16156: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then break else @@ -14734,7 +16162,7 @@ cat "conftest.$ac_ext" >&5 fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" cat >"conftest.$ac_ext" <<_ACEOF -#line 14737 "configure" +#line 16165 "configure" #include "confdefs.h" #define _FILE_OFFSET_BITS 64 #include @@ -14755,16 +16183,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14758: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16186: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14761: \$? = $ac_status" >&5 + echo "$as_me:16189: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14764: \"$ac_try\"") >&5 + { (eval echo "$as_me:16192: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14767: \$? = $ac_status" >&5 + echo "$as_me:16195: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_sys_file_offset_bits=64; break else @@ -14775,7 +16203,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" break done fi -echo "$as_me:14778: result: $ac_cv_sys_file_offset_bits" >&5 +echo "$as_me:16206: result: $ac_cv_sys_file_offset_bits" >&5 echo "${ECHO_T}$ac_cv_sys_file_offset_bits" >&6 if test "$ac_cv_sys_file_offset_bits" != no; then @@ -14785,7 +16213,7 @@ EOF fi rm -rf conftest* - echo "$as_me:14788: checking for _LARGE_FILES value needed for large files" >&5 + echo "$as_me:16216: checking for _LARGE_FILES value needed for large files" >&5 echo $ECHO_N "checking for _LARGE_FILES value needed for large files... $ECHO_C" >&6 if test "${ac_cv_sys_large_files+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -14793,7 +16221,7 @@ else while :; do ac_cv_sys_large_files=no cat >"conftest.$ac_ext" <<_ACEOF -#line 14796 "configure" +#line 16224 "configure" #include "confdefs.h" #include /* Check that off_t can represent 2**63 - 1 correctly. @@ -14813,16 +16241,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14816: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16244: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14819: \$? = $ac_status" >&5 + echo "$as_me:16247: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14822: \"$ac_try\"") >&5 + { (eval echo "$as_me:16250: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14825: \$? = $ac_status" >&5 + echo "$as_me:16253: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then break else @@ -14831,7 +16259,7 @@ cat "conftest.$ac_ext" >&5 fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" cat >"conftest.$ac_ext" <<_ACEOF -#line 14834 "configure" +#line 16262 "configure" #include "confdefs.h" #define _LARGE_FILES 1 #include @@ -14852,16 +16280,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14855: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16283: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14858: \$? = $ac_status" >&5 + echo "$as_me:16286: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14861: \"$ac_try\"") >&5 + { (eval echo "$as_me:16289: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14864: \$? = $ac_status" >&5 + echo "$as_me:16292: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_sys_large_files=1; break else @@ -14872,7 +16300,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" break done fi -echo "$as_me:14875: result: $ac_cv_sys_large_files" >&5 +echo "$as_me:16303: result: $ac_cv_sys_large_files" >&5 echo "${ECHO_T}$ac_cv_sys_large_files" >&6 if test "$ac_cv_sys_large_files" != no; then @@ -14885,7 +16313,7 @@ rm -rf conftest* fi if test "$enable_largefile" != no ; then - echo "$as_me:14888: checking for _LARGEFILE_SOURCE value needed for large files" >&5 + echo "$as_me:16316: checking for _LARGEFILE_SOURCE value needed for large files" >&5 echo $ECHO_N "checking for _LARGEFILE_SOURCE value needed for large files... $ECHO_C" >&6 if test "${ac_cv_sys_largefile_source+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -14893,7 +16321,7 @@ else while :; do ac_cv_sys_largefile_source=no cat >"conftest.$ac_ext" <<_ACEOF -#line 14896 "configure" +#line 16324 "configure" #include "confdefs.h" #include #include @@ -14908,16 +16336,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14911: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16339: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14914: \$? = $ac_status" >&5 + echo "$as_me:16342: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14917: \"$ac_try\"") >&5 + { (eval echo "$as_me:16345: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14920: \$? = $ac_status" >&5 + echo "$as_me:16348: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then break else @@ -14926,7 +16354,7 @@ cat "conftest.$ac_ext" >&5 fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" cat >"conftest.$ac_ext" <<_ACEOF -#line 14929 "configure" +#line 16357 "configure" #include "confdefs.h" #define _LARGEFILE_SOURCE 1 #include @@ -14942,16 +16370,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:14945: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16373: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:14948: \$? = $ac_status" >&5 + echo "$as_me:16376: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:14951: \"$ac_try\"") >&5 + { (eval echo "$as_me:16379: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:14954: \$? = $ac_status" >&5 + echo "$as_me:16382: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_sys_largefile_source=1; break else @@ -14962,7 +16390,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" break done fi -echo "$as_me:14965: result: $ac_cv_sys_largefile_source" >&5 +echo "$as_me:16393: result: $ac_cv_sys_largefile_source" >&5 echo "${ECHO_T}$ac_cv_sys_largefile_source" >&6 if test "$ac_cv_sys_largefile_source" != no; then @@ -14976,13 +16404,13 @@ rm -rf conftest* # We used to try defining _XOPEN_SOURCE=500 too, to work around a bug # in glibc 2.1.3, but that breaks too many other things. # If you want fseeko and ftello with glibc, upgrade to a fixed glibc. -echo "$as_me:14979: checking for fseeko" >&5 +echo "$as_me:16407: checking for fseeko" >&5 echo $ECHO_N "checking for fseeko... $ECHO_C" >&6 if test "${ac_cv_func_fseeko+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 14985 "configure" +#line 16413 "configure" #include "confdefs.h" #include #include @@ -14996,16 +16424,16 @@ int (*my_fseeko)(FILE *, off_t, int) = fseeko; } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:14999: \"$ac_link\"") >&5 +if { (eval echo "$as_me:16427: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:15002: \$? = $ac_status" >&5 + echo "$as_me:16430: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:15005: \"$ac_try\"") >&5 + { (eval echo "$as_me:16433: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:15008: \$? = $ac_status" >&5 + echo "$as_me:16436: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_func_fseeko=yes else @@ -15015,7 +16443,7 @@ ac_cv_func_fseeko=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:15018: result: $ac_cv_func_fseeko" >&5 +echo "$as_me:16446: result: $ac_cv_func_fseeko" >&5 echo "${ECHO_T}$ac_cv_func_fseeko" >&6 if test $ac_cv_func_fseeko = yes; then @@ -15054,14 +16482,14 @@ fi fi - echo "$as_me:15057: checking whether to use struct dirent64" >&5 + echo "$as_me:16485: checking whether to use struct dirent64" >&5 echo $ECHO_N "checking whether to use struct dirent64... $ECHO_C" >&6 if test "${cf_cv_struct_dirent64+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 15064 "configure" +#line 16492 "configure" #include "confdefs.h" #pragma GCC diagnostic error "-Wincompatible-pointer-types" @@ -15088,16 +16516,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:15091: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16519: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:15094: \$? = $ac_status" >&5 + echo "$as_me:16522: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:15097: \"$ac_try\"") >&5 + { (eval echo "$as_me:16525: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:15100: \$? = $ac_status" >&5 + echo "$as_me:16528: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_struct_dirent64=yes else @@ -15108,7 +16536,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:15111: result: $cf_cv_struct_dirent64" >&5 +echo "$as_me:16539: result: $cf_cv_struct_dirent64" >&5 echo "${ECHO_T}$cf_cv_struct_dirent64" >&6 test "$cf_cv_struct_dirent64" = yes && cat >>confdefs.h <<\EOF @@ -15118,7 +16546,7 @@ EOF fi ### Enable compiling-in rcs id's -echo "$as_me:15121: checking if RCS identifiers should be compiled-in" >&5 +echo "$as_me:16549: checking if RCS identifiers should be compiled-in" >&5 echo $ECHO_N "checking if RCS identifiers should be compiled-in... $ECHO_C" >&6 # Check whether --with-rcs-ids or --without-rcs-ids was given. @@ -15128,7 +16556,7 @@ if test "${with_rcs_ids+set}" = set; then else with_rcs_ids=no fi; -echo "$as_me:15131: result: $with_rcs_ids" >&5 +echo "$as_me:16559: result: $with_rcs_ids" >&5 echo "${ECHO_T}$with_rcs_ids" >&6 test "$with_rcs_ids" = yes && cat >>confdefs.h <<\EOF @@ -15138,7 +16566,7 @@ EOF ############################################################################### ### Note that some functions (such as const) are normally disabled anyway. -echo "$as_me:15141: checking if you want to build with function extensions" >&5 +echo "$as_me:16569: checking if you want to build with function extensions" >&5 echo $ECHO_N "checking if you want to build with function extensions... $ECHO_C" >&6 # Check whether --enable-ext-funcs or --disable-ext-funcs was given. @@ -15148,7 +16576,7 @@ if test "${enable_ext_funcs+set}" = set; then else with_ext_funcs=yes fi; -echo "$as_me:15151: result: $with_ext_funcs" >&5 +echo "$as_me:16579: result: $with_ext_funcs" >&5 echo "${ECHO_T}$with_ext_funcs" >&6 if test "$with_ext_funcs" = yes ; then NCURSES_EXT_FUNCS=1 @@ -15166,7 +16594,7 @@ else fi ### use option --enable-const to turn on use of const beyond that in XSI. -echo "$as_me:15169: checking for extended use of const keyword" >&5 +echo "$as_me:16597: checking for extended use of const keyword" >&5 echo $ECHO_N "checking for extended use of const keyword... $ECHO_C" >&6 # Check whether --enable-const or --disable-const was given. @@ -15176,7 +16604,7 @@ if test "${enable_const+set}" = set; then else with_ext_const=no fi; -echo "$as_me:15179: result: $with_ext_const" >&5 +echo "$as_me:16607: result: $with_ext_const" >&5 echo "${ECHO_T}$with_ext_const" >&6 NCURSES_CONST='/*nothing*/' if test "$with_ext_const" = yes ; then @@ -15186,7 +16614,7 @@ fi ############################################################################### # These options are relatively safe to experiment with. -echo "$as_me:15189: checking if you want all development code" >&5 +echo "$as_me:16617: checking if you want all development code" >&5 echo $ECHO_N "checking if you want all development code... $ECHO_C" >&6 # Check whether --with-develop or --without-develop was given. @@ -15196,7 +16624,7 @@ if test "${with_develop+set}" = set; then else with_develop=no fi; -echo "$as_me:15199: result: $with_develop" >&5 +echo "$as_me:16627: result: $with_develop" >&5 echo "${ECHO_T}$with_develop" >&6 ############################################################################### @@ -15205,7 +16633,7 @@ echo "${ECHO_T}$with_develop" >&6 # This is still experimental (20080329), but should ultimately be moved to # the script-block --with-normal, etc. -echo "$as_me:15208: checking if you want to link with the pthread library" >&5 +echo "$as_me:16636: checking if you want to link with the pthread library" >&5 echo $ECHO_N "checking if you want to link with the pthread library... $ECHO_C" >&6 # Check whether --with-pthread or --without-pthread was given. @@ -15215,27 +16643,27 @@ if test "${with_pthread+set}" = set; then else with_pthread=no fi; -echo "$as_me:15218: result: $with_pthread" >&5 +echo "$as_me:16646: result: $with_pthread" >&5 echo "${ECHO_T}$with_pthread" >&6 if test "$with_pthread" != no ; then - echo "$as_me:15222: checking for pthread.h" >&5 + echo "$as_me:16650: checking for pthread.h" >&5 echo $ECHO_N "checking for pthread.h... $ECHO_C" >&6 if test "${ac_cv_header_pthread_h+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 15228 "configure" +#line 16656 "configure" #include "confdefs.h" #include _ACEOF -if { (eval echo "$as_me:15232: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:16660: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:15238: \$? = $ac_status" >&5 + echo "$as_me:16666: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -15254,7 +16682,7 @@ else fi rm -f conftest.err "conftest.$ac_ext" fi -echo "$as_me:15257: result: $ac_cv_header_pthread_h" >&5 +echo "$as_me:16685: result: $ac_cv_header_pthread_h" >&5 echo "${ECHO_T}$ac_cv_header_pthread_h" >&6 if test "$ac_cv_header_pthread_h" = yes; then @@ -15264,7 +16692,7 @@ EOF for cf_lib_pthread in pthread c_r do - echo "$as_me:15267: checking if we can link with the $cf_lib_pthread library" >&5 + echo "$as_me:16695: checking if we can link with the $cf_lib_pthread library" >&5 echo $ECHO_N "checking if we can link with the $cf_lib_pthread library... $ECHO_C" >&6 cf_save_LIBS="$LIBS" @@ -15285,7 +16713,7 @@ done LIBS="$cf_add_libs" cat >"conftest.$ac_ext" <<_ACEOF -#line 15288 "configure" +#line 16716 "configure" #include "confdefs.h" #include @@ -15302,16 +16730,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:15305: \"$ac_link\"") >&5 +if { (eval echo "$as_me:16733: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:15308: \$? = $ac_status" >&5 + echo "$as_me:16736: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:15311: \"$ac_try\"") >&5 + { (eval echo "$as_me:16739: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:15314: \$? = $ac_status" >&5 + echo "$as_me:16742: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then with_pthread=yes else @@ -15321,7 +16749,7 @@ with_pthread=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS="$cf_save_LIBS" - echo "$as_me:15324: result: $with_pthread" >&5 + echo "$as_me:16752: result: $with_pthread" >&5 echo "${ECHO_T}$with_pthread" >&6 test "$with_pthread" = yes && break done @@ -15349,7 +16777,7 @@ cat >>confdefs.h <<\EOF EOF else - { { echo "$as_me:15352: error: Cannot link with pthread library" >&5 + { { echo "$as_me:16780: error: Cannot link with pthread library" >&5 echo "$as_me: error: Cannot link with pthread library" >&2;} { (exit 1); exit 1; }; } fi @@ -15358,7 +16786,7 @@ fi fi -echo "$as_me:15361: checking if you want to use weak-symbols for pthreads" >&5 +echo "$as_me:16789: checking if you want to use weak-symbols for pthreads" >&5 echo $ECHO_N "checking if you want to use weak-symbols for pthreads... $ECHO_C" >&6 # Check whether --enable-weak-symbols or --disable-weak-symbols was given. @@ -15368,18 +16796,18 @@ if test "${enable_weak_symbols+set}" = set; then else use_weak_symbols=no fi; -echo "$as_me:15371: result: $use_weak_symbols" >&5 +echo "$as_me:16799: result: $use_weak_symbols" >&5 echo "${ECHO_T}$use_weak_symbols" >&6 if test "$use_weak_symbols" = yes ; then -echo "$as_me:15375: checking if $CC supports weak symbols" >&5 +echo "$as_me:16803: checking if $CC supports weak symbols" >&5 echo $ECHO_N "checking if $CC supports weak symbols... $ECHO_C" >&6 if test "${cf_cv_weak_symbols+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 15382 "configure" +#line 16810 "configure" #include "confdefs.h" #include @@ -15405,16 +16833,16 @@ weak_symbol(fopen); } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:15408: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:16836: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:15411: \$? = $ac_status" >&5 + echo "$as_me:16839: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:15414: \"$ac_try\"") >&5 + { (eval echo "$as_me:16842: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:15417: \$? = $ac_status" >&5 + echo "$as_me:16845: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_weak_symbols=yes else @@ -15425,7 +16853,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:15428: result: $cf_cv_weak_symbols" >&5 +echo "$as_me:16856: result: $cf_cv_weak_symbols" >&5 echo "${ECHO_T}$cf_cv_weak_symbols" >&6 else @@ -15454,13 +16882,13 @@ EOF fi # OpenSUSE is installing ncurses6, using reentrant option. -echo "$as_me:15457: checking for _nc_TABSIZE" >&5 +echo "$as_me:16885: checking for _nc_TABSIZE" >&5 echo $ECHO_N "checking for _nc_TABSIZE... $ECHO_C" >&6 if test "${ac_cv_func__nc_TABSIZE+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 15463 "configure" +#line 16891 "configure" #include "confdefs.h" #define _nc_TABSIZE autoconf_temporary #include /* least-intrusive standard header which defines gcc2 __stub macros */ @@ -15491,16 +16919,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:15494: \"$ac_link\"") >&5 +if { (eval echo "$as_me:16922: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:15497: \$? = $ac_status" >&5 + echo "$as_me:16925: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:15500: \"$ac_try\"") >&5 + { (eval echo "$as_me:16928: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:15503: \$? = $ac_status" >&5 + echo "$as_me:16931: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_func__nc_TABSIZE=yes else @@ -15510,7 +16938,7 @@ ac_cv_func__nc_TABSIZE=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:15513: result: $ac_cv_func__nc_TABSIZE" >&5 +echo "$as_me:16941: result: $ac_cv_func__nc_TABSIZE" >&5 echo "${ECHO_T}$ac_cv_func__nc_TABSIZE" >&6 if test "$ac_cv_func__nc_TABSIZE" = yes; then assume_reentrant=yes @@ -15522,7 +16950,7 @@ fi # opaque outside of that, so there is no --enable-opaque option. We can use # this option without --with-pthreads, but this will be always set for # pthreads. -echo "$as_me:15525: checking if you want experimental reentrant code" >&5 +echo "$as_me:16953: checking if you want experimental reentrant code" >&5 echo $ECHO_N "checking if you want experimental reentrant code... $ECHO_C" >&6 # Check whether --enable-reentrant or --disable-reentrant was given. @@ -15532,7 +16960,7 @@ if test "${enable_reentrant+set}" = set; then else with_reentrant=$assume_reentrant fi; -echo "$as_me:15535: result: $with_reentrant" >&5 +echo "$as_me:16963: result: $with_reentrant" >&5 echo "${ECHO_T}$with_reentrant" >&6 if test "$with_reentrant" = yes ; then cf_cv_enable_reentrant=1 @@ -15555,7 +16983,7 @@ fi ### Allow using a different wrap-prefix if test "$cf_cv_enable_reentrant" != 0 || test "$BROKEN_LINKER" = 1 ; then - echo "$as_me:15558: checking for prefix used to wrap public variables" >&5 + echo "$as_me:16986: checking for prefix used to wrap public variables" >&5 echo $ECHO_N "checking for prefix used to wrap public variables... $ECHO_C" >&6 # Check whether --with-wrap-prefix or --without-wrap-prefix was given. @@ -15565,7 +16993,7 @@ if test "${with_wrap_prefix+set}" = set; then else NCURSES_WRAP_PREFIX=_nc_ fi; - echo "$as_me:15568: result: $NCURSES_WRAP_PREFIX" >&5 + echo "$as_me:16996: result: $NCURSES_WRAP_PREFIX" >&5 echo "${ECHO_T}$NCURSES_WRAP_PREFIX" >&6 else NCURSES_WRAP_PREFIX=_nc_ @@ -15579,7 +17007,7 @@ EOF ### use option --disable-echo to suppress full display compiling commands -echo "$as_me:15582: checking if you want to see long compiling messages" >&5 +echo "$as_me:17010: checking if you want to see long compiling messages" >&5 echo $ECHO_N "checking if you want to see long compiling messages... $ECHO_C" >&6 # Check whether --enable-echo or --disable-echo was given. @@ -15613,10 +17041,10 @@ else ECHO_CC='' fi; -echo "$as_me:15616: result: $enableval" >&5 +echo "$as_me:17044: result: $enableval" >&5 echo "${ECHO_T}$enableval" >&6 -echo "$as_me:15619: checking if you want to use C11 _Noreturn feature" >&5 +echo "$as_me:17047: checking if you want to use C11 _Noreturn feature" >&5 echo $ECHO_N "checking if you want to use C11 _Noreturn feature... $ECHO_C" >&6 # Check whether --enable-stdnoreturn or --disable-stdnoreturn was given. @@ -15633,17 +17061,17 @@ else enable_stdnoreturn=no fi; -echo "$as_me:15636: result: $enable_stdnoreturn" >&5 +echo "$as_me:17064: result: $enable_stdnoreturn" >&5 echo "${ECHO_T}$enable_stdnoreturn" >&6 if test $enable_stdnoreturn = yes; then -echo "$as_me:15640: checking for C11 _Noreturn feature" >&5 +echo "$as_me:17068: checking for C11 _Noreturn feature" >&5 echo $ECHO_N "checking for C11 _Noreturn feature... $ECHO_C" >&6 if test "${cf_cv_c11_noreturn+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 15646 "configure" +#line 17074 "configure" #include "confdefs.h" $ac_includes_default @@ -15659,16 +17087,16 @@ if (feof(stdin)) giveup() } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:15662: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:17090: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:15665: \$? = $ac_status" >&5 + echo "$as_me:17093: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:15668: \"$ac_try\"") >&5 + { (eval echo "$as_me:17096: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:15671: \$? = $ac_status" >&5 + echo "$as_me:17099: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_c11_noreturn=yes else @@ -15679,7 +17107,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:15682: result: $cf_cv_c11_noreturn" >&5 +echo "$as_me:17110: result: $cf_cv_c11_noreturn" >&5 echo "${ECHO_T}$cf_cv_c11_noreturn" >&6 else cf_cv_c11_noreturn=no, @@ -15735,16 +17163,16 @@ then then test -n "$verbose" && echo " repairing CFLAGS: $CFLAGS" 1>&6 -echo "${as_me:-configure}:15738: testing repairing CFLAGS: $CFLAGS ..." 1>&5 +echo "${as_me:-configure}:17166: testing repairing CFLAGS: $CFLAGS ..." 1>&5 CFLAGS="$cf_temp_flags" test -n "$verbose" && echo " ... fixed $CFLAGS" 1>&6 -echo "${as_me:-configure}:15743: testing ... fixed $CFLAGS ..." 1>&5 +echo "${as_me:-configure}:17171: testing ... fixed $CFLAGS ..." 1>&5 test -n "$verbose" && echo " ... extra $EXTRA_CFLAGS" 1>&6 -echo "${as_me:-configure}:15747: testing ... extra $EXTRA_CFLAGS ..." 1>&5 +echo "${as_me:-configure}:17175: testing ... extra $EXTRA_CFLAGS ..." 1>&5 fi ;; @@ -15783,16 +17211,16 @@ then then test -n "$verbose" && echo " repairing CPPFLAGS: $CPPFLAGS" 1>&6 -echo "${as_me:-configure}:15786: testing repairing CPPFLAGS: $CPPFLAGS ..." 1>&5 +echo "${as_me:-configure}:17214: testing repairing CPPFLAGS: $CPPFLAGS ..." 1>&5 CPPFLAGS="$cf_temp_flags" test -n "$verbose" && echo " ... fixed $CPPFLAGS" 1>&6 -echo "${as_me:-configure}:15791: testing ... fixed $CPPFLAGS ..." 1>&5 +echo "${as_me:-configure}:17219: testing ... fixed $CPPFLAGS ..." 1>&5 test -n "$verbose" && echo " ... extra $EXTRA_CFLAGS" 1>&6 -echo "${as_me:-configure}:15795: testing ... extra $EXTRA_CFLAGS ..." 1>&5 +echo "${as_me:-configure}:17223: testing ... extra $EXTRA_CFLAGS ..." 1>&5 fi ;; @@ -15831,23 +17259,23 @@ then then test -n "$verbose" && echo " repairing LDFLAGS: $LDFLAGS" 1>&6 -echo "${as_me:-configure}:15834: testing repairing LDFLAGS: $LDFLAGS ..." 1>&5 +echo "${as_me:-configure}:17262: testing repairing LDFLAGS: $LDFLAGS ..." 1>&5 LDFLAGS="$cf_temp_flags" test -n "$verbose" && echo " ... fixed $LDFLAGS" 1>&6 -echo "${as_me:-configure}:15839: testing ... fixed $LDFLAGS ..." 1>&5 +echo "${as_me:-configure}:17267: testing ... fixed $LDFLAGS ..." 1>&5 test -n "$verbose" && echo " ... extra $EXTRA_CFLAGS" 1>&6 -echo "${as_me:-configure}:15843: testing ... extra $EXTRA_CFLAGS ..." 1>&5 +echo "${as_me:-configure}:17271: testing ... extra $EXTRA_CFLAGS ..." 1>&5 fi ;; esac fi -echo "$as_me:15850: checking if you want to turn on gcc warnings" >&5 +echo "$as_me:17278: checking if you want to turn on gcc warnings" >&5 echo $ECHO_N "checking if you want to turn on gcc warnings... $ECHO_C" >&6 # Check whether --enable-warnings or --disable-warnings was given. @@ -15864,7 +17292,7 @@ else enable_warnings=no fi; -echo "$as_me:15867: result: $enable_warnings" >&5 +echo "$as_me:17295: result: $enable_warnings" >&5 echo "${ECHO_T}$enable_warnings" >&6 if test "$enable_warnings" = "yes" then @@ -15888,10 +17316,10 @@ do done cat >"conftest.$ac_ext" <<_ACEOF -#line 15891 "configure" +#line 17319 "configure" #include "confdefs.h" -#include +$ac_includes_default #include int @@ -15903,32 +17331,32 @@ String foo = malloc(1); free((void*)foo) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:15906: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:17334: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:15909: \$? = $ac_status" >&5 + echo "$as_me:17337: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:15912: \"$ac_try\"") >&5 + { (eval echo "$as_me:17340: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:15915: \$? = $ac_status" >&5 + echo "$as_me:17343: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then -echo "$as_me:15918: checking for X11/Xt const-feature" >&5 +echo "$as_me:17346: checking for X11/Xt const-feature" >&5 echo $ECHO_N "checking for X11/Xt const-feature... $ECHO_C" >&6 if test "${cf_cv_const_x_string+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 15925 "configure" +#line 17353 "configure" #include "confdefs.h" #undef _CONST_X_STRING #define _CONST_X_STRING /* X11R7.8 (perhaps) */ #undef XTSTRINGDEFINES /* X11R5 and later */ -#include +$ac_includes_default #include int @@ -15940,16 +17368,16 @@ String foo = malloc(1); *foo = 0 } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:15943: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:17371: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:15946: \$? = $ac_status" >&5 + echo "$as_me:17374: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:15949: \"$ac_try\"") >&5 + { (eval echo "$as_me:17377: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:15952: \$? = $ac_status" >&5 + echo "$as_me:17380: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_const_x_string=no @@ -15964,7 +17392,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:15967: result: $cf_cv_const_x_string" >&5 +echo "$as_me:17395: result: $cf_cv_const_x_string" >&5 echo "${ECHO_T}$cf_cv_const_x_string" >&6 LIBS="$cf_save_LIBS_CF_CONST_X_STRING" @@ -15993,7 +17421,7 @@ fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi cat > "conftest.$ac_ext" <&5 -echo "$as_me: checking for $CC warning options..." >&6;} + echo "$as_me:17440: checking for $CC warning options" >&5 +echo $ECHO_N "checking for $CC warning options... $ECHO_C" >&6 + test -n "$verbose" && echo "$as_me:17442: result: " >&5 +echo "${ECHO_T}" >&6 cf_save_CFLAGS="$CFLAGS" EXTRA_CFLAGS="$EXTRA_CFLAGS -Wall" for cf_opt in \ @@ -16025,12 +17455,12 @@ echo "$as_me: checking for $CC warning options..." >&6;} wd981 do CFLAGS="$cf_save_CFLAGS $EXTRA_CFLAGS -$cf_opt" - if { (eval echo "$as_me:16028: \"$ac_compile\"") >&5 + if { (eval echo "$as_me:17458: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:16031: \$? = $ac_status" >&5 + echo "$as_me:17461: \$? = $ac_status" >&5 (exit "$ac_status"); }; then - test -n "$verbose" && echo "$as_me:16033: result: ... -$cf_opt" >&5 + test -n "$verbose" && echo "$as_me:17463: result: ... -$cf_opt" >&5 echo "${ECHO_T}... -$cf_opt" >&6 EXTRA_CFLAGS="$EXTRA_CFLAGS -$cf_opt" fi @@ -16038,8 +17468,10 @@ echo "${ECHO_T}... -$cf_opt" >&6 CFLAGS="$cf_save_CFLAGS" elif test "$GCC" = yes && test "$GCC_VERSION" != "unknown" then - { echo "$as_me:16041: checking for $CC warning options..." >&5 -echo "$as_me: checking for $CC warning options..." >&6;} + echo "$as_me:17471: checking for $CC warning options" >&5 +echo $ECHO_N "checking for $CC warning options... $ECHO_C" >&6 + test -n "$verbose" && echo "$as_me:17473: result: " >&5 +echo "${ECHO_T}" >&6 cf_save_CFLAGS="$CFLAGS" cf_warn_CONST="" test "$with_ext_const" = yes && cf_warn_CONST="Wwrite-strings" @@ -16061,12 +17493,12 @@ echo "$as_me: checking for $CC warning options..." >&6;} Wundef Wno-inline $cf_gcc_warnings $cf_warn_CONST Wno-unknown-pragmas Wswitch-enum do CFLAGS="$cf_save_CFLAGS $EXTRA_CFLAGS -$cf_opt" - if { (eval echo "$as_me:16064: \"$ac_compile\"") >&5 + if { (eval echo "$as_me:17496: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:16067: \$? = $ac_status" >&5 + echo "$as_me:17499: \$? = $ac_status" >&5 (exit "$ac_status"); }; then - test -n "$verbose" && echo "$as_me:16069: result: ... -$cf_opt" >&5 + test -n "$verbose" && echo "$as_me:17501: result: ... -$cf_opt" >&5 echo "${ECHO_T}... -$cf_opt" >&6 case "$cf_opt" in (Winline) @@ -16074,7 +17506,7 @@ echo "${ECHO_T}... -$cf_opt" >&6 ([34].*) test -n "$verbose" && echo " feature is broken in gcc $GCC_VERSION" 1>&6 -echo "${as_me:-configure}:16077: testing feature is broken in gcc $GCC_VERSION ..." 1>&5 +echo "${as_me:-configure}:17509: testing feature is broken in gcc $GCC_VERSION ..." 1>&5 continue;; esac @@ -16084,7 +17516,7 @@ echo "${as_me:-configure}:16077: testing feature is broken in gcc $GCC_VERSION . ([12].*) test -n "$verbose" && echo " feature is broken in gcc $GCC_VERSION" 1>&6 -echo "${as_me:-configure}:16087: testing feature is broken in gcc $GCC_VERSION ..." 1>&5 +echo "${as_me:-configure}:17519: testing feature is broken in gcc $GCC_VERSION ..." 1>&5 continue;; esac @@ -16117,10 +17549,12 @@ cat > conftest.i <&5 -echo "$as_me: checking for $CC __attribute__ directives..." >&6;} + echo "$as_me:17552: checking for $CC __attribute__ directives" >&5 +echo $ECHO_N "checking for $CC __attribute__ directives... $ECHO_C" >&6 + test -n "$verbose" && echo "$as_me:17554: result: " >&5 +echo "${ECHO_T}" >&6 cat > "conftest.$ac_ext" < #include "confdefs.h" #include "conftest.h" @@ -16170,12 +17604,12 @@ EOF ;; esac - if { (eval echo "$as_me:16173: \"$ac_compile\"") >&5 + if { (eval echo "$as_me:17607: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:16176: \$? = $ac_status" >&5 + echo "$as_me:17610: \$? = $ac_status" >&5 (exit "$ac_status"); }; then - test -n "$verbose" && echo "$as_me:16178: result: ... $cf_attribute" >&5 + test -n "$verbose" && echo "$as_me:17612: result: ... $cf_attribute" >&5 echo "${ECHO_T}... $cf_attribute" >&6 cat conftest.h >>confdefs.h case "$cf_attribute" in @@ -16243,7 +17677,7 @@ if test "x$enable_warnings" = "xyes"; then fi ### use option --enable-assertions to turn on generation of assertion code -echo "$as_me:16246: checking if you want to enable runtime assertions" >&5 +echo "$as_me:17680: checking if you want to enable runtime assertions" >&5 echo $ECHO_N "checking if you want to enable runtime assertions... $ECHO_C" >&6 # Check whether --enable-assertions or --disable-assertions was given. @@ -16253,7 +17687,7 @@ if test "${enable_assertions+set}" = set; then else with_assertions=no fi; -echo "$as_me:16256: result: $with_assertions" >&5 +echo "$as_me:17690: result: $with_assertions" >&5 echo "${ECHO_T}$with_assertions" >&6 if test -n "$GCC" then @@ -16306,7 +17740,7 @@ case "$CFLAGS $CPPFLAGS" in ;; esac -echo "$as_me:16309: checking whether to add trace feature to all models" >&5 +echo "$as_me:17743: checking whether to add trace feature to all models" >&5 echo $ECHO_N "checking whether to add trace feature to all models... $ECHO_C" >&6 # Check whether --with-trace or --without-trace was given. @@ -16316,115 +17750,21 @@ if test "${with_trace+set}" = set; then else cf_with_trace=$cf_all_traces fi; -echo "$as_me:16319: result: $cf_with_trace" >&5 +echo "$as_me:17753: result: $cf_with_trace" >&5 echo "${ECHO_T}$cf_with_trace" >&6 if test "$cf_with_trace" = yes ; then ADA_TRACE=TRUE -cf_fix_cppflags=no -cf_new_cflags= -cf_new_cppflags= -cf_new_extra_cppflags= - -for cf_add_cflags in -DTRACE -do -case "$cf_fix_cppflags" in -(no) - case "$cf_add_cflags" in - (-undef|-nostdinc*|-I*|-D*|-U*|-E|-P|-C) - case "$cf_add_cflags" in - (-D*) - cf_tst_cflags=`echo "${cf_add_cflags}" |sed -e 's/^-D[^=]*='\''\"[^"]*//'` - - test "x${cf_add_cflags}" != "x${cf_tst_cflags}" \ - && test -z "${cf_tst_cflags}" \ - && cf_fix_cppflags=yes - - if test "$cf_fix_cppflags" = yes ; then - - test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " - cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" - - continue - elif test "${cf_tst_cflags}" = "\"'" ; then - - test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " - cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" - - continue - fi - ;; - esac - case "$CPPFLAGS" in - (*$cf_add_cflags) - ;; - (*) - case "$cf_add_cflags" in - (-D*) - cf_tst_cppflags=`echo "x$cf_add_cflags" | sed -e 's/^...//' -e 's/=.*//'` - -CPPFLAGS=`echo "$CPPFLAGS" | \ - sed -e 's/-[UD]'"$cf_tst_cppflags"'\(=[^ ]*\)\?[ ]/ /g' \ - -e 's/-[UD]'"$cf_tst_cppflags"'\(=[^ ]*\)\?$//g'` - - ;; - esac - - test -n "$cf_new_cppflags" && cf_new_cppflags="$cf_new_cppflags " - cf_new_cppflags="${cf_new_cppflags}$cf_add_cflags" - - ;; - esac - ;; - (*) - - test -n "$cf_new_cflags" && cf_new_cflags="$cf_new_cflags " - cf_new_cflags="${cf_new_cflags}$cf_add_cflags" - - ;; - esac - ;; -(yes) - - test -n "$cf_new_extra_cppflags" && cf_new_extra_cppflags="$cf_new_extra_cppflags " - cf_new_extra_cppflags="${cf_new_extra_cppflags}$cf_add_cflags" - - cf_tst_cflags=`echo "${cf_add_cflags}" |sed -e 's/^[^"]*"'\''//'` - - test "x${cf_add_cflags}" != "x${cf_tst_cflags}" \ - && test -z "${cf_tst_cflags}" \ - && cf_fix_cppflags=no - ;; -esac -done - -if test -n "$cf_new_cflags" ; then - - test -n "$CFLAGS" && CFLAGS="$CFLAGS " - CFLAGS="${CFLAGS}$cf_new_cflags" - -fi - -if test -n "$cf_new_cppflags" ; then - - test -n "$CPPFLAGS" && CPPFLAGS="$CPPFLAGS " - CPPFLAGS="${CPPFLAGS}$cf_new_cppflags" - -fi - -if test -n "$cf_new_extra_cppflags" ; then - - test -n "$EXTRA_CPPFLAGS" && EXTRA_CPPFLAGS="$EXTRA_CPPFLAGS " - EXTRA_CPPFLAGS="${EXTRA_CPPFLAGS}$cf_new_extra_cppflags" - -fi +cat >>confdefs.h <<\EOF +#define TRACE 1 +EOF else ADA_TRACE=FALSE fi -echo "$as_me:16427: checking if we want to use GNAT projects" >&5 +echo "$as_me:17767: checking if we want to use GNAT projects" >&5 echo $ECHO_N "checking if we want to use GNAT projects... $ECHO_C" >&6 # Check whether --enable-gnat-projects or --disable-gnat-projects was given. @@ -16441,21 +17781,21 @@ else enable_gnat_projects=yes fi; -echo "$as_me:16444: result: $enable_gnat_projects" >&5 +echo "$as_me:17784: result: $enable_gnat_projects" >&5 echo "${ECHO_T}$enable_gnat_projects" >&6 ### Checks for libraries. case $cf_cv_system_name in (*mingw32*) -echo "$as_me:16451: checking if ssp library is needed" >&5 +echo "$as_me:17791: checking if ssp library is needed" >&5 echo $ECHO_N "checking if ssp library is needed... $ECHO_C" >&6 if test "${cf_cv_need_libssp+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 16458 "configure" +#line 17798 "configure" #include "confdefs.h" #include @@ -16472,16 +17812,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:16475: \"$ac_link\"") >&5 +if { (eval echo "$as_me:17815: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:16478: \$? = $ac_status" >&5 + echo "$as_me:17818: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:16481: \"$ac_try\"") >&5 + { (eval echo "$as_me:17821: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16484: \$? = $ac_status" >&5 + echo "$as_me:17824: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_need_libssp=no else @@ -16491,7 +17831,7 @@ cat "conftest.$ac_ext" >&5 cf_save_LIBS="$LIBS" LIBS="$LIBS -lssp" cat >"conftest.$ac_ext" <<_ACEOF -#line 16494 "configure" +#line 17834 "configure" #include "confdefs.h" #include @@ -16508,16 +17848,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:16511: \"$ac_link\"") >&5 +if { (eval echo "$as_me:17851: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:16514: \$? = $ac_status" >&5 + echo "$as_me:17854: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:16517: \"$ac_try\"") >&5 + { (eval echo "$as_me:17857: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16520: \$? = $ac_status" >&5 + echo "$as_me:17860: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_need_libssp=yes else @@ -16531,7 +17871,7 @@ rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:16534: result: $cf_cv_need_libssp" >&5 +echo "$as_me:17874: result: $cf_cv_need_libssp" >&5 echo "${ECHO_T}$cf_cv_need_libssp" >&6 if test "x$cf_cv_need_libssp" = xyes @@ -16558,36 +17898,162 @@ fi ;; (*) -echo "$as_me:16561: checking for clock_gettime" >&5 +cf_save_libs="$LIBS" +echo "$as_me:17902: checking for clock_gettime" >&5 echo $ECHO_N "checking for clock_gettime... $ECHO_C" >&6 -if test "${cf_cv_func_clock_gettime+set}" = set; then +if test "${ac_cv_func_clock_gettime+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else - - cat >"conftest.$ac_ext" <<_ACEOF -#line 16568 "configure" + cat >"conftest.$ac_ext" <<_ACEOF +#line 17908 "configure" #include "confdefs.h" -#include +#define clock_gettime autoconf_temporary +#include /* least-intrusive standard header which defines gcc2 __stub macros */ +#undef clock_gettime + +#ifdef __cplusplus +extern "C" +#endif + +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char clock_gettime (void); + int main (void) { -struct timespec ts; - int rc = clock_gettime(CLOCK_REALTIME, &ts); (void) rc; (void)ts + +/* The GNU C library defines stubs for functions which it implements + to always fail with ENOSYS. Some functions are actually named + something starting with __ and the normal name is an alias. */ +#if defined (__stub_clock_gettime) || defined (__stub___clock_gettime) +#error found stub for clock_gettime +#endif + + return clock_gettime (); ; return 0; } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:16581: \"$ac_link\"") >&5 +if { (eval echo "$as_me:17939: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:16584: \$? = $ac_status" >&5 + echo "$as_me:17942: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:16587: \"$ac_try\"") >&5 + { (eval echo "$as_me:17945: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16590: \$? = $ac_status" >&5 + echo "$as_me:17948: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_func_clock_gettime=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_func_clock_gettime=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +fi +echo "$as_me:17958: result: $ac_cv_func_clock_gettime" >&5 +echo "${ECHO_T}$ac_cv_func_clock_gettime" >&6 +if test "$ac_cv_func_clock_gettime" = yes; then + cf_cv_test_clock_gettime=yes +else + echo "$as_me:17963: checking for clock_gettime in -lrt" >&5 +echo $ECHO_N "checking for clock_gettime in -lrt... $ECHO_C" >&6 +if test "${ac_cv_lib_rt_clock_gettime+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + ac_check_lib_save_LIBS=$LIBS +LIBS="-lrt $LIBS" +cat >"conftest.$ac_ext" <<_ACEOF +#line 17971 "configure" +#include "confdefs.h" + +/* Override any gcc2 internal prototype to avoid an error. */ +#ifdef __cplusplus +extern "C" +#endif +/* We use char because int might match the return type of a gcc2 + builtin and then its argument prototype would still apply. */ +char clock_gettime (void); +int +main (void) +{ +clock_gettime (); + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:17990: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:17993: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:17996: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:17999: \$? = $ac_status" >&5 + (exit "$ac_status"); }; }; then + ac_cv_lib_rt_clock_gettime=yes +else + echo "$as_me: failed program was:" >&5 +cat "conftest.$ac_ext" >&5 +ac_cv_lib_rt_clock_gettime=no +fi +rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" +LIBS=$ac_check_lib_save_LIBS +fi +echo "$as_me:18010: result: $ac_cv_lib_rt_clock_gettime" >&5 +echo "${ECHO_T}$ac_cv_lib_rt_clock_gettime" >&6 +if test "$ac_cv_lib_rt_clock_gettime" = yes; then + LIBS="-lrt $LIBS" + cf_cv_test_clock_gettime=yes +else + cf_cv_test_clock_gettime=no +fi + +fi + +if test "$cf_cv_test_clock_gettime" = yes ; then +echo "$as_me:18022: checking if clock_gettime links" >&5 +echo $ECHO_N "checking if clock_gettime links... $ECHO_C" >&6 +if test "${cf_cv_func_clock_gettime+set}" = set; then + echo $ECHO_N "(cached) $ECHO_C" >&6 +else + + cat >"conftest.$ac_ext" <<_ACEOF +#line 18029 "configure" +#include "confdefs.h" + +$ac_includes_default +#include + +int +main (void) +{ +struct timespec ts; + int rc = clock_gettime(CLOCK_REALTIME, &ts) + + clock_gettime(CLOCK_MONOTONIC, &ts); + (void) rc; (void)ts + ; + return 0; +} +_ACEOF +rm -f "conftest.$ac_objext" "conftest$ac_exeext" +if { (eval echo "$as_me:18047: \"$ac_link\"") >&5 + (eval $ac_link) 2>&5 + ac_status=$? + echo "$as_me:18050: \$? = $ac_status" >&5 + (exit "$ac_status"); } && + { ac_try='test -s "conftest$ac_exeext"' + { (eval echo "$as_me:18053: \"$ac_try\"") >&5 + (eval $ac_try) 2>&5 + ac_status=$? + echo "$as_me:18056: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_func_clock_gettime=yes else @@ -16598,8 +18064,11 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:16601: result: $cf_cv_func_clock_gettime" >&5 +echo "$as_me:18067: result: $cf_cv_func_clock_gettime" >&5 echo "${ECHO_T}$cf_cv_func_clock_gettime" >&6 +else + cf_cv_func_clock_gettime=no +fi if test "$cf_cv_func_clock_gettime" = yes then @@ -16609,13 +18078,13 @@ cat >>confdefs.h <<\EOF EOF else -echo "$as_me:16612: checking for gettimeofday" >&5 +echo "$as_me:18081: checking for gettimeofday" >&5 echo $ECHO_N "checking for gettimeofday... $ECHO_C" >&6 if test "${ac_cv_func_gettimeofday+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 16618 "configure" +#line 18087 "configure" #include "confdefs.h" #define gettimeofday autoconf_temporary #include /* least-intrusive standard header which defines gcc2 __stub macros */ @@ -16646,16 +18115,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:16649: \"$ac_link\"") >&5 +if { (eval echo "$as_me:18118: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:16652: \$? = $ac_status" >&5 + echo "$as_me:18121: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:16655: \"$ac_try\"") >&5 + { (eval echo "$as_me:18124: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16658: \$? = $ac_status" >&5 + echo "$as_me:18127: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_func_gettimeofday=yes else @@ -16665,7 +18134,7 @@ ac_cv_func_gettimeofday=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:16668: result: $ac_cv_func_gettimeofday" >&5 +echo "$as_me:18137: result: $ac_cv_func_gettimeofday" >&5 echo "${ECHO_T}$ac_cv_func_gettimeofday" >&6 if test "$ac_cv_func_gettimeofday" = yes; then @@ -16675,7 +18144,7 @@ EOF else -echo "$as_me:16678: checking for gettimeofday in -lbsd" >&5 +echo "$as_me:18147: checking for gettimeofday in -lbsd" >&5 echo $ECHO_N "checking for gettimeofday in -lbsd... $ECHO_C" >&6 if test "${ac_cv_lib_bsd_gettimeofday+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -16683,7 +18152,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-lbsd $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 16686 "configure" +#line 18155 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -16702,16 +18171,16 @@ gettimeofday (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:16705: \"$ac_link\"") >&5 +if { (eval echo "$as_me:18174: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:16708: \$? = $ac_status" >&5 + echo "$as_me:18177: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:16711: \"$ac_try\"") >&5 + { (eval echo "$as_me:18180: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16714: \$? = $ac_status" >&5 + echo "$as_me:18183: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_bsd_gettimeofday=yes else @@ -16722,7 +18191,7 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:16725: result: $ac_cv_lib_bsd_gettimeofday" >&5 +echo "$as_me:18194: result: $ac_cv_lib_bsd_gettimeofday" >&5 echo "${ECHO_T}$ac_cv_lib_bsd_gettimeofday" >&6 if test "$ac_cv_lib_bsd_gettimeofday" = yes; then @@ -16755,13 +18224,13 @@ fi esac ### Checks for header files. -echo "$as_me:16758: checking for signed char" >&5 +echo "$as_me:18227: checking for signed char" >&5 echo $ECHO_N "checking for signed char... $ECHO_C" >&6 if test "${ac_cv_type_signed_char+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 16764 "configure" +#line 18233 "configure" #include "confdefs.h" $ac_includes_default int @@ -16776,16 +18245,16 @@ if (sizeof (signed char)) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:16779: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:18248: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:16782: \$? = $ac_status" >&5 + echo "$as_me:18251: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:16785: \"$ac_try\"") >&5 + { (eval echo "$as_me:18254: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16788: \$? = $ac_status" >&5 + echo "$as_me:18257: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_type_signed_char=yes else @@ -16795,10 +18264,10 @@ ac_cv_type_signed_char=no fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:16798: result: $ac_cv_type_signed_char" >&5 +echo "$as_me:18267: result: $ac_cv_type_signed_char" >&5 echo "${ECHO_T}$ac_cv_type_signed_char" >&6 -echo "$as_me:16801: checking size of signed char" >&5 +echo "$as_me:18270: checking size of signed char" >&5 echo $ECHO_N "checking size of signed char... $ECHO_C" >&6 if test "${ac_cv_sizeof_signed_char+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -16807,7 +18276,7 @@ else if test "$cross_compiling" = yes; then # Depending upon the size, compute the lo and hi bounds. cat >"conftest.$ac_ext" <<_ACEOF -#line 16810 "configure" +#line 18279 "configure" #include "confdefs.h" $ac_includes_default int @@ -16819,21 +18288,21 @@ int _array_ [1 - 2 * !((sizeof (signed char)) >= 0)] } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:16822: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:18291: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:16825: \$? = $ac_status" >&5 + echo "$as_me:18294: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:16828: \"$ac_try\"") >&5 + { (eval echo "$as_me:18297: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16831: \$? = $ac_status" >&5 + echo "$as_me:18300: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_lo=0 ac_mid=0 while :; do cat >"conftest.$ac_ext" <<_ACEOF -#line 16836 "configure" +#line 18305 "configure" #include "confdefs.h" $ac_includes_default int @@ -16845,16 +18314,16 @@ int _array_ [1 - 2 * !((sizeof (signed char)) <= $ac_mid)] } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:16848: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:18317: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:16851: \$? = $ac_status" >&5 + echo "$as_me:18320: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:16854: \"$ac_try\"") >&5 + { (eval echo "$as_me:18323: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16857: \$? = $ac_status" >&5 + echo "$as_me:18326: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_hi=$ac_mid; break else @@ -16870,7 +18339,7 @@ cat "conftest.$ac_ext" >&5 ac_hi=-1 ac_mid=-1 while :; do cat >"conftest.$ac_ext" <<_ACEOF -#line 16873 "configure" +#line 18342 "configure" #include "confdefs.h" $ac_includes_default int @@ -16882,16 +18351,16 @@ int _array_ [1 - 2 * !((sizeof (signed char)) >= $ac_mid)] } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:16885: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:18354: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:16888: \$? = $ac_status" >&5 + echo "$as_me:18357: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:16891: \"$ac_try\"") >&5 + { (eval echo "$as_me:18360: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16894: \$? = $ac_status" >&5 + echo "$as_me:18363: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_lo=$ac_mid; break else @@ -16907,7 +18376,7 @@ rm -f "conftest.$ac_objext" "conftest.$ac_ext" while test "x$ac_lo" != "x$ac_hi"; do ac_mid=`expr '(' "$ac_hi" - "$ac_lo" ')' / 2 + "$ac_lo"` cat >"conftest.$ac_ext" <<_ACEOF -#line 16910 "configure" +#line 18379 "configure" #include "confdefs.h" $ac_includes_default int @@ -16919,16 +18388,16 @@ int _array_ [1 - 2 * !((sizeof (signed char)) <= $ac_mid)] } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:16922: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:18391: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:16925: \$? = $ac_status" >&5 + echo "$as_me:18394: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:16928: \"$ac_try\"") >&5 + { (eval echo "$as_me:18397: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16931: \$? = $ac_status" >&5 + echo "$as_me:18400: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_hi=$ac_mid else @@ -16941,12 +18410,12 @@ done ac_cv_sizeof_signed_char=$ac_lo else if test "$cross_compiling" = yes; then - { { echo "$as_me:16944: error: cannot run test program while cross compiling" >&5 + { { echo "$as_me:18413: error: cannot run test program while cross compiling" >&5 echo "$as_me: error: cannot run test program while cross compiling" >&2;} { (exit 1); exit 1; }; } else cat >"conftest.$ac_ext" <<_ACEOF -#line 16949 "configure" +#line 18418 "configure" #include "confdefs.h" $ac_includes_default int @@ -16962,15 +18431,15 @@ fclose (f); } _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:16965: \"$ac_link\"") >&5 +if { (eval echo "$as_me:18434: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:16968: \$? = $ac_status" >&5 + echo "$as_me:18437: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:16970: \"$ac_try\"") >&5 + { (eval echo "$as_me:18439: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:16973: \$? = $ac_status" >&5 + echo "$as_me:18442: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_sizeof_signed_char=`cat conftest.val` else @@ -16986,7 +18455,7 @@ else ac_cv_sizeof_signed_char=0 fi fi -echo "$as_me:16989: result: $ac_cv_sizeof_signed_char" >&5 +echo "$as_me:18458: result: $ac_cv_sizeof_signed_char" >&5 echo "${ECHO_T}$ac_cv_sizeof_signed_char" >&6 cat >>confdefs.h <&5 +echo "$as_me:18467: checking for $ac_hdr that defines DIR" >&5 echo $ECHO_N "checking for $ac_hdr that defines DIR... $ECHO_C" >&6 if eval "test \"\${$as_ac_Header+set}\" = set"; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 17004 "configure" +#line 18473 "configure" #include "confdefs.h" #include #include <$ac_hdr> @@ -17016,16 +18485,16 @@ return 0; } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:17019: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:18488: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:17022: \$? = $ac_status" >&5 + echo "$as_me:18491: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:17025: \"$ac_try\"") >&5 + { (eval echo "$as_me:18494: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:17028: \$? = $ac_status" >&5 + echo "$as_me:18497: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then eval "$as_ac_Header=yes" else @@ -17035,7 +18504,7 @@ eval "$as_ac_Header=no" fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:17038: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 +echo "$as_me:18507: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then cat >>confdefs.h <&5 + echo "$as_me:18520: checking for opendir in -ldir" >&5 echo $ECHO_N "checking for opendir in -ldir... $ECHO_C" >&6 if test "${ac_cv_lib_dir_opendir+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -17056,7 +18525,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-ldir $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 17059 "configure" +#line 18528 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -17075,16 +18544,16 @@ opendir (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:17078: \"$ac_link\"") >&5 +if { (eval echo "$as_me:18547: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:17081: \$? = $ac_status" >&5 + echo "$as_me:18550: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:17084: \"$ac_try\"") >&5 + { (eval echo "$as_me:18553: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:17087: \$? = $ac_status" >&5 + echo "$as_me:18556: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_dir_opendir=yes else @@ -17095,14 +18564,14 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:17098: result: $ac_cv_lib_dir_opendir" >&5 +echo "$as_me:18567: result: $ac_cv_lib_dir_opendir" >&5 echo "${ECHO_T}$ac_cv_lib_dir_opendir" >&6 if test "$ac_cv_lib_dir_opendir" = yes; then LIBS="$LIBS -ldir" fi else - echo "$as_me:17105: checking for opendir in -lx" >&5 + echo "$as_me:18574: checking for opendir in -lx" >&5 echo $ECHO_N "checking for opendir in -lx... $ECHO_C" >&6 if test "${ac_cv_lib_x_opendir+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -17110,7 +18579,7 @@ else ac_check_lib_save_LIBS=$LIBS LIBS="-lx $LIBS" cat >"conftest.$ac_ext" <<_ACEOF -#line 17113 "configure" +#line 18582 "configure" #include "confdefs.h" /* Override any gcc2 internal prototype to avoid an error. */ @@ -17129,16 +18598,16 @@ opendir (); } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:17132: \"$ac_link\"") >&5 +if { (eval echo "$as_me:18601: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:17135: \$? = $ac_status" >&5 + echo "$as_me:18604: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:17138: \"$ac_try\"") >&5 + { (eval echo "$as_me:18607: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:17141: \$? = $ac_status" >&5 + echo "$as_me:18610: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_lib_x_opendir=yes else @@ -17149,7 +18618,7 @@ fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" LIBS=$ac_check_lib_save_LIBS fi -echo "$as_me:17152: result: $ac_cv_lib_x_opendir" >&5 +echo "$as_me:18621: result: $ac_cv_lib_x_opendir" >&5 echo "${ECHO_T}$ac_cv_lib_x_opendir" >&6 if test "$ac_cv_lib_x_opendir" = yes; then LIBS="$LIBS -lx" @@ -17157,13 +18626,13 @@ fi fi -echo "$as_me:17160: checking whether time.h and sys/time.h may both be included" >&5 +echo "$as_me:18629: checking whether time.h and sys/time.h may both be included" >&5 echo $ECHO_N "checking whether time.h and sys/time.h may both be included... $ECHO_C" >&6 if test "${ac_cv_header_time+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 17166 "configure" +#line 18635 "configure" #include "confdefs.h" #include #include @@ -17179,16 +18648,16 @@ return 0; } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:17182: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:18651: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:17185: \$? = $ac_status" >&5 + echo "$as_me:18654: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:17188: \"$ac_try\"") >&5 + { (eval echo "$as_me:18657: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:17191: \$? = $ac_status" >&5 + echo "$as_me:18660: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_header_time=yes else @@ -17198,7 +18667,7 @@ ac_cv_header_time=no fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:17201: result: $ac_cv_header_time" >&5 +echo "$as_me:18670: result: $ac_cv_header_time" >&5 echo "${ECHO_T}$ac_cv_header_time" >&6 if test $ac_cv_header_time = yes; then @@ -17216,13 +18685,13 @@ ac_link='$CC -o "conftest$ac_exeext" $CFLAGS $CPPFLAGS $LDFLAGS "conftest.$ac_ex ac_compiler_gnu=$ac_cv_c_compiler_gnu ac_main_return="return" -echo "$as_me:17219: checking for an ANSI C-conforming const" >&5 +echo "$as_me:18688: checking for an ANSI C-conforming const" >&5 echo $ECHO_N "checking for an ANSI C-conforming const... $ECHO_C" >&6 if test "${ac_cv_c_const+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 17225 "configure" +#line 18694 "configure" #include "confdefs.h" int @@ -17232,13 +18701,13 @@ main (void) #ifndef __cplusplus /* Ultrix mips cc rejects this. */ typedef int charset[2]; - const charset x; (void)x; + const charset x; /* SunOS 4.1.1 cc rejects this. */ char const *const *ccp; char **p; /* NEC SVR4.0.2 mips cc rejects this. */ struct point {int x, y;}; - static struct point const zero = {0,0}; (void)zero; + static struct point const zero = {0,0}; /* AIX XL C 1.02.0.0 rejects this. It does not let you subtract one const X* pointer from another in an arm of an if-expression whose if-part is not a constant @@ -17254,7 +18723,7 @@ main (void) char const *s = 0 ? (char *) 0 : (char const *) 0; *t++ = 0; - (void)s; + (void)s; (void)x; (void)zero; } { /* Someone thinks the Sun supposedly-ANSI compiler will reject this. */ int x[] = {25, 17}; @@ -17284,16 +18753,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" -if { (eval echo "$as_me:17287: \"$ac_compile\"") >&5 +if { (eval echo "$as_me:18756: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:17290: \$? = $ac_status" >&5 + echo "$as_me:18759: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest.$ac_objext"' - { (eval echo "$as_me:17293: \"$ac_try\"") >&5 + { (eval echo "$as_me:18762: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:17296: \$? = $ac_status" >&5 + echo "$as_me:18765: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_c_const=yes else @@ -17303,7 +18772,7 @@ ac_cv_c_const=no fi rm -f "conftest.$ac_objext" "conftest.$ac_ext" fi -echo "$as_me:17306: result: $ac_cv_c_const" >&5 +echo "$as_me:18775: result: $ac_cv_c_const" >&5 echo "${ECHO_T}$ac_cv_c_const" >&6 if test $ac_cv_c_const = no; then @@ -17315,7 +18784,7 @@ fi ### Checks for external-data -echo "$as_me:17318: checking if data-only library module links" >&5 +echo "$as_me:18787: checking if data-only library module links" >&5 echo $ECHO_N "checking if data-only library module links... $ECHO_C" >&6 if test "${cf_cv_link_dataonly+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -17323,20 +18792,20 @@ else rm -f conftest.a cat >conftest.$ac_ext <&5 + if { (eval echo "$as_me:18798: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:17332: \$? = $ac_status" >&5 + echo "$as_me:18801: \$? = $ac_status" >&5 (exit "$ac_status"); } ; then - mv conftest.o data.o && \ - ( $AR $ARFLAGS conftest.a data.o ) 2>&5 1>/dev/null + mv conftest.$OBJEXT data.$OBJEXT && \ + ( $AR $ARFLAGS conftest.a data.$OBJEXT ) 2>&5 1>/dev/null fi - rm -f conftest.$ac_ext data.o + rm -f conftest.$ac_ext data.$OBJEXT cat >conftest.$ac_ext <&5 + if { (eval echo "$as_me:18825: \"$ac_compile\"") >&5 (eval $ac_compile) 2>&5 ac_status=$? - echo "$as_me:17359: \$? = $ac_status" >&5 + echo "$as_me:18828: \$? = $ac_status" >&5 (exit "$ac_status"); }; then - mv conftest.o func.o && \ - ( $AR $ARFLAGS conftest.a func.o ) 2>&5 1>/dev/null + mv conftest.$OBJEXT func.$OBJEXT && \ + ( $AR $ARFLAGS conftest.a func.$OBJEXT ) 2>&5 1>/dev/null fi - rm -f conftest.$ac_ext func.o + rm -f conftest.$ac_ext func.$OBJEXT ( eval $RANLIB conftest.a ) 2>&5 >/dev/null cf_saveLIBS="$LIBS" LIBS="conftest.a $LIBS" @@ -17369,7 +18838,7 @@ EOF cf_cv_link_dataonly=unknown else cat >"conftest.$ac_ext" <<_ACEOF -#line 17372 "configure" +#line 18841 "configure" #include "confdefs.h" extern int testfunc(void); @@ -17380,15 +18849,15 @@ else _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:17383: \"$ac_link\"") >&5 +if { (eval echo "$as_me:18852: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:17386: \$? = $ac_status" >&5 + echo "$as_me:18855: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:17388: \"$ac_try\"") >&5 + { (eval echo "$as_me:18857: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:17391: \$? = $ac_status" >&5 + echo "$as_me:18860: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_link_dataonly=yes else @@ -17403,7 +18872,7 @@ fi fi -echo "$as_me:17406: result: $cf_cv_link_dataonly" >&5 +echo "$as_me:18875: result: $cf_cv_link_dataonly" >&5 echo "${ECHO_T}$cf_cv_link_dataonly" >&6 if test "$cf_cv_link_dataonly" = no ; then @@ -17422,23 +18891,23 @@ unistd.h \ do as_ac_Header=`echo "ac_cv_header_$ac_header" | $as_tr_sh` -echo "$as_me:17425: checking for $ac_header" >&5 +echo "$as_me:18894: checking for $ac_header" >&5 echo $ECHO_N "checking for $ac_header... $ECHO_C" >&6 if eval "test \"\${$as_ac_Header+set}\" = set"; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 17431 "configure" +#line 18900 "configure" #include "confdefs.h" #include <$ac_header> _ACEOF -if { (eval echo "$as_me:17435: \"$ac_cpp "conftest.$ac_ext"\"") >&5 +if { (eval echo "$as_me:18904: \"$ac_cpp "conftest.$ac_ext"\"") >&5 (eval $ac_cpp "conftest.$ac_ext") 2>conftest.er1 ac_status=$? $EGREP -v '^ *\+' conftest.er1 >conftest.err rm -f conftest.er1 cat conftest.err >&5 - echo "$as_me:17441: \$? = $ac_status" >&5 + echo "$as_me:18910: \$? = $ac_status" >&5 (exit "$ac_status"); } >/dev/null; then if test -s conftest.err; then ac_cpp_err=$ac_c_preproc_warn_flag @@ -17457,7 +18926,7 @@ else fi rm -f conftest.err "conftest.$ac_ext" fi -echo "$as_me:17460: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 +echo "$as_me:18929: result: `eval echo '${'"$as_ac_Header"'}'`" >&5 echo "${ECHO_T}`eval echo '${'"$as_ac_Header"'}'`" >&6 if test "`eval echo '${'"$as_ac_Header"'}'`" = yes; then cat >>confdefs.h <&5 +echo "$as_me:18939: checking for working mkstemp" >&5 echo $ECHO_N "checking for working mkstemp... $ECHO_C" >&6 if test "${cf_cv_func_mkstemp+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -17478,7 +18947,7 @@ if test "$cross_compiling" = yes; then cf_cv_func_mkstemp=maybe else cat >"conftest.$ac_ext" <<_ACEOF -#line 17481 "configure" +#line 18950 "configure" #include "confdefs.h" $ac_includes_default @@ -17513,15 +18982,15 @@ int main(void) _ACEOF rm -f "conftest$ac_exeext" -if { (eval echo "$as_me:17516: \"$ac_link\"") >&5 +if { (eval echo "$as_me:18985: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:17519: \$? = $ac_status" >&5 + echo "$as_me:18988: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='"./conftest$ac_exeext"' - { (eval echo "$as_me:17521: \"$ac_try\"") >&5 + { (eval echo "$as_me:18990: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:17524: \$? = $ac_status" >&5 + echo "$as_me:18993: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then cf_cv_func_mkstemp=yes @@ -17536,16 +19005,16 @@ rm -f core ./core.* ./*.core "conftest$ac_exeext" "conftest.$ac_objext" "conftes fi fi -echo "$as_me:17539: result: $cf_cv_func_mkstemp" >&5 +echo "$as_me:19008: result: $cf_cv_func_mkstemp" >&5 echo "${ECHO_T}$cf_cv_func_mkstemp" >&6 if test "x$cf_cv_func_mkstemp" = xmaybe ; then - echo "$as_me:17542: checking for mkstemp" >&5 + echo "$as_me:19011: checking for mkstemp" >&5 echo $ECHO_N "checking for mkstemp... $ECHO_C" >&6 if test "${ac_cv_func_mkstemp+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else cat >"conftest.$ac_ext" <<_ACEOF -#line 17548 "configure" +#line 19017 "configure" #include "confdefs.h" #define mkstemp autoconf_temporary #include /* least-intrusive standard header which defines gcc2 __stub macros */ @@ -17576,16 +19045,16 @@ main (void) } _ACEOF rm -f "conftest.$ac_objext" "conftest$ac_exeext" -if { (eval echo "$as_me:17579: \"$ac_link\"") >&5 +if { (eval echo "$as_me:19048: \"$ac_link\"") >&5 (eval $ac_link) 2>&5 ac_status=$? - echo "$as_me:17582: \$? = $ac_status" >&5 + echo "$as_me:19051: \$? = $ac_status" >&5 (exit "$ac_status"); } && { ac_try='test -s "conftest$ac_exeext"' - { (eval echo "$as_me:17585: \"$ac_try\"") >&5 + { (eval echo "$as_me:19054: \"$ac_try\"") >&5 (eval $ac_try) 2>&5 ac_status=$? - echo "$as_me:17588: \$? = $ac_status" >&5 + echo "$as_me:19057: \$? = $ac_status" >&5 (exit "$ac_status"); }; }; then ac_cv_func_mkstemp=yes else @@ -17595,7 +19064,7 @@ ac_cv_func_mkstemp=no fi rm -f "conftest.$ac_objext" "conftest$ac_exeext" "conftest.$ac_ext" fi -echo "$as_me:17598: result: $ac_cv_func_mkstemp" >&5 +echo "$as_me:19067: result: $ac_cv_func_mkstemp" >&5 echo "${ECHO_T}$ac_cv_func_mkstemp" >&6 fi @@ -17614,237 +19083,9 @@ fi cf_with_ada=yes if test "$cf_with_ada" != "no" ; then - -for cf_prog_gnat in gnat gnatmake gprconfig gprbuild -do - -cf_upper_prog_gnat=`echo "${cf_prog_gnat}" | sed y%abcdefghijklmnopqrstuvwxyz./-%ABCDEFGHIJKLMNOPQRSTUVWXYZ___%` - - unset ac_cv_path_cf_TEMP_gnat - unset cf_TEMP_gnat - # Extract the first word of "$cf_prog_gnat", so it can be a program name with args. -set dummy $cf_prog_gnat; ac_word=$2 -echo "$as_me:17627: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 -if test "${ac_cv_path_cf_TEMP_gnat+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - case $cf_TEMP_gnat in - [\\/]* | ?:[\\/]*) - ac_cv_path_cf_TEMP_gnat="$cf_TEMP_gnat" # Let the user override the test with a path. - ;; - *) - ac_save_IFS=$IFS; IFS=$ac_path_separator -ac_dummy="$PATH" -for ac_dir in $ac_dummy; do - IFS=$ac_save_IFS - test -z "$ac_dir" && ac_dir=. - if $as_executable_p "$ac_dir/$ac_word"; then - ac_cv_path_cf_TEMP_gnat="$ac_dir/$ac_word" - echo "$as_me:17644: found $ac_dir/$ac_word" >&5 - break -fi -done - - test -z "$ac_cv_path_cf_TEMP_gnat" && ac_cv_path_cf_TEMP_gnat="no" - ;; -esac -fi -cf_TEMP_gnat=$ac_cv_path_cf_TEMP_gnat - -if test -n "$cf_TEMP_gnat"; then - echo "$as_me:17656: result: $cf_TEMP_gnat" >&5 -echo "${ECHO_T}$cf_TEMP_gnat" >&6 -else - echo "$as_me:17659: result: no" >&5 -echo "${ECHO_T}no" >&6 -fi - - eval "cf_cv_PATH_$cf_upper_prog_gnat=$ac_cv_path_cf_TEMP_gnat" - - if test "x$cf_TEMP_gnat" != xno; then - unset cf_cv_gnat_version - unset cf_TEMP_gnat - -echo "$as_me:17669: checking for $cf_prog_gnat version" >&5 -echo $ECHO_N "checking for $cf_prog_gnat version... $ECHO_C" >&6 -if test "${cf_cv_gnat_version+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - -cf_cv_gnat_version=`$cf_prog_gnat --version 2>&1 | \ - grep '[0-9].[0-9][0-9]*' |\ - sed -e '2,$d' -e 's/[^0-9 \.]//g' -e 's/^[ ]*//' -e 's/ .*//'` - -fi -echo "$as_me:17680: result: $cf_cv_gnat_version" >&5 -echo "${ECHO_T}$cf_cv_gnat_version" >&6 -test -z "$cf_cv_gnat_version" && cf_cv_gnat_version=no -eval cf_TEMP_gnat=$cf_cv_gnat_version; unset cf_cv_gnat_version - - fi - eval "cf_cv_VERSION_$cf_upper_prog_gnat=$cf_TEMP_gnat" - - unset cf_TEMP_gnat - unset cf_cv_gnat_version - unset ac_cv_path_cf_TEMP_gnat -done - -if test "x$cf_cv_VERSION_GNATMAKE" = "xno"; then - cf_ada_make= - cf_cv_prog_gnat_correct=no -else - cf_ada_make=gnatmake - if test "x$cf_cv_VERSION_GPRCONFIG" = "xno"; then - # gprconfig is newer than gnatmake; we can continue... - cf_ada_config="##" - else - rm -rf ./conftest* ./*~conftest* - if mkdir conftest.src - then - cf_ada_config="" - cd conftest.src - for cf_gprconfig in Ada C - do - echo "$as_me:17709: checking for gprconfig name for $cf_gprconfig" >&5 -echo $ECHO_N "checking for gprconfig name for $cf_gprconfig... $ECHO_C" >&6 - if test "$cf_gprconfig" = C - then - for cf_gprconfig_param in \ - "$cf_gprconfig,,,,GNATGCC" \ - "$cf_gprconfig,,,,GCC" \ - "$cf_gprconfig" - do - cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&5 | ${AWK:-awk} '/^\*/{print $3;}' | head -n 1` - test -n "$cf_gprconfig_value" && break - done - else - cf_gprconfig_param=$cf_gprconfig - cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&5 | ${AWK:-awk} '/^\*/{print $3;}' | head -n 1` - fi - if test -n "$cf_gprconfig_value" - then - eval "cf_ada_config_$cf_gprconfig=$cf_gprconfig_value" - echo "$as_me:17728: result: $cf_gprconfig_value" >&5 -echo "${ECHO_T}$cf_gprconfig_value" >&6 - else - echo "$as_me:17731: result: missing" >&5 -echo "${ECHO_T}missing" >&6 - cf_ada_config="#" - break - fi - done - cd .. - rm -rf ./conftest* ./*~conftest* - fi - fi - if test "x$cf_ada_config" != "x#" - then - -echo "$as_me:17744: checking for gnat version" >&5 -echo $ECHO_N "checking for gnat version... $ECHO_C" >&6 -if test "${cf_cv_gnat_version+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - -cf_cv_gnat_version=`${cf_ada_make:-gnatmake} --version 2>&1 | \ - grep '[0-9].[0-9][0-9]*' |\ - sed -e '2,$d' -e 's/[^0-9 \.]//g' -e 's/^[ ]*//' -e 's/ .*//'` - -fi -echo "$as_me:17755: result: $cf_cv_gnat_version" >&5 -echo "${ECHO_T}$cf_cv_gnat_version" >&6 -test -z "$cf_cv_gnat_version" && cf_cv_gnat_version=no - -case "$cf_cv_gnat_version" in -(3.1[1-9]*|3.[2-9]*|[4-9].*|[1-9][0-9].[0-9]*|20[0-9][0-9]) - cf_cv_prog_gnat_correct=yes - ;; -(*) - { echo "$as_me:17764: WARNING: Unsupported GNAT version $cf_cv_gnat_version. We require 3.11 or better. Disabling Ada95 binding." >&5 -echo "$as_me: WARNING: Unsupported GNAT version $cf_cv_gnat_version. We require 3.11 or better. Disabling Ada95 binding." >&2;} - cf_cv_prog_gnat_correct=no - ;; -esac - - # Extract the first word of "m4", so it can be a program name with args. -set dummy m4; ac_word=$2 -echo "$as_me:17772: checking for $ac_word" >&5 -echo $ECHO_N "checking for $ac_word... $ECHO_C" >&6 -if test "${ac_cv_prog_M4_exists+set}" = set; then - echo $ECHO_N "(cached) $ECHO_C" >&6 -else - if test -n "$M4_exists"; then - ac_cv_prog_M4_exists="$M4_exists" # Let the user override the test. -else - ac_save_IFS=$IFS; IFS=$ac_path_separator -ac_dummy="$PATH" -for ac_dir in $ac_dummy; do - IFS=$ac_save_IFS - test -z "$ac_dir" && ac_dir=. - $as_executable_p "$ac_dir/$ac_word" || continue -ac_cv_prog_M4_exists="yes" -echo "$as_me:17787: found $ac_dir/$ac_word" >&5 -break -done - - test -z "$ac_cv_prog_M4_exists" && ac_cv_prog_M4_exists="no" -fi -fi -M4_exists=$ac_cv_prog_M4_exists -if test -n "$M4_exists"; then - echo "$as_me:17796: result: $M4_exists" >&5 -echo "${ECHO_T}$M4_exists" >&6 -else - echo "$as_me:17799: result: no" >&5 -echo "${ECHO_T}no" >&6 -fi - - if test "$ac_cv_prog_M4_exists" = no; then - cf_cv_prog_gnat_correct=no - { echo "$as_me:17805: WARNING: Ada95 binding required program m4 not found. Ada95 binding disabled" >&5 -echo "$as_me: WARNING: Ada95 binding required program m4 not found. Ada95 binding disabled" >&2;} - fi - if test "$cf_cv_prog_gnat_correct" = yes; then - echo "$as_me:17809: checking if GNAT works" >&5 -echo $ECHO_N "checking if GNAT works... $ECHO_C" >&6 - -rm -rf ./conftest* ./*~conftest* -cat >>conftest.ads <>conftest.adb <&5 2>&1 ) ; then - if ( ./conftest 1>&5 2>&1 ) ; then - cf_cv_prog_gnat_correct=yes - else - cf_cv_prog_gnat_correct=no - fi -else - cf_cv_prog_gnat_correct=no -fi -rm -rf ./conftest* ./*~conftest* - - echo "$as_me:17837: result: $cf_cv_prog_gnat_correct" >&5 -echo "${ECHO_T}$cf_cv_prog_gnat_correct" >&6 - fi - else - cf_cv_prog_gnat_correct=no - fi -fi - if test "$cf_cv_prog_gnat_correct" = yes; then - echo "$as_me:17847: checking optimization options for ADAFLAGS" >&5 + echo "$as_me:19088: checking optimization options for ADAFLAGS" >&5 echo $ECHO_N "checking optimization options for ADAFLAGS... $ECHO_C" >&6 case "$CFLAGS" in (*-g*) @@ -17861,10 +19102,10 @@ echo $ECHO_N "checking optimization options for ADAFLAGS... $ECHO_C" >&6 ;; esac - echo "$as_me:17864: result: $ADAFLAGS" >&5 + echo "$as_me:19105: result: $ADAFLAGS" >&5 echo "${ECHO_T}$ADAFLAGS" >&6 -echo "$as_me:17867: checking if GNATPREP supports -T option" >&5 +echo "$as_me:19108: checking if GNATPREP supports -T option" >&5 echo $ECHO_N "checking if GNATPREP supports -T option... $ECHO_C" >&6 if test "${cf_cv_gnatprep_opt_t+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -17874,11 +19115,11 @@ cf_cv_gnatprep_opt_t=no gnatprep -T 2>/dev/null >/dev/null && cf_cv_gnatprep_opt_t=yes fi -echo "$as_me:17877: result: $cf_cv_gnatprep_opt_t" >&5 +echo "$as_me:19118: result: $cf_cv_gnatprep_opt_t" >&5 echo "${ECHO_T}$cf_cv_gnatprep_opt_t" >&6 test "$cf_cv_gnatprep_opt_t" = yes && GNATPREP_OPTS="-T $GNATPREP_OPTS" -echo "$as_me:17881: checking if GNAT supports generics" >&5 +echo "$as_me:19122: checking if GNAT supports generics" >&5 echo $ECHO_N "checking if GNAT supports generics... $ECHO_C" >&6 case "$cf_cv_gnat_version" in (3.1[1-9]*|3.[2-9]*|[4-9].*|[1-9][0-9].[0-9]*|20[0-9][0-9]) @@ -17888,7 +19129,7 @@ case "$cf_cv_gnat_version" in cf_gnat_generics=no ;; esac -echo "$as_me:17891: result: $cf_gnat_generics" >&5 +echo "$as_me:19132: result: $cf_gnat_generics" >&5 echo "${ECHO_T}$cf_gnat_generics" >&6 if test "$cf_gnat_generics" = yes @@ -17900,7 +19141,7 @@ else cf_generic_objects= fi -echo "$as_me:17903: checking if GNAT supports SIGINT" >&5 +echo "$as_me:19144: checking if GNAT supports SIGINT" >&5 echo $ECHO_N "checking if GNAT supports SIGINT... $ECHO_C" >&6 if test "${cf_cv_gnat_sigint+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 @@ -17948,7 +19189,7 @@ fi rm -rf ./conftest* ./*~conftest* fi -echo "$as_me:17951: result: $cf_cv_gnat_sigint" >&5 +echo "$as_me:19192: result: $cf_cv_gnat_sigint" >&5 echo "${ECHO_T}$cf_cv_gnat_sigint" >&6 if test "$cf_cv_gnat_sigint" = yes ; then @@ -17961,7 +19202,7 @@ cf_gnat_libraries=no cf_gnat_projects=no if test "$enable_gnat_projects" != no ; then -echo "$as_me:17964: checking if GNAT supports project files" >&5 +echo "$as_me:19205: checking if GNAT supports project files" >&5 echo $ECHO_N "checking if GNAT supports project files... $ECHO_C" >&6 case "$cf_cv_gnat_version" in (3.[0-9]*) @@ -18024,15 +19265,15 @@ CF_EOF esac ;; esac -echo "$as_me:18027: result: $cf_gnat_projects" >&5 +echo "$as_me:19268: result: $cf_gnat_projects" >&5 echo "${ECHO_T}$cf_gnat_projects" >&6 fi # enable_gnat_projects if test "$cf_gnat_projects" = yes then - echo "$as_me:18033: checking if GNAT supports libraries" >&5 + echo "$as_me:19274: checking if GNAT supports libraries" >&5 echo $ECHO_N "checking if GNAT supports libraries... $ECHO_C" >&6 - echo "$as_me:18035: result: $cf_gnat_libraries" >&5 + echo "$as_me:19276: result: $cf_gnat_libraries" >&5 echo "${ECHO_T}$cf_gnat_libraries" >&6 fi @@ -18052,7 +19293,7 @@ then then USE_GNAT_MAKE_GPR="" else - { echo "$as_me:18055: WARNING: use old makefile rules since tools are missing" >&5 + { echo "$as_me:19296: WARNING: use old makefile rules since tools are missing" >&5 echo "$as_me: WARNING: use old makefile rules since tools are missing" >&2;} fi fi @@ -18064,7 +19305,7 @@ else USE_GNAT_LIBRARIES="#" fi -echo "$as_me:18067: checking for Ada95 compiler" >&5 +echo "$as_me:19308: checking for Ada95 compiler" >&5 echo $ECHO_N "checking for Ada95 compiler... $ECHO_C" >&6 # Check whether --with-ada-compiler or --without-ada-compiler was given. @@ -18075,12 +19316,12 @@ else cf_ada_compiler=gnatmake fi; -echo "$as_me:18078: result: $cf_ada_compiler" >&5 +echo "$as_me:19319: result: $cf_ada_compiler" >&5 echo "${ECHO_T}$cf_ada_compiler" >&6 cf_ada_package=terminal_interface -echo "$as_me:18083: checking for Ada95 include directory" >&5 +echo "$as_me:19324: checking for Ada95 include directory" >&5 echo $ECHO_N "checking for Ada95 include directory... $ECHO_C" >&6 # Check whether --with-ada-include or --without-ada-include was given. @@ -18097,26 +19338,24 @@ else cf_path_syntax="$ac_default_prefix" fi -case ".$withval" in -(.\$\(*\)*|.\'*\'*) +case "x$withval" in +(x\$\(*\)*|x\'*\'*) ;; -(..|./*|.\\*) +(x.|x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; -(.[a-zA-Z]:[\\/]*) # OS/2 EMX - ;; -(.\$\{*prefix\}*|.\$\{*dir\}*) +(x\$\{*prefix\}*|x\$\{*dir\}*) eval withval="$withval" - case ".$withval" in - (.NONE/*) + case "x$withval" in + (xNONE/*) withval=`echo "$withval" | sed -e s%NONE%$cf_path_syntax%` ;; esac ;; -(.no|.NONE/*) +(xno|xNONE/*) withval=`echo "$withval" | sed -e s%NONE%$cf_path_syntax%` ;; (*) - { { echo "$as_me:18119: error: expected a pathname, not \"$withval\"" >&5 + { { echo "$as_me:19358: error: expected a pathname, not \"$withval\"" >&5 echo "$as_me: error: expected a pathname, not \"$withval\"" >&2;} { (exit 1); exit 1; }; } ;; @@ -18125,10 +19364,10 @@ esac fi eval ADA_INCLUDE="$withval" -echo "$as_me:18128: result: $ADA_INCLUDE" >&5 +echo "$as_me:19367: result: $ADA_INCLUDE" >&5 echo "${ECHO_T}$ADA_INCLUDE" >&6 -echo "$as_me:18131: checking for Ada95 object directory" >&5 +echo "$as_me:19370: checking for Ada95 object directory" >&5 echo $ECHO_N "checking for Ada95 object directory... $ECHO_C" >&6 # Check whether --with-ada-objects or --without-ada-objects was given. @@ -18145,26 +19384,24 @@ else cf_path_syntax="$ac_default_prefix" fi -case ".$withval" in -(.\$\(*\)*|.\'*\'*) +case "x$withval" in +(x\$\(*\)*|x\'*\'*) ;; -(..|./*|.\\*) +(x.|x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; -(.[a-zA-Z]:[\\/]*) # OS/2 EMX - ;; -(.\$\{*prefix\}*|.\$\{*dir\}*) +(x\$\{*prefix\}*|x\$\{*dir\}*) eval withval="$withval" - case ".$withval" in - (.NONE/*) + case "x$withval" in + (xNONE/*) withval=`echo "$withval" | sed -e s%NONE%$cf_path_syntax%` ;; esac ;; -(.no|.NONE/*) +(xno|xNONE/*) withval=`echo "$withval" | sed -e s%NONE%$cf_path_syntax%` ;; (*) - { { echo "$as_me:18167: error: expected a pathname, not \"$withval\"" >&5 + { { echo "$as_me:19404: error: expected a pathname, not \"$withval\"" >&5 echo "$as_me: error: expected a pathname, not \"$withval\"" >&2;} { (exit 1); exit 1; }; } ;; @@ -18173,10 +19410,10 @@ esac fi eval ADA_OBJECTS="$withval" -echo "$as_me:18176: result: $ADA_OBJECTS" >&5 +echo "$as_me:19413: result: $ADA_OBJECTS" >&5 echo "${ECHO_T}$ADA_OBJECTS" >&6 -echo "$as_me:18179: checking whether to build an Ada95 shared library" >&5 +echo "$as_me:19416: checking whether to build an Ada95 shared library" >&5 echo $ECHO_N "checking whether to build an Ada95 shared library... $ECHO_C" >&6 # Check whether --with-ada-sharedlib or --without-ada-sharedlib was given. @@ -18197,11 +19434,11 @@ then fi fi -echo "$as_me:18200: result: $with_ada_sharedlib" >&5 +echo "$as_me:19437: result: $with_ada_sharedlib" >&5 echo "${ECHO_T}$with_ada_sharedlib" >&6 if test "x$cf_ada_sharedlib_warn" != xno then - { echo "$as_me:18204: WARNING: disabling Ada95 shared library since GNAT projects are not supported" >&5 + { echo "$as_me:19441: WARNING: disabling Ada95 shared library since GNAT projects are not supported" >&5 echo "$as_me: WARNING: disabling Ada95 shared library since GNAT projects are not supported" >&2;} fi @@ -18219,7 +19456,7 @@ fi # allow the Ada binding to be renamed -echo "$as_me:18222: checking for Ada95 curses library name" >&5 +echo "$as_me:19459: checking for Ada95 curses library name" >&5 echo $ECHO_N "checking for Ada95 curses library name... $ECHO_C" >&6 # Check whether --with-ada-libname or --without-ada-libname was given. @@ -18235,16 +19472,16 @@ case "x$ADA_LIBNAME" in ;; esac -echo "$as_me:18238: result: $ADA_LIBNAME" >&5 +echo "$as_me:19475: result: $ADA_LIBNAME" >&5 echo "${ECHO_T}$ADA_LIBNAME" >&6 else - { { echo "$as_me:18242: error: No usable Ada compiler found" >&5 + { { echo "$as_me:19479: error: No usable Ada compiler found" >&5 echo "$as_me: error: No usable Ada compiler found" >&2;} { (exit 1); exit 1; }; } fi else - { { echo "$as_me:18247: error: The Ada compiler is needed for this package" >&5 + { { echo "$as_me:19484: error: The Ada compiler is needed for this package" >&5 echo "$as_me: error: The Ada compiler is needed for this package" >&2;} { (exit 1); exit 1; }; } fi @@ -18284,7 +19521,7 @@ elif test "$includedir" != "/usr/include"; then fi ### Build up pieces for makefile rules -echo "$as_me:18287: checking default library suffix" >&5 +echo "$as_me:19524: checking default library suffix" >&5 echo $ECHO_N "checking default library suffix... $ECHO_C" >&6 case $DFT_LWR_MODEL in @@ -18295,10 +19532,10 @@ echo $ECHO_N "checking default library suffix... $ECHO_C" >&6 (shared) DFT_ARG_SUFFIX='' ;; esac test -n "$LIB_SUFFIX" && DFT_ARG_SUFFIX="${LIB_SUFFIX}${DFT_ARG_SUFFIX}" -echo "$as_me:18298: result: $DFT_ARG_SUFFIX" >&5 +echo "$as_me:19535: result: $DFT_ARG_SUFFIX" >&5 echo "${ECHO_T}$DFT_ARG_SUFFIX" >&6 -echo "$as_me:18301: checking default library-dependency suffix" >&5 +echo "$as_me:19538: checking default library-dependency suffix" >&5 echo $ECHO_N "checking default library-dependency suffix... $ECHO_C" >&6 case X$DFT_LWR_MODEL in @@ -18381,10 +19618,10 @@ echo $ECHO_N "checking default library-dependency suffix... $ECHO_C" >&6 DFT_LIB_SUFFIX="${LIB_SUFFIX}${EXTRA_SUFFIX}${DFT_LIB_SUFFIX}" DFT_DEP_SUFFIX="${LIB_SUFFIX}${EXTRA_SUFFIX}${DFT_DEP_SUFFIX}" fi -echo "$as_me:18384: result: $DFT_DEP_SUFFIX" >&5 +echo "$as_me:19621: result: $DFT_DEP_SUFFIX" >&5 echo "${ECHO_T}$DFT_DEP_SUFFIX" >&6 -echo "$as_me:18387: checking default object directory" >&5 +echo "$as_me:19624: checking default object directory" >&5 echo $ECHO_N "checking default object directory... $ECHO_C" >&6 case $DFT_LWR_MODEL in @@ -18400,7 +19637,7 @@ echo $ECHO_N "checking default object directory... $ECHO_C" >&6 DFT_OBJ_SUBDIR='obj_s' ;; esac esac -echo "$as_me:18403: result: $DFT_OBJ_SUBDIR" >&5 +echo "$as_me:19640: result: $DFT_OBJ_SUBDIR" >&5 echo "${ECHO_T}$DFT_OBJ_SUBDIR" >&6 ### Set up low-level terminfo dependencies for makefiles. @@ -18418,7 +19655,7 @@ fi USE_ARG_SUFFIX=${DFT_ARG_SUFFIX} -USE_LIB_SUFFIX=${DFT_ARG_SUFFIX} +ABI_SUFFIX=${DFT_ARG_SUFFIX} USE_CFG_SUFFIX=${DFT_ARG_SUFFIX} @@ -18462,7 +19699,11 @@ else fi ac_config_files="$ac_config_files $SUB_MAKEFILES src/library.gpr:src/library.gpr.in doc/adacurses${DFT_ARG_SUFFIX}-config.1:doc/MKada_config.in Makefile" + ac_config_commands="$ac_config_commands default" + +DEFS=-DHAVE_CONFIG_H + cat >confcache <<\_ACEOF # This file is a shell script that caches the results of configure # tests run on this system so they can be shared between configure @@ -18542,7 +19783,7 @@ DEFS=-DHAVE_CONFIG_H : "${CONFIG_STATUS=./config.status}" ac_clean_files_save=$ac_clean_files ac_clean_files="$ac_clean_files $CONFIG_STATUS" -{ echo "$as_me:18545: creating $CONFIG_STATUS" >&5 +{ echo "$as_me:19786: creating $CONFIG_STATUS" >&5 echo "$as_me: creating $CONFIG_STATUS" >&6;} cat >"$CONFIG_STATUS" <<_ACEOF #! $SHELL @@ -18678,7 +19919,7 @@ EOF cat >>"$CONFIG_STATUS" <>"$CONFIG_STATUS" <<\EOF echo "$ac_cs_version"; exit 0 ;; --he | --h) # Conflict between --help and --header - { { echo "$as_me:18726: error: ambiguous option: $1 + { { echo "$as_me:19967: error: ambiguous option: $1 Try \`$0 --help' for more information." >&5 echo "$as_me: error: ambiguous option: $1 Try \`$0 --help' for more information." >&2;} @@ -18742,7 +19983,7 @@ Try \`$0 --help' for more information." >&2;} ac_need_defaults=false;; # This is an error. - -*) { { echo "$as_me:18745: error: unrecognized option: $1 + -*) { { echo "$as_me:19986: error: unrecognized option: $1 Try \`$0 --help' for more information." >&5 echo "$as_me: error: unrecognized option: $1 Try \`$0 --help' for more information." >&2;} @@ -18761,7 +20002,7 @@ cat >&5 << _ACEOF ## Running config.status. ## ## ----------------------- ## -This file was extended by $as_me 2.52.20231210, executed with +This file was extended by $as_me 2.52.20250126, executed with CONFIG_FILES = $CONFIG_FILES CONFIG_HEADERS = $CONFIG_HEADERS CONFIG_LINKS = $CONFIG_LINKS @@ -18817,7 +20058,7 @@ do "Makefile" ) CONFIG_FILES="$CONFIG_FILES Makefile" ;; "default" ) CONFIG_COMMANDS="$CONFIG_COMMANDS default" ;; "include/ncurses_cfg.h" ) CONFIG_HEADERS="$CONFIG_HEADERS include/ncurses_cfg.h:include/ncurses_cfg.hin" ;; - *) { { echo "$as_me:18820: error: invalid argument: $ac_config_target" >&5 + *) { { echo "$as_me:20061: error: invalid argument: $ac_config_target" >&5 echo "$as_me: error: invalid argument: $ac_config_target" >&2;} { (exit 1); exit 1; }; };; esac @@ -18917,6 +20158,13 @@ s,@target_vendor@,$target_vendor,;t t s,@target_os@,$target_os,;t t s,@GREP@,$GREP,;t t s,@FGREP@,$FGREP,;t t +s,@cf_TEMP_gnat@,$cf_TEMP_gnat,;t t +s,@M4_exists@,$M4_exists,;t t +s,@cf_ada_make@,$cf_ada_make,;t t +s,@cf_ada_config@,$cf_ada_config,;t t +s,@cf_ada_config_Ada@,$cf_ada_config_Ada,;t t +s,@cf_ada_config_C@,$cf_ada_config_C,;t t +s,@cf_cv_path_gnatgcc@,$cf_cv_path_gnatgcc,;t t s,@CC@,$CC,;t t s,@CFLAGS@,$CFLAGS,;t t s,@LDFLAGS@,$LDFLAGS,;t t @@ -18932,6 +20180,8 @@ s,@INSTALL_PROGRAM@,$INSTALL_PROGRAM,;t t s,@INSTALL_SCRIPT@,$INSTALL_SCRIPT,;t t s,@INSTALL_DATA@,$INSTALL_DATA,;t t s,@LN_S@,$LN_S,;t t +s,@GLOB_FULLPATH_POSIX@,$GLOB_FULLPATH_POSIX,;t t +s,@GLOB_FULLPATH_OTHER@,$GLOB_FULLPATH_OTHER,;t t s,@INSTALL_OPT_S@,$INSTALL_OPT_S,;t t s,@INSTALL_OPT_O@,$INSTALL_OPT_O,;t t s,@PKG_CONFIG@,$PKG_CONFIG,;t t @@ -18944,7 +20194,6 @@ s,@CTAGS@,$CTAGS,;t t s,@ETAGS@,$ETAGS,;t t s,@MAKE_LOWER_TAGS@,$MAKE_LOWER_TAGS,;t t s,@MAKE_UPPER_TAGS@,$MAKE_UPPER_TAGS,;t t -s,@cf_cv_makeflags@,$cf_cv_makeflags,;t t s,@RANLIB@,$RANLIB,;t t s,@ac_ct_RANLIB@,$ac_ct_RANLIB,;t t s,@LD@,$LD,;t t @@ -18953,6 +20202,8 @@ s,@AR@,$AR,;t t s,@ac_ct_AR@,$ac_ct_AR,;t t s,@ARFLAGS@,$ARFLAGS,;t t s,@DESTDIR@,$DESTDIR,;t t +s,@SET_DESTDIR@,$SET_DESTDIR,;t t +s,@MERGE_PREFIX@,$MERGE_PREFIX,;t t s,@BUILD_CC@,$BUILD_CC,;t t s,@BUILD_CPP@,$BUILD_CPP,;t t s,@BUILD_CFLAGS@,$BUILD_CFLAGS,;t t @@ -18963,16 +20214,16 @@ s,@BUILD_EXEEXT@,$BUILD_EXEEXT,;t t s,@BUILD_OBJEXT@,$BUILD_OBJEXT,;t t s,@DFT_LWR_MODEL@,$DFT_LWR_MODEL,;t t s,@DFT_UPR_MODEL@,$DFT_UPR_MODEL,;t t +s,@REQUIRE_PKG@,$REQUIRE_PKG,;t t s,@NCURSES_CONFIG@,$NCURSES_CONFIG,;t t s,@ac_ct_NCURSES_CONFIG@,$ac_ct_NCURSES_CONFIG,;t t +s,@cf_cv_screen@,$cf_cv_screen,;t t s,@NCURSES_MAJOR@,$NCURSES_MAJOR,;t t s,@NCURSES_MINOR@,$NCURSES_MINOR,;t t s,@NCURSES_PATCH@,$NCURSES_PATCH,;t t s,@cf_cv_rel_version@,$cf_cv_rel_version,;t t s,@cf_cv_abi_version@,$cf_cv_abi_version,;t t -s,@cf_cv_builtin_bool@,$cf_cv_builtin_bool,;t t -s,@cf_cv_header_stdbool_h@,$cf_cv_header_stdbool_h,;t t -s,@cf_cv_type_of_bool@,$cf_cv_type_of_bool,;t t +s,@cf_cv_enable_sigwinch@,$cf_cv_enable_sigwinch,;t t s,@LIB_PREFIX@,$LIB_PREFIX,;t t s,@LIB_SUFFIX@,$LIB_SUFFIX,;t t s,@CC_G_OPT@,$CC_G_OPT,;t t @@ -19007,12 +20258,6 @@ s,@HAVE_STDNORETURN_H@,$HAVE_STDNORETURN_H,;t t s,@STDC_NORETURN@,$STDC_NORETURN,;t t s,@ADAFLAGS@,$ADAFLAGS,;t t s,@ADA_TRACE@,$ADA_TRACE,;t t -s,@cf_TEMP_gnat@,$cf_TEMP_gnat,;t t -s,@M4_exists@,$M4_exists,;t t -s,@cf_ada_make@,$cf_ada_make,;t t -s,@cf_ada_config@,$cf_ada_config,;t t -s,@cf_ada_config_Ada@,$cf_ada_config_Ada,;t t -s,@cf_ada_config_C@,$cf_ada_config_C,;t t s,@GNATPREP_OPTS@,$GNATPREP_OPTS,;t t s,@cf_compile_generics@,$cf_compile_generics,;t t s,@cf_generic_objects@,$cf_generic_objects,;t t @@ -19036,7 +20281,7 @@ s,@DFT_ARG_SUFFIX@,$DFT_ARG_SUFFIX,;t t s,@DFT_DEP_SUFFIX@,$DFT_DEP_SUFFIX,;t t s,@DFT_OBJ_SUBDIR@,$DFT_OBJ_SUBDIR,;t t s,@USE_ARG_SUFFIX@,$USE_ARG_SUFFIX,;t t -s,@USE_LIB_SUFFIX@,$USE_LIB_SUFFIX,;t t +s,@ABI_SUFFIX@,$ABI_SUFFIX,;t t s,@USE_CFG_SUFFIX@,$USE_CFG_SUFFIX,;t t s,@TEST_ARG2@,$TEST_ARG2,;t t s,@TEST_LIBS2@,$TEST_LIBS2,;t t @@ -19073,14 +20318,14 @@ EOF # is no need to browse any of the substitutions). # These are the two extra sed commands mentioned above. (echo ':t - /@[a-zA-Z_][a-zA-Z_0-9]*@/!b' && cat "$tmp"/subs.frag) >"$tmp"/subs-$ac_sed_frag.sed + /@[a-zA-Z_][a-zA-Z_0-9]*@/!b' && sed -e 's/\\\\*$//g' -e 's/$/\\/' -e 's/;t t\\/;t t/' -e 't' -e '3,'$ac_max_sed_lines's/$/\\/' "$tmp"/subs.frag) >"$tmp"/subs-$ac_sed_frag.sed # It is possible to make a multiline substitution using escaped newlines. # Ensure that we do not split the substitution between script fragments. ac_BEG=$ac_end ac_END=`expr "$ac_end" + "$ac_max_sed_lines"` sed "1,${ac_BEG}d; ${ac_END}p; q" "$tmp"/subs.sed >"$tmp"/subs.next if test -s "$tmp"/subs.next; then - grep '^s,@[^@,][^@,]*@,.*\\$' "$tmp"/subs.next >"$tmp"/subs.edit + grep '^s,@[^@,][^@,]*@,.*$' "$tmp"/subs.next | grep -v '^s,@.*;t t$' >"$tmp"/subs.edit if test ! -s "$tmp"/subs.edit; then grep "^s,@[^@,][^@,]*@,.*,;t t$" "$tmp"/subs.next >"$tmp"/subs.edit if test ! -s "$tmp"/subs.edit; then @@ -19178,7 +20423,7 @@ done; } esac if test x"$ac_file" != x-; then - { echo "$as_me:19181: creating $ac_file" >&5 + { echo "$as_me:20426: creating $ac_file" >&5 echo "$as_me: creating $ac_file" >&6;} rm -f "$ac_file" fi @@ -19196,7 +20441,7 @@ echo "$as_me: creating $ac_file" >&6;} -) echo "$tmp"/stdin ;; [\\/$]*) # Absolute (can't be DOS-style, as IFS=:) - test -f "$f" || { { echo "$as_me:19199: error: cannot find input file: $f" >&5 + test -f "$f" || { { echo "$as_me:20444: error: cannot find input file: $f" >&5 echo "$as_me: error: cannot find input file: $f" >&2;} { (exit 1); exit 1; }; } echo "$f";; @@ -19209,7 +20454,7 @@ echo "$as_me: error: cannot find input file: $f" >&2;} echo "$srcdir/$f" else # /dev/null tree - { { echo "$as_me:19212: error: cannot find input file: $f" >&5 + { { echo "$as_me:20457: error: cannot find input file: $f" >&5 echo "$as_me: error: cannot find input file: $f" >&2;} { (exit 1); exit 1; }; } fi;; @@ -19225,7 +20470,7 @@ cat >>"$CONFIG_STATUS" <<\EOF if test -n "$ac_seen"; then ac_used=`grep '@datarootdir@' "$ac_item"` if test -z "$ac_used"; then - { echo "$as_me:19228: WARNING: datarootdir was used implicitly but not set: + { echo "$as_me:20473: WARNING: datarootdir was used implicitly but not set: $ac_seen" >&5 echo "$as_me: WARNING: datarootdir was used implicitly but not set: $ac_seen" >&2;} @@ -19234,7 +20479,7 @@ $ac_seen" >&2;} fi ac_seen=`grep '${datarootdir}' "$ac_item"` if test -n "$ac_seen"; then - { echo "$as_me:19237: WARNING: datarootdir was used explicitly but not set: + { echo "$as_me:20482: WARNING: datarootdir was used explicitly but not set: $ac_seen" >&5 echo "$as_me: WARNING: datarootdir was used explicitly but not set: $ac_seen" >&2;} @@ -19279,7 +20524,7 @@ cat >>"$CONFIG_STATUS" <<\EOF ac_init=`$EGREP '[ ]*'$ac_name'[ ]*=' "$ac_file"` if test -z "$ac_init"; then ac_seen=`echo "$ac_seen" |sed -e 's,^,'"$ac_file"':,'` - { echo "$as_me:19282: WARNING: Variable $ac_name is used but was not set: + { echo "$as_me:20527: WARNING: Variable $ac_name is used but was not set: $ac_seen" >&5 echo "$as_me: WARNING: Variable $ac_name is used but was not set: $ac_seen" >&2;} @@ -19290,7 +20535,7 @@ $ac_seen" >&2;} $EGREP -n '@[A-Z_][A-Z_0-9]+@' "$ac_file" >>"$tmp"/out if test -s "$tmp"/out; then ac_seen=`sed -e 's,^,'"$ac_file"':,' < "$tmp"/out` - { echo "$as_me:19293: WARNING: Some variables may not be substituted: + { echo "$as_me:20538: WARNING: Some variables may not be substituted: $ac_seen" >&5 echo "$as_me: WARNING: Some variables may not be substituted: $ac_seen" >&2;} @@ -19339,7 +20584,7 @@ for ac_file in : $CONFIG_HEADERS; do test "x$ac_file" = x: && continue * ) ac_file_in=$ac_file.in ;; esac - test x"$ac_file" != x- && { echo "$as_me:19342: creating $ac_file" >&5 + test x"$ac_file" != x- && { echo "$as_me:20587: creating $ac_file" >&5 echo "$as_me: creating $ac_file" >&6;} # First look for the input files in the build tree, otherwise in the @@ -19350,7 +20595,7 @@ echo "$as_me: creating $ac_file" >&6;} -) echo "$tmp"/stdin ;; [\\/$]*) # Absolute (can't be DOS-style, as IFS=:) - test -f "$f" || { { echo "$as_me:19353: error: cannot find input file: $f" >&5 + test -f "$f" || { { echo "$as_me:20598: error: cannot find input file: $f" >&5 echo "$as_me: error: cannot find input file: $f" >&2;} { (exit 1); exit 1; }; } echo $f;; @@ -19363,7 +20608,7 @@ echo "$as_me: error: cannot find input file: $f" >&2;} echo "$srcdir/$f" else # /dev/null tree - { { echo "$as_me:19366: error: cannot find input file: $f" >&5 + { { echo "$as_me:20611: error: cannot find input file: $f" >&5 echo "$as_me: error: cannot find input file: $f" >&2;} { (exit 1); exit 1; }; } fi;; @@ -19421,7 +20666,7 @@ cat >>"$CONFIG_STATUS" <<\EOF rm -f "$tmp"/in if test x"$ac_file" != x-; then if cmp -s "$ac_file" "$tmp/config.h" 2>/dev/null; then - { echo "$as_me:19424: $ac_file is unchanged" >&5 + { echo "$as_me:20669: $ac_file is unchanged" >&5 echo "$as_me: $ac_file is unchanged" >&6;} else ac_dir=`$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \ @@ -19505,4 +20750,5 @@ if test "$no_create" != yes; then # would make configure fail if this is the last instruction. "$ac_cs_success" || { (exit 1); exit 1; } fi + ${MAKE:-make} preinstall diff --git a/Ada95/configure.in b/Ada95/configure.in index 3384df2..646924d 100644 --- a/Ada95/configure.in +++ b/Ada95/configure.in @@ -1,5 +1,5 @@ dnl*************************************************************************** -dnl Copyright 2018-2022,2023 Thomas E. Dickey * +dnl Copyright 2018-2024,2025 Thomas E. Dickey * dnl Copyright 2010-2016,2018 Free Software Foundation, Inc. * dnl * dnl Permission is hereby granted, free of charge, to any person obtaining a * @@ -29,7 +29,7 @@ dnl*************************************************************************** dnl dnl Author: Thomas E. Dickey dnl -dnl $Id: configure.in,v 1.91 2023/02/18 23:21:29 tom Exp $ +dnl $Id: configure.in,v 1.97 2025/12/25 23:49:07 tom Exp $ dnl Process this file with autoconf to produce a configure script. dnl dnl For additional information, see @@ -38,9 +38,10 @@ dnl https://invisible-island.net/autoconf/my-autoconf.html dnl dnl --------------------------------------------------------------------------- AC_PREREQ(2.52.20210509) -AC_REVISION($Revision: 1.91 $) -AC_INIT(gen/gen.c) -AC_CONFIG_HEADER(include/ncurses_cfg.h:include/ncurses_cfg.hin) +AC_REVISION($Revision: 1.97 $) +AC_INIT +AC_CONFIG_SRCDIR([gen/gen.c]) +AC_CONFIG_HEADERS([include/ncurses_cfg.h:include/ncurses_cfg.hin]) AC_DEFUN([AC_PATH_XTRA],[])dnl ignore dependencies on this @@ -59,7 +60,7 @@ cf_user_CFLAGS="$CFLAGS" CF_CFG_DEFAULTS ### Checks for programs. -CF_PROG_CC(gnatgcc gcc cc) +CF_WITH_ADA AC_PROG_CPP AC_PROG_GCC_TRADITIONAL CF_PROG_CC_C_O(CC,[$CFLAGS $CPPFLAGS]) @@ -106,7 +107,6 @@ fi AC_PROG_MAKE_SET CF_MAKE_PHONY CF_MAKE_TAGS -CF_MAKEFLAGS dnl These are standard among *NIX systems, but not when cross-compiling AC_CHECK_TOOL(RANLIB, ranlib, ':') @@ -115,20 +115,7 @@ AC_CHECK_TOOL(AR, ar, ar) CF_AR_FLAGS CF_PATHSEP -dnl Special option for use by system-builders: the install-prefix is used to -dnl adjust the location into which the actual install is done, so that an -dnl archive can be built without modifying the host system's configuration. -AC_MSG_CHECKING(if you have specified an install-prefix) -AC_ARG_WITH(install-prefix, - [ --with-install-prefix prefixes actual install-location ($DESTDIR)], - [case "$withval" in - (yes|no) - ;; - (*) DESTDIR="$withval" - ;; - esac]) -AC_MSG_RESULT($DESTDIR) -AC_SUBST(DESTDIR) +CF_INSTALL_PREFIX ############################################################################### CF_HELP_MESSAGE(Build-Tools Needed to Compile Temporary Applications for Cross-compiling:) @@ -410,7 +397,7 @@ AC_MSG_RESULT($cf_with_trace) if test "$cf_with_trace" = yes ; then ADA_TRACE=TRUE - CF_ADD_CFLAGS(-DTRACE) + AC_DEFINE(TRACE,1,[Define to 1 if we have support trace functions]) else ADA_TRACE=FALSE fi @@ -435,7 +422,7 @@ AC_HEADER_DIRENT AC_HEADER_TIME ### checks for compiler characteristics -AC_LANG_C +AC_LANG([C]) AC_C_CONST ### Checks for external-data @@ -455,7 +442,6 @@ cf_with_ada=yes dnl Check for availability of GNU Ada Translator (GNAT). dnl At the moment we support no other Ada95 compiler. if test "$cf_with_ada" != "no" ; then - CF_PROG_GNAT if test "$cf_cv_prog_gnat_correct" = yes; then CF_FIXUP_ADAFLAGS @@ -527,8 +513,8 @@ fi USE_ARG_SUFFIX=${DFT_ARG_SUFFIX} AC_SUBST(USE_ARG_SUFFIX) -USE_LIB_SUFFIX=${DFT_ARG_SUFFIX} -AC_SUBST(USE_LIB_SUFFIX) +ABI_SUFFIX=${DFT_ARG_SUFFIX} +AC_SUBST(ABI_SUFFIX) USE_CFG_SUFFIX=${DFT_ARG_SUFFIX} AC_SUBST(USE_CFG_SUFFIX) @@ -580,11 +566,12 @@ fi AC_SUBST(ADAGEN_LDFLAGS) -AC_OUTPUT( \ +AC_CONFIG_FILES([\ $SUB_MAKEFILES \ src/library.gpr:src/library.gpr.in \ doc/adacurses${DFT_ARG_SUFFIX}-config.1:doc/MKada_config.in \ - Makefile,[ + Makefile]) +AC_CONFIG_COMMANDS([default],[ $AWK -v PACKAGE=$PACKAGE -f $srcdir/mk-pkg.awk > Makefile if test -z "$USE_OLD_MAKERULES" ; then $AWK -f $srcdir/mk-1st.awk <$srcdir/src/modules >>src/Makefile @@ -617,5 +604,7 @@ cf_cv_system_name="$cf_cv_system_name" host="$host" target="$target" -],cat)dnl +]) +AC_SETUP_DEFS([cat]) +AC_OUTPUT ${MAKE:-make} preinstall diff --git a/Ada95/doc/Makefile.in b/Ada95/doc/Makefile.in index 0aed33f..27b1af7 100644 --- a/Ada95/doc/Makefile.in +++ b/Ada95/doc/Makefile.in @@ -1,6 +1,6 @@ -# $Id: Makefile.in,v 1.9 2021/07/03 15:45:33 tom Exp $ +# $Id: Makefile.in,v 1.11 2025/10/18 16:08:08 tom Exp $ ############################################################################## -# Copyright 2019-2020,2021 Thomas E. Dickey # +# Copyright 2019-2024,2025 Thomas E. Dickey # # Copyright 2011-2015,2018 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -35,7 +35,7 @@ SHELL = @SHELL@ VPATH = @srcdir@ -DESTDIR = @DESTDIR@ +@SET_DESTDIR@ srcdir = @srcdir@ prefix = @prefix@ exec_prefix = @exec_prefix@ @@ -49,8 +49,8 @@ INSTALL_DATA = @INSTALL_DATA@ DFT_ARG_SUFFIX = @DFT_ARG_SUFFIX@ THIS = @ADA_LIBNAME@ -DOCDIR = $(DESTDIR)$(datadir)/doc/$(THIS) -MANDIR = $(DESTDIR)$(mandir)/man1 +DOCDIR = $(DESTDIR)$(datadir@MERGE_PREFIX@)/doc/$(THIS) +MANDIR = $(DESTDIR)$(mandir@MERGE_PREFIX@)/man1 ################################################################################ diff --git a/Ada95/gen/Makefile.in b/Ada95/gen/Makefile.in index 525ce99..7045ac9 100644 --- a/Ada95/gen/Makefile.in +++ b/Ada95/gen/Makefile.in @@ -1,5 +1,5 @@ ############################################################################## -# Copyright 2019-2022,2024 Thomas E. Dickey # +# Copyright 2019-2024,2025 Thomas E. Dickey # # Copyright 1998-2015,2018 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -30,7 +30,7 @@ # Author: Juergen Pfeifer, 1996 # and: Thomas E. Dickey, 1997 # -# $Id: Makefile.in,v 1.103 2024/01/19 16:51:56 tom Exp $ +# $Id: Makefile.in,v 1.109 2025/10/18 22:11:58 tom Exp $ # .SUFFIXES: @@ -38,16 +38,19 @@ SHELL = @SHELL@ VPATH = @srcdir@ THIS = Makefile +@SET_DESTDIR@ + x = @EXEEXT@ top_srcdir = @top_srcdir@ -DESTDIR = @DESTDIR@ srcdir = @srcdir@ prefix = @prefix@ exec_prefix = @exec_prefix@ bindir = @bindir@ includedir = @includedir@ +BINDIR = $(DESTDIR)$(bindir@MERGE_PREFIX@) + INSTALL = @INSTALL@ @INSTALL_OPT_O@ INSTALL_SCRIPT = @INSTALL_SCRIPT@ INSTALL_DATA = @INSTALL_DATA@ @@ -111,36 +114,37 @@ ABASE = $(ALIB)-curses ADA_SRCDIR = ../src -GEN_TARGETS = $(ADA_SRCDIR)/$(ABASE).ads \ - $(ADA_SRCDIR)/$(ABASE).adb \ - $(ADA_SRCDIR)/$(ABASE)-aux.ads \ - $(ADA_SRCDIR)/$(ABASE)-trace.ads \ - $(ADA_SRCDIR)/$(ABASE)-menus.ads \ - $(ADA_SRCDIR)/$(ABASE)-forms.ads \ - $(ADA_SRCDIR)/$(ABASE)-mouse.ads \ - $(ADA_SRCDIR)/$(ABASE)-panels.ads \ - $(ADA_SRCDIR)/$(ABASE)-menus-menu_user_data.ads \ - $(ADA_SRCDIR)/$(ABASE)-menus-item_user_data.ads \ - $(ADA_SRCDIR)/$(ABASE)-forms-form_user_data.ads \ - $(ADA_SRCDIR)/$(ABASE)-forms-field_types.ads \ - $(ADA_SRCDIR)/$(ABASE)-forms-field_user_data.ads \ - $(ADA_SRCDIR)/$(ABASE)-panels-user_data.ads \ - $(ADA_SRCDIR)/$(ABASE)_constants.ads +GEN_TARGETS = options.m4 \ + $(ADA_SRCDIR)/$(ABASE).ads \ + $(ADA_SRCDIR)/$(ABASE).adb \ + $(ADA_SRCDIR)/$(ABASE)-aux.ads \ + $(ADA_SRCDIR)/$(ABASE)-trace.ads \ + $(ADA_SRCDIR)/$(ABASE)-menus.ads \ + $(ADA_SRCDIR)/$(ABASE)-forms.ads \ + $(ADA_SRCDIR)/$(ABASE)-mouse.ads \ + $(ADA_SRCDIR)/$(ABASE)-panels.ads \ + $(ADA_SRCDIR)/$(ABASE)-menus-menu_user_data.ads \ + $(ADA_SRCDIR)/$(ABASE)-menus-item_user_data.ads \ + $(ADA_SRCDIR)/$(ABASE)-forms-form_user_data.ads \ + $(ADA_SRCDIR)/$(ABASE)-forms-field_types.ads \ + $(ADA_SRCDIR)/$(ABASE)-forms-field_user_data.ads \ + $(ADA_SRCDIR)/$(ABASE)-panels-user_data.ads \ + $(ADA_SRCDIR)/$(ABASE)_constants.ads GEN_SRC = $(srcdir)/$(ABASE).ads.m4 \ $(srcdir)/$(ABASE).adb.m4 \ - $(srcdir)/$(ABASE)-aux.ads.m4 \ - $(srcdir)/$(ABASE)-trace.ads.m4 \ - $(srcdir)/$(ABASE)-menus.ads.m4 \ - $(srcdir)/$(ABASE)-forms.ads.m4 \ - $(srcdir)/$(ABASE)-mouse.ads.m4 \ - $(srcdir)/$(ABASE)-panels.ads.m4 \ - $(srcdir)/$(ABASE)-menus-menu_user_data.ads.m4 \ - $(srcdir)/$(ABASE)-menus-item_user_data.ads.m4 \ - $(srcdir)/$(ABASE)-forms-form_user_data.ads.m4 \ - $(srcdir)/$(ABASE)-forms-field_types.ads.m4 \ - $(srcdir)/$(ABASE)-forms-field_user_data.ads.m4 \ - $(srcdir)/$(ABASE)-panels-user_data.ads.m4 + $(srcdir)/$(ABASE)-aux.ads.m4 \ + $(srcdir)/$(ABASE)-trace.ads.m4 \ + $(srcdir)/$(ABASE)-menus.ads.m4 \ + $(srcdir)/$(ABASE)-forms.ads.m4 \ + $(srcdir)/$(ABASE)-mouse.ads.m4 \ + $(srcdir)/$(ABASE)-panels.ads.m4 \ + $(srcdir)/$(ABASE)-menus-menu_user_data.ads.m4 \ + $(srcdir)/$(ABASE)-menus-item_user_data.ads.m4 \ + $(srcdir)/$(ABASE)-forms-form_user_data.ads.m4 \ + $(srcdir)/$(ABASE)-forms-field_types.ads.m4 \ + $(srcdir)/$(ABASE)-forms-field_user_data.ads.m4 \ + $(srcdir)/$(ABASE)-panels-user_data.ads.m4 ################################################################################ @@ -162,19 +166,24 @@ libs : $(GEN_TARGETS) sources: -$(DESTDIR)$(bindir) : +$(BINDIR) : mkdir -p $@ install \ -install.libs :: $(DESTDIR)$(bindir) $(ADACURSES_CONFIG) - $(INSTALL_SCRIPT) $(ADACURSES_CONFIG) $(DESTDIR)$(bindir)/$(ADACURSES_CONFIG) +install.libs :: \ + $(GEN_TARGETS) \ + $(BINDIR) \ + $(ADACURSES_CONFIG) + $(INSTALL_SCRIPT) $(ADACURSES_CONFIG) $(BINDIR)/$(ADACURSES_CONFIG) uninstall \ uninstall.libs :: - -rm -f $(DESTDIR)$(bindir)/$(ADACURSES_CONFIG) + -rm -f $(BINDIR)/$(ADACURSES_CONFIG) $(PROG_GENERATE): gen.o @ECHO_LD@ $(LINK) $(CFLAGS_NORMAL) gen.o $(ACTUAL_LDFLAGS) -o $@ + @$(PROG_GENERATE) "-?" + @echo "... made $@" gen.o: $(srcdir)/gen.c $(HOST_CC) $(CFLAGS_NORMAL) -c -o $@ $(srcdir)/gen.c diff --git a/Ada95/gen/adacurses-config.in b/Ada95/gen/adacurses-config.in index a539417..742e9c6 100644 --- a/Ada95/gen/adacurses-config.in +++ b/Ada95/gen/adacurses-config.in @@ -1,7 +1,7 @@ #! /bin/sh -# $Id: adacurses-config.in,v 1.15 2022/07/16 21:16:43 tom Exp $ +# $Id: adacurses-config.in,v 1.17 2025/11/12 00:56:49 Branden.Robinson Exp $ ############################################################################## -# Copyright 2019-2020,2022 Thomas E. Dickey # +# Copyright 2019-2022,2025 Thomas E. Dickey # # Copyright 2007-2014,2016 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -31,7 +31,7 @@ # # This script returns the options to add to `gnatmake' for using AdaCurses. -DESTDIR=@DESTDIR@ +: "${@SET_DESTDIR@}" prefix=@prefix@ exec_prefix=@exec_prefix@ libdir=@libdir@ @@ -66,14 +66,14 @@ case "x$1" in Usage: ${THIS_CFG} [options] Options: - --cflags echos the gnat (Ada compiler) flags needed to compile with ${THIS} - --libs echos the gnat libraries needed to link with ${THIS} + --cflags echoes the gnat (Ada compiler) flags needed to compile with ${THIS} + --libs echoes the gnat libraries needed to link with ${THIS} - --version echos the release+patchdate version of ${THIS} + --version echoes the release+patchdate version of ${THIS} --help prints this message -If no options are given, echos the full set of flags needed by gnatmake. +If no options are given, echoes the full set of flags needed by gnatmake. ENDHELP ;; *) diff --git a/Ada95/gen/gen.c b/Ada95/gen/gen.c index b37de1b..21f54a5 100644 --- a/Ada95/gen/gen.c +++ b/Ada95/gen/gen.c @@ -1,5 +1,5 @@ /**************************************************************************** - * Copyright 2020-2021,2024 Thomas E. Dickey * + * Copyright 2020-2024,2025 Thomas E. Dickey * * Copyright 1998-2014,2016 Free Software Foundation, Inc. * * * * Permission is hereby granted, free of charge, to any person obtaining a * @@ -35,7 +35,7 @@ /* Version Control - $Id: gen.c,v 1.79 2024/01/19 13:41:45 tom Exp $ + $Id: gen.c,v 1.84 2025/11/12 00:49:19 Branden.Robinson Exp $ --------------------------------------------------------------------------*/ /* This program prints on its standard output the source for the @@ -189,7 +189,7 @@ find_pos(const UCHAR * const data, int main(int argc, const char *argv[]) { - FILE *fp = 0; + FILE *fp = NULL; const int x = 0x12345678; little_endian = (*((const char *)&x) == 0x78); @@ -203,6 +203,10 @@ main(int argc, const char *argv[]) { fp = fopen(argv[2], "wb"); } + else if (argc == 2 && !strcmp(argv[1], "-?")) + { + return EXIT_SUCCESS; + } else if (argc == 2) { fp = stdout; @@ -301,7 +305,7 @@ main(int argc, const char *argv[]) PRINT_NAMED_CONSTANT(E_INVALID_FIELD); PRINT_NAMED_CONSTANT(E_CURRENT); - print_comment(fp, "Input key codes not defined in any ncurses manpage"); + print_comment(fp, "Input key codes not defined in any ncurses man page"); PRINT_NAMED_CONSTANT(KEY_MIN); PRINT_NAMED_CONSTANT(KEY_MAX); #ifdef KEY_CODE_YES diff --git a/Ada95/include/Makefile.in b/Ada95/include/Makefile.in index 89bb27d..1bb1aa6 100644 --- a/Ada95/include/Makefile.in +++ b/Ada95/include/Makefile.in @@ -1,6 +1,6 @@ -# $Id: Makefile.in,v 1.7 2021/07/03 15:45:33 tom Exp $ +# $Id: Makefile.in,v 1.8 2025/10/18 15:23:07 tom Exp $ ############################################################################## -# Copyright 2020,2021 Thomas E. Dickey # +# Copyright 2020-2021,2025 Thomas E. Dickey # # Copyright 2010-2015,2018 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -44,7 +44,8 @@ SHELL = @SHELL@ VPATH = @srcdir@ THIS = Makefile -DESTDIR = @DESTDIR@ +@SET_DESTDIR@ + srcdir = @srcdir@ prefix = @prefix@ exec_prefix = @exec_prefix@ diff --git a/Ada95/include/ncurses_cfg.hin b/Ada95/include/ncurses_cfg.hin index f8bcb66..c19ac8a 100644 --- a/Ada95/include/ncurses_cfg.hin +++ b/Ada95/include/ncurses_cfg.hin @@ -1,5 +1,5 @@ /**************************************************************************** - * Copyright 2020 Thomas E. Dickey * + * Copyright 2020,2024 Thomas E. Dickey * * Copyright 2005-2017,2018 Free Software Foundation, Inc. * * * * Permission is hereby granted, free of charge, to any person obtaining a * @@ -31,7 +31,7 @@ * Author: Thomas E. Dickey 1997 * ****************************************************************************/ /* - * $Id: ncurses_cfg.hin,v 1.11 2020/02/02 23:34:34 tom Exp $ + * $Id: ncurses_cfg.hin,v 1.13 2024/06/08 14:04:14 tom Exp $ * * This is a template-file used to generate the "ncurses_cfg.h" file. * @@ -41,7 +41,7 @@ * * See: * https://invisible-island.net/autoconf/ - * ftp://ftp.invisible-island.net/autoconf/ + * https://invisible-island.net/archives/autoconf/ */ #ifndef NC_CONFIG_H #define NC_CONFIG_H diff --git a/Ada95/make-tar.sh b/Ada95/make-tar.sh index 083812d..a964150 100755 --- a/Ada95/make-tar.sh +++ b/Ada95/make-tar.sh @@ -1,7 +1,7 @@ #!/bin/sh -# $Id: make-tar.sh,v 1.23 2022/11/05 20:29:41 tom Exp $ +# $Id: make-tar.sh,v 1.26 2025/06/20 19:42:53 tom Exp $ ############################################################################## -# Copyright 2019-2021,2022 Thomas E. Dickey # +# Copyright 2019-2022,2025 Thomas E. Dickey # # Copyright 2010-2015,2017 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -44,6 +44,7 @@ TARGET=`pwd` # make timestamps of generated files predictable same_timestamp() { + [ -f ../NEWS ] || echo "OOPS $1" touch -r ../NEWS "$1" } @@ -61,10 +62,12 @@ grep_patchdate() { # The rpm spec-file in the ncurses tree is a template. Fill in the version # information from dist.mk edit_specfile() { + RPM_DATE=`date +'%a %b %d %Y' -d "$NCURSES_PATCH"` sed \ -e "s/\\/$NCURSES_MAJOR/g" \ -e "s/\\/$NCURSES_MINOR/g" \ - -e "s/\\/$NCURSES_PATCH/g" "$1" >"$1.new" + -e "s/\\/$NCURSES_PATCH/g" \ + -e "s/\\/$RPM_DATE/g" "$1" >"$1.new" chmod u+w "$1" mv "$1.new" "$1" same_timestamp "$1" @@ -73,7 +76,7 @@ edit_specfile() { make_changelog() { [ -f "$1" ] && chmod u+w "$1" cat >"$1" <MANIFEST ) -same_timestamp $BUILD/$ROOTNAME/MANIFEST +touch "$BUILD/$ROOTNAME"/MANIFEST +( cd "$BUILD/$ROOTNAME" && find . -type f -print | "$SOURCE/misc/csort" >MANIFEST ) +same_timestamp "$BUILD/$ROOTNAME"/MANIFEST -cd $BUILD || exit +cd "$BUILD" || exit # Remove build-artifacts. find . -name RCS -exec rm -rf {} \; -find $BUILD/$ROOTNAME -type d -exec rmdir {} \; 2>/dev/null -find $BUILD/$ROOTNAME -type d -exec rmdir {} \; 2>/dev/null -find $BUILD/$ROOTNAME -type d -exec rmdir {} \; 2>/dev/null +find "$BUILD/$ROOTNAME" -type d -exec rmdir {} \; 2>/dev/null +find "$BUILD/$ROOTNAME" -type d -exec rmdir {} \; 2>/dev/null +find "$BUILD/$ROOTNAME" -type d -exec rmdir {} \; 2>/dev/null # There is no need for this script in the tar file. -rm -f $ROOTNAME/make-tar.sh +rm -f "$ROOTNAME"/make-tar.sh # Remove build-artifacts. find . -name "*.gz" -exec rm -rf {} \; @@ -165,10 +168,10 @@ chmod -R u+w . # Cleanup timestamps [ -n "$TOUCH_DIRS" ] && "$TOUCH_DIRS" "$ROOTNAME" -tar cf - $TAR_OPTIONS $ROOTNAME | gzip >"$DESTDIR/$ROOTNAME.tar.gz" +tar cf - $TAR_OPTIONS "$ROOTNAME" | gzip >"$DESTDIR/$ROOTNAME.tar.gz" cd "$DESTDIR" || exit pwd -ls -l $ROOTNAME.tar.gz +ls -l "$ROOTNAME".tar.gz # vi:ts=4 sw=4 diff --git a/Ada95/package/AdaCurses-doc.spec b/Ada95/package/AdaCurses-doc.spec index c5b68dd..a5aee9c 100644 --- a/Ada95/package/AdaCurses-doc.spec +++ b/Ada95/package/AdaCurses-doc.spec @@ -3,13 +3,13 @@ Summary: AdaCurses - Ada95 binding documentation for ncurses %define AppVersion MAJOR.MINOR %define AppRelease YYYYMMDD %define AppPackage %{AppProgram}-doc -# $Id: AdaCurses-doc.spec,v 1.7 2019/11/23 21:15:53 tom Exp $ +# $Id: AdaCurses-doc.spec,v 1.10 2025/06/21 18:34:55 tom Exp $ Name: %{AppPackage} Version: %{AppVersion} Release: %{AppRelease} -License: MIT +License: X11 License Distribution Modification Variant Group: Applications/Development -URL: ftp://ftp.invisible-island.net/%{AppProgram} +URL: https://invisible-island.net/%{AppProgram} Source0: %{AppProgram}-%{AppRelease}.tgz Packager: Thomas Dickey @@ -51,6 +51,9 @@ exit 0 %changelog # each patch should add its ChangeLog entries here +* RPM_DATE Thomas Dickey +- testing ncurses MAJOR.MINOR.YYYYMMDD + * Sat Nov 16 2019 Thomas Dickey - modify clean-rule to work around Fedora NFS bugs. diff --git a/Ada95/package/AdaCurses.spec b/Ada95/package/AdaCurses.spec index 540e8e5..64e9a19 100644 --- a/Ada95/package/AdaCurses.spec +++ b/Ada95/package/AdaCurses.spec @@ -2,13 +2,13 @@ Summary: Ada95 binding for ncurses %define AppProgram AdaCurses %define AppVersion MAJOR.MINOR %define AppRelease YYYYMMDD -# $Id: AdaCurses.spec,v 1.31 2022/12/18 00:08:17 tom Exp $ +# $Id: AdaCurses.spec,v 1.36 2025/06/21 18:34:55 tom Exp $ Name: %{AppProgram} Version: %{AppVersion} Release: %{AppRelease} -License: MIT +License: X11 License Distribution Modification Variant Group: Applications/Development -URL: ftp://ftp.invisible-island.net/%{AppProgram} +URL: https://invisible-island.net/%{AppProgram} Source0: %{AppProgram}-%{AppRelease}.tgz Packager: Thomas Dickey @@ -69,6 +69,7 @@ INSTALL_PROGRAM='${INSTALL}' \ --disable-rpath-link \ --disable-echo \ --verbose \ + --with-screen=ncursesw6dev \ --enable-warnings make @@ -106,6 +107,9 @@ exit 0 %changelog # each patch should add its ChangeLog entries here +* RPM_DATE Thomas Dickey +- testing ncurses MAJOR.MINOR.YYYYMMDD + * Sat Dec 17 2022 Thomas Dickey - install sample programs in libexec diff --git a/Ada95/package/debian/adacurses.lintian-overrides b/Ada95/package/debian/adacurses.lintian-overrides new file mode 100644 index 0000000..1e4bd36 --- /dev/null +++ b/Ada95/package/debian/adacurses.lintian-overrides @@ -0,0 +1,4 @@ +# $Id: adacurses.lintian-overrides,v 1.1 2025/06/14 19:16:06 tom Exp $ + +# dh_fixperms sets *.ali to 444, but lintian disagrees +non-standard-file-perm 0444 != 0644 [usr/lib/ada/adalib/*.ali] diff --git a/package/debian/ncurses6.triggers b/Ada95/package/debian/adacurses.triggers similarity index 100% rename from package/debian/ncurses6.triggers rename to Ada95/package/debian/adacurses.triggers diff --git a/Ada95/package/debian/control b/Ada95/package/debian/control index 1a9aefd..81b2216 100644 --- a/Ada95/package/debian/control +++ b/Ada95/package/debian/control @@ -3,9 +3,10 @@ Maintainer: Thomas E. Dickey Section: misc Priority: optional Build-Depends: debhelper (>= 5), + chrpath, gnat, gprbuild -Homepage: https://invisible-island.net/adacurses/ +Homepage: https://invisible-island.net/ncurses/ncurses-Ada95.html Standards-Version: 4.6.1.0 Package: adacurses diff --git a/Ada95/package/debian/copyright b/Ada95/package/debian/copyright index b406015..3acd2d0 100644 --- a/Ada95/package/debian/copyright +++ b/Ada95/package/debian/copyright @@ -1,79 +1,60 @@ -Upstream source https://invisible-island.net/ncurses/Ada95.html +Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Upstream-Name: AdaCurses +Upstream-Contact: Thomas E. Dickey +Source: https://invisible-island.net/ncurses/Ada95.html -Current ncurses maintainer: Thomas Dickey - -------------------------------------------------------------------------------- Files: * -Copyright: 2017-2023,2024 by Thomas E. Dickey +Copyright: 2017-2024,2025 by Thomas E. Dickey Copyright: 1998-2016,2017 Free Software Foundation, Inc. -License: X11 +License: X11 License Distribution Modification Variant + Permission is hereby granted, free of charge, to any person obtaining a + copy of this software and associated documentation files (the + "Software"), to deal in the Software without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, distribute with modifications, sublicense, and/or sell + copies of the Software, and to permit persons to whom the Software is + furnished to do so, subject to the following conditions: + . + The above copyright notice and this permission notice shall be included + in all copies or substantial portions of the Software. + . + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS + OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. + IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, + DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR + OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR + THE USE OR OTHER DEALINGS IN THE SOFTWARE. + . + Except as contained in this notice, the name(s) of the above copyright + holders shall not be used in advertising or otherwise to promote the + sale, use or other dealings in this Software without prior written + authorization. +Comment: + https://invisible-island.net/ncurses/ncurses-license.html -Files: aclocal.m4 package -Copyright: 2010-2023,2024 by Thomas E. Dickey -License: X11 - - Permission is hereby granted, free of charge, to any person obtaining a - copy of this software and associated documentation files (the - "Software"), to deal in the Software without restriction, including - without limitation the rights to use, copy, modify, merge, publish, - distribute, distribute with modifications, sublicense, and/or sell - copies of the Software, and to permit persons to whom the Software is - furnished to do so, subject to the following conditions: - - The above copyright notice and this permission notice shall be included - in all copies or substantial portions of the Software. - - THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS - OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF - MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. - IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, - DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR - OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR - THE USE OR OTHER DEALINGS IN THE SOFTWARE. - - Except as contained in this notice, the name(s) of the above copyright - holders shall not be used in advertising or otherwise to promote the - sale, use or other dealings in this Software without prior written - authorization. - -------------------------------------------------------------------------------- -Files: install-sh -Copyright: 1994 X Consortium -License: X11 - - Permission is hereby granted, free of charge, to any person obtaining a copy - of this software and associated documentation files (the "Software"), to - deal in the Software without restriction, including without limitation the - rights to use, copy, modify, merge, publish, distribute, sublicense, and/or - sell copies of the Software, and to permit persons to whom the Software is - furnished to do so, subject to the following conditions: - - The above copyright notice and this permission notice shall be included in - all copies or substantial portions of the Software. - - THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR - IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, - FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE - X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN - AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC- - TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. - - Except as contained in this notice, the name of the X Consortium shall not - be used in advertising or otherwise to promote the sale, use or other deal- - ings in this Software without prior written authorization from the X Consor- - tium. - - FSF changes to this file are in the public domain. - - Calling this script install-sh is preferred over install.sh, to prevent - `make' implicit rules from creating a file called install from it - when there is no Makefile. - - This script is compatible with the BSD install script, but was written - from scratch. It can only install one file at a time, a restriction - shared with many OS's install programs. - -On Debian systems, the complete text of the GNU General -Public License can be found in '/usr/share/common-licenses/GPL-2' - --- vile: txtmode file-encoding=utf-8 +Files: install-sh +Copyright: 1994 X Consortium +License: X11 + Permission is hereby granted, free of charge, to any person obtaining a copy + of this software and associated documentation files (the "Software"), to + deal in the Software without restriction, including without limitation the + rights to use, copy, modify, merge, publish, distribute, sublicense, and/or + sell copies of the Software, and to permit persons to whom the Software is + furnished to do so, subject to the following conditions: + . + The above copyright notice and this permission notice shall be included in + all copies or substantial portions of the Software. + . + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR + IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE + ABOVE LISTED COPYRIGHT HOLDER(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER + LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING + FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS + IN THE SOFTWARE. + . + Except as contained in this notice, the name(s) of the above copyright + holders shall not be used in advertising or otherwise to promote the sale, + use or other dealings in this Software without prior written authorization. +Comment: vile: txtmode file-encoding=utf-8 diff --git a/Ada95/package/debian/rules b/Ada95/package/debian/rules index 0adde8d..d46d6e3 100755 --- a/Ada95/package/debian/rules +++ b/Ada95/package/debian/rules @@ -1,11 +1,18 @@ #!/usr/bin/make -f -# MAde with the aid of dh_make, by Craig Small +# $Id: rules,v 1.18 2025/06/14 20:41:28 tom Exp $ +# Made with the aid of dh_make, by Craig Small # Sample debian/rules that uses debhelper. GNU copyright 1997 by Joey Hess. # Some lines taken from debmake, by Cristoph Lameter. # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +SHELL = /bin/bash +DPKG_EXPORT_BUILDFLAGS = 1 +export DEB_BUILD_MAINT_OPTIONS := hardening=+all qa=+bug reproducible=+all + +include /usr/share/dpkg/buildflags.mk + # These are used for cross-compiling and for saving the configure script # from having to guess our platform (since we know it already) DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) @@ -13,10 +20,7 @@ DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) TARGET_DIR = $(CURDIR)/debian/adacurses SAMPLE_DIR = $(TARGET_DIR)/usr/libexec/AdaCurses - -CFLAGS = $(shell dpkg-buildflags --get CFLAGS) $(CC_NORMAL) -CPPFLAGS = $(shell dpkg-buildflags --get CPPFLAGS) -LDFLAGS = $(shell dpkg-buildflags --get LDFLAGS) +OUR_LIBDIR = /usr/lib/$(DEB_HOST_GNU_TYPE) ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) CFLAGS += -O0 @@ -27,20 +31,21 @@ ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS))) INSTALL_PROGRAM += -s endif +verbose = # -v configure: configure-stamp configure-stamp: dh_testdir - CFLAGS="$(CFLAGS)" \ - CPPFLAGS="$(CPPFLAGS)" \ - LDFLAGS="$(LDFLAGS)" ./configure \ + ./configure \ --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) \ + --libdir=$(OUR_LIBDIR) \ --prefix=/usr \ --disable-rpath-link \ --with-shared \ --with-ada-sharedlib \ + --with-screen=ncursesw6td \ --without-pkg-config touch configure-stamp @@ -61,14 +66,14 @@ clean: rm -f configure-stamp build-stamp install-stamp - dh_clean + dh_clean $(verbose) install: install-stamp install-stamp: build-stamp dh_testdir dh_testroot - dh_prep - dh_installdirs + dh_prep $(verbose) + dh_installdirs $(verbose) $(MAKE) install DESTDIR=$(TARGET_DIR) @@ -76,6 +81,8 @@ install-stamp: build-stamp ( cd samples && $(MAKE) install.examples DESTDIR=$(TARGET_DIR) BINDIR=$(SAMPLE_DIR) ) ( cd doc && $(MAKE) install.html DESTDIR=$(TARGET_DIR) ) + find $(TARGET_DIR) -type f -name '*.so*' -print -exec chrpath -d {} \; + touch install-stamp # Build architecture-independent files here. @@ -86,18 +93,19 @@ binary-indep: build install binary-arch: build install dh_testdir dh_testroot - dh_installdocs - dh_installexamples - dh_installchangelogs NEWS - dh_strip - dh_compress - dh_fixperms - dh_installdeb - dh_makeshlibs - dh_shlibdeps - dh_gencontrol - dh_md5sums - dh_builddeb + dh_lintian $(verbose) + dh_installdocs $(verbose) + dh_installexamples $(verbose) + dh_installchangelogs $(verbose) NEWS + dh_strip $(verbose) + dh_compress $(verbose) + dh_fixperms $(verbose) + dh_installdeb $(verbose) + dh_makeshlibs $(verbose) + dh_shlibdeps $(verbose) -l$(OUR_LIBDIR) + dh_gencontrol $(verbose) + dh_md5sums $(verbose) + dh_builddeb $(verbose) binary: binary-indep binary-arch .PHONY: build clean binary-indep binary-arch binary install install-stamp diff --git a/Ada95/package/debian/watch b/Ada95/package/debian/watch index 1b870ba..5a8f1d2 100644 --- a/Ada95/package/debian/watch +++ b/Ada95/package/debian/watch @@ -1,4 +1,4 @@ version=3 -opts=passive ftp://ftp.invisible-island.net/AdaCurses/AdaCurses-([\d.]+)\.tgz \ +opts=passive https://invisible-island.net/archives/AdaCurses/AdaCurses-([\d.]+)\.tgz \ debian uupdate diff --git a/Ada95/samples/Makefile.in b/Ada95/samples/Makefile.in index 3731085..d3cee07 100644 --- a/Ada95/samples/Makefile.in +++ b/Ada95/samples/Makefile.in @@ -1,5 +1,5 @@ ############################################################################## -# Copyright 2018-2020,2021 Thomas E. Dickey # +# Copyright 2018-2024,2025 Thomas E. Dickey # # Copyright 1998-2015,2018 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -29,7 +29,7 @@ # # Author: Juergen Pfeifer, 1996 # -# $Id: Makefile.in,v 1.64 2021/07/03 15:45:33 tom Exp $ +# $Id: Makefile.in,v 1.67 2025/10/18 13:40:00 tom Exp $ # .SUFFIXES: @@ -37,6 +37,8 @@ SHELL = @SHELL@ VPATH = @srcdir@ THIS = Makefile +@SET_DESTDIR@ + x = @EXEEXT@ srcdir = @srcdir@ @@ -78,9 +80,9 @@ LDFLAGS = @LDFLAGS@ @LD_MODEL@ @LIBS@ RANLIB = @RANLIB@ ################################################################################ -BINDIR = $(DESTDIR)$(bindir) -DATADIR = $(DESTDIR)$(datadir) -LIBDIR = $(DESTDIR)$(libdir) +BINDIR = $(DESTDIR)$(bindir@MERGE_PREFIX@) +DATADIR = $(DESTDIR)$(datadir@MERGE_PREFIX@) +LIBDIR = $(DESTDIR)$(libdir@MERGE_PREFIX@) MY_DATADIR = $(DATADIR)/@ADA_LIBNAME@ THIS_DATADIR = $(datadir)/@ADA_LIBNAME@ @@ -133,7 +135,7 @@ sources : libs \ install \ -install.libs :: +install.libs :: $(PROGS) @echo made $@ uninstall \ diff --git a/Ada95/samples/sample-explanation.adb_p b/Ada95/samples/sample-explanation.adb_p index f99ceb6..79348e9 100644 --- a/Ada95/samples/sample-explanation.adb_p +++ b/Ada95/samples/sample-explanation.adb_p @@ -7,7 +7,7 @@ -- B O D Y -- -- -- ------------------------------------------------------------------------------ --- Copyright 2019,2020 Thomas E. Dickey -- +-- Copyright 2019-2020,2025 Thomas E. Dickey -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- -- copy of this software and associated documentation files (the -- @@ -35,8 +35,8 @@ ------------------------------------------------------------------------------ -- Author: Juergen Pfeifer, 1996 -- Version Control --- $Revision: 1.5 $ --- $Date: 2020/02/02 23:34:34 $ +-- $Revision: 1.6 $ +-- $Date: 2025/01/24 20:39:23 $ -- Binding Version 01.00 ------------------------------------------------------------------------------ -- Poor mans help system. This scans a sequential file for key lines and @@ -136,7 +136,7 @@ package body Sample.Explanation is H : Help_Line_Access := Top_Line; begin if Top_Line /= null then - for L in 0 .. (Height - 1) loop + for L in 0 .. Height - 1 loop Add (W, L, 0, H.all.Line.all); exit when H.all.Next = null; H := H.all.Next; diff --git a/Ada95/samples/sample-menu_demo-handler.adb b/Ada95/samples/sample-menu_demo-handler.adb index ebbaf43..eab03f1 100644 --- a/Ada95/samples/sample-menu_demo-handler.adb +++ b/Ada95/samples/sample-menu_demo-handler.adb @@ -16,7 +16,7 @@ -- without limitation the rights to use, copy, modify, merge, publish, -- -- distribute, distribute with modifications, sublicense, and/or sell -- -- copies of the Software, and to permit persons to whom the Software is -- --- furnished to do so, subject to the following conditions : -- +-- furnished to do so, subject to the following conditions: -- -- -- -- The above copyright notice and this permission notice shall be included -- -- in all copies or substantial portions of the Software. -- @@ -36,7 +36,7 @@ ------------------------------------------------------------------------------ -- Author: Juergen Pfeifer, 1996 -- Version Control --- $Revision: 1.17 $ +-- $Revision: 1.18 $ -- $Date: 2020/02/02 23:34:34 $ -- Binding Version 01.00 ------------------------------------------------------------------------------ diff --git a/Ada95/src/Makefile.in b/Ada95/src/Makefile.in index eb4489b..ec12cf6 100644 --- a/Ada95/src/Makefile.in +++ b/Ada95/src/Makefile.in @@ -1,5 +1,5 @@ ############################################################################## -# Copyright 2018-2020,2021 Thomas E. Dickey # +# Copyright 2018-2024,2025 Thomas E. Dickey # # Copyright 1999-2016,2018 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -29,7 +29,7 @@ # # Author: Juergen Pfeifer, 1996 # -# $Id: Makefile.in,v 1.96 2021/07/03 15:45:33 tom Exp $ +# $Id: Makefile.in,v 1.102 2025/10/18 13:35:27 tom Exp $ # .SUFFIXES: @@ -37,13 +37,12 @@ SHELL = @SHELL@ VPATH = @srcdir@ THIS = Makefile -ADA_MFLAGS = @cf_cv_makeflags@ +ADA_MFLAGS = @SET_MAKE@ +@SET_DESTDIR@ MODEL = ../../@DFT_OBJ_SUBDIR@ -DESTDIR = @DESTDIR@ - top_srcdir = @top_srcdir@ srcdir = @srcdir@ prefix = @prefix@ @@ -51,7 +50,7 @@ exec_prefix = @exec_prefix@ includedir = @includedir@ libdir = @libdir@ -LIBDIR = $(DESTDIR)$(libdir) +LIBDIR = $(DESTDIR)$(libdir@MERGE_PREFIX@) ADA_INCLUDE = $(DESTDIR)@ADA_INCLUDE@ ADA_OBJECTS = $(DESTDIR)@ADA_OBJECTS@ @@ -284,9 +283,11 @@ STATIC_DIRS = \ $(BUILD_DIR)/static-obj @USE_GNAT_PROJECTS@$(BUILD_DIR_LIB)/$(STATIC_LIBNAME) :: \ -@USE_GNAT_PROJECTS@ $(ABASE)-trace.adb \ -@USE_GNAT_PROJECTS@ $(STATIC_C_OBJS) \ @USE_GNAT_PROJECTS@ $(STATIC_DIRS) +@USE_GNAT_PROJECTS@$(BUILD_DIR_LIB)/$(STATIC_LIBNAME) :: \ +@USE_GNAT_PROJECTS@ $(ABASE)-trace.adb \ +@USE_GNAT_PROJECTS@ $(STATIC_C_OBJS) +@USE_GNAT_PROJECTS@ @echo "Making $@" @USE_GNAT_PROJECTS@ @cf_ada_config@gprconfig --batch --config=Ada --config=C,,,,@cf_ada_config_C@ @USE_GNAT_PROJECTS@ -rm -f $(GNAT_PROJECT) @USE_GNAT_PROJECTS@ $(SHELL) $(srcdir)/library-cfg.sh static library.gpr $(CFLAGS_NORMAL) >$(GNAT_PROJECT) @@ -320,6 +321,7 @@ STATIC_DIRS = \ #NEW:BEGIN #@USE_GNAT_LIBRARIES@install \ #@USE_GNAT_LIBRARIES@install.libs :: +#@USE_GNAT_LIBRARIES@ @echo "Making $@" #@USE_GNAT_LIBRARIES@ @cf_ada_config@gprconfig --batch --config=Ada --config=C,,,,@cf_ada_config_C@ #@USE_GNAT_LIBRARIES@ -rm -f $(GNAT_PROJECT) #@USE_GNAT_LIBRARIES@ $(SHELL) $(srcdir)/library-cfg.sh static library.gpr $(CFLAGS_NORMAL) >$(GNAT_PROJECT) @@ -344,6 +346,7 @@ uninstall.libs :: #NEW:BEGIN #@USE_GNAT_LIBRARIES@uninstall \ #@USE_GNAT_LIBRARIES@uninstall.libs :: +#@USE_GNAT_LIBRARIES@ @echo "Making $@" #@USE_GNAT_LIBRARIES@ @cf_ada_config@gprconfig --batch --config=Ada --config=C,,,,@cf_ada_config_C@ #@USE_GNAT_LIBRARIES@ -rm -f $(GNAT_PROJECT) #@USE_GNAT_LIBRARIES@ $(SHELL) $(srcdir)/library-cfg.sh static library.gpr $(CFLAGS_NORMAL) >$(GNAT_PROJECT) @@ -369,9 +372,11 @@ SHARED_DIRS = \ @MAKE_ADA_SHAREDLIB@all :: $(BUILD_DIR_LIB)/$(SHARED_LIBNAME) @MAKE_ADA_SHAREDLIB@$(BUILD_DIR_LIB)/$(SHARED_LIBNAME) :: \ +@MAKE_ADA_SHAREDLIB@ $(SHARED_DIRS) +@MAKE_ADA_SHAREDLIB@$(BUILD_DIR_LIB)/$(SHARED_LIBNAME) :: \ @MAKE_ADA_SHAREDLIB@ $(ABASE)-trace.adb \ -@MAKE_ADA_SHAREDLIB@ $(SHARED_DIRS) \ @MAKE_ADA_SHAREDLIB@ $(SHARED_OBJS) +@MAKE_ADA_SHAREDLIB@ @echo "Making $@" @MAKE_ADA_SHAREDLIB@ cp $(SHARED_OBJS) $(BUILD_DIR)/dynamic-obj/ @MAKE_ADA_SHAREDLIB@ @cf_ada_config@gprconfig --batch --config=Ada --config=C,,,,@cf_ada_config_C@ @MAKE_ADA_SHAREDLIB@ -rm -f $(GNAT_PROJECT) diff --git a/Ada95/src/library.gpr.in b/Ada95/src/library.gpr.in index 37cbb9d..b256b07 100644 --- a/Ada95/src/library.gpr.in +++ b/Ada95/src/library.gpr.in @@ -1,5 +1,5 @@ ------------------------------------------------------------------------------ --- Copyright 2019,2020 Thomas E. Dickey -- +-- Copyright 2019-2020,2025 Thomas E. Dickey -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- -- copy of this software and associated documentation files (the -- @@ -25,7 +25,7 @@ -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------ --- $Id: library.gpr.in,v 1.3 2020/06/27 20:47:40 tom Exp $ +-- $Id: library.gpr.in,v 1.5 2025/10/04 20:20:42 tom Exp $ -- http://gcc.gnu.org/onlinedocs/gnat_ugn_unw/Library-Projects.html -- http://www.adaworld.com/debian/debian-ada-policy.html project AdaCurses is @@ -43,7 +43,7 @@ project AdaCurses is for Source_Dirs use (Source_Dir & "/src", Source_Dir2, Build_Dir & "/src"); - -- for Library_Options use ("-lncurses@USE_LIB_SUFFIX@", "-lpanel@USE_LIB_SUFFIX@", "-lmenu@USE_LIB_SUFFIX@", "-lform@USE_LIB_SUFFIX@"); + -- for Library_Options use ("-lncurses@ABI_SUFFIX@", "-lpanel@ABI_SUFFIX@", "-lmenu@ABI_SUFFIX@", "-lform@ABI_SUFFIX@"); package Compiler is for Default_Switches ("Ada") use ("-g", diff --git a/Ada95/src/modules b/Ada95/src/modules index 29a0d8b..cb1fb84 100644 --- a/Ada95/src/modules +++ b/Ada95/src/modules @@ -1,6 +1,6 @@ -# $Id: modules,v 1.4 2020/02/02 23:34:34 tom Exp $ +# $Id: modules,v 1.5 2024/06/15 20:51:03 tom Exp $ ############################################################################## -# Copyright 2020 Thomas E. Dickey # +# Copyright 2020,2024 Thomas E. Dickey # # Copyright 2010 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -69,3 +69,5 @@ $(ABASE)-text_io-decimal_io $(srcdir) $(srcdir) body $(ABASE)-text_io-enumeration_io $(srcdir) $(srcdir) body $(ABASE)-text_io-modular_io $(srcdir) $(srcdir) body $(ABASE)-text_io-complex_io $(srcdir) $(srcdir) body + +# vile:makemode diff --git a/Ada95/src/terminal_interface-curses-forms.adb b/Ada95/src/terminal_interface-curses-forms.adb index f50420e..2e6fd16 100644 --- a/Ada95/src/terminal_interface-curses-forms.adb +++ b/Ada95/src/terminal_interface-curses-forms.adb @@ -7,7 +7,7 @@ -- B O D Y -- -- -- ------------------------------------------------------------------------------ --- Copyright 2020 Thomas E. Dickey -- +-- Copyright 2020,2025 Thomas E. Dickey -- -- Copyright 1999-2011,2014 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -36,8 +36,8 @@ ------------------------------------------------------------------------------ -- Author: Juergen Pfeifer, 1996 -- Version Control: --- $Revision: 1.33 $ --- $Date: 2020/02/02 23:34:34 $ +-- $Revision: 1.34 $ +-- $Date: 2025/01/24 20:39:23 $ -- Binding Version 01.00 ------------------------------------------------------------------------------ with Ada.Unchecked_Deallocation; @@ -1006,7 +1006,7 @@ package body Terminal_Interface.Curses.Forms is (Field_Array, Field_Array_Access); begin if FA /= null and then Free_Fields then - for I in FA'First .. (FA'Last - 1) loop + for I in FA'First .. FA'Last - 1 loop if FA.all (I) /= Null_Field then Delete (FA.all (I)); end if; diff --git a/Ada95/src/terminal_interface-curses-menus.adb b/Ada95/src/terminal_interface-curses-menus.adb index 76f3e36..9febcf9 100644 --- a/Ada95/src/terminal_interface-curses-menus.adb +++ b/Ada95/src/terminal_interface-curses-menus.adb @@ -7,7 +7,7 @@ -- B O D Y -- -- -- ------------------------------------------------------------------------------ --- Copyright 2018,2020 Thomas E. Dickey -- +-- Copyright 2018-2020,2025 Thomas E. Dickey -- -- Copyright 1999-2011,2014 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -36,8 +36,8 @@ ------------------------------------------------------------------------------ -- Author: Juergen Pfeifer, 1996 -- Version Control: --- $Revision: 1.34 $ --- $Date: 2020/02/02 23:34:34 $ +-- $Revision: 1.35 $ +-- $Date: 2025/01/24 20:39:23 $ -- Binding Version 01.00 ------------------------------------------------------------------------------ with Ada.Unchecked_Deallocation; @@ -878,7 +878,7 @@ package body Terminal_Interface.Curses.Menus is (Item_Array, Item_Array_Access); begin if IA /= null and then Free_Items then - for I in IA'First .. (IA'Last - 1) loop + for I in IA'First .. IA'Last - 1 loop if IA.all (I) /= Null_Item then Delete (IA.all (I)); end if; diff --git a/Ada95/src/terminal_interface-curses-panels-user_data.adb b/Ada95/src/terminal_interface-curses-panels-user_data.adb index 504b07d..4a951a4 100644 --- a/Ada95/src/terminal_interface-curses-panels-user_data.adb +++ b/Ada95/src/terminal_interface-curses-panels-user_data.adb @@ -7,7 +7,7 @@ -- B O D Y -- -- -- ------------------------------------------------------------------------------ --- Copyright 2020 Thomas E. Dickey -- +-- Copyright 2020,2025 Thomas E. Dickey -- -- Copyright 1999-2003,2009 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -36,7 +36,7 @@ ------------------------------------------------------------------------------ -- Author: Juergen Pfeifer, 1996 -- Version Control: --- $Revision: 1.13 $ +-- $Revision: 1.14 $ -- Binding Version 01.00 ------------------------------------------------------------------------------ with Interfaces.C; diff --git a/MANIFEST b/MANIFEST index a9395d2..dc791db 100644 --- a/MANIFEST +++ b/MANIFEST @@ -36,6 +36,8 @@ ./Ada95/mk-pkg.awk ./Ada95/package/AdaCurses-doc.spec ./Ada95/package/AdaCurses.spec +./Ada95/package/debian/adacurses.lintian-overrides +./Ada95/package/debian/adacurses.triggers ./Ada95/package/debian/compat ./Ada95/package/debian/control ./Ada95/package/debian/copyright @@ -556,21 +558,18 @@ ./include/headers ./include/nc_access.h ./include/nc_alloc.h -./include/nc_mingw.h ./include/nc_panel.h ./include/nc_string.h ./include/nc_termios.h ./include/nc_tparm.h -./include/nc_win32.h +./include/nc_win32.h.in ./include/ncurses_cfg.hin ./include/ncurses_defs ./include/ncurses_dll.h.in -./include/ncurses_mingw.h ./include/term_entry.h ./include/termcap.h.in ./include/tic.h ./include/unctrl.h.in -./include/win32_curses.h ./install-sh ./man/MKada_config.in ./man/MKncu_config.in @@ -900,6 +899,7 @@ ./ncurses/llib-ltinfow ./ncurses/modules ./ncurses/new_pair.h +./ncurses/report_ctype.c ./ncurses/report_hashing.c ./ncurses/report_offsets.c ./ncurses/term.priv.h @@ -1007,12 +1007,11 @@ ./ncurses/win32con/gettimeofday.c ./ncurses/win32con/wcwidth.c ./ncurses/win32con/win32_driver.c -./ncurses/win32con/win_driver.c ./package/debian-mingw/changelog ./package/debian-mingw/compat ./package/debian-mingw/control ./package/debian-mingw/copyright -./package/debian-mingw/mingw32-ncurses6.lintian-overrides +./package/debian-mingw/mingw32-ncurses6td.lintian-overrides ./package/debian-mingw/rules ./package/debian-mingw/source/format ./package/debian-mingw/watch @@ -1020,7 +1019,7 @@ ./package/debian-mingw64/compat ./package/debian-mingw64/control ./package/debian-mingw64/copyright -./package/debian-mingw64/mingw64-ncurses6.lintian-overrides +./package/debian-mingw64/mingw64-ncurses6td.lintian-overrides ./package/debian-mingw64/rules ./package/debian-mingw64/source/format ./package/debian-mingw64/watch @@ -1028,10 +1027,10 @@ ./package/debian/compat ./package/debian/control ./package/debian/copyright -./package/debian/ncurses6.lintian-overrides -./package/debian/ncurses6.triggers -./package/debian/ncursest6.lintian-overrides -./package/debian/ncursest6.triggers +./package/debian/ncurses6td.lintian-overrides +./package/debian/ncurses6td.triggers +./package/debian/ncursest6td.lintian-overrides +./package/debian/ncursest6td.triggers ./package/debian/rules ./package/debian/source/format ./package/debian/watch @@ -1190,6 +1189,8 @@ ./test/package/debian/control ./test/package/debian/copyright ./test/package/debian/docs +./test/package/debian/ncurses-examples.lintian-overrides +./test/package/debian/ncursest-examples.lintian-overrides ./test/package/debian/rules ./test/package/debian/source/format ./test/package/debian/watch diff --git a/Makefile.in b/Makefile.in index 1303e17..9a55006 100644 --- a/Makefile.in +++ b/Makefile.in @@ -1,6 +1,6 @@ -# $Id: Makefile.in,v 1.46 2022/10/01 22:53:36 tom Exp $ +# $Id: Makefile.in,v 1.51 2025/10/25 18:01:01 tom Exp $ ############################################################################## -# Copyright 2018-2021,2022 Thomas E. Dickey # +# Copyright 2018-2022,2025 Thomas E. Dickey # # Copyright 1998-2014,2015 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -35,11 +35,10 @@ SHELL = @SHELL@ VPATH = @srcdir@ -DESTDIR=@DESTDIR@ -RPATH_LIST=@RPATH_LIST@ -TOP_MFLAGS = @cf_cv_makeflags@ DESTDIR="$(DESTDIR)" RPATH_LIST="$(RPATH_LIST)" - @SET_MAKE@ +@SET_DESTDIR@ +RPATH_LIST = @RPATH_LIST@ +TOP_MFLAGS = DESTDIR="$(DESTDIR)" RPATH_LIST="$(RPATH_LIST)" NCURSES_MAJOR = @NCURSES_MAJOR@ NCURSES_MINOR = @NCURSES_MINOR@ @@ -93,6 +92,7 @@ preinstall : @ echo '' @ echo ' extended funcs: '`test @NCURSES_EXT_FUNCS@ != 0 && echo yes || echo no` @ echo ' xterm terminfo: '@WHICH_XTERM@ + @ echo ' ABI suffix: '`if test -n "@ABI_SUFFIX@"; then echo @ABI_SUFFIX@; else echo "(none)"; fi` @ echo '' @ echo ' bin directory: '$(bindir) @ echo ' lib directory: '$(libdir) @@ -114,13 +114,10 @@ preinstall : distclean \ realclean :: -check : - @ echo The test-programs are interactive - - # Put the common rules here so that we can easily construct the list of # directories to visit. all \ +check \ clean \ distclean \ mostlyclean \ diff --git a/Makefile.os2 b/Makefile.os2 index bc3407d..68d4f89 100644 --- a/Makefile.os2 +++ b/Makefile.os2 @@ -1,5 +1,5 @@ ############################################################################## -# Copyright 2020,2021 Thomas E. Dickey # +# Copyright 2020-2021,2025 Thomas E. Dickey # # Copyright 1998-2000,2006 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -26,7 +26,7 @@ # use or other dealings in this Software without prior written # # authorization. # ################################################################################ -# $Id: Makefile.os2,v 1.13 2021/06/17 21:20:30 tom Exp $ +# $Id: Makefile.os2,v 1.15 2025/07/12 10:48:01 tom Exp $ # # Wrapper Makefile for ncurses library under OS/2. # Author: Juan Jose Garcia Ripoll . @@ -247,7 +247,7 @@ OS2NAME=ncurses-$(NCURSES_MAJOR).$(NCURSES_MINOR)-emx os2dist : $(MAKE) -f Makefile.os2 os2clean ./configure --without-debug --with-install-prefix=`pwd|sed -e 's@^.:@@'`/$(OS2NAME) - $(MAKE) -f Makefile.os2 $(CF_MFLAGS) install.os2 + $(MAKE) -f Makefile.os2 install.os2 -rm -f $(OS2NAME).zip echo NCurses-$(NCURSES_MAJOR).$(NCURSES_MINOR)-$(NCURSES_PATCH) for emx > $(OS2NAME)/FILE_ID.DIZ echo Binary release. >> $(OS2NAME)/FILE_ID.DIZ diff --git a/NEWS b/NEWS index 8bedbc8..c10767b 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,5 @@ ------------------------------------------------------------------------------- --- Copyright 2018-2023,2024 Thomas E. Dickey -- +-- Copyright 2018-2024,2025 Thomas E. Dickey -- -- Copyright 1998-2017,2018 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -26,7 +26,7 @@ -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------- --- $Id: NEWS,v 1.4114 2024/04/27 18:00:35 tom Exp $ +-- $Id: NEWS,v 1.4390 2025/12/30 20:31:07 tom Exp $ ------------------------------------------------------------------------------- This is a log of changes that ncurses has gone through since Zeyd started @@ -46,6 +46,575 @@ See the AUTHORS file for the corresponding full names. Changes through 1.9.9e did not credit all contributions; it is not possible to add this information. +20251230 6.6 release for upload to ftp.gnu.org + + update announcement + + corrected an ifdef needed for mouse support in MinGW/Windows + + eliminate remaining duplicate code between MinGW/Windows drivers + +20251227 + + make win32_curses.h obsolete in favor of nc_win32.h + + modify MinGW32 configuration to account for its use of Windows-style + pathnames in filesystem checks. + + replace --enable-exp-win32 option with --enable-named-pipes + +20251220 + > in-progress work to merge MinGW/Windows port. + + eliminate EXP_WIN32_DRIVER with USE_NAMED_PIPES + + change MS_TERMINAL to DEFAULT_TERM_VAR + +20251213 + + in-progress work to merge MinGW/Windows port. + + add a null-pointer check in tic -c option. + + add a limit-check in infocmp -i option (report/example by Yixuan Cao). + +20251206 + + in-progress work to merge MinGW/Windows port. + +20251129 + + in-progress work to merge MinGW/Windows port. + +20251123 + + revert change using NCURSES_SBOOL in tic.h which interfered with + sign-extension in tigetflag (Debian #1121191, cf: 20251101). + +20251122 + + in-progress work to merge MinGW/Windows port. + + correct expression for TINFO_LIB variable in misc/ncurses-config.in + (Debian #1121208, cf: 20251004). + +20251115 + + check for special case of wcrtomb() converting a single byte code to + a different single byte code, which glibc does for code 160 in the + KOI8-R encoding (report by Yury V Zaytsev). + + improve formatting/style of manpages (patches by Branden Robinson). + + amend recent changes to mouse handling to avoid a case which caused + a loop in wgetch until additional input is provided (htop #1769, + cf: 20250913). + +20251101 + + adjust generated terminfo.5 to omit tbl "x" column modifier if that + is unsupported, i.e., with old nroff/tbl (adapted from patch by + Branden Robinson). + + in-progress work to merge MinGW/Windows port. + +20251025 + + amend locale-portability fix in tty_update.c (MidnightCommander #4799, + cf: 20240203). + + add testing utility report_ctype + + update configure macros, improving check for $host_os + + correct a recent change to curs_termino.3x, along with formatting + fixes for manpages. + + corrected note about box() in curs_border.3x (patch by Jakub Horky, + cf: 20250201). + +20251018 + + add check for build-time utilities, in case cross-compiling is setup + with an invalid $BUILD_CC (prompted by discussion with Stas Sergeev). + + modify configure-script and makefiles to make it easier to override + the "--with-install-prefix" default with environment variable + (report by Stas Sergeev). + +20251010 + + fix stray "\" in curs_extend.3x, regen html manpages. + + regen html manpages with man2html 1.42, fixing a few cases where + headers were not linked (report by Branden Robinson). + +20251004 + + improve formatting/style of manpages (patches by Branden Robinson). + + in-progress work to merge MinGW/Windows port. + + improve configure check for "install". + +20250927 + + in-progress work to merge MinGW/Windows port. + +20250920 + + in-progress work to merge MinGW/Windows port. + + add configure check for , build-fix for flatpacks + (report by Stas Sergeev). + + update config.guess, config.sub + +20250913 + + update ncurses-howto. + + modify MKfallback.sh to eliminate TERMINFO environment variable. + + improve checks in run_tic.sh script, change some variable names to + reduce packager confusion (report by Stas Sergeev). + + disallow configure options which apply only to multiuser systems, to + improve ports to single-user systems such as Haiku (report by Stas + Sergeev). + + update ncurses/wcwidth.c, for MinGW ports, from xterm. + + correct _nc_to_char() for the case when wctob() is not found by + configure script (report/patch by Benno Schulenberg). + > patches by Robin Haberkorn + + modify handle_wheel case 2 to ignore the event as in case 1 for + mouse version 1, since that corresponds to a button 6 or 7 event + which is not supported with ABI 6. + + use separate read/write pointers in the mouse event queue to work + with too-close events for the click-detection to work reliably, + and further improve that in case mouseinterval(0) is used to + suppress click-detection. + +20250830 + + in-progress work to merge MinGW/Windows port. + + build-fix for experimental Windows configuration (report by Kirill + Makurin). + + improve pattern used for configure --with-xterm-kbs option. + +20250823 + + improve style of MKterminfo.sh script (patches by Branden Robinson). + + improve formatting/style of manpages (patches by Branden Robinson). + + remove redundant definition of ConsoleInfo. + + change scope of TTY, GET_TTY and SET_TTY to ncurses-internals + +20250816 + + remove redundant reference to compiler in libtool configuration of + mk-1st.awk (report by Lorinczy Zsigmond). + + build-fixes for --enable-exp-win32 configuration + + improve formatting/style of manpages (patches by Branden Robinson). + +20250809 + + add configure check for Win32 named pipes feature, using that to make + nc_mingw.h obsolete in favor of nc_win32.h + + amend limit used in alloc_pair, by applying an adjustment for default + colors only when the maximum number of color pairs is greater than + the maximum number of colors (report by "Ingvix"). + +20250802 + + fixes for reading Unicode characters in MinGW/Windows port (report by + Axel Reinhold). + +20250726 + + modify configure script cases for $host_os, to accommodate 64-bit + big-endian POWER linux with glibc (patch by Cosima Neidahl). + + add warning to configure script to address conflict between the + --enable-lp64 option and the options for overriding the types used + for chtype and mmask_t. + +20250720 + + further improve readability of header-files + + add a consistency-check for termio(s)/tty headers, to help with + cross-compiles (report by Stas Sergeev). + + remove some unused configure-macros + + add xterm+keypad to pccon+base -TD + + trim trailing blanks from a few files (report by Stas Sergeev). + +20250712 + + improve readability of term.h + + modify recursive make rules to avoid interference with GNU make's + "-j" option (report by Stas Sergeev). + +20250705 + + when installing the terminfo database, check if symbolic links are + supported before attemping to link lib/terminfo from share/terminfo + (report by Kirill Makurin). + + modify configure check for MAKEFLAGS/MFLAGS to ignore existing value + of these environment variables (report by Stas Sergeev). + + reserve -c/-l options in test/*.c for command/logging like vttest. + + add options to test/worm.c for benchmarking (Nibby Nebbulous) + + improve formatting/style of manpages (patches by Branden Robinson). + + improve readability of header-files (patches by Branden Robinson). + +20250628 + + fix a few compiler-warnings. + + simplify include for wchar.h in Windows port by removing the platform + ifdef's (report by Kirill Makurin). + + regen Ada95/configure (report by Sven Joachim). + +20250621 + + revise loop in wins_nwstr, to ensure that non-spacing characters are + combined with the base spacing character (report by Karl Knechtel). + + fixes for port using clang-cl or cl MSVC (report by Kirill Makurin). + + improve test-packages: + + convert debian*/copyright to DEP-5 format. + + modify ".spec" test-files to work around timestamp-clamping in + recent Fedora releases. + +20250614 + + reduce lintian warnings for test-packages. + + clean up some shellcheck warnings + + improve test/configure checks for X libraries, reducing duplicates + + fix some typos/errata in license text, to help with scripted checks + +20250531 + + improve logic in misc/run_tic.in for constructing symbolic link + when $DESTDIR is set. + +20250524 + + correct option-name used in configure script, which resulted in size + change for cchar_t (cf: 20250517). + +20250517 + + initial changes for some ABI 7 features: + + disable wgetch-events + + add feature for extending mouse-buttons + + add feature for extending direct-color support + + use bracketed+paste in nsterm, rlogin-color, screen, terminology -TD + +20250510 + + add rv/xr codes for domterm, mintty, mlterm -TD + + add xr code for putty -TD + + update teraterm to 5.0 -TD + + add rlogin-color -TD + +20250503 + + update/correct some of the rv/xr strings, checked with tack -TD + + use ansi+rca in sclp -TD + + use vt220+pcedit in sclp (Werner Fink) + + move some building blocks from illumos to sun-color, based on + illumos source-history -TD + + improve use-clauses: ansi+cup, ansi+idl1, ansi+rca, ansi+rca2, + ansi+sgrso, ansi+sgrul -TD + + add ecma+standout, ecma+underline -TD + + add rv code for alacritty -TD + + add rv/xr codes for contour, ghostty, iterm2, kitty, konsole, + vscode, vte, wezterm -TD + +20250426 + + expand note on extensions in curs_addch.3x + + add illumos, sun-16color, sun-256color, sun-direct -TD + + add wyse+cvis -TD + +20250419 + + add note on scrolling and lower-right corner to waddch and wadd_wch + manual pages. + +20250412 + + add pangoterm -TD + + add kf1 to kf5 to sclp (report by Werner Fink) + + add vt100+pf1-pf4 -TD + +20250405 + + improve formatting/style of manpages (patches by Branden Robinson). + + improve infocmp -E/-e fallback feature (report by Ville Rissanen): + + prefix names with "ti_" if they begin with a digit, e.g., 9term + + escape backslashes and double-quotes in description fields + + modify infocmp -E/-e fallback feature to reduce stricter compiler + warnings for the extended capability data. + + add sclp -TD + + add op to vt525 -TD + + update contour -TD + +20250329 + + add XM/xm to ms-terminal, to enable mouse with experimental Windows + driver -TD + + add -x option to infocmp in MKfallback.sh + + improve experimental Windows driver by restoring the scroll buffer + and console mode, e.g., when reset_prog_mode or endwin is called + (patch by Daniel Starke). + + add a buffer-limit check in postprocess_termcap (report/testcase by + Yifan Zhang). + +20250322 + + add a null pointer check in mouse-initialization, for the + experimental Windows driver (patch by Daniel Starke). + + improve makefile dependency in Ada95/src + + add note in user_caps.5 addressing a quibble about dates. + +20250315 + + improve formatting/style of manpages (patches by Branden Robinson). + +20250308 + + remove test in wgetch which applied notimeout to the initial read + of a character (patch by Branden Robinson). + + improve formatting/style of manpages (patches by Branden Robinson). + + fix a few compiler-warnings in MinGW port. + +20250301 + + add color to vt525 (Branden Robinson) + + add vt520-w and vt525-w (Branden Robinson) + + improve formatting/style of manpages (patches by Branden Robinson). + + improve configurability of alloca() as used in Windows ports. + + fix some typos in manpages. + + modify configure script checks for stdbool.h to fix build with older + gcc version. + +20250222 + + modify treatment of "n" parameter for waddnstr, waddnwstr, and + wins_nwstr to return OK when "n" is zero, for consistency with other + implementations (report by Benjamin Barenblat, cf: 20231118). + + formatting improvements for terminfo.5 (Debian #1096164). + +20250216 + + add limit-checks in alloc_entry.c and alloc_ttype.c to avoid indexing + errors when using infocmp to compare all capabilities when processing + a malformed terminfo binary which has a valid header (testcase by + "Ekkosun"). + +20250215 + + add gzip option for suppressing filename/timestamp information to an + overlooked case (cf: 20240330). + + correct spelling errors found with codespell. + + fix some typos in manpages (report by Sven Joachim) + + amend change to lib_set_term.c to work with thread configuration + (report by Rajeev Pillai, cf: 20250208). + +20250208 + + change etip.h.in to include either/both of and , + needed for another old BSD. + + update st (report by Alexander Kashpir) -TD + + add note for ghostty 1.1.0 -TD + + fix a few issues found with coverity. + +20250201 + + add to the possible headers declaring the C++ std::bad_alloc + (report by Carl Hansen). + + modify check for stdbool.h to be more conservative in case the + headers are used with a compiler other than that which was used to + configure (Redhat #2342514). + + improve MKlib_gen.sh handling of "bool" type, for building link_test + + improve formatting/style of manpages (patches by Branden Robinson). + +20250125 + + improve error-handling in c++ binding (report by Mingjie Shen). + + strict compiler-warning fixes for upcoming gcc15 + +20250118 + + improve pattern used for configure --with-xterm-kbs option (report by + Mingyu Wang) + + update configure macros, from work on cdk and dialog. + + change a parameter name in curs_sp_funcs.3x, for consistency (patch + by "WHR"). + > patches by Branden Robinson: + + improve formatting/style of manpages + + change winwstr() to a generated function, using the macro definition, + moving its handling of negative length parameter into winnwstr(). + + correct actual-function name in a few trace calls. + +20250111 + + add check for infinite loop in tic's use-resolution. + + increase limit on use-clauses from 32 to 40, warn but allow entries + which exceed the old limit. + + add some null-pointer checks after mallocs in test-programs. + +20250104 + + modify tput to warn about capabilities which expect parameters where + none are given; also repair the feature where multiple capabilities + can be handled on a single line. + + cleanup use-clauses -TD + + add linux+lockeys, xterm+r5+lockeys, xterm+r5+fkeys -TD + + add vt220+ufkeys, vt220+sfkeys + + revert man/manlinks.sed change, which loses aliases (cf: 20241228). + + modify MKlib_gen.c to allow for Solaris's definition of NULL as 0L + +20241228 + + correct conditional-compile for a case when the C compiler does not + have a bool type. + + add ghostty -TD + > patches by Branden Robinson: + + add comments to generated term.h to hint the configure options used + + use same subdir-convention for term.h, in configure script + + improve formatting/style of manpages + +20241221 + + modify ncurses/tinfo/MKfallback.sh to work with MacOS sed, which + lacks BSD-style \< and \> + + trim padding from sgr expression used in trim_sgr0, to avoid copying + the padding into the resulting sgr0 (report by Rajeev Pillai). + + strict compiler-warning fixes for upcoming gcc15 + +20241214 + + avoid redefining bool in curses.h if the platform already supports + that type (cf: 20241123). + + move include from etip.h.in to cursesw.h, to work around + breakage in Apple's port of ncurses. + + strict compiler-warning fixes for upcoming gcc15 + +20241207 + + strict compiler-warning fixes for upcoming gcc15 + +20241130 + + improve configure check for lint program. + + adjust options in test-programs to allow for consistent use of -c/-l + for command/logging. + + modify win_driver.c for MinGW to handle shift-tab and control-tab as + back-tab (report by Axel Reinhold) + +20241123 + + remove dependency on stdbool.h from configure script check for type + of bool when C++ binding is omitted (report by Sam James). + + compiler-warning fixes + +20241109 + + work around musl header ifdef's (report by Urs Jansen, cf: Gentoo + #920266). + + improve error-reporting in write_entry.c (report by Changqing Li). + + remove unused #include from DJGPP configuration (report by Stas + Sergeev). + + workaround/fix issues from clang-analyze + +20241102 + + remove djgpp-specific initialization to binary mode (report/patch by + Stas Sergeev). + + add extended-keys for djgpp 2.05 -TD + +20241026 + + update ms-terminal -TD + + add ms-terminal-direct -TD + + correct dimensions in test/popup_msg.c, fixing an overrun (patch by + Stas Sergeev, cf: 20211219). + +20241019 + + fixes for compiler warnings/cppcheck. + + build-fixes for DJGPP configuration (patches by Stas Sergeev) + +20241006 + + fixes for compiler warnings/cppcheck. + + use xterm+alt+title in wezterm -TD + +20240928 + + improve error-message from infocmp when a terminal entry cannot be + opened (patch by Branden Robinson). + + improve filtering of -L options in misc/gen-pkgconfig.in and in + misc/ncurses-config.in + + add check in wresize() for out-of-range dimensions (report by Peter + Bierma). + +20240922 + + add a few null-pointer checks in ncurses + + improve test-driver in ncurses/link_test.c + + restore background character in manpages as described in X/Open + Curses section 3.3.6, and add option "-c" to test programs to + illustrate a non-blank character in the window background property. + + improve formatting/style of manpages (patches by Branden Robinson). + + modify ncurses*-config to add -I option in --cflag where needed for + --disable-overwrite to match ".pc" files. + + disallow directories and block/character devices in safe-open. + + amend scr_restore() and scr_init() to remove the target window only + after validating the source window which will replace the target + (report by Zixi Liu). + +20240914 + + modify _nc_flush() to also flush stderr to help the flash capability + to work in bash (patch by Harm te Hennepe, cf: 20201128) + + omit -g and -fXXX flags from CFLAGS in misc/ncurses-config.in + + improve formatting/style of manpages (patches by Branden Robinson). + + improve examples in NCURSES-Programming-HOWTO.html + + update comments in terminfo.src -TD + +20240831 + + build-fix for a case in msys2 where gettimeofday() was available but + the fallback was partly configured. + > patch by Rafael Kitover: + + separate the _NC_WINDOWS platform macro into _NC_WINDOWS_NATIVE, + for MinGW and other native Win32 support, and _NC_WINDOWS, to make + some Win32 features available under the Cygwin runtime, in this case + the term-driver. + + make some minor adjustments to allow + ./configure --enable-term-driver + to also work on Cygwin platforms such as Cygwin and MSYS2. + +20240824 + + modify infocmp and tabs to use actual name in usage and header. + + modify test/demo_keyok.c to accept ^Q for quit, for consistency. + +20240817 + + review/update foot for 1.18.1 -TD + + add a note about DomTerm 3.2.0 -TD + + add new glob-expressions variables to list in config.status script + (patch by Werner Fink). + + add --enable-install-prefix to modify behavior of $DESTDIR to merge + or replace the value set by --prefix (adapted from suggestion by + Eli Zaretskii). + +20240810 + + modify misc/Makefile.in and misc/run_tic.in so that $DESTDIR is set + and used only in the makefile. + + modify CF_WITH_PKG_CONFIG_LIBDIR to allow for pkg-config using + DOS/Windows pathname syntax (report by Eli Zaretskii). + + improve glob-expressions in configure script + + remove unused Get_Menu_Screen() macro from menu.priv.h + + update config.guess, config.sub + +20240727 + + improve formatting/style of manpages (patches by Branden Robinson). + + fixes for compiler warnings/cppcheck. + + modify wattron/wattroff calls in form/m_post.c to call wattr_on and + wattr_off to omit cast used in the former for X/Open compatibility + (patch by Bill Gray). + + modify wezterm, omitting its broken left/right margin feature (report + by Thayne McCombs) -TD + +20240720 + + improve formatting/style of manpages (patches by Branden Robinson). + + modify configure script and misc/Makefile to accept glob expressions + that include Windows/DOS drive-letters (report by Eli Zaretskii). + + fix misspelled ifdef and correct return-value of _nc_mingw_tcflush in + win_driver.c (report/patch by Eli Zaretskii). + +20240713 + + modify misc/ncurses-config.in, improved match with pkg-config output. + +20240706 + + update configure script to use macro changes from dialog. + + modify CF_NCURSES_PTHREADS to avoid equating package and library + names. + +20240629 + + build-fix for ncurses-examples with newer PDCurses, which no longer + has stubs for unimplemented features. + + add help-popup for test_instr.c, test_inwstr.c + + modify checks in delwin to avoid checking if the window is a pad + until first checking if it is still on the active window-list + (cf: 20211115). + + improve -t option of test/gdc.c, allowing hours only, or hours and + minutes only. + +20240622 + + improve test/gdc.c (patch by Branden Robinson). + + improve formatting/style of manpages (patches by Branden Robinson). + + adjust naming of mingw *-config scripts to match the pkg-config names + + widen pattern in pc/*-config scripts to disallow more linker options + + add --cflags-only-I and --cflags-only-other options to + misc/ncurses-config.in + + revert change to CF_BUILD_CC macro (report by Vassili Courzakis, + cf: 20240518). + +20240615 + + improve formatting/style of manpages (patches by Branden Robinson). + + review/update modules files. + + improve install-rules in Ada95 makefiles (report by Branden Robinson). + + improve formatting/style of manpages in test-directory. + +20240608 + + change winwstr to return wide character count instead of OK (patch + by Branden Robinson). + + improve formatting/style of manpages (patches by Branden Robinson). + + rename testing dpkg's for ncurses6 to resolve a naming conflict with + Debian's ncurses packages. + +20240601 + + improve formatting/style of manpages (patches by Branden Robinson). + + change Ada95/configure to use --with-screen option rather than + --enable-widec, to provide more choices of underlying curses library + +20240525 + + build-fix for configure option --disable-ext-funcs + + improve formatting/style of manpages (patches by Branden Robinson). + + review/update iTerm2 for 3.5.0 -TD + +20240519 + + update Ada95/configure to match change for -DTRACE + + revert change to include/ncurses_defs, which caused build failure if + tracing was not enabled (report by Branden Robinson). + +20240518 + + improve formatting/style of manpages (patches by Branden Robinson). + + move makefile's -DTRACE into include/ncurses_cfg.h, to simplify use + of CFLAGS/CPPFLAGS. + + improve check for clock_gettime(), from xterm. + + modify configure script to work around broken gnatgcc script found in + gcc-13 builds. + +20240511 + + improve formatting/style of manpages (patches by Branden Robinson). + + limit value from ESCDELAY environment variable to 30 seconds, like + other delay limits. + + limit values from LINES and COLUMNS environment variables to 512 + (report by Miroslav Lichvar). + +20240504 + + update ncurses/wcwidth.c, for MinGW ports, from xterm. + + trim obsolete comment about tack from INSTALL. + 20240427 6.5 release for upload to ftp.gnu.org + update announcement + fixes/corrections for manpages (patches by Branden Robinson). @@ -223,7 +792,7 @@ it is not possible to add this information. modem (prompted by discussion with Werner Fink, Michal Suchanek, OpenSUSE #1201384, Debian #60377). + build-fixes for --with-caps variations. - + correct a couple of section-references in INSTALL. + + correct a couple of section references in INSTALL. 20231028 + move xterm focus mode 1004 from xterm+sm+1006 into xterm+focus as @@ -319,7 +888,7 @@ it is not possible to add this information. + minor grammatical fix for manpages (Branden Robinson). 20230729 - + improve manpages for wgetnstr() and wget_wnstr(). + + improve manpages for wgetnstr() and wget_nwstr(). + modify MinGW configuration to provide for running in MSYS/MSYS2 shells, assuming ConPTY support (patch by Pavel Fedin). + add assignment in CF_MAN_PAGES to fill in value for TERMINFO_DIRS in @@ -4262,7 +4831,7 @@ it is not possible to add this information. 20140621 + change shared-library suffix for AIX 5 and 6 to ".so", avoiding conflict with the static library (report by Ben Lentz). - + document RPATH_LIST in INSTALLATION file, as part of workarounds for + + document RPATH_LIST in INSTALL file, as part of workarounds for upgrading an ncurses library using the "--with-shared" option. + modify test/ncurses.c c/C tests to cycle through subsets of the total number of colors, to better illustrate 8/16/88/256-colors by @@ -10577,7 +11146,7 @@ it is not possible to add this information. (adapted from a patch by Ilya Zakharevich). + correct parameter types of vidputs() and vidattr() to agree with header files (report by William P Setzer). - + fix typos in several man-pages (patch by William P Setzer). + + fix typos in several man pages (patch by William P Setzer). + remove unneeded ifdef for __GNUG__ in CF_CPP_VSCAN_FUNC configure macro, which made ncurses C++ binding fail to build with other C++ compilers such as HPUX 11.x (report by Albert Chin-A-Young). @@ -10630,7 +11199,7 @@ it is not possible to add this information. wide-character structures (report by ). + ensure that _XOPEN_SOURCE_EXTENDED is defined in curses.priv.h if compiling for wide-character configuration. - + make addwnstr() handle non-spacing characters (patch by Sven + + make addnwstr() handle non-spacing characters (patch by Sven Verdoolaege). 20010630 @@ -11109,7 +11678,7 @@ it is not possible to add this information. absolute pathname for the build tree's lib directory (prompted by discussion with Albert Chin-A-Young). + modify "make install.man" and "make uninstall.man" to include tack's - man-page. + man page. + various fixes for install scripts used to support configure --srcdir and --with-install-prefix (reported by Matthew Clarke ). @@ -11336,7 +11905,7 @@ it is not possible to add this information. 20000708 5.1 release for upload to ftp.gnu.org + document configure options in INSTALL. - + add man-page for ncurses trace functions. + + add man page for ncurses trace functions. + correct return value shown in curs_touch.3x for is_linetouched() and is_wintouched(), in curs_initscr.3x for isendwin(), and in curs_termattr.3x for has_ic() and has_il(). @@ -12465,7 +13034,7 @@ it is not possible to add this information. running screen built with ncurses. + check if tmp_fp is opened in tic.c before closing it (patch by Pavel Roskin ). - + correct several font specification typos in man-pages. + + correct several font specification typos in man pages. 981220 + correct default value for BUILD_CC (reported by Larry Virden). @@ -12814,7 +13383,7 @@ it is not possible to add this information. + modify init_pair so that if a color-pair is reinitialized, we will repaint the areas of the screen whose color changes, like SVr4 curses (reported by Christian Maurer ). - + modify getsyx/setsyx macros to comply with SVr4 man-page which + + modify getsyx/setsyx macros to comply with SVr4 man page which says that leaveok() affects their behavior (report by Darryl Miles, patch by Alexander V Lukyanov). @@ -12827,7 +13396,7 @@ it is not possible to add this information. + implement tparm dynamic variables (reported by Xiaodan Tang). 980613 - + update man-page for for wattr_set, wattr_get (cf: 980509) + + update man page for wattr_set, wattr_get (cf: 980509) + correct limits in hashtest, which would cause nonprinting characters to be written to large screens. + correct configure script, when --without-cxx was specified: the @@ -13009,12 +13578,12 @@ it is not possible to add this information. option (patch by Jesse Thilo). + correct some places in configure script where $enableval was used rather than $withval (patch by Darryl Miles ). - + modify some man-pages so no '.' or '..' falls between TH and SH + + modify some man pages so no '.' or '..' falls between TH and SH macros, to accommodate man_db program (reported by Ian T. Zimmerman ). + terminfo.src 10.2.1 downloaded from ESR's webpage (ESR). > several changes by Juergen Pfeifer: - + add copyright notices (and rcs id's) on remaining man-pages. + + add copyright notices (and rcs id's) on remaining man pages. + corrected prototypes for slk_* functions, using chtype rather than attr_t. + implemented the wcolor_set() and slk_color() functions @@ -13164,7 +13733,7 @@ it is not possible to add this information. implemented. + correct _tracef calls in _tracedump(), which did not separate format from parameters. - + correct getopt string for tic "-o" option, and add it to man-page + + correct getopt string for tic "-o" option, and add it to man page synopsis (reported by Darren Hiebert ). + correct typo in panel/Makefile.in, reversed if-statement in scrolling optimization (Alexander V. Lukyanov). @@ -13251,7 +13820,7 @@ it is not possible to add this information. + resynchronizes the generated html manpages 971213 - + additional fixes for man-pages section-references + + additional fixes for man pages' section references + add (for debugging) a check for ich/ich1 conflict with smir/rmir to tic, etc. + remove hpa/vpa from rxvt terminal description because they are not @@ -13263,7 +13832,7 @@ it is not possible to add this information. + modify protection when installing libraries to (normally) not executable. HP-UX shared libraries are an exception. + add configure check for 'tack'. - + implement script for renaming section-references in man-page install, + + implement script for renaming section references in man page install, for Debian configuration. + add validity-check for SP in trace code in baudrate() (reported by Daniel Weaver). @@ -14398,9 +14967,9 @@ it is not possible to add this information. 970104 + workaround defect in autoconf 2.12 (which terminates configuration if no C++ compiler is found) by adding an option --without-cxx. - + modify several man-pages to use tbl, where .nf/.fi was used (reported + + modify several man pages to use tbl, where .nf/.fi was used (reported by Jesse Thilo). - + correct font-codes in some man-pages (patch by Jesse Thilo + + correct font codes in some man pages (patch by Jesse Thilo ) + use configure script's knowledge of existence of g++ library for the c++ Makefile (reported by Paul Jackson). @@ -14666,7 +15235,7 @@ it is not possible to add this information. simpler to construct tests (for double-check of _nc_hash_map tests). + correct ifdef's for c++ in curses.h + change default xterm type to xterm-x11r6. - + correct quoting in configure that made man-pages installed with + + correct quoting in configure that made man pages installed with $datadir instead of actual terminfo path. + correct whitespace in include/Caps, which caused kf11, clr_eol and clr_end to be omitted from terminfo.5 @@ -14878,7 +15447,7 @@ it is not possible to add this information. 960707 + rollback ESR's #305 change to terminfo.src (it breaks existing applications, e.g., 'less 290'). - + correct path of edit_man.sh, and fix typo that made all man-pages + + correct path of edit_man.sh, and fix typo that made all man pages preformatted. + restore man/menu_requestname.3x omitted in Zeyd's resync (oops). + auto-configure the GCC_PRINTFLIKE/GCC_SCANFLIKE macros (reported by @@ -14890,7 +15459,7 @@ it is not possible to add this information. descriptions. + work around autoconf bug, force $INSTALL to absolute path (reported by Zeyd). - + modify man-page install for BSDI to install preformatted .0 files + + modify man page install for BSDI to install preformatted .0 files (reported by David MacKenzie). + add/use gcc __attribute__ for printf and scanf in curses.h + added SGR attributes test-case to ncurses @@ -14991,7 +15560,7 @@ it is not possible to add this information. + misc/ncurses-intro.html syntax fix (Kajiyama Tamito). 960601 - snapshot - + auto-configure man-page compression-format and renames for Debian. + + auto-configure man page compression format and renames for Debian. + corrected several typos in curses.h.in (i.e., the mvXXXX macros). + re-order curses.priv.h for lint. + added rules for lintlib, lint diff --git a/README.OpenSource b/README.OpenSource index 5d19beb..4bc2e9f 100644 --- a/README.OpenSource +++ b/README.OpenSource @@ -3,9 +3,9 @@ "Name": "ncurses", "License": "MIT", "License File": "COPYING", - "Version Number": "6.5", + "Version Number": "6.6", "Owner": "liyiming13@huawei.com", - "Upstream URL": "https://invisible-mirror.net/archives/ncurses/ncurses-6.5.tar.gz", + "Upstream URL": "https://invisible-mirror.net/archives/ncurses/ncurses-6.6.tar.gz", "Description": "The ncurses (new curses) library is a free software emulation of curses in System V Release 4.0 (SVr4), and more. It uses terminfo format, supports pads and color and multiple highlights and forms characters and function-key mapping, and has all the other SVr4-curses enhancements over BSD curses. SVr4 curses became the basis of X/Open Curses." } ] \ No newline at end of file diff --git a/VERSION b/VERSION index 8ebef8f..f05a0db 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -5:0:10 6.5 20240427 +5:0:10 6.6 20251230 diff --git a/aclocal.m4 b/aclocal.m4 index 1c2b788..1463b24 100644 --- a/aclocal.m4 +++ b/aclocal.m4 @@ -1,5 +1,5 @@ dnl*************************************************************************** -dnl Copyright 2018-2023,2024 Thomas E. Dickey * +dnl Copyright 2018-2024,2025 Thomas E. Dickey * dnl Copyright 1998-2017,2018 Free Software Foundation, Inc. * dnl * dnl Permission is hereby granted, free of charge, to any person obtaining a * @@ -29,7 +29,7 @@ dnl*************************************************************************** dnl dnl Author: Thomas E. Dickey 1995-on dnl -dnl $Id: aclocal.m4,v 1.1069 2024/03/30 22:15:45 tom Exp $ +dnl $Id: aclocal.m4,v 1.1148 2025/12/25 23:44:16 tom Exp $ dnl Macros used in NCURSES auto-configuration script. dnl dnl These macros are maintained separately from NCURSES. The copyright on @@ -42,7 +42,7 @@ dnl https://invisible-island.net/autoconf/my-autoconf.html dnl dnl --------------------------------------------------------------------------- dnl --------------------------------------------------------------------------- -dnl AM_LANGINFO_CODESET version: 7 updated: 2023/01/11 04:05:23 +dnl AM_LANGINFO_CODESET version: 8 updated: 2025/12/22 04:16:14 dnl ------------------- dnl Inserted as requested by gettext 0.10.40 dnl File from /usr/share/aclocal @@ -54,10 +54,10 @@ dnl From Bruno Haible. AC_DEFUN([AM_LANGINFO_CODESET], [ AC_CACHE_CHECK([for nl_langinfo and CODESET], am_cv_langinfo_codeset, - [AC_TRY_LINK([ + [AC_LINK_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default #include ], - [char* cs = nl_langinfo(CODESET); (void)cs], + [char* cs = nl_langinfo(CODESET); (void)cs])], am_cv_langinfo_codeset=yes, am_cv_langinfo_codeset=no) ]) @@ -67,7 +67,7 @@ $ac_includes_default fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_ABI_DEFAULTS version: 5 updated: 2023/10/21 08:54:23 +dnl CF_ABI_DEFAULTS version: 6 updated: 2025/05/17 14:54:28 dnl --------------- dnl Provide configure-script defaults for different ncurses ABIs. AC_DEFUN([CF_ABI_DEFAULTS],[ @@ -79,6 +79,7 @@ cf_dft_chtype=auto cf_dft_ext_colors=no cf_dft_ext_const=no cf_dft_ext_mouse=no +cf_dft_ext_mouse2=no cf_dft_ext_putwin=no cf_dft_ext_spfuncs=no cf_dft_filter_syms=no @@ -86,6 +87,7 @@ cf_dft_interop=no cf_dft_mmask_t=auto cf_dft_opaque_curses=no cf_dft_ordinate_type=short +cf_dft_rgb_color=no cf_dft_signed_char=no cf_dft_tparm_arg=long cf_dft_widec=no @@ -114,8 +116,10 @@ esac case x$cf_cv_abi_default in (x[[789]]) cf_dft_ccharw_max=6 + cf_dft_ext_mouse2=yes cf_dft_mmask_t=uint64_t cf_dft_ordinate_type=int + cf_dft_rgb_color=yes cf_dft_signed_char=yes # also: remove the wgetch-events feature in ABI 7 ;; @@ -286,7 +290,7 @@ CXXFLAGS="$CFLAGS" CFLAGS="$cf_save_CXXFLAGS" ])dnl dnl --------------------------------------------------------------------------- -dnl CF_ADD_INCDIR version: 17 updated: 2021/09/04 06:35:04 +dnl CF_ADD_INCDIR version: 18 updated: 2025/12/22 04:16:14 dnl ------------- dnl Add an include-directory to $CPPFLAGS. Don't add /usr/include, since it is dnl redundant. We don't normally need to add -I/usr/local/include for gcc, @@ -318,8 +322,8 @@ if test -n "$1" ; then then cf_save_CPPFLAGS=$CPPFLAGS CF_APPEND_TEXT(CPPFLAGS,-I$cf_add_incdir) - AC_TRY_COMPILE([#include ], - [printf("Hello")], + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ], + [printf("Hello")])], [], [cf_have_incdir=yes]) CPPFLAGS=$cf_save_CPPFLAGS @@ -478,7 +482,7 @@ dnl Allow user to enable a normally-off option. AC_DEFUN([CF_ARG_ENABLE], [CF_ARG_OPTION($1,[$2],[$3],[$4],no)])dnl dnl --------------------------------------------------------------------------- -dnl CF_ARG_OPTION version: 5 updated: 2015/05/10 19:52:14 +dnl CF_ARG_OPTION version: 6 updated: 2025/08/05 04:09:09 dnl ------------- dnl Restricted form of AC_ARG_ENABLE that ensures user doesn't give bogus dnl values. @@ -487,7 +491,7 @@ dnl Parameters: dnl $1 = option name dnl $2 = help-string dnl $3 = action to perform if option is not default -dnl $4 = action if perform if option is default +dnl $4 = action to perform if option is default dnl $5 = default option value (either 'yes' or 'no') AC_DEFUN([CF_ARG_OPTION], [AC_ARG_ENABLE([$1],[$2],[test "$enableval" != ifelse([$5],no,yes,no) && enableval=ifelse([$5],no,no,yes) @@ -501,7 +505,7 @@ ifelse([$3],,[ :]dnl ])dnl ])])dnl dnl --------------------------------------------------------------------------- -dnl CF_AR_FLAGS version: 9 updated: 2021/01/01 13:31:04 +dnl CF_AR_FLAGS version: 10 updated: 2025/12/14 20:07:31 dnl ----------- dnl Check for suitable "ar" (archiver) options for updating an archive. dnl @@ -547,8 +551,8 @@ AC_CACHE_CHECK(for options to update archives, cf_cv_ar_flags,[ int testdata[[3]] = { 123, 456, 789 }; EOF if AC_TRY_EVAL(ac_compile) ; then - echo "$AR $ARFLAGS $cf_ar_flags conftest.a conftest.$ac_cv_objext" >&AC_FD_CC - $AR $ARFLAGS "$cf_ar_flags" conftest.a "conftest.$ac_cv_objext" 2>&AC_FD_CC 1>/dev/null + echo "$AR $ARFLAGS $cf_ar_flags conftest.a conftest.$ac_cv_objext" >&AS_MESSAGE_LOG_FD + $AR $ARFLAGS "$cf_ar_flags" conftest.a "conftest.$ac_cv_objext" 2>&AS_MESSAGE_LOG_FD 1>/dev/null if test -f conftest.a ; then cf_cv_ar_flags="$cf_ar_flags" break @@ -598,54 +602,25 @@ AC_DEFUN([CF_AWK_BIG_PRINTF], esac ])dnl dnl --------------------------------------------------------------------------- -dnl CF_BOOL_DECL version: 9 updated: 2023/12/03 09:21:34 +dnl CF_BOOL_DECL version: 12 updated: 2025/12/24 12:27:29 dnl ------------ -dnl Test if 'bool' is a builtin type in the configured C++ compiler. Some +dnl Test if 'bool' is a builtin type in the configured C/C++ compiler. Some dnl older compilers (e.g., gcc 2.5.8) don't support 'bool' directly; gcc dnl 2.6.3 does, in anticipation of the ANSI C++ standard. dnl -dnl Treat the configuration-variable specially here, since we're directly -dnl substituting its value (i.e., 1/0). -dnl dnl $1 is the shell variable to store the result in, if not $cv_cv_builtin_bool AC_DEFUN([CF_BOOL_DECL], [ -AC_MSG_CHECKING(if we should include stdbool.h) - -AC_CACHE_VAL(cf_cv_header_stdbool_h,[ - AC_TRY_COMPILE([],[bool foo = false; (void)foo], - [cf_cv_header_stdbool_h=0], - [AC_TRY_COMPILE([ -#ifndef __BEOS__ -#include -#endif -],[bool foo = false; (void)foo], - [cf_cv_header_stdbool_h=1], - [cf_cv_header_stdbool_h=0])])]) - -if test "$cf_cv_header_stdbool_h" = 1 -then AC_MSG_RESULT(yes) -else AC_MSG_RESULT(no) -fi - -AC_MSG_CHECKING([for builtin bool type]) - -AC_CACHE_VAL(ifelse($1,,cf_cv_builtin_bool,[$1]),[ - AC_TRY_COMPILE([ -#include -#include -],[bool x = false; (void)x], - [ifelse($1,,cf_cv_builtin_bool,[$1])=1], - [ifelse($1,,cf_cv_builtin_bool,[$1])=0]) - ]) - -if test "$ifelse($1,,cf_cv_builtin_bool,[$1])" = 1 -then AC_MSG_RESULT(yes) -else AC_MSG_RESULT(no) -fi +AC_REQUIRE([CF_C99_STDBOOL_H]) +AC_CACHE_CHECK(for builtin bool type, ifelse($1,,cf_cv_builtin_bool,[$1]),[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ +$ac_includes_default +],[bool x = false; (void)x])], + [ifelse($1,,cf_cv_builtin_bool,[$1])=yes], + [ifelse($1,,cf_cv_builtin_bool,[$1])=no])]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_BOOL_SIZE version: 20 updated: 2023/02/18 17:41:25 +dnl CF_BOOL_SIZE version: 22 updated: 2025/02/22 20:49:45 dnl ------------ dnl Test for the size of 'bool' in the configured C++ compiler (e.g., a type). dnl Don't bother looking for bool.h, since it has been deprecated. @@ -654,6 +629,7 @@ dnl If the current compiler is C rather than C++, we get the bool definition dnl from . AC_DEFUN([CF_BOOL_SIZE], [ +AC_REQUIRE([CF_C99_STDBOOL_H]) AC_CHECK_SIZEOF(bool,,[ $ac_includes_default @@ -669,7 +645,7 @@ $ac_includes_default #else -#if $cf_cv_header_stdbool_h +#if $USE_STDBOOL_H #include #endif @@ -693,7 +669,7 @@ $ac_includes_default #else -#if $cf_cv_header_stdbool_h +#if $USE_STDBOOL_H #include #endif @@ -702,7 +678,7 @@ $ac_includes_default int main(void) { FILE *fp = fopen("cf_test.out", "w"); - if (fp != 0) { + if (fp != NULL) { bool x = true; if ((bool)(-x) >= 0) fputs("unsigned ", fp); @@ -741,7 +717,7 @@ if test "$cf_cv_type_of_bool" = unknown ; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_BUILD_CC version: 11 updated: 2022/12/04 15:40:08 +dnl CF_BUILD_CC version: 14 updated: 2024/12/14 11:58:01 dnl ----------- dnl If we're cross-compiling, allow the user to override the tools and their dnl options. The configure script is oriented toward identifying the host @@ -819,7 +795,7 @@ if test "$cross_compiling" = yes ; then AC_TRY_RUN([#include int main(int argc, char *argv[]) { - ${cf_cv_main_return:-return}(argc < 0 || argv == 0 || argv[0] == 0); + ${cf_cv_main_return:-return}(argc < 0 || argv == (void*)0 || argv[0] == (void*)0); } ], cf_ok_build_cc=yes, @@ -858,7 +834,7 @@ AC_SUBST(BUILD_EXEEXT) AC_SUBST(BUILD_OBJEXT) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_C11_NORETURN version: 4 updated: 2023/02/18 17:41:25 +dnl CF_C11_NORETURN version: 5 updated: 2025/12/14 17:40:20 dnl --------------- AC_DEFUN([CF_C11_NORETURN], [ @@ -871,12 +847,12 @@ AC_MSG_RESULT($enable_stdnoreturn) if test $enable_stdnoreturn = yes; then AC_CACHE_CHECK([for C11 _Noreturn feature], cf_cv_c11_noreturn, - [AC_TRY_COMPILE([ + [AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default #include static _Noreturn void giveup(void) { exit(0); } ], - [if (feof(stdin)) giveup()], + [if (feof(stdin)) giveup()])], cf_cv_c11_noreturn=yes, cf_cv_c11_noreturn=no) ]) @@ -896,6 +872,27 @@ AC_SUBST(HAVE_STDNORETURN_H) AC_SUBST(STDC_NORETURN) ])dnl dnl --------------------------------------------------------------------------- +dnl CF_C99_STDBOOL_H version: 2 updated: 2025/12/24 12:27:29 +dnl ---------------- +dnl Check if we can compile using and get a valid "bool" type. +AC_DEFUN([CF_C99_STDBOOL_H], +[ +AC_CACHE_CHECK(if we can include stdbool.h,cf_cv_header_stdbool_h,[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ +$ac_includes_default +#include +],[bool foo = false; (void)foo])], + [cf_cv_header_stdbool_h=yes], + [AC_COMPILE_IFELSE([AC_LANG_PROGRAM([],[bool foo = false; (void)foo])], + [cf_cv_header_stdbool_h=no])])]) + +if test "$cf_cv_header_stdbool_h" = yes +then USE_STDBOOL_H=1 +else USE_STDBOOL_H=0 +fi +AC_SUBST(USE_STDBOOL_H) +])dnl +dnl --------------------------------------------------------------------------- dnl CF_CC_ENV_FLAGS version: 11 updated: 2023/02/20 11:15:46 dnl --------------- dnl Check for user's environment-breakage by stuffing CFLAGS/CPPFLAGS content @@ -960,7 +957,7 @@ case "$CC" in esac ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CFG_DEFAULTS version: 16 updated: 2021/01/04 19:33:05 +dnl CF_CFG_DEFAULTS version: 17 updated: 2025/12/24 12:27:29 dnl --------------- dnl Determine the default configuration into which we'll install ncurses. This dnl can be overridden by the user's command-line options. There's two items to @@ -990,7 +987,7 @@ AC_MSG_RESULT($prefix) if test "x$prefix" = "xNONE" ; then AC_MSG_CHECKING(for default include-directory) -test -n "$verbose" && echo 1>&AC_FD_MSG +test -n "$verbose" && echo 1>&AS_MESSAGE_FD for cf_symbol in \ "$includedir" \ "$includedir/ncurses" \ @@ -1005,31 +1002,31 @@ do if test -f "$cf_dir/curses.h" ; then if ( ${FGREP-fgrep} NCURSES_VERSION "$cf_dir/curses.h" >/dev/null 2>&1 ) ; then includedir="$cf_symbol" - test -n "$verbose" && echo $ECHO_N " found " 1>&AC_FD_MSG + test -n "$verbose" && echo $ECHO_N " found " 1>&AS_MESSAGE_FD break fi fi - test -n "$verbose" && echo " tested $cf_dir" 1>&AC_FD_MSG + test -n "$verbose" && echo " tested $cf_dir" 1>&AS_MESSAGE_FD done AC_MSG_RESULT($includedir) fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CGETENT version: 7 updated: 2023/02/18 17:41:25 +dnl CF_CGETENT version: 8 updated: 2025/12/24 12:27:29 dnl ---------- dnl Check if the terminal-capability database functions are available. If not, dnl ncurses has a much-reduced version. AC_DEFUN([CF_CGETENT],[ AC_CACHE_CHECK(for terminal-capability database functions,cf_cv_cgetent,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default],[ - char temp[128]; + char temp[[128]]; char *buf = temp; char *db_array = temp; cgetent(&buf, &db_array, "vt100"); cgetcap(buf, "tc", '='); cgetmatch(buf, "tc"); - ], + ])], [cf_cv_cgetent=yes], [cf_cv_cgetent=no]) ]) @@ -1038,10 +1035,10 @@ if test "$cf_cv_cgetent" = yes then AC_DEFINE(HAVE_BSD_CGETENT,1,[Define to 1 if we have BSD cgetent]) AC_CACHE_CHECK(if cgetent uses const parameter,cf_cv_cgetent_const,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #pragma GCC diagnostic error "-Wincompatible-pointer-types-discards-qualifiers" $ac_includes_default],[ - char temp[128]; + char temp[[128]]; char *buf = temp; #ifndef _NETBSD_SOURCE /* given, since April 2004 in stdlib.h */ const char *db_array = temp; @@ -1049,7 +1046,7 @@ $ac_includes_default],[ #endif cgetcap(buf, "tc", '='); cgetmatch(buf, "tc"); - ], + ])], [cf_cv_cgetent_const=yes], [cf_cv_cgetent_const=no]) ]) @@ -1095,7 +1092,7 @@ if test ".$system_name" != ".$cf_cv_system_name" ; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_ENVIRON version: 5 updated: 2023/02/18 17:41:25 +dnl CF_CHECK_ENVIRON version: 6 updated: 2025/12/24 12:27:29 dnl ---------------- dnl Check for data that is usually declared in , e.g., the 'environ' dnl variable. Define a DECL_xxx symbol if we must declare it ourselves. @@ -1105,9 +1102,9 @@ dnl $2 = the assumed type AC_DEFUN([CF_CHECK_ENVIRON], [ AC_CACHE_CHECK(if external $1 is declared, cf_cv_dcl_$1,[ - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default], - ifelse([$2],,void*,[$2]) x = (ifelse([$2],,void*,[$2])) $1; (void)x, + [ifelse([$2],,void*,[$2]) x = (ifelse([$2],,void*,[$2])) $1; (void)x])], [cf_cv_dcl_$1=yes], [cf_cv_dcl_$1=no]) ]) @@ -1121,7 +1118,7 @@ fi CF_CHECK_EXTERN_DATA($1,ifelse([$2],,int,[$2])) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_ERRNO version: 14 updated: 2023/02/18 17:41:25 +dnl CF_CHECK_ERRNO version: 15 updated: 2025/12/23 18:53:34 dnl -------------- dnl Check for data that is usually declared in or , e.g., dnl the 'errno' variable. Define a DECL_xxx symbol if we must declare it @@ -1132,10 +1129,10 @@ dnl $2 = the assumed type AC_DEFUN([CF_CHECK_ERRNO], [ AC_CACHE_CHECK(if external $1 is declared, cf_cv_dcl_$1,[ - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default #include ], - ifelse([$2],,int,[$2]) x = (ifelse([$2],,int,[$2])) $1; (void)x, + [ifelse([$2],,int,[$2]) x = (ifelse([$2],,int,[$2])) $1; (void)x])], [cf_cv_dcl_$1=yes], [cf_cv_dcl_$1=no]) ]) @@ -1149,7 +1146,7 @@ fi CF_CHECK_EXTERN_DATA($1,ifelse([$2],,int,[$2])) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_EXTERN_DATA version: 5 updated: 2021/09/04 06:35:04 +dnl CF_CHECK_EXTERN_DATA version: 6 updated: 2025/12/23 18:53:34 dnl -------------------- dnl Check for existence of external data in the current set of libraries. If dnl we can modify it, it is real enough. @@ -1158,11 +1155,11 @@ dnl $2 = its type AC_DEFUN([CF_CHECK_EXTERN_DATA], [ AC_CACHE_CHECK(if external $1 exists, cf_cv_have_$1,[ - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #undef $1 extern $2 $1; ], - [$1 = 2], + [$1 = 2])], [cf_cv_have_$1=yes], [cf_cv_have_$1=no]) ]) @@ -1174,7 +1171,7 @@ fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_FVISIBILITY version: 2 updated: 2020/04/04 16:16:13 +dnl CF_CHECK_FVISIBILITY version: 3 updated: 2025/12/24 12:27:29 dnl -------------------- dnl Check whether the compiler understands -fvisibility=hidden dnl @@ -1185,18 +1182,18 @@ AC_DEFUN([CF_CHECK_FVISIBILITY],[ AC_CACHE_CHECK(if $1 -fvisibility=hidden option works,$3,[ cf_save_cflags="[$]$2" $2="[$]$2 -fvisibility=hidden" - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ __attribute__ ((visibility("default"))) int somefunc() {return 42;} ],[ if (somefunc()) return 1; -], +])], [$3=yes], [$3=no]) $2=$cf_save_cflags ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_GETENV version: 4 updated: 2023/12/03 10:18:09 +dnl CF_CHECK_GETENV version: 5 updated: 2024/12/14 16:09:34 dnl --------------- dnl Check if repeated getenv calls return the same pointer, e.g., it does not dnl discard the previous pointer when returning a new one. @@ -1248,7 +1245,7 @@ int main(void) for (j = 0; environ[j]; ++j) { mynames[j] = str_alloc(environ[j]); equals = strchr(mynames[j], '='); - if (equals != 0) { + if (equals != NULL) { *equals++ = '\\0'; myvalues[j] = str_alloc(equals); } else { @@ -1380,26 +1377,26 @@ if test "$cf_cv_check_gpm_wgetch" != yes ; then fi ])])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_LIBSSP version: 1 updated: 2021/10/30 10:40:19 +dnl CF_CHECK_LIBSSP version: 2 updated: 2025/12/24 12:27:29 dnl --------------- dnl Check if libssp is needed, e.g., to work around misconfigured libraries dnl used in cross-compiling to MinGW. AC_DEFUN([CF_CHECK_LIBSSP],[ AC_CACHE_CHECK(if ssp library is needed,cf_cv_need_libssp,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ DIR *dp = opendir("."); -],cf_cv_need_libssp=no,[ +])],cf_cv_need_libssp=no,[ cf_save_LIBS="$LIBS" LIBS="$LIBS -lssp" - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ DIR *dp = opendir("."); - ],cf_cv_need_libssp=yes, + ])],cf_cv_need_libssp=yes, cf_cv_need_libssp=maybe) LIBS="$cf_save_LIBS" ])dnl @@ -1411,7 +1408,7 @@ then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_LIBTOOL_VERSION version: 2 updated: 2021/05/01 16:24:34 +dnl CF_CHECK_LIBTOOL_VERSION version: 3 updated: 2024/06/12 04:19:01 dnl ------------------------ dnl Show the version of libtool dnl @@ -1427,6 +1424,7 @@ then AC_MSG_CHECKING(version of $LIBTOOL) CF_LIBTOOL_VERSION AC_MSG_RESULT($cf_cv_libtool_version) + ifdef([LT_PACKAGE_VERSION],,[ if test -n "$cf_cv_libtool_version" then cf_check_libtool_version=`$LIBTOOL --version 2>&1 | sed -e '/^$/d' -e 's,[[()]],...,g' -e 's,[[ ]],-,g' -e '2,$d'` @@ -1440,12 +1438,107 @@ then else AC_MSG_ERROR(No version found for $LIBTOOL) fi + ]) else AC_MSG_ERROR(GNU libtool has not been found) fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_WCHAR_H version: 5 updated: 2023/12/03 09:21:34 +dnl CF_CHECK_MULTIUSER version: 1 updated: 2025/09/13 11:43:46 +dnl ------------------ +dnl Runtime features which check for root permissions apply only to multiuser +dnl systems. Check for single-user systems by inspecting /etc/passwd. +AC_DEFUN([CF_CHECK_MULTIUSER],[ +AC_CACHE_CHECK(for conventional multiuser system,cf_cv_multiuser,[ + cf_cv_multiuser=no + if test -f /etc/passwd + then + sed \ + -e '/true$/d' \ + -e '/false$/d' \ + -e '/nologin$/d' \ + -e '/^[[^:]]*:[[^:]]*:[[0-9]]:/d' \ + -e '/^[[^:]]*:[[^:]]*:[[0-9]][[0-9]]:/d' \ + -e '/:$/d' < /etc/passwd >conftest.tmp + test -s conftest.tmp && cf_cv_multiuser=yes + rm -f conftest.tmp + fi +]) +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_CHECK_NAMED_PIPES version: 2 updated: 2025/12/24 12:27:29 +dnl -------------------- +dnl Check for existence of Windows named-pipe functions, set cache variable +dnl to reflect the result. +AC_DEFUN([CF_CHECK_NAMED_PIPES],[ +AC_CACHE_CHECK(for named pipe functions,cf_cv_named_pipes,[ + cf_save_CPPFLAGS="$CPPFLAGS" + CPPFLAGS="$CPPFLAGS -DWINVER=0x0600 -DWIN32_LEAN_AND_MEAN" + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include ], + [ + HANDLE handle = 0; + ULONG pPid = 0; + if (GetNamedPipeInfo(handle, NULL, NULL, NULL, NULL)) { + if (GetNamedPipeServerProcessId(handle, &pPid)) { + ${cf_cv_main_return:-return} (0); + } + } + ])],[cf_cv_named_pipes=yes],[cf_cv_named_pipes=no]) + CPPFLAGS="$cf_save_CPPFLAGS" +])dnl +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_CHECK_TBL_X_OPTION version: 2 updated: 2025/11/11 20:09:36 +dnl --------------------- +AC_DEFUN([CF_CHECK_TBL_X_OPTION],[ +AC_REQUIRE([CF_PROG_TBL]) + +AC_CACHE_CHECK(if $NROFF_TBL supports 'x' column modifier,cf_cv_tbl_x_option_okay,[ + if test "$cross_compiling" = yes ; then + cf_cv_tbl_x_option_okay=unknown + else + cf_cv_tbl_x_option_okay=no + cat > conftest <<-CF_EOF + .TS + L. + table cell + .TE + CF_EOF + if $NROFF_TBL < conftest > /dev/null 2>&1 + then + cat > conftest <<-CF_EOF + .TS + Lx. + table cell + .TE + CF_EOF + if $NROFF_TBL < conftest > /dev/null 2>&1 + then + cf_cv_tbl_x_option_okay=yes + fi + else + AC_MSG_ERROR([$NROFF_TBL not available.]) + fi + rm -f conftest + fi +]) + +TBL_X_OPTION=$cf_cv_tbl_x_option_okay +AC_SUBST(TBL_X_OPTION) +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_CHECK_TYPE2 version: 3 updated: 2025/08/08 20:44:18 +dnl -------------- +dnl Check if the given type can be declared via the given header. +dnl $1 = the type to check +dnl $2 = the header (i.e., not one of the default includes) +AC_DEFUN([CF_CHECK_TYPE2],[ + AC_CHECK_TYPES($1,,,[ +$ac_includes_default +ifelse($2,,,[#include <$2>])]) +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_CHECK_WCHAR_H version: 6 updated: 2025/12/24 12:27:29 dnl ---------------- dnl Check if wchar.h can be used, i.e., without defining _XOPEN_SOURCE_EXTENDED AC_DEFUN([CF_CHECK_WCHAR_H],[ @@ -1454,7 +1547,7 @@ wchar.h \ wctype.h \ ) AC_CACHE_CHECK(if wchar.h can be used as is,cf_cv_wchar_h_okay,[ -AC_TRY_COMPILE( +AC_COMPILE_IFELSE([AC_LANG_PROGRAM( [ $ac_includes_default #ifdef HAVE_WCHAR_H @@ -1465,7 +1558,7 @@ $ac_includes_default #endif ],[ wint_t foo = 0; - int bar = iswpunct(foo); (void) bar], + int bar = iswpunct(foo); (void) bar])], [cf_cv_wchar_h_okay=yes], [cf_cv_wchar_h_okay=no])]) @@ -1475,7 +1568,7 @@ then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CHECK_WCWIDTH_GRAPHICS version: 4 updated: 2023/12/03 10:17:07 +dnl CF_CHECK_WCWIDTH_GRAPHICS version: 5 updated: 2024/12/14 16:09:34 dnl ------------------------- dnl Most "modern" terminal emulators are based to some degree on VT100, and dnl should support line-drawing. Even with Unicode. There is a problem. @@ -1594,8 +1687,8 @@ main(void) setlocale(LC_ALL, "en_US.UTF-8") || setlocale(LC_ALL, "en_US.utf8") || setlocale(LC_ALL, "en_US.utf-8")) { - if ((fp = fopen("conftest.in", "r")) != 0) { - while (fgets(buffer, MY_LEN, fp) != 0) { + if ((fp = fopen("conftest.in", "r")) != NULL) { + while (fgets(buffer, MY_LEN, fp) != NULL) { if (*buffer == '-') { fprintf(stderr, "\\t%s", buffer); } else if (sscanf(buffer, "%x %s", &value, notes) == 2) { @@ -1619,7 +1712,7 @@ main(void) ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CLANG_COMPILER version: 9 updated: 2023/02/18 17:41:25 +dnl CF_CLANG_COMPILER version: 11 updated: 2025/12/14 17:46:02 dnl ----------------- dnl Check if the given compiler is really clang. clang's C driver defines dnl __GNUC__ (fooling the configure script into setting $GCC to yes) but does @@ -1638,12 +1731,12 @@ ifelse([$2],,CLANG_COMPILER,[$2])=no if test "$ifelse([$1],,[$1],GCC)" = yes ; then AC_MSG_CHECKING(if this is really Clang ifelse([$1],GXX,C++,C) compiler) cf_save_CFLAGS="$ifelse([$3],,CFLAGS,[$3])" - AC_TRY_COMPILE([],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([],[ #ifdef __clang__ #else #error __clang__ is not defined #endif -],[ifelse([$2],,CLANG_COMPILER,[$2])=yes +])],[ifelse([$2],,CLANG_COMPILER,[$2])=yes ],[]) ifelse([$3],,CFLAGS,[$3])="$cf_save_CFLAGS" AC_MSG_RESULT($ifelse([$2],,CLANG_COMPILER,[$2])) @@ -1672,9 +1765,9 @@ if test "x$ifelse([$2],,CLANG_COMPILER,[$2])" = "xyes" ; then AC_MSG_CHECKING(if option $cf_clang_opt works) cf_save_CFLAGS="$CFLAGS" CFLAGS="$CFLAGS $cf_clang_opt" - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ - printf("hello!\\n");],[ + printf("hello!\\n");])],[ cf_clang_optok=yes],[ cf_clang_optok=no]) AC_MSG_RESULT($cf_clang_optok) @@ -1687,7 +1780,7 @@ if test "x$ifelse([$2],,CLANG_COMPILER,[$2])" = "xyes" ; then fi ]) dnl --------------------------------------------------------------------------- -dnl CF_CONST_X_STRING version: 8 updated: 2023/12/01 17:22:50 +dnl CF_CONST_X_STRING version: 10 updated: 2025/12/14 17:40:20 dnl ----------------- dnl The X11R4-X11R6 Xt specification uses an ambiguous String type for most dnl character-strings. @@ -1712,22 +1805,22 @@ AC_REQUIRE([AC_PATH_XTRA]) CF_SAVE_XTRA_FLAGS([CF_CONST_X_STRING]) -AC_TRY_COMPILE( +AC_COMPILE_IFELSE([AC_LANG_PROGRAM( [ -#include +$ac_includes_default #include ], -[String foo = malloc(1); free((void*)foo)],[ +[String foo = malloc(1); free((void*)foo)])],[ AC_CACHE_CHECK(for X11/Xt const-feature,cf_cv_const_x_string,[ - AC_TRY_COMPILE( + AC_COMPILE_IFELSE([AC_LANG_PROGRAM( [ #undef _CONST_X_STRING #define _CONST_X_STRING /* X11R7.8 (perhaps) */ #undef XTSTRINGDEFINES /* X11R5 and later */ -#include +$ac_includes_default #include - ],[String foo = malloc(1); *foo = 0],[ + ],[String foo = malloc(1); *foo = 0])],[ cf_cv_const_x_string=no ],[ cf_cv_const_x_string=yes @@ -1748,7 +1841,7 @@ esac ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CPP_OVERRIDE version: 1 updated: 2022/08/20 16:07:10 +dnl CF_CPP_OVERRIDE version: 2 updated: 2024/11/09 18:07:29 dnl --------------- dnl Check if the C++ compiler accepts the override keyword. This is a C++-11 dnl feature. @@ -1763,7 +1856,7 @@ AC_CACHE_CHECK(if $CXX accepts override keyword,cf_cv_cpp_override,[ class base { public: - virtual int foo(float x) = 0; + virtual int foo(float x) = 0; }; @@ -1819,7 +1912,7 @@ fi test "$cf_cv_cpp_param_init" = yes && AC_DEFINE(CPP_HAS_PARAM_INIT,1,[Define to 1 if C++ has parameter initialization]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CPP_STATIC_CAST version: 3 updated: 2013/04/13 18:03:21 +dnl CF_CPP_STATIC_CAST version: 4 updated: 2025/12/24 12:27:29 dnl ------------------ dnl Check if the C++ compiler accepts static_cast in generics. This appears to dnl not be supported in g++ before 3.0 @@ -1831,7 +1924,7 @@ AC_CACHE_CHECK(if $CXX accepts static_cast,cf_cv_cpp_static_cast,[ AC_LANG_SAVE AC_LANG_CPLUSPLUS - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ class NCursesPanel { public: @@ -1863,7 +1956,7 @@ public: virtual ~NCursesUserPanel() {}; }; ],[ - const char* p_UserData = static_cast(0)], + const char* p_UserData = static_cast(0)])], [cf_cv_cpp_static_cast=yes], [cf_cv_cpp_static_cast=no]) @@ -1903,19 +1996,19 @@ AC_DEFUN([CF_CXX_AR_FLAGS],[ AC_SUBST(CXX_ARFLAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CXX_IOSTREAM_NAMESPACE version: 2 updated: 2012/10/06 17:56:13 +dnl CF_CXX_IOSTREAM_NAMESPACE version: 3 updated: 2025/12/24 12:27:29 dnl ------------------------- dnl For c++, check if iostream uses "std::" namespace. AC_DEFUN([CF_CXX_IOSTREAM_NAMESPACE],[ AC_CHECK_HEADERS(iostream) if test x"$ac_cv_header_iostream" = xyes ; then AC_MSG_CHECKING(if iostream uses std-namespace) - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include using std::endl; using std::cerr;],[ cerr << "testing" << endl; -],[cf_iostream_namespace=yes],[cf_iostream_namespace=no]) +])],[cf_iostream_namespace=yes],[cf_iostream_namespace=no]) AC_MSG_RESULT($cf_iostream_namespace) if test "$cf_iostream_namespace" = yes ; then AC_DEFINE(IOSTREAM_NAMESPACE,1,[Define to 1 if C++ has namespace iostream]) @@ -1923,7 +2016,7 @@ cerr << "testing" << endl; fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_C_INLINE version: 6 updated: 2019/09/07 13:38:36 +dnl CF_C_INLINE version: 7 updated: 2025/12/24 12:27:29 dnl ----------- dnl Check if the C compiler supports "inline". dnl $1 is the name of a shell variable to set if inline is supported @@ -1945,8 +2038,8 @@ if test "$ac_cv_c_inline" != no ; then AC_CACHE_CHECK(if $CC supports options to tune inlining,cf_cv_gcc_inline,[ cf_save_CFLAGS=$CFLAGS CFLAGS="$CFLAGS --param max-inline-insns-single=$2" - AC_TRY_COMPILE([inline int foo(void) { return 1; }], - [${cf_cv_main_return:-return} foo()], + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([inline int foo(void) { return 1; }], + [${cf_cv_main_return:-return} foo()])], [cf_cv_gcc_inline=yes], [cf_cv_gcc_inline=no]) CFLAGS=$cf_save_CFLAGS @@ -2196,7 +2289,7 @@ AC_ARG_ENABLE(rpath, AC_MSG_RESULT($cf_cv_enable_rpath) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_ENABLE_STRING_HACKS version: 6 updated: 2021/01/05 19:23:48 +dnl CF_ENABLE_STRING_HACKS version: 7 updated: 2025/11/11 20:09:36 dnl ---------------------- dnl On a few platforms, the compiler and/or loader nags with untruthful dnl comments stating that "most" uses of strcat/strcpy/sprintf are incorrect, @@ -2207,10 +2300,10 @@ dnl functions versus the total of incorrect uses. Samples of a few thousand dnl instances are meaningless compared to the hundreds of millions of lines of dnl existing C code. dnl -dnl strlcat/strlcpy are (as of 2012) non-standard, and are available on some +dnl strlcat/strlcpy are standard as of POSIX.1-2024, and are available on some dnl platforms, in implementations of varying quality. Likewise, snprintf is dnl standard - but evolved through phases, and older implementations are likely -dnl to yield surprising results, as documented in manpages on various systems. +dnl to yield surprising results, as documented in man pages on various systems. AC_DEFUN([CF_ENABLE_STRING_HACKS], [ AC_MSG_CHECKING(if you want to work around bogus compiler/loader warnings) @@ -2274,7 +2367,7 @@ AC_DEFUN([CF_ERRNO], CF_CHECK_ERRNO(errno) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_ETIP_DEFINES version: 7 updated: 2023/10/28 11:59:01 +dnl CF_ETIP_DEFINES version: 8 updated: 2025/12/24 12:27:29 dnl --------------- dnl Test for conflicting definitions of exception in gcc 2.8.0, etc., between dnl math.h and builtin.h, only for ncurses @@ -2296,9 +2389,9 @@ do CXXFLAGS="$cf_save_CXXFLAGS -I${srcdir}/c++ -I${srcdir}/menu -Iinclude -I${srcdir}/include" test -n "$cf_math" && CXXFLAGS="$CXXFLAGS -DETIP_NEEDS_${cf_math}" test -n "$cf_excp" && CXXFLAGS="$CXXFLAGS -DETIP_NEEDS_${cf_excp}" -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include -],[],[ +],[])],[ test -n "$cf_math" && AC_DEFINE_UNQUOTED(ETIP_NEEDS_${cf_math}) test -n "$cf_excp" && AC_DEFINE_UNQUOTED(ETIP_NEEDS_${cf_excp}) cf_result="$cf_math $cf_excp" @@ -2310,7 +2403,7 @@ AC_MSG_RESULT([${cf_result:-(none)}]) CXXFLAGS="$cf_save_CXXFLAGS" ]) dnl --------------------------------------------------------------------------- -dnl CF_FIND_LINKAGE version: 22 updated: 2020/12/31 20:19:42 +dnl CF_FIND_LINKAGE version: 23 updated: 2025/12/22 04:16:14 dnl --------------- dnl Find a library (specifically the linkage used in the code fragment), dnl searching for it if it is not already in the library path. @@ -2333,7 +2426,7 @@ dnl $cf_cv_library_file_$3 - library-file if needed, e.g., -l$3 AC_DEFUN([CF_FIND_LINKAGE],[ # If the linkage is not already in the $CPPFLAGS/$LDFLAGS configuration, these -# will be set on completion of the AC_TRY_LINK below. +# will be set on completion of the AC_LINK_IFELSE below. cf_cv_header_path_$3= cf_cv_library_path_$3= @@ -2341,7 +2434,7 @@ CF_MSG_LOG([Starting [FIND_LINKAGE]($3,$6)]) cf_save_LIBS="$LIBS" -AC_TRY_LINK([$1],[$2],[ +AC_LINK_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ cf_cv_find_linkage_$3=yes cf_cv_header_path_$3=/usr/include cf_cv_library_path_$3=/usr/lib @@ -2349,7 +2442,7 @@ AC_TRY_LINK([$1],[$2],[ LIBS="-l$3 $7 $cf_save_LIBS" -AC_TRY_LINK([$1],[$2],[ +AC_LINK_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ cf_cv_find_linkage_$3=yes cf_cv_header_path_$3=/usr/include cf_cv_library_path_$3=/usr/lib @@ -2371,7 +2464,7 @@ AC_TRY_LINK([$1],[$2],[ CF_VERBOSE(... testing $cf_cv_header_path_$3) CPPFLAGS="$cf_save_CPPFLAGS" CF_APPEND_TEXT(CPPFLAGS,-I$cf_cv_header_path_$3) - AC_TRY_COMPILE([$1],[$2],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ CF_VERBOSE(... found $3 headers in $cf_cv_header_path_$3) cf_cv_find_linkage_$3=maybe cf_test_CPPFLAGS="$CPPFLAGS" @@ -2391,7 +2484,7 @@ AC_TRY_LINK([$1],[$2],[ ifelse([$6],,,[ CPPFLAGS="$cf_test_CPPFLAGS" LIBS="-l$3 $7 $cf_save_LIBS" - AC_TRY_LINK([$1],[$2],[ + AC_LINK_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ CF_VERBOSE(... found $3 library in system) cf_cv_find_linkage_$3=yes]) CPPFLAGS="$cf_save_CPPFLAGS" @@ -2407,7 +2500,7 @@ AC_TRY_LINK([$1],[$2],[ CPPFLAGS="$cf_test_CPPFLAGS" LIBS="-l$3 $7 $cf_save_LIBS" LDFLAGS="$cf_save_LDFLAGS -L$cf_cv_library_path_$3" - AC_TRY_LINK([$1],[$2],[ + AC_LINK_IFELSE([AC_LANG_PROGRAM([$1],[$2])],[ CF_VERBOSE(... found $3 library in $cf_cv_library_path_$3) cf_cv_find_linkage_$3=yes cf_cv_library_file_$3="-l$3" @@ -2534,7 +2627,7 @@ fi AC_SUBST(EXTRA_CFLAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_FOPEN_BIN_R version: 3 updated: 2023/01/05 18:05:46 +dnl CF_FOPEN_BIN_R version: 4 updated: 2024/12/14 16:09:34 dnl -------------- dnl Check if fopen works when the "b" (binary) flag is added to the mode dnl parameter. POSIX ignores the "b", which c89 specified. Some very old @@ -2548,14 +2641,14 @@ int main(void) { FILE *fp = fopen("conftest.tmp", "wb"); int rc = 0; - if (fp != 0) { + if (fp != NULL) { int p, q; for (p = 0; p < 256; ++p) { fputc(p, fp); } fclose(fp); fp = fopen("conftest.tmp", "rb"); - if (fp != 0) { + if (fp != NULL) { for (p = 0; p < 256; ++p) { q = fgetc(fp); if (q != p) { @@ -2588,7 +2681,7 @@ unset ac_ct_$1 unset $1 ])dnl dnl --------------------------------------------------------------------------- -dnl CF_FUNC_DLSYM version: 4 updated: 2015/09/12 14:46:44 +dnl CF_FUNC_DLSYM version: 6 updated: 2025/12/24 12:27:29 dnl ------------- dnl Test for dlsym() and related functions, as well as libdl. dnl @@ -2608,13 +2701,16 @@ if test "$cf_have_dlsym" = yes ; then test "$cf_have_libdl" = yes && { CF_ADD_LIB(dl) } AC_MSG_CHECKING(whether able to link to dl*() functions) - AC_TRY_LINK([#include ],[ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ + #include + #include + ],[ void *obj; - if ((obj = dlopen("filename", 0)) != 0) { + if ((obj = dlopen("filename", 0)) != NULL) { if (dlsym(obj, "symbolname") == 0) { dlclose(obj); } - }],[ + }])],[ AC_DEFINE(HAVE_LIBDL,1,[Define to 1 if we have dl library])],[ AC_MSG_ERROR(Cannot link test program for libdl)]) AC_MSG_RESULT(ok) @@ -2623,19 +2719,36 @@ else fi ]) dnl --------------------------------------------------------------------------- -dnl CF_FUNC_GETTIME version: 2 updated: 2023/02/25 08:45:56 +dnl CF_FUNC_GETTIME version: 4 updated: 2025/12/23 18:53:34 dnl --------------- dnl Check for gettimeofday or clock_gettime. In 2023, the former is still more dnl widely supported, but "deprecated" (2008), so we will use the latter if it dnl is available, to reduce compiler warnings. AC_DEFUN([CF_FUNC_GETTIME],[ -AC_CACHE_CHECK(for clock_gettime,cf_cv_func_clock_gettime,[ - AC_TRY_LINK([#include ], +cf_save_libs="$LIBS" +AC_CHECK_FUNC(clock_gettime, + cf_cv_test_clock_gettime=yes, + AC_CHECK_LIB(rt, clock_gettime, + [LIBS="-lrt $LIBS" + cf_cv_test_clock_gettime=yes], + cf_cv_test_clock_gettime=no)) + +if test "$cf_cv_test_clock_gettime" = yes ; then +AC_CACHE_CHECK(if clock_gettime links,cf_cv_func_clock_gettime,[ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ +$ac_includes_default +#include + ], [struct timespec ts; - int rc = clock_gettime(CLOCK_REALTIME, &ts); (void) rc; (void)ts], + int rc = clock_gettime(CLOCK_REALTIME, &ts) + + clock_gettime(CLOCK_MONOTONIC, &ts); + (void) rc; (void)ts])], [cf_cv_func_clock_gettime=yes], [cf_cv_func_clock_gettime=no]) ]) +else + cf_cv_func_clock_gettime=no +fi if test "$cf_cv_func_clock_gettime" = yes then @@ -2650,17 +2763,17 @@ AC_CHECK_LIB(bsd, gettimeofday, fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_FUNC_GETTTYNAM version: 2 updated: 2023/01/05 18:06:28 +dnl CF_FUNC_GETTTYNAM version: 5 updated: 2025/12/24 12:27:29 dnl ----------------- dnl Check if the 4.3BSD function getttyname exists, as well as if dnl defines the _PATH_TTYS symbol. If the corresponding file exists, but the dnl other checks fail, just define HAVE_PATH_TTYS. AC_DEFUN([CF_FUNC_GETTTYNAM],[ AC_CACHE_CHECK(if _PATH_TTYS is defined in ttyent.h,cf_cv_PATH_TTYS,[ -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ -FILE *fp = fopen(_PATH_TTYS, "r"); (void)fp], +FILE *fp = fopen(_PATH_TTYS, "r"); (void)fp])], [cf_cv_PATH_TTYS=yes], [cf_cv_PATH_TTYS=no])]) @@ -2682,12 +2795,11 @@ then AC_CACHE_CHECK(if _PATH_TTYS file exists,cf_cv_have_PATH_TTYS,[ AC_TRY_RUN([ $ac_includes_default - #include int main(void) { FILE *fp = fopen(_PATH_TTYS, "r"); - ${cf_cv_main_return:-return} (fp == 0); + ${cf_cv_main_return:-return} (fp == NULL); }], [cf_cv_have_PATH_TTYS=yes], [cf_cv_have_PATH_TTYS=no], @@ -2699,11 +2811,11 @@ if test $cf_cv_PATH_TTYS != no then AC_DEFINE(HAVE_PATH_TTYS,1,[define to 1 if system can map tty name to terminal type]) AC_CACHE_CHECK(for getttynam,cf_cv_func_getttynam,[ - AC_TRY_LINK([#include ], - [struct ttyent *fp = getttynam("/dev/tty"); (void)fp], + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include ], + [struct ttyent *fp = getttynam("/dev/tty"); (void)fp])], [cf_cv_func_getttynam=yes], [cf_cv_func_getttynam=no])]) - test "$cf_cv_func_getttynam" = yes && AC_DEFINE(HAVE_GETTTYNAM) + test "$cf_cv_func_getttynam" = yes && AC_DEFINE(HAVE_GETTTYNAM,1,[define to 1 if the system has getttynam()]) fi ])dnl dnl --------------------------------------------------------------------------- @@ -2775,7 +2887,7 @@ int main(void) { test "$cf_cv_func_nanosleep" = "yes" && AC_DEFINE(HAVE_NANOSLEEP,1,[Define to 1 if we have nanosleep()]) ]) dnl --------------------------------------------------------------------------- -dnl CF_FUNC_OPENPTY version: 7 updated: 2023/12/03 09:21:34 +dnl CF_FUNC_OPENPTY version: 8 updated: 2025/12/24 12:27:29 dnl --------------- dnl Check for openpty() function, along with header. It may need the dnl "util" library as well. @@ -2787,13 +2899,13 @@ AC_CACHE_CHECK(for openpty header,cf_cv_func_openpty,[ test "$cf_cv_lib_util" = yes && { CF_ADD_LIB(util) } for cf_header in pty.h libutil.h util.h do - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include <$cf_header> ],[ int x = openpty((int *)0, (int *)0, (char *)0, (struct termios *)0, (struct winsize *)0); (void)x; -],[ +])],[ cf_cv_func_openpty=$cf_header break ],[ @@ -2866,14 +2978,14 @@ int main(void) { test "$cf_cv_working_poll" = "yes" && AC_DEFINE(HAVE_WORKING_POLL,1,[Define to 1 if the poll function seems to work]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_FUNC_TERMIOS version: 3 updated: 2012/10/06 17:56:13 +dnl CF_FUNC_TERMIOS version: 4 updated: 2025/12/24 12:27:29 dnl --------------- dnl Some old/broken variations define tcgetattr() only as a macro in dnl termio(s).h AC_DEFUN([CF_FUNC_TERMIOS],[ AC_REQUIRE([CF_STRUCT_TERMIOS]) AC_CACHE_CHECK(for tcgetattr, cf_cv_have_tcgetattr,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #ifdef HAVE_UNISTD_H #include @@ -2889,13 +3001,13 @@ AC_TRY_LINK([ #endif ],[ TTY foo; -tcgetattr(1, &foo);], +tcgetattr(1, &foo);])], [cf_cv_have_tcgetattr=yes], [cf_cv_have_tcgetattr=no])]) test "$cf_cv_have_tcgetattr" = yes && AC_DEFINE(HAVE_TCGETATTR,1,[Define to 1 if we have tcgetattr]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_FUNC_VSSCANF version: 8 updated: 2023/12/03 19:09:59 +dnl CF_FUNC_VSSCANF version: 9 updated: 2025/12/24 12:27:29 dnl --------------- dnl Check for vsscanf() function, which is in c9x but generally not in earlier dnl versions of C. It can often be simulated by other functions on older @@ -2903,7 +3015,7 @@ dnl systems (where FILE is not opaque). AC_DEFUN([CF_FUNC_VSSCANF], [ AC_CACHE_CHECK(for vsscanf function or workaround,cf_cv_func_vsscanf,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #include @@ -2917,8 +3029,8 @@ myfunc(const char *str, const char *fmt, ...) } ],[ myfunc("55", "%d"); -],[cf_cv_func_vsscanf=vsscanf],[ -AC_TRY_LINK([ +])],[cf_cv_func_vsscanf=vsscanf],[ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ FILE strbuf; @@ -2928,8 +3040,8 @@ AC_TRY_LINK([ strbuf._ptr = strbuf._base = (unsigned char *) str; strbuf._cnt = strlen(str); strbuf._file = _NFILE; - return (vfscanf(&strbuf, "%d", ap))],[cf_cv_func_vsscanf=vfscanf],[ -AC_TRY_LINK([ + return (vfscanf(&strbuf, "%d", ap))])],[cf_cv_func_vsscanf=vfscanf],[ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ FILE strbuf; @@ -2939,7 +3051,7 @@ AC_TRY_LINK([ strbuf._ptr = strbuf._base = (unsigned char *) str; strbuf._cnt = strlen(str); strbuf._file = _NFILE; - return (_doscan(&strbuf, "%d", ap))],[cf_cv_func_vsscanf=_doscan],[ + return (_doscan(&strbuf, "%d", ap))])],[cf_cv_func_vsscanf=_doscan],[ cf_cv_func_vsscanf=no])])])]) case "$cf_cv_func_vsscanf" in @@ -2950,7 +3062,7 @@ esac ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GCC_ATTRIBUTES version: 24 updated: 2021/03/20 12:00:25 +dnl CF_GCC_ATTRIBUTES version: 28 updated: 2025/12/25 18:43:31 dnl ----------------- dnl Test for availability of useful gcc __attribute__ directives to quiet dnl compiler warnings. Though useful, not all are supported -- and contrary @@ -2977,7 +3089,8 @@ cat > conftest.i < "conftest.$ac_ext" < @@ -3005,7 +3118,7 @@ EOF do CF_UPPER(cf_ATTRIBUTE,$cf_attribute) cf_directive="__attribute__(($cf_attribute))" - echo "checking for $CC $cf_directive" 1>&AC_FD_CC + echo "checking for $CC $cf_directive" 1>&AS_MESSAGE_LOG_FD case "$cf_attribute" in (printf) @@ -3080,7 +3193,7 @@ CF_INTEL_COMPILER(GCC,INTEL_COMPILER,CFLAGS) CF_CLANG_COMPILER(GCC,CLANG_COMPILER,CFLAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GCC_WARNINGS version: 41 updated: 2021/01/01 16:53:59 +dnl CF_GCC_WARNINGS version: 45 updated: 2025/12/24 09:07:25 dnl --------------- dnl Check if the compiler supports useful warning options. There's a few that dnl we don't use, simply because they're too noisy: @@ -3121,7 +3234,8 @@ then # remark #981: operands are evaluated in unspecified order # warning #279: controlling expression is constant - AC_CHECKING([for $CC warning options]) + AC_MSG_CHECKING([for $CC warning options]) + test -n "$verbose" && AC_MSG_RESULT() cf_save_CFLAGS="$CFLAGS" EXTRA_CFLAGS="$EXTRA_CFLAGS -Wall" for cf_opt in \ @@ -3144,7 +3258,8 @@ then CFLAGS="$cf_save_CFLAGS" elif test "$GCC" = yes && test "$GCC_VERSION" != "unknown" then - AC_CHECKING([for $CC warning options]) + AC_MSG_CHECKING([for $CC warning options]) + test -n "$verbose" && AC_MSG_RESULT() cf_save_CFLAGS="$CFLAGS" cf_warn_CONST="" test "$with_ext_const" = yes && cf_warn_CONST="Wwrite-strings" @@ -3194,20 +3309,21 @@ rm -rf ./conftest* AC_SUBST(EXTRA_CFLAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GETOPT_HEADER version: 8 updated: 2021/06/19 19:16:16 +dnl CF_GETOPT_HEADER version: 10 updated: 2025/12/14 17:40:20 dnl ---------------- dnl Check for getopt's variables which are commonly defined in stdlib.h, dnl unistd.h or (nonstandard) in getopt.h AC_DEFUN([CF_GETOPT_HEADER], -[ -AC_HAVE_HEADERS(unistd.h getopt.h) +[AC_REQUIRE([AC_HEADER_STDC]) + +AC_CHECK_HEADERS(getopt.h) AC_CACHE_CHECK(for header declaring getopt variables,cf_cv_getopt_header,[ cf_cv_getopt_header=none for cf_header in stdio.h stdlib.h unistd.h getopt.h do -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include <$cf_header>], -[int x = optind; char *y = optarg; (void)x; (void)y], +[int x = optind; char *y = optarg; (void)x; (void)y])], [cf_cv_getopt_header=$cf_header break]) done @@ -3220,6 +3336,26 @@ if test "$cf_cv_getopt_header" = getopt.h ; then fi ])dnl dnl --------------------------------------------------------------------------- +dnl CF_GLOB_FULLPATH version: 2 updated: 2024/08/03 12:34:02 +dnl ---------------- +dnl Use this in case-statements to check for pathname syntax, i.e., absolute +dnl pathnames. The "x" is assumed since we provide an alternate form for DOS. +AC_DEFUN([CF_GLOB_FULLPATH],[ +AC_REQUIRE([CF_WITH_SYSTYPE])dnl +case "$cf_cv_system_name" in +(cygwin*|msys*|mingw32*|mingw64|os2*) + GLOB_FULLPATH_POSIX='/*' + GLOB_FULLPATH_OTHER='[[a-zA-Z]]:[[\\/]]*' + ;; +(*) + GLOB_FULLPATH_POSIX='/*' + GLOB_FULLPATH_OTHER=$GLOB_FULLPATH_POSIX + ;; +esac +AC_SUBST(GLOB_FULLPATH_POSIX) +AC_SUBST(GLOB_FULLPATH_OTHER) +])dnl +dnl --------------------------------------------------------------------------- dnl CF_GNATPREP_OPT_T version: 1 updated: 2014/08/02 18:37:25 dnl ----------------- AC_DEFUN([CF_GNATPREP_OPT_T],[ @@ -3261,7 +3397,7 @@ AC_SUBST(cf_compile_generics) AC_SUBST(cf_generic_objects) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GNAT_PROJECTS version: 13 updated: 2021/01/02 17:09:14 +dnl CF_GNAT_PROJECTS version: 14 updated: 2025/12/24 12:27:29 dnl ---------------- dnl GNAT projects are configured with ".gpr" project files. dnl GNAT libraries are a further development, using the project feature. @@ -3322,7 +3458,7 @@ CF_EOF -XLIBRARY_DIR="`cd ../conftest.lib;pwd`" \ -XSOURCE_DIR="`pwd`" \ -XSONAME=libConfTest.so.1 \ - -XLIB_KIND=static 1>&AC_FD_CC 2>&1 ) ; then + -XLIB_KIND=static 1>&AS_MESSAGE_LOG_FD 2>&1 ) ; then cf_gnat_projects=yes fi cd .. @@ -3426,7 +3562,7 @@ fi AC_SUBST(USE_GNAT_SIGINT) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GNAT_TRY_LINK version: 4 updated: 2021/01/01 13:31:04 +dnl CF_GNAT_TRY_LINK version: 5 updated: 2025/12/24 12:27:29 dnl ---------------- dnl Verify that a test program compiles/links with GNAT. dnl $cf_ada_make is set to the program that compiles/links @@ -3445,7 +3581,7 @@ CF_EOF cat >>conftest.adb <&AC_FD_CC 2>&1 ) ; then +if ( "$cf_ada_make" $ADAFLAGS conftest 1>&AS_MESSAGE_LOG_FD 2>&1 ) ; then ifelse($3,, :,[ $3]) ifelse($4,,,[else $4]) @@ -3453,7 +3589,7 @@ fi rm -rf ./conftest* ./*~conftest* ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GNAT_TRY_RUN version: 6 updated: 2021/01/01 13:31:04 +dnl CF_GNAT_TRY_RUN version: 7 updated: 2025/12/24 12:27:29 dnl --------------- dnl Verify that a test program compiles and runs with GNAT dnl $cf_ada_make is set to the program that compiles/links @@ -3472,8 +3608,8 @@ CF_EOF cat >>conftest.adb <&AC_FD_CC 2>&1 ) ; then - if ( ./conftest 1>&AC_FD_CC 2>&1 ) ; then +if ( "$cf_ada_make" $ADAFLAGS conftest 1>&AS_MESSAGE_LOG_FD 2>&1 ) ; then + if ( ./conftest 1>&AS_MESSAGE_LOG_FD 2>&1 ) ; then ifelse($3,, :,[ $3]) ifelse($4,,,[ else $4]) @@ -3500,7 +3636,7 @@ test -z "$cf_cv_gnat_version" && cf_cv_gnat_version=no ifelse($1,,,[eval $1=$cf_cv_gnat_version; unset cf_cv_gnat_version]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GNU_SOURCE version: 10 updated: 2018/12/10 20:09:41 +dnl CF_GNU_SOURCE version: 11 updated: 2025/12/14 17:40:20 dnl ------------- dnl Check if we must define _GNU_SOURCE to get a reasonable value for dnl _XOPEN_SOURCE, upon which many POSIX definitions depend. This is a defect @@ -3516,14 +3652,14 @@ AC_DEFUN([CF_GNU_SOURCE], cf_gnu_xopen_source=ifelse($1,,500,$1) AC_CACHE_CHECK(if this is the GNU C library,cf_cv_gnu_library,[ -AC_TRY_COMPILE([#include ],[ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if __GLIBC__ > 0 && __GLIBC_MINOR__ >= 0 return 0; #elif __NEWLIB__ > 0 && __NEWLIB_MINOR__ >= 0 return 0; #else # error not GNU C library - #endif], + #endif])], [cf_cv_gnu_library=yes], [cf_cv_gnu_library=no]) ]) @@ -3536,14 +3672,14 @@ if test x$cf_cv_gnu_library = xyes; then AC_CACHE_CHECK(if _DEFAULT_SOURCE can be used as a basis,cf_cv_gnu_library_219,[ cf_save="$CPPFLAGS" CF_APPEND_TEXT(CPPFLAGS,-D_DEFAULT_SOURCE) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 19) || (__GLIBC__ > 2) return 0; #elif (__NEWLIB__ == 2 && __NEWLIB_MINOR__ >= 4) || (__GLIBC__ > 3) return 0; #else # error GNU C library __GLIBC__.__GLIBC_MINOR__ is too old - #endif], + #endif])], [cf_cv_gnu_library_219=yes], [cf_cv_gnu_library_219=no]) CPPFLAGS="$cf_save" @@ -3553,7 +3689,7 @@ if test x$cf_cv_gnu_library = xyes; then cf_save="$CPPFLAGS" AC_CACHE_CHECK(if _XOPEN_SOURCE=$cf_gnu_xopen_source works with _DEFAULT_SOURCE,cf_cv_gnu_dftsrc_219,[ CF_ADD_CFLAGS(-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=$cf_gnu_xopen_source) - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #include ],[ @@ -3561,7 +3697,7 @@ if test x$cf_cv_gnu_library = xyes; then return 0; #else # error GNU C library is too old - #endif], + #endif])], [cf_cv_gnu_dftsrc_219=yes], [cf_cv_gnu_dftsrc_219=no]) ]) @@ -3573,17 +3709,17 @@ if test x$cf_cv_gnu_library = xyes; then if test "x$cf_cv_gnu_dftsrc_219" != xyes; then AC_CACHE_CHECK(if we must define _GNU_SOURCE,cf_cv_gnu_source,[ - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef _XOPEN_SOURCE #error expected _XOPEN_SOURCE to be defined - #endif], + #endif])], [cf_cv_gnu_source=no], [cf_save="$CPPFLAGS" CF_ADD_CFLAGS(-D_GNU_SOURCE) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifdef _XOPEN_SOURCE #error expected _XOPEN_SOURCE to be undefined - #endif], + #endif])], [cf_cv_gnu_source=no], [cf_cv_gnu_source=yes]) CPPFLAGS="$cf_save" @@ -3594,10 +3730,10 @@ if test x$cf_cv_gnu_library = xyes; then then AC_CACHE_CHECK(if we should also define _DEFAULT_SOURCE,cf_cv_default_source,[ CF_APPEND_TEXT(CPPFLAGS,-D_GNU_SOURCE) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifdef _DEFAULT_SOURCE #error expected _DEFAULT_SOURCE to be undefined - #endif], + #endif])], [cf_cv_default_source=no], [cf_cv_default_source=yes]) ]) @@ -3611,7 +3747,7 @@ if test x$cf_cv_gnu_library = xyes; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GPP_LIBRARY version: 13 updated: 2021/01/01 13:31:04 +dnl CF_GPP_LIBRARY version: 14 updated: 2025/12/24 12:27:29 dnl -------------- dnl If we're trying to use g++, test if libg++ is installed (a rather common dnl problem :-). If we have the compiler but no library, we'll be able to @@ -3631,10 +3767,10 @@ if test "$GXX" = yes; then AC_MSG_CHECKING([for lib$cf_gpp_libname]) cf_save="$LIBS" CF_ADD_LIB($cf_gpp_libname) - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include <$cf_gpp_libname/builtin.h> ], - [two_arg_error_handler_t foo2 = lib_error_handler], + [two_arg_error_handler_t foo2 = lib_error_handler])], [cf_cxx_library=yes CF_ADD_LIB($cf_gpp_libname,CXXLIBS) if test "$cf_gpp_libname" = cpp ; then @@ -3642,10 +3778,10 @@ if test "$GXX" = yes; then else AC_DEFINE(HAVE_GXX_BUILTIN_H,1,[Define to 1 if we have g++ builtin.h]) fi], - [AC_TRY_LINK([ + [AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ], - [two_arg_error_handler_t foo2 = lib_error_handler], + [two_arg_error_handler_t foo2 = lib_error_handler])], [cf_cxx_library=yes CF_ADD_LIB($cf_gpp_libname,CXXLIBS) AC_DEFINE(HAVE_BUILTIN_H,1,[Define to 1 if we have builtin.h])], @@ -3673,7 +3809,7 @@ if test "$GXX" = yes; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GXX_WARNINGS version: 11 updated: 2021/01/08 16:50:55 +dnl CF_GXX_WARNINGS version: 14 updated: 2025/12/24 09:07:25 dnl --------------- dnl Check if the compiler supports useful warning options. dnl @@ -3722,7 +3858,8 @@ then # remark #981: operands are evaluated in unspecified order # warning #269: invalid format string conversion - AC_CHECKING([for $CC warning options]) + AC_MSG_CHECKING([for $CC warning options]) + test -n "$verbose" && AC_MSG_RESULT() cf_save_CXXFLAGS="$CXXFLAGS" EXTRA_CXXFLAGS="-Wall" for cf_opt in \ @@ -3747,7 +3884,8 @@ then elif test "$GXX" = yes then - AC_CHECKING([for $CXX warning options]) + AC_MSG_CHECKING([for $CXX warning options]) + test -n "$verbose" && AC_MSG_RESULT() cf_save_CXXFLAGS="$CXXFLAGS" EXTRA_CXXFLAGS="-W -Wall" cf_gxx_extra_warnings="" @@ -3836,7 +3974,7 @@ fi ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_HASHED_DB_LIBS version: 10 updated: 2021/01/02 17:09:14 +dnl CF_HASHED_DB_LIBS version: 12 updated: 2025/12/24 12:27:29 dnl ----------------- dnl Given that we have the header and version for hashed database, find the dnl library information. @@ -3851,14 +3989,14 @@ do CF_ADD_LIB($cf_db_libs) fi CF_MSG_LOG(checking for library $cf_db_libs) - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default #include ],[ char *path = "/tmp/foo"; #ifdef DB_VERSION_MAJOR #if DB_VERSION_MAJOR >= 4 - DB *result = 0; + DB *result = NULL; db_create(&result, NULL, 0); result->open(result, NULL, @@ -3868,7 +4006,7 @@ $ac_includes_default DB_CREATE, 0644); #elif DB_VERSION_MAJOR >= 3 - DB *result = 0; + DB *result = NULL; db_create(&result, NULL, 0); result->open(result, path, @@ -3877,7 +4015,7 @@ $ac_includes_default DB_CREATE, 0644); #elif DB_VERSION_MAJOR >= 2 - DB *result = 0; + DB *result = NULL; db_open(path, DB_HASH, DB_CREATE, @@ -3893,8 +4031,8 @@ $ac_includes_default DB_HASH, 0); #endif - ${cf_cv_main_return:-return}(result != 0) -],[ + ${cf_cv_main_return:-return}(result != NULL) +])],[ if test -n "$cf_db_libs" ; then cf_cv_hashed_db_libs=$cf_db_libs else @@ -3908,7 +4046,7 @@ done ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_HASHED_DB_VERSION version: 5 updated: 2023/02/18 17:41:25 +dnl CF_HASHED_DB_VERSION version: 6 updated: 2025/12/24 12:27:29 dnl -------------------- dnl Given that we have the header file for hashed database, find the version dnl information. @@ -3920,7 +4058,7 @@ cf_cv_hashed_db_version=unknown for cf_db_version in 1 2 3 4 5 6 do CF_MSG_LOG(checking for db version $cf_db_version) - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default #include @@ -3938,7 +4076,7 @@ $ac_includes_default #error $cf_db_version is not 1 #endif #endif -],[DBT *foo = 0],[ +],[DBT *foo = 0])],[ cf_cv_hashed_db_version=$cf_db_version break ]) @@ -4178,7 +4316,45 @@ fi AC_SUBST(INSTALL_OPT_S) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_INTEL_COMPILER version: 9 updated: 2023/02/18 17:41:25 +dnl CF_INSTALL_PREFIX version: 2 updated: 2025/10/18 11:14:21 +dnl ----------------- +dnl Special option for use by system-builders: the install-prefix is used to +dnl adjust the location into which the actual install is done, so that an +dnl archive can be built without modifying the host system's configuration. +AC_DEFUN([CF_INSTALL_PREFIX],[ +AC_MSG_CHECKING(for an installation directory prefix) +AC_ARG_WITH(install-prefix, + [ --with-install-prefix=DESTDIR use DESTDIR as installation directory prefix], + [case "x$withval" in + (xyes|xno) + ;; + (*) DESTDIR="$withval" + ;; + esac]) +AC_MSG_RESULT([${DESTDIR:-(none)}]) +AC_SUBST(DESTDIR) + +SET_DESTDIR= +test -n "$DESTDIR" && SET_DESTDIR="DESTDIR=$DESTDIR" +AC_SUBST(SET_DESTDIR) + +AC_MSG_CHECKING(if installation directory prefix should be merged) +CF_ARG_ENABLE(install-prefix, + [ --enable-install-prefix merge DESTDIR with installation prefix], + cf_install_prefix=yes, + cf_install_prefix=no) +AC_MSG_RESULT($cf_install_prefix) + +if test "$cf_install_prefix" = yes ; then + MERGE_PREFIX=':$(prefix)%=%' +else + MERGE_PREFIX='' +fi + +AC_SUBST(MERGE_PREFIX) +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_INTEL_COMPILER version: 10 updated: 2025/12/14 17:40:20 dnl ----------------- dnl Check if the given compiler is really the Intel compiler for Linux. It dnl tries to imitate gcc, but does not return an error when it finds a mismatch @@ -4201,12 +4377,12 @@ if test "$ifelse([$1],,[$1],GCC)" = yes ; then AC_MSG_CHECKING(if this is really Intel ifelse([$1],GXX,C++,C) compiler) cf_save_CFLAGS="$ifelse([$3],,CFLAGS,[$3])" ifelse([$3],,CFLAGS,[$3])="$ifelse([$3],,CFLAGS,[$3]) -no-gcc" - AC_TRY_COMPILE([],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([],[ #ifdef __INTEL_COMPILER #else #error __INTEL_COMPILER is not defined #endif -],[ifelse([$2],,INTEL_COMPILER,[$2])=yes +])],[ifelse([$2],,INTEL_COMPILER,[$2])=yes cf_save_CFLAGS="$cf_save_CFLAGS -we147" ],[]) ifelse([$3],,CFLAGS,[$3])="$cf_save_CFLAGS" @@ -4216,14 +4392,14 @@ cf_save_CFLAGS="$cf_save_CFLAGS -we147" fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_ISASCII version: 5 updated: 2023/12/03 09:21:34 +dnl CF_ISASCII version: 6 updated: 2025/12/24 12:27:29 dnl ---------- dnl Check if we have either a function or macro for 'isascii()'. AC_DEFUN([CF_ISASCII], [ AC_MSG_CHECKING(for isascii) AC_CACHE_VAL(cf_cv_have_isascii,[ - AC_TRY_LINK([#include ],[int x = isascii(' '); (void)x], + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include ],[int x = isascii(' '); (void)x])], [cf_cv_have_isascii=yes], [cf_cv_have_isascii=no]) ])dnl @@ -4231,7 +4407,7 @@ AC_MSG_RESULT($cf_cv_have_isascii) test "$cf_cv_have_isascii" = yes && AC_DEFINE(HAVE_ISASCII,1,[Define to 1 if we have isascii()]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_LARGEFILE version: 13 updated: 2023/12/03 19:09:59 +dnl CF_LARGEFILE version: 14 updated: 2025/12/22 04:16:14 dnl ------------ dnl Add checks for large file support. AC_DEFUN([CF_LARGEFILE],[ @@ -4261,7 +4437,7 @@ ifdef([AC_FUNC_FSEEKO],[ fi AC_CACHE_CHECK(whether to use struct dirent64, cf_cv_struct_dirent64,[ - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #pragma GCC diagnostic error "-Wincompatible-pointer-types" #include #include @@ -4276,7 +4452,7 @@ extern struct dirent64 * readdir(DIR *); struct dirent *y = readdir(dp); int z = x - y; (void)z; - ], + ])], [cf_cv_struct_dirent64=yes], [cf_cv_struct_dirent64=no]) ]) @@ -4285,7 +4461,7 @@ extern struct dirent64 * readdir(DIR *); ]) ]) dnl --------------------------------------------------------------------------- -dnl CF_LDFLAGS_STATIC version: 14 updated: 2021/01/02 17:09:14 +dnl CF_LDFLAGS_STATIC version: 17 updated: 2025/12/24 12:27:29 dnl ----------------- dnl Check for compiler/linker flags used to temporarily force usage of static dnl libraries. This depends on the compiler and platform. Use this to help @@ -4306,21 +4482,21 @@ if test "$GCC" = yes ; then esac else case "$cf_cv_system_name" in - (aix[[4-7]]*) # from ld manpage + (aix[[4-7]]*) # from ld man page LDFLAGS_STATIC=-bstatic LDFLAGS_SHARED=-bdynamic ;; - (hpux*) # from ld manpage for hpux10.20, hpux11.11 + (hpux*) # from ld man page for hpux10.20, hpux11.11 # We could also use just "archive" and "shared". LDFLAGS_STATIC=-Wl,-a,archive_shared LDFLAGS_SHARED=-Wl,-a,shared_archive ;; - (irix*) # from ld manpage IRIX64 + (irix*) # from ld man page IRIX64 LDFLAGS_STATIC=-Bstatic LDFLAGS_SHARED=-Bdynamic ;; - (osf[[45]]*) # from ld manpage osf4.0d, osf5.1 - # alternative "-oldstyle_liblookup" (not in cc manpage) + (osf[[45]]*) # from ld man page osf4.0d, osf5.1 + # alternative "-oldstyle_liblookup" (not in cc man page) LDFLAGS_STATIC=-noso LDFLAGS_SHARED=-so_archive ;; @@ -4342,21 +4518,21 @@ then int cf_ldflags_static(FILE *fp) { return fflush(fp); } EOF if AC_TRY_EVAL(ac_compile) ; then - ( $AR $ARFLAGS libconftest.a conftest.o ) 2>&AC_FD_CC 1>/dev/null - ( eval $RANLIB libconftest.a ) 2>&AC_FD_CC >/dev/null + ( $AR $ARFLAGS libconftest.a conftest.$OBJEXT ) 2>&AS_MESSAGE_LOG_FD 1>/dev/null + ( eval $RANLIB libconftest.a ) 2>&AS_MESSAGE_LOG_FD >/dev/null fi rm -f conftest.* cf_save_LIBS="$LIBS" LIBS="$LDFLAGS_STATIC -L`pwd` -lconftest $LDFLAGS_DYNAMIC $LIBS" - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #line __oline__ "configure" #include int cf_ldflags_static(FILE *fp); ],[ return cf_ldflags_static(stdin); -],[ +])],[ # some linkers simply ignore the -dynamic case x`file "conftest$ac_exeext" 2>/dev/null` in (*static*) @@ -4387,7 +4563,7 @@ AC_SUBST(LDFLAGS_STATIC) AC_SUBST(LDFLAGS_SHARED) ]) dnl --------------------------------------------------------------------------- -dnl CF_LD_RPATH_OPT version: 9 updated: 2021/01/01 13:31:04 +dnl CF_LD_RPATH_OPT version: 10 updated: 2025/12/15 04:04:20 dnl --------------- dnl For the given system and compiler, find the compiler flags to pass to the dnl loader to use the "rpath" feature. @@ -4435,7 +4611,7 @@ then AC_MSG_CHECKING(if we need a space after rpath option) cf_save_LIBS="$LIBS" CF_ADD_LIBS(${LD_RPATH_OPT}$libdir) - AC_TRY_LINK(, , cf_rpath_space=no, cf_rpath_space=yes) + AC_LINK_IFELSE([AC_LANG_PROGRAM([], [])], cf_rpath_space=no, cf_rpath_space=yes) LIBS="$cf_save_LIBS" AC_MSG_RESULT($cf_rpath_space) test "$cf_rpath_space" = yes && LD_RPATH_OPT="$LD_RPATH_OPT " @@ -4567,9 +4743,12 @@ CF_SUBDIR_PATH($1,$2,lib) $1="$cf_library_path_list [$]$1" ])dnl dnl --------------------------------------------------------------------------- -dnl CF_LIBTOOL_VERSION version: 1 updated: 2013/04/06 18:03:09 +dnl CF_LIBTOOL_VERSION version: 2 updated: 2024/06/12 04:19:01 dnl ------------------ AC_DEFUN([CF_LIBTOOL_VERSION],[ +ifdef([LT_PACKAGE_VERSION],[ + cf_cv_libtool_version=LT_PACKAGE_VERSION +],[ if test -n "$LIBTOOL" && test "$LIBTOOL" != none then cf_cv_libtool_version=`$LIBTOOL --version 2>&1 | sed -e '/^$/d' |sed -e '2,$d' -e 's/([[^)]]*)//g' -e 's/^[[^1-9]]*//' -e 's/[[^0-9.]].*//'` @@ -4578,6 +4757,7 @@ else fi test -z "$cf_cv_libtool_version" && unset cf_cv_libtool_version ])dnl +])dnl dnl --------------------------------------------------------------------------- dnl CF_LIB_PREFIX version: 14 updated: 2021/01/01 13:31:04 dnl ------------- @@ -4603,7 +4783,7 @@ ifelse($1,,,[$1=$LIB_PREFIX]) AC_SUBST(LIB_PREFIX) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_LIB_RULES version: 100 updated: 2023/06/03 15:17:30 +dnl CF_LIB_RULES version: 103 updated: 2025/11/11 20:09:36 dnl ------------ dnl Append definitions and rules for the given models to the subdirectory dnl Makefiles, and the recursion rule for the top-level Makefile. If the @@ -4621,6 +4801,7 @@ dnl Note: Libs_To_Make is mixed case, since it is not a pure autoconf variable. AC_DEFUN([CF_LIB_RULES], [AC_REQUIRE([AC_PROG_FGREP])dnl AC_REQUIRE([CF_MAKE_PHONY])dnl +AC_REQUIRE([CF_GLOB_FULLPATH])dnl cf_prefix=$LIB_PREFIX AC_REQUIRE([CF_SUBST_NCURSES_VERSION]) @@ -4703,7 +4884,7 @@ CF_EOF if test "$cf_item" = shared ; then if test -n "${LIB_SUFFIX}" then - cf_shared_suffix=`echo "$cf_suffix" | sed 's/^'"${USE_LIB_SUFFIX}"'//'` + cf_shared_suffix=`echo "$cf_suffix" | sed 's/^'"${ABI_SUFFIX}"'//'` else cf_shared_suffix="$cf_suffix" fi @@ -4724,16 +4905,16 @@ CF_EOF case "$cf_cv_system_name" in (darwin*) # "w", etc? - cf_suffix="${USE_LIB_SUFFIX}"'.${'$cf_version_name'}'"$cf_shared_suffix" + cf_suffix="${ABI_SUFFIX}"'.${'$cf_version_name'}'"$cf_shared_suffix" ;; (*) cf_suffix="$cf_suffix"'.${'$cf_version_name'}' ;; esac fi - if test -n "${USE_LIB_SUFFIX}" + if test -n "${ABI_SUFFIX}" then - cf_shared_suffix=`echo "$cf_suffix" | sed 's/^'"${USE_LIB_SUFFIX}"'//'` + cf_shared_suffix=`echo "$cf_suffix" | sed 's/^'"${ABI_SUFFIX}"'//'` else cf_shared_suffix="$cf_suffix" fi @@ -4785,10 +4966,10 @@ CF_EOF cf_add_lib= case "$cf_l_parts" in (*termlib*) - cf_add_lib=`echo "$cf_liblist" |sed -e s%${LIB_NAME}${USE_LIB_SUFFIX}%${TINFO_LIB_SUFFIX}%g` + cf_add_lib=`echo "$cf_liblist" |sed -e s%${LIB_NAME}${ABI_SUFFIX}%${TINFO_LIB_SUFFIX}%g` ;; (*ticlib*) - cf_add_lib=`echo "$cf_liblist" |sed -e s%${LIB_NAME}${USE_LIB_SUFFIX}%${TICS_LIB_SUFFIX}%g` + cf_add_lib=`echo "$cf_liblist" |sed -e s%${LIB_NAME}${ABI_SUFFIX}%${TICS_LIB_SUFFIX}%g` ;; (*) break @@ -4871,7 +5052,7 @@ CF_EOF if test "$cf_dir" = ncurses ; then case "$cf_subset" in (*base*) - cf_libname=${cf_libname}$USE_LIB_SUFFIX + cf_libname=${cf_libname}$ABI_SUFFIX ;; (*termlib*) cf_libname=$TINFO_LIB_SUFFIX @@ -4882,14 +5063,14 @@ CF_EOF esac elif test "$cf_dir" = c++ ; then CF_MAP_LIB_BASENAME(cf_libname,cxx) - cf_libname=${cf_libname}$USE_LIB_SUFFIX + cf_libname=${cf_libname}$ABI_SUFFIX else CF_MAP_LIB_BASENAME(cf_libname,$cf_dir) - cf_libname=${cf_libname}$USE_LIB_SUFFIX + cf_libname=${cf_libname}$ABI_SUFFIX fi if test -n "${USE_ARG_SUFFIX}" ; then - # undo $USE_LIB_SUFFIX add-on in CF_LIB_SUFFIX - cf_suffix=`echo "$cf_suffix" |sed -e "s%^${USE_LIB_SUFFIX}%%"` + # undo $ABI_SUFFIX add-on in CF_LIB_SUFFIX + cf_suffix=`echo "$cf_suffix" |sed -e "s%^${ABI_SUFFIX}%%"` fi # These dependencies really are for development, not @@ -4910,8 +5091,8 @@ CF_EOF cf_dir_suffix= old_cf_suffix="$cf_suffix" if test "$cf_cv_shlib_version_infix" = yes ; then - if test -n "$USE_LIB_SUFFIX" ; then - case "$USE_LIB_SUFFIX" in + if test -n "$ABI_SUFFIX" ; then + case "$ABI_SUFFIX" in (tw*) cf_libname=`echo "$cf_libname" | sed 's/tw'$EXTRA_SUFFIX'$//'` cf_suffix=`echo "$cf_suffix" | sed 's/^tw'$EXTRA_SUFFIX'//'` @@ -4941,8 +5122,8 @@ CF_EOF traces=$LIB_TRACING \ MODEL=$cf_ITEM \ CXX_MODEL=$CXX_MODEL \ + ABI_SUFFIX=$ABI_SUFFIX \ LIB_SUFFIX=$LIB_SUFFIX \ - USE_LIB_SUFFIX=$USE_LIB_SUFFIX \ make_phony="${cf_cv_make_PHONY:-no}" \ model=$cf_subdir \ prefix=$cf_prefix \ @@ -5127,7 +5308,7 @@ echo creating headers.sh cat >headers.sh <>headers.sh <>headers.sh <>headers.sh <&AC_FD_CC 1>/dev/null + mv conftest.$OBJEXT data.$OBJEXT && \ + ( $AR $ARFLAGS conftest.a data.$OBJEXT ) 2>&AS_MESSAGE_LOG_FD 1>/dev/null fi - rm -f conftest.$ac_ext data.o + rm -f conftest.$ac_ext data.$OBJEXT cat >conftest.$ac_ext <&AC_FD_CC 1>/dev/null + mv conftest.$OBJEXT func.$OBJEXT && \ + ( $AR $ARFLAGS conftest.a func.$OBJEXT ) 2>&AS_MESSAGE_LOG_FD 1>/dev/null fi - rm -f conftest.$ac_ext func.o - ( eval $RANLIB conftest.a ) 2>&AC_FD_CC >/dev/null + rm -f conftest.$ac_ext func.$OBJEXT + ( eval $RANLIB conftest.a ) 2>&AS_MESSAGE_LOG_FD >/dev/null cf_saveLIBS="$LIBS" LIBS="conftest.a $LIBS" AC_TRY_RUN([ @@ -5451,7 +5632,7 @@ AC_SUBST(BROKEN_LINKER) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_LINK_FUNCS version: 13 updated: 2023/12/03 09:24:04 +dnl CF_LINK_FUNCS version: 14 updated: 2024/12/14 16:09:34 dnl ------------- dnl Most Unix systems have both link and symlink, a few don't have symlink. dnl A few non-Unix systems implement symlink, but not link. @@ -5486,7 +5667,7 @@ int main(void) char dst[] = "conftest.chk"; struct stat src_sb, dst_sb; FILE *fp = fopen(src, "w"); - if (fp == 0) { fail = 3; } else { + if (fp == NULL) { fail = 3; } else { fclose(fp); stat(src, &src_sb); if ($cf_func(src, dst) < 0) { fail = 1; @@ -5518,50 +5699,7 @@ int main(void) fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MAKEFLAGS version: 21 updated: 2021/09/04 06:47:34 -dnl ------------ -dnl Some 'make' programs support ${MAKEFLAGS}, some ${MFLAGS}, to pass 'make' -dnl options to lower-levels. It is very useful for "make -n" -- if we have it. -dnl (GNU 'make' does both, something POSIX 'make', which happens to make the -dnl ${MAKEFLAGS} variable incompatible because it adds the assignments :-) -AC_DEFUN([CF_MAKEFLAGS], -[AC_REQUIRE([AC_PROG_FGREP])dnl - -AC_CACHE_CHECK(for makeflags variable, cf_cv_makeflags,[ - cf_cv_makeflags='' - for cf_option in '-${MAKEFLAGS}' '${MFLAGS}' - do - cat >cf_makeflags.tmp </dev/null | ${FGREP-fgrep} -v "ing directory" | sed -e 's,[[ ]]*$,,'` - case "$cf_result" in - (.*k|.*kw) - cf_result="`${MAKE:-make} -k -f cf_makeflags.tmp CC=cc 2>/dev/null`" - case "$cf_result" in - (.*CC=*) cf_cv_makeflags= - ;; - (*) cf_cv_makeflags=$cf_option - ;; - esac - break - ;; - (.-) - ;; - (*) - CF_MSG_LOG(given option \"$cf_option\", no match \"$cf_result\") - ;; - esac - done - rm -f cf_makeflags.tmp -]) - -AC_SUBST(cf_cv_makeflags) -])dnl -dnl --------------------------------------------------------------------------- -dnl CF_MAKE_PHONY version: 3 updated: 2021/01/08 16:08:21 +dnl CF_MAKE_PHONY version: 4 updated: 2025/12/24 12:27:29 dnl ------------- dnl Check if the make-program handles a ".PHONY" target, e.g,. a target which dnl acts as a placeholder. @@ -5632,7 +5770,7 @@ CF_EOF fi break done - ) >&AC_FD_CC 2>&1 + ) >&AS_MESSAGE_LOG_FD 2>&1 cf_cv_make_PHONY="`cat conftest.tmp`" rm -rf conftest* ]) @@ -5681,9 +5819,9 @@ AC_SUBST(MAKE_UPPER_TAGS) AC_SUBST(MAKE_LOWER_TAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MANPAGE_FORMAT version: 19 updated: 2024/03/30 08:27:40 +dnl CF_MANPAGE_FORMAT version: 20 updated: 2025/11/11 20:09:36 dnl ----------------- -dnl Option to allow user to override automatic configuration of manpage format. +dnl Option to allow user to override automatic configuration of man page format. dnl There are several special cases: dnl dnl compress - man checks for, can display compressed files @@ -5696,15 +5834,15 @@ dnl formatted - installer should format (put files in cat-directory) dnl catonly - installer should only format, e.g., for a turnkey system. dnl dnl There are other configurations which this macro does not test, e.g., HPUX's -dnl compressed manpages (but uncompressed manpages are fine, and HPUX's naming +dnl compressed man pages (but uncompressed man pages are fine, and HPUX's naming dnl convention would not match our use). AC_DEFUN([CF_MANPAGE_FORMAT], [ AC_REQUIRE([CF_PATHSEP]) -AC_MSG_CHECKING(format of man-pages) +AC_MSG_CHECKING(format of man pages) AC_ARG_WITH(manpage-format, - [ --with-manpage-format specify manpage-format: gzip/compress/bzip2/xz, + [ --with-manpage-format specify man page format: gzip/compress/bzip2/xz, BSDI/normal and optionally formatted/catonly, e.g., gzip,formatted], [MANPAGE_FORMAT=$withval], @@ -5721,7 +5859,7 @@ case "$MANPAGE_FORMAT" in MANPATH="/usr/man:/usr/share/man" fi - # look for the 'date' man-page (it is most likely to be installed!) + # look for the 'date' man page (it is most likely to be installed!) MANPAGE_FORMAT= cf_preform="no" cf_catonly="yes" @@ -5768,7 +5906,7 @@ case "$MANPAGE_FORMAT" in test "$cf_found" = yes && break fi done - # only check the first directory in $MANPATH where we find manpages + # only check the first directory in $MANPATH where we find man pages if test -n "$MANPAGE_FORMAT" ; then break fi @@ -5792,7 +5930,7 @@ esac AC_MSG_RESULT($MANPAGE_FORMAT) if test -n "$cf_unknown" ; then - AC_MSG_WARN(Unexpected manpage-format $cf_unknown) + AC_MSG_WARN(Unexpected man page format $cf_unknown) fi cf_manpage_format=no @@ -5840,17 +5978,17 @@ AC_SUBST(cf_manpage_coptions) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MANPAGE_RENAMES version: 17 updated: 2022/10/23 07:46:29 +dnl CF_MANPAGE_RENAMES version: 18 updated: 2025/11/11 20:09:36 dnl ------------------ -dnl The Debian people have their own naming convention for manpages. This +dnl The Debian people have their own naming convention for man pages. This dnl option lets us override the name of the file containing renaming, or dnl disable it altogether. AC_DEFUN([CF_MANPAGE_RENAMES], [ -AC_MSG_CHECKING(for manpage renaming) +AC_MSG_CHECKING(for man page renaming) AC_ARG_WITH(manpage-renames, - [ --with-manpage-renames specify manpage-renaming], + [ --with-manpage-renames specify man page renaming], [MANPAGE_RENAMES=$withval], [MANPAGE_RENAMES=yes]) @@ -5879,17 +6017,17 @@ AC_MSG_RESULT($MANPAGE_RENAMES) AC_SUBST(MANPAGE_RENAMES) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MANPAGE_SYMLINKS version: 7 updated: 2023/01/21 16:37:17 +dnl CF_MANPAGE_SYMLINKS version: 8 updated: 2025/11/11 20:09:36 dnl ------------------- -dnl Some people expect each tool to make all aliases for manpages in the +dnl Some people expect each tool to make all aliases for man pages in the dnl man-directory. This accommodates the older, less-capable implementations dnl of 'man', and is optional. AC_DEFUN([CF_MANPAGE_SYMLINKS], [ -AC_MSG_CHECKING(if manpage aliases will be installed) +AC_MSG_CHECKING(if man page aliases will be installed) AC_ARG_WITH(manpage-aliases, - [ --with-manpage-aliases specify manpage-aliases using .so], + [ --with-manpage-aliases specify man page aliases using .so], [MANPAGE_ALIASES=$withval], [MANPAGE_ALIASES=yes]) @@ -5906,10 +6044,10 @@ esac MANPAGE_SYMLINKS=no if test "$MANPAGE_ALIASES" = yes ; then -AC_MSG_CHECKING(if manpage symlinks should be used) +AC_MSG_CHECKING(if man page symlinks should be used) AC_ARG_WITH(manpage-symlinks, - [ --with-manpage-symlinks specify manpage-aliases using symlinks], + [ --with-manpage-symlinks specify man page aliases using symlinks], [MANPAGE_SYMLINKS=$withval], [MANPAGE_SYMLINKS=$cf_use_symlinks]) @@ -5925,54 +6063,30 @@ fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MANPAGE_TBL version: 3 updated: 2002/01/19 22:51:32 +dnl CF_MANPAGE_TBL version: 4 updated: 2025/11/11 20:09:36 dnl -------------- -dnl This option causes manpages to be run through tbl(1) to generate tables +dnl This option causes man pages to be run through tbl(1) to generate tables dnl correctly. AC_DEFUN([CF_MANPAGE_TBL], [ -AC_MSG_CHECKING(for manpage tbl) +AC_MSG_CHECKING(for man page tbl) AC_ARG_WITH(manpage-tbl, - [ --with-manpage-tbl specify manpage processing with tbl], + [ --with-manpage-tbl specify man page processing with tbl], [MANPAGE_TBL=$withval], [MANPAGE_TBL=no]) AC_MSG_RESULT($MANPAGE_TBL) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MB_LEN_MAX version: 1 updated: 2024/03/02 15:45:10 -dnl ------------- -dnl Check if defines a usable MB_LEN_MAX. That may be because it is -dnl not defined, or it may be a bogus value. -AC_DEFUN([CF_MB_LEN_MAX],[ -AC_CACHE_CHECK(if MB_LEN_MAX is usable,cf_cv_mb_len_max,[ -AC_TRY_COMPILE([ -$ac_includes_default -#include ], -[ -#if defined(MB_LEN_MAX) && MB_LEN_MAX >= 6 - ${cf_cv_main_return:-return}(0); -#else -#error MB_LEN_MAX is not usable -#endif -], [cf_cv_mb_len_max=yes], - [cf_cv_mb_len_max=no])]) -if test "$cf_cv_mb_len_max" = yes -then - AC_DEFINE(HAVE_CONSISTENT_MB_LEN_MAX,1,[Define to 1 if MB_LEN_MAX is usable]) -else - AC_MSG_WARN(MB_LEN_MAX is missing/inconsistent in system headers) -fi -])dnl -dnl --------------------------------------------------------------------------- -dnl CF_MAN_PAGES version: 59 updated: 2024/03/30 08:27:40 +dnl CF_MAN_PAGES version: 64 updated: 2025/11/11 20:09:36 dnl ------------ -dnl Try to determine if the man-pages on the system are compressed, and if +dnl Try to determine if the man pages on the system are compressed, and if dnl so, what format is used. Use this information to construct a script that -dnl will install man-pages. +dnl will install man pages. AC_DEFUN([CF_MAN_PAGES], [ +AC_REQUIRE([CF_CHECK_TBL_X_OPTION]) CF_HELP_MESSAGE(Options to Specify How Manpages are Installed:) CF_MANPAGE_FORMAT CF_MANPAGE_RENAMES @@ -5991,8 +6105,8 @@ cf_edit_man=./edit_man.sh cf_man_alias=`pwd`/man_alias.sed cat >$cf_edit_man <>$cf_edit_man <>$cf_edit_man <\$TMP.unx + mv \$TMP.unx \$TMP +fi +CF_EOF + cat >>$cf_edit_man <\$TMP.out @@ -6143,14 +6266,21 @@ CF_EOF if test "$with_overwrite" != yes ; then cat >>$cf_edit_man <\$TMP.out + sed -e "/\\#[ ]*include/s,\$TMP.out mv \$TMP.out \$TMP CF_EOF fi if test "$with_curses_h" != yes ; then cat >>$cf_edit_man <\$TMP.out + sed -e "/\\#[ ]*include/s,curses.h,ncurses.h," \ + < \$TMP >\$TMP.out mv \$TMP.out \$TMP CF_EOF fi @@ -6165,7 +6295,7 @@ CF_EOF if test -n "$cf_manpage_compress" ; then cat >>$cf_edit_man < #include #include ], - [double x = rand(); printf("result = %g\\n", ]ifelse([$2],,sin(x),$2)[)], + [double x = rand(); printf("result = %g\\n", ]ifelse([$2],,sin(x),$2)[)])], [cf_cv_need_libm=no], [cf_cv_need_libm=yes])]) @@ -6329,12 +6459,12 @@ then LIBS="$LIBS -lm" AC_CACHE_CHECK(if -lm is available for math functions, cf_cv_have_libm,[ - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include #include #include ], - [double x = rand(); printf("result = %g\\n", ]ifelse([$2],,sin(x),$2)[)], + [double x = rand(); printf("result = %g\\n", ]ifelse([$2],,sin(x),$2)[)])], [cf_cv_have_libm=yes], [cf_cv_have_libm=no])]) LIBS="$cf_save_LIBS" @@ -6353,6 +6483,31 @@ then fi ]) dnl --------------------------------------------------------------------------- +dnl CF_MB_LEN_MAX version: 2 updated: 2025/12/24 12:27:29 +dnl ------------- +dnl Check if defines a usable MB_LEN_MAX. That may be because it is +dnl not defined, or it may be a bogus value. +AC_DEFUN([CF_MB_LEN_MAX],[ +AC_CACHE_CHECK(if MB_LEN_MAX is usable,cf_cv_mb_len_max,[ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ +$ac_includes_default +#include ], +[ +#if defined(MB_LEN_MAX) && MB_LEN_MAX >= 6 + ${cf_cv_main_return:-return}(0); +#else +#error MB_LEN_MAX is not usable +#endif +])], [cf_cv_mb_len_max=yes], + [cf_cv_mb_len_max=no])]) +if test "$cf_cv_mb_len_max" = yes +then + AC_DEFINE(HAVE_CONSISTENT_MB_LEN_MAX,1,[Define to 1 if MB_LEN_MAX is usable]) +else + AC_MSG_WARN(MB_LEN_MAX is missing/inconsistent in system headers) +fi +])dnl +dnl --------------------------------------------------------------------------- dnl CF_MIXEDCASE_FILENAMES version: 9 updated: 2021/01/01 16:53:59 dnl ---------------------- dnl Check if the file-system supports mixed-case filenames. If we're able to @@ -6383,7 +6538,7 @@ fi test "$cf_cv_mixedcase" = yes && AC_DEFINE(MIXEDCASE_FILENAMES,1,[Define to 1 if filesystem supports mixed-case filenames.]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MKSTEMP version: 13 updated: 2023/12/01 17:22:50 +dnl CF_MKSTEMP version: 14 updated: 2025/12/14 18:08:20 dnl ---------- dnl Check for a working mkstemp. This creates two files, checks that they are dnl successfully created and distinct (AmigaOS apparently fails on the last). @@ -6393,7 +6548,7 @@ unistd.h \ ) AC_CACHE_CHECK(for working mkstemp, cf_cv_func_mkstemp,[ rm -rf ./conftest* -AC_TRY_RUN([ +AC_RUN_IFELSE([AC_LANG_SOURCE([[ $ac_includes_default int main(void) @@ -6423,7 +6578,7 @@ int main(void) result = 1; ${cf_cv_main_return:-return}(result); } -],[cf_cv_func_mkstemp=yes +]])],[cf_cv_func_mkstemp=yes ],[cf_cv_func_mkstemp=no ],[cf_cv_func_mkstemp=maybe]) ]) @@ -6435,12 +6590,12 @@ if test "x$cf_cv_func_mkstemp" = xyes || test "x$ac_cv_func_mkstemp" = xyes ; th fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_MSG_LOG version: 5 updated: 2010/10/23 15:52:32 +dnl CF_MSG_LOG version: 6 updated: 2025/12/14 17:51:46 dnl ---------- dnl Write a debug message to config.log, along with the line number in the dnl configure script. AC_DEFUN([CF_MSG_LOG],[ -echo "${as_me:-configure}:__oline__: testing $* ..." 1>&AC_FD_CC +echo "${as_me:-configure}:__oline__: testing $* ..." 1>&AS_MESSAGE_LOG_FD ])dnl dnl --------------------------------------------------------------------------- dnl CF_NCURSES_ABI_6 version: 5 updated: 2023/01/07 16:32:06 @@ -6558,7 +6713,7 @@ AC_DEFUN([CF_OBJ_SUBDIR], esac ])dnl dnl --------------------------------------------------------------------------- -dnl CF_OUTPUT_MANPAGE_RENAMES version: 2 updated: 2022/10/22 19:12:31 +dnl CF_OUTPUT_MANPAGE_RENAMES version: 3 updated: 2025/11/11 20:09:36 dnl ------------------------- dnl This runs in the output step to config.status, after man_db.renames has dnl been generated. @@ -6566,7 +6721,7 @@ AC_DEFUN([CF_OUTPUT_MANPAGE_RENAMES], [ AC_REQUIRE([CF_MANPAGE_RENAMES]) if test "$MANPAGE_RENAMES" != no ; then - # Construct a sed-script to perform renaming within man-pages + # Construct a sed script to perform renaming within man pages test -n "$verbose" && echo "creating edit_man.sed" test ! -d man && mkdir man FGREP="${FGREP-grep -F}" $SHELL "$srcdir/man/make_sed.sh" "$MANPAGE_RENAMES" >./edit_man.sed @@ -6634,39 +6789,39 @@ if test -n "$cf_path_prog" ; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PATH_SYNTAX version: 18 updated: 2020/12/31 18:40:20 +dnl CF_PATH_SYNTAX version: 20 updated: 2025/12/16 04:09:03 dnl -------------- dnl Check the argument to see that it looks like a pathname. Rewrite it if it dnl begins with one of the prefix/exec_prefix variables, and then again if the dnl result begins with 'NONE'. This is necessary to work around autoconf's dnl delayed evaluation of those symbols. AC_DEFUN([CF_PATH_SYNTAX],[ +AC_REQUIRE([CF_GLOB_FULLPATH])dnl + if test "x$prefix" != xNONE; then cf_path_syntax="$prefix" else cf_path_syntax="$ac_default_prefix" fi -case ".[$]$1" in -(.\[$]\(*\)*|.\'*\'*) +case "x[$]$1" in +(x\[$]\(*\)*|x\'*\'*) ;; -(..|./*|.\\*) +(x.|x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; -(.[[a-zA-Z]]:[[\\/]]*) # OS/2 EMX - ;; -(.\[$]\{*prefix\}*|.\[$]\{*dir\}*) +(x\[$]\{*prefix\}*|x\[$]\{*dir\}*) eval $1="[$]$1" - case ".[$]$1" in - (.NONE/*) + case "x[$]$1" in + (xNONE/*) $1=`echo "[$]$1" | sed -e s%NONE%$cf_path_syntax%` ;; esac ;; -(.no|.NONE/*) +(xno|xNONE/*) $1=`echo "[$]$1" | sed -e s%NONE%$cf_path_syntax%` ;; (*) - ifelse([$2],,[AC_MSG_ERROR([expected a pathname, not \"[$]$1\"])],$2) + ifelse([$2],,[AC_MSG_ERROR([expected a pathname, not "[$]$1"])],$2) ;; esac ])dnl @@ -6709,7 +6864,7 @@ fi AC_SUBST(PKG_CONFIG) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_POSIX_C_SOURCE version: 12 updated: 2023/02/18 17:41:25 +dnl CF_POSIX_C_SOURCE version: 13 updated: 2025/12/14 17:40:20 dnl ----------------- dnl Define _POSIX_C_SOURCE to the given level, and _POSIX_SOURCE if needed. dnl @@ -6738,10 +6893,10 @@ CF_REMOVE_DEFINE(cf_trim_CPPFLAGS,$cf_save_CPPFLAGS,_POSIX_C_SOURCE) AC_CACHE_CHECK(if we should define _POSIX_C_SOURCE,cf_cv_posix_c_source,[ CF_MSG_LOG(if the symbol is already defined go no further) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef _POSIX_C_SOURCE #error _POSIX_C_SOURCE is not defined -#endif], +#endif])], [cf_cv_posix_c_source=no], [cf_want_posix_source=no case .$cf_POSIX_C_SOURCE in @@ -6757,10 +6912,10 @@ AC_CACHE_CHECK(if we should define _POSIX_C_SOURCE,cf_cv_posix_c_source,[ ;; esac if test "$cf_want_posix_source" = yes ; then - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifdef _POSIX_SOURCE #error _POSIX_SOURCE is defined -#endif],[], +#endif])],[], cf_cv_posix_c_source="$cf_cv_posix_c_source -D_POSIX_SOURCE") fi CF_MSG_LOG(ifdef from value $cf_POSIX_C_SOURCE) @@ -6768,10 +6923,10 @@ AC_CACHE_CHECK(if we should define _POSIX_C_SOURCE,cf_cv_posix_c_source,[ CPPFLAGS="$cf_trim_CPPFLAGS" CF_APPEND_TEXT(CPPFLAGS,$cf_cv_posix_c_source) CF_MSG_LOG(if the second compile does not leave our definition intact error) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef _POSIX_C_SOURCE #error _POSIX_C_SOURCE is not defined -#endif],, +#endif])],, [cf_cv_posix_c_source=no]) CFLAGS="$cf_save_CFLAGS" CPPFLAGS="$cf_save_CPPFLAGS" @@ -6788,7 +6943,7 @@ fi # cf_cv_posix_visible ])dnl dnl --------------------------------------------------------------------------- -dnl CF_POSIX_VISIBLE version: 1 updated: 2018/12/31 20:46:17 +dnl CF_POSIX_VISIBLE version: 2 updated: 2025/12/14 17:40:20 dnl ---------------- dnl POSIX documents test-macros which an application may set before any system dnl headers are included to make features available. @@ -6804,18 +6959,18 @@ dnl conflicting definition. AC_DEFUN([CF_POSIX_VISIBLE], [ AC_CACHE_CHECK(if the POSIX test-macros are already defined,cf_cv_posix_visible,[ -AC_TRY_COMPILE([#include ],[ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if defined(__POSIX_VISIBLE) && ((__POSIX_VISIBLE - 0L) > 0) \ && defined(__XSI_VISIBLE) && ((__XSI_VISIBLE - 0L) > 0) \ && defined(__BSD_VISIBLE) && ((__BSD_VISIBLE - 0L) > 0) \ && defined(__ISO_C_VISIBLE) && ((__ISO_C_VISIBLE - 0L) > 0) #error conflicting symbols found #endif -],[cf_cv_posix_visible=no],[cf_cv_posix_visible=yes]) +])],[cf_cv_posix_visible=no],[cf_cv_posix_visible=yes]) ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PREDEFINE version: 3 updated: 2023/02/18 17:41:25 +dnl CF_PREDEFINE version: 4 updated: 2025/12/24 12:27:29 dnl ------------ dnl Add definitions to CPPFLAGS to ensure they're predefined for all compiles. dnl @@ -6824,22 +6979,22 @@ dnl $2 = value (if any) to use for a predefinition AC_DEFUN([CF_PREDEFINE], [ AC_MSG_CHECKING(if we must define $1) -AC_TRY_COMPILE([#include +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef $1 #error $1 is not defined -#endif],[cf_result=no],[cf_result=yes]) +#endif])],[cf_result=no],[cf_result=yes]) AC_MSG_RESULT($cf_result) if test "$cf_result" = yes ; then CPPFLAGS="$CPPFLAGS ifelse([$2],,-D$1,[-D$1=$2])" elif test "x$2" != "x" ; then AC_MSG_CHECKING(checking for compatible value versus $2) - AC_TRY_COMPILE([#include + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if $1-$2 < 0 #error $1-$2 is negative -#endif],[cf_result=yes],[cf_result=no]) +#endif])],[cf_result=yes],[cf_result=no]) AC_MSG_RESULT($cf_result) if test "$cf_result" = no ; then # perhaps we can override it - try... @@ -6905,7 +7060,7 @@ CF_ACVERSION_CHECK(2.52, CF_CC_ENV_FLAGS ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PROG_CC_C_O version: 6 updated: 2021/01/01 13:31:04 +dnl CF_PROG_CC_C_O version: 7 updated: 2025/12/24 12:27:29 dnl -------------- dnl Analogous to AC_PROG_CC_C_O, but more useful: tests only $CC, ensures that dnl the output file can be renamed, and allows for a shell variable that can @@ -6929,7 +7084,7 @@ int main(void) CF_EOF # We do the test twice because some compilers refuse to overwrite an # existing .o file with -o, though they will create one. -ac_try='[$]$1 $2 -c conftest.$ac_ext -o conftest2.$ac_objext >&AC_FD_CC' +ac_try='[$]$1 $2 -c conftest.$ac_ext -o conftest2.$ac_objext >&AS_MESSAGE_LOG_FD' if AC_TRY_EVAL(ac_try) && test -f conftest2.$ac_objext && AC_TRY_EVAL(ac_try); then @@ -6946,7 +7101,7 @@ else fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PROG_GNAT version: 12 updated: 2021/01/02 17:09:14 +dnl CF_PROG_GNAT version: 13 updated: 2025/12/24 12:27:29 dnl ------------ dnl Check for gnat/gnatmake/etc, ensure that the toolset is complete. AC_DEFUN([CF_PROG_GNAT],[ @@ -6995,12 +7150,12 @@ else "$cf_gprconfig,,,,GCC" \ "$cf_gprconfig" do - cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&AC_FD_CC | ${AWK:-awk} '/^\*/{print [$]3;}' | head -n 1` + cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&AS_MESSAGE_LOG_FD | ${AWK:-awk} '/^\*/{print [$]3;}' | head -n 1` test -n "$cf_gprconfig_value" && break done else cf_gprconfig_param=$cf_gprconfig - cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&AC_FD_CC | ${AWK:-awk} '/^\*/{print [$]3;}' | head -n 1` + cf_gprconfig_value=`echo s| gprconfig --config=$cf_gprconfig_param 2>&AS_MESSAGE_LOG_FD | ${AWK:-awk} '/^\*/{print [$]3;}' | head -n 1` fi if test -n "$cf_gprconfig_value" then @@ -7051,15 +7206,25 @@ AC_SUBST(cf_ada_config_Ada) AC_SUBST(cf_ada_config_C) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PROG_INSTALL version: 10 updated: 2021/01/04 19:33:05 +dnl CF_PROG_INSTALL version: 13 updated: 2025/10/21 16:28:49 dnl --------------- dnl Force $INSTALL to be an absolute-path. Otherwise, edit_man.sh and the dnl misc/tabset install won't work properly. Usually this happens only when dnl using the fallback mkinstalldirs script AC_DEFUN([CF_PROG_INSTALL], [AC_PROG_INSTALL -case $INSTALL in -(/*) +AC_REQUIRE([CF_GLOB_FULLPATH])dnl +if test "x$INSTALL" = "x./install-sh -c"; then + if test -f /usr/sbin/install ; then + case "$host_os" in + (linux*gnu*|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) + INSTALL=/usr/sbin/install + ;; + esac + fi +fi +case x$INSTALL in +(x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) ;; (*) CF_DIRNAME(cf_dir,$INSTALL) @@ -7089,14 +7254,17 @@ fi AC_SUBST(LDCONFIG) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_PROG_LINT version: 5 updated: 2022/08/20 15:44:13 +dnl CF_PROG_LINT version: 7 updated: 2024/11/30 14:37:45 dnl ------------ AC_DEFUN([CF_PROG_LINT], [ AC_CHECK_PROGS(LINT, lint cppcheck splint) case "x$LINT" in +(xlint|x*/lint) # NetBSD 10 + test -z "$LINT_OPTS" && LINT_OPTS="-chapbrxzgFS -v -Ac11" + ;; (xcppcheck|x*/cppcheck) - test -z "$LINT_OPTS" && LINT_OPTS="--enable=all" + test -z "$LINT_OPTS" && LINT_OPTS="--enable=all -D__CPPCHECK__" ;; esac AC_SUBST(LINT_OPTS) @@ -7125,7 +7293,15 @@ AC_MSG_RESULT($cf_prog_ln_sf) test "$cf_prog_ln_sf" = yes && LN_S="$LN_S -f" ])dnl dnl --------------------------------------------------------------------------- -dnl CF_REGEX version: 18 updated: 2021/01/01 16:53:59 +dnl CF_PROG_TBL version: 1 updated: 2025/11/01 18:43:38 +dnl ----------- +dnl Allow the "tbl" program to be configured. +dnl "TBL" is too short, and likely to conflict. +AC_DEFUN([CF_PROG_TBL],[ +AC_PATH_PROG(NROFF_TBL,tbl) +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_REGEX version: 20 updated: 2025/12/24 12:27:29 dnl -------- dnl Attempt to determine if we've got one of the flavors of regular-expression dnl code that we can support. @@ -7181,12 +7357,12 @@ case "$cf_regex_func" in (compile) for cf_regex_hdr in regexp.h regexpr.h do - AC_TRY_LINK([#include <$cf_regex_hdr>],[ + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include <$cf_regex_hdr>],[ char *p = compile("", "", "", 0); int x = step("", ""); (void)p; (void)x; - ],[ + ])],[ cf_cv_regex_hdrs=$cf_regex_hdr break ]) @@ -7195,15 +7371,16 @@ case "$cf_regex_func" in (*) for cf_regex_hdr in regex.h do - AC_TRY_LINK([#include + AC_LINK_IFELSE([AC_LANG_PROGRAM([#include +#include #include <$cf_regex_hdr>],[ - regex_t *p = 0; + regex_t *p = NULL; int x = regcomp(p, "", 0); int y = regexec(p, "", 0, 0, 0); (void)x; (void)y; regfree(p); - ],[ + ])],[ cf_cv_regex_hdrs=$cf_regex_hdr break ]) @@ -7269,6 +7446,30 @@ define([CF_REMOVE_LIB], $1=`echo "$2" | sed -e 's/-l$3[[ ]]//g' -e 's/-l$3[$]//'` ])dnl dnl --------------------------------------------------------------------------- +dnl CF_REQUIRE_PKG version: 1 updated: 2025/01/10 19:55:54 +dnl -------------- +dnl Update $REQUIRE_PKG, which lists the known required packages for this +dnl program. +dnl +dnl $1 = package(s) to require, e.g., in the generated ".pc" file +define([CF_REQUIRE_PKG], +[ +for cf_required in $1 +do + # check for duplicates + for cf_require_pkg in $REQUIRE_PKG + do + if test "$cf_required" = "$cf_require_pkg" + then + cf_required= + break + fi + done + test -n "$cf_required" && REQUIRE_PKG="$REQUIRE_PKG $cf_required" +done +AC_SUBST(REQUIRE_PKG) +])dnl +dnl --------------------------------------------------------------------------- dnl CF_RESTORE_XTRA_FLAGS version: 1 updated: 2020/01/11 16:47:45 dnl --------------------- dnl Restore flags saved in CF_SAVE_XTRA_FLAGS @@ -7280,7 +7481,7 @@ CFLAGS="$cf_save_CFLAGS_$1" CPPFLAGS="$cf_save_CPPFLAGS_$1" ])dnl dnl --------------------------------------------------------------------------- -dnl CF_RPATH_HACK version: 13 updated: 2021/01/03 18:30:50 +dnl CF_RPATH_HACK version: 14 updated: 2025/12/15 04:04:20 dnl ------------- AC_DEFUN([CF_RPATH_HACK], [AC_REQUIRE([AC_PROG_FGREP])dnl @@ -7296,8 +7497,8 @@ if test -n "$LD_RPATH_OPT" ; then then cf_rpath_oops= -AC_TRY_LINK([#include ], - [printf("Hello");], +AC_LINK_IFELSE([AC_LANG_PROGRAM([#include ], + [printf("Hello");])], [cf_rpath_oops=`"$cf_ldd_prog" "conftest$ac_exeext" | ${FGREP-fgrep} ' not found' | sed -e 's% =>.*$%%' |sort | uniq` cf_rpath_list=`"$cf_ldd_prog" "conftest$ac_exeext" | ${FGREP-fgrep} / | sed -e 's%^.*[[ ]]/%/%' -e 's%/[[^/]][[^/]]*$%%' |sort | uniq`]) @@ -7423,7 +7624,7 @@ do done ])dnl dnl --------------------------------------------------------------------------- -dnl CF_SHARED_OPTS version: 111 updated: 2024/03/29 20:08:49 +dnl CF_SHARED_OPTS version: 114 updated: 2025/12/15 04:04:20 dnl -------------- dnl -------------- dnl Attempt to determine the appropriate CC/LD options for creating a shared @@ -7513,7 +7714,7 @@ AC_DEFUN([CF_SHARED_OPTS], for CC_SHARED_OPTS in -fPIC -fpic '' do CFLAGS="$cf_save_CFLAGS $CC_SHARED_OPTS" - AC_TRY_COMPILE([#include ],[int x = 1; (void)x],[break],[]) + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[int x = 1; (void)x])],[break],[]) done AC_MSG_RESULT($CC_SHARED_OPTS) CFLAGS="$cf_save_CFLAGS" @@ -7588,7 +7789,7 @@ CF_EOF AC_CACHE_CHECK([if ld -search_paths_first works], cf_cv_ldflags_search_paths_first, [ cf_save_LDFLAGS=$LDFLAGS LDFLAGS="$LDFLAGS -Wl,-search_paths_first" - AC_TRY_LINK(, [int i;], cf_cv_ldflags_search_paths_first=yes, cf_cv_ldflags_search_paths_first=no) + AC_LINK_IFELSE([AC_LANG_PROGRAM([], [int i;])], cf_cv_ldflags_search_paths_first=yes, cf_cv_ldflags_search_paths_first=no) LDFLAGS=$cf_save_LDFLAGS]) if test "$cf_cv_ldflags_search_paths_first" = yes; then LDFLAGS="$LDFLAGS -Wl,-search_paths_first" @@ -7718,7 +7919,7 @@ CF_EOF -L*) ldopts+=("\`echo \"\[$]1\" | sed \"s/^-L/-LIBPATH:/\"\`") ;; - *.obj | *.o) + *.obj | *.$OBJEXT) ldopts+=("\[$]1") ;; -Wl,*) @@ -7895,7 +8096,7 @@ CF_EOF for cf_shared_opts in -xcode=pic32 -xcode=pic13 -KPIC -Kpic -O do CFLAGS="$cf_shared_opts $cf_save_CFLAGS" - AC_TRY_COMPILE([#include ],[printf("Hello\\n");],[break]) + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[printf("Hello\\n");])],[break]) done CFLAGS="$cf_save_CFLAGS" CC_SHARED_OPTS=$cf_shared_opts @@ -7939,7 +8140,7 @@ cat > conftest.$ac_ext < #include -],[int x = SIGWINCH; (void)x], +],[int x = SIGWINCH; (void)x])], [cf_cv_define_sigwinch=yes], - [AC_TRY_COMPILE([ + [AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #undef _XOPEN_SOURCE #undef _POSIX_SOURCE #undef _POSIX_C_SOURCE #include #include -],[int x = SIGWINCH; (void)x], +],[int x = SIGWINCH; (void)x])], [cf_cv_define_sigwinch=maybe], [cf_cv_define_sigwinch=no]) ]) @@ -8037,7 +8238,7 @@ cf_cv_fixup_sigwinch=unknown cf_sigwinch=32 while test "$cf_sigwinch" != 1 do - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #undef _XOPEN_SOURCE #undef _POSIX_SOURCE #undef _POSIX_C_SOURCE @@ -8047,7 +8248,7 @@ do #if SIGWINCH != $cf_sigwinch #error SIGWINCH is not $cf_sigwinch #endif -int x = SIGWINCH; (void)x], +int x = SIGWINCH; (void)x])], [cf_cv_fixup_sigwinch=$cf_sigwinch break]) @@ -8061,7 +8262,7 @@ done fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_SIG_ATOMIC_T version: 5 updated: 2020/03/10 18:53:47 +dnl CF_SIG_ATOMIC_T version: 6 updated: 2025/12/24 12:27:29 dnl --------------- dnl signal handler, but there are some gcc dependencies in that recommendation. dnl Try anyway. @@ -8074,7 +8275,7 @@ AC_CACHE_VAL(cf_cv_sig_atomic_t,[ "sig_atomic_t" \ "int" do - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #include #include @@ -8087,7 +8288,7 @@ static void handler(int sig) x = 5; }], [signal(SIGINT, handler); - x = 1], + x = 1])], [cf_cv_sig_atomic_t=$cf_type], [cf_cv_sig_atomic_t=no]) test "$cf_cv_sig_atomic_t" != no && break @@ -8097,7 +8298,7 @@ AC_MSG_RESULT($cf_cv_sig_atomic_t) test "$cf_cv_sig_atomic_t" != no && AC_DEFINE_UNQUOTED(SIG_ATOMIC_T, $cf_cv_sig_atomic_t,[Define to signal global datatype]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_SIZECHANGE version: 18 updated: 2021/09/04 06:35:04 +dnl CF_SIZECHANGE version: 19 updated: 2025/12/22 04:16:14 dnl ------------- dnl Check for definitions & structures needed for window size-changing dnl @@ -8117,7 +8318,7 @@ do then CF_APPEND_TEXT(CPPFLAGS,-D$cf_opts) fi - AC_TRY_COMPILE([#include + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include #ifdef HAVE_TERMIOS_H #include #else @@ -8155,13 +8356,13 @@ do no TIOCGSIZE or TIOCGWINSZ #endif /* TIOCGWINSZ */ #endif /* TIOCGSIZE */ - ], + ])], [cf_cv_sizechange=yes], [cf_cv_sizechange=no]) CPPFLAGS="$cf_save_CPPFLAGS" if test "$cf_cv_sizechange" = yes ; then - echo "size-change succeeded ($cf_opts)" >&AC_FD_CC + echo "size-change succeeded ($cf_opts)" >&AS_MESSAGE_LOG_FD test -n "$cf_opts" && cf_cv_sizechange="$cf_opts" break fi @@ -8294,7 +8495,7 @@ if test -n "$ADA_SUBDIRS"; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_STDCPP_LIBRARY version: 12 updated: 2021/01/01 13:31:04 +dnl CF_STDCPP_LIBRARY version: 13 updated: 2025/12/24 12:27:29 dnl ----------------- dnl Check for -lstdc++, which is GNU's standard C++ library. dnl If $CXXLIBS is set, add that to the libraries used for test-linking. @@ -8307,9 +8508,9 @@ if test -n "$GXX" ; then cf_save="$LIBS" LIBS="$LIBS $CXXLIBS" AC_MSG_CHECKING(if we already have C++ library) - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ - std::cout << "Hello World!" << std::endl;], + std::cout << "Hello World!" << std::endl;])], [cf_have_libstdcpp=yes], [cf_have_libstdcpp=no]) AC_MSG_RESULT($cf_have_libstdcpp) @@ -8334,9 +8535,9 @@ if test -n "$GXX" ; then cf_save="$LIBS" LIBS="$LIBS $CXXLIBS" CF_ADD_LIB($cf_stdcpp_libname) - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ - std::cout << "Hello World!" << std::endl;], + std::cout << "Hello World!" << std::endl;])], [cf_cv_libstdcpp=yes], [cf_cv_libstdcpp=no]) LIBS="$cf_save" @@ -8352,7 +8553,7 @@ dnl Remove "-g" option from the compiler options AC_DEFUN([CF_STRIP_G_OPT], [$1=`echo "${$1}" | CF__SED_TRIMBLANKS(-e 's%-g %%' -e 's%-g$%%')`])dnl dnl --------------------------------------------------------------------------- -dnl CF_STRUCT_SIGACTION version: 6 updated: 2023/12/03 09:21:34 +dnl CF_STRUCT_SIGACTION version: 7 updated: 2025/12/24 12:27:29 dnl ------------------- dnl Check if we need _POSIX_SOURCE defined to use struct sigaction. We'll only dnl do this if we've found the sigaction function. @@ -8361,17 +8562,17 @@ AC_REQUIRE([CF_XOPEN_SOURCE]) if test "$ac_cv_func_sigaction" = yes; then AC_MSG_CHECKING(whether sigaction needs _POSIX_SOURCE) -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #include ], - [struct sigaction act; (void)act], + [struct sigaction act; (void)act])], [sigact_bad=no], [ -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #define _POSIX_SOURCE #include #include ], - [struct sigaction act; (void)act], + [struct sigaction act; (void)act])], [sigact_bad=yes AC_DEFINE(_POSIX_SOURCE,1,[Define to 1 if we must define _POSIX_SOURCE])], [sigact_bad=unknown])]) @@ -8379,13 +8580,13 @@ AC_MSG_RESULT($sigact_bad) fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_STRUCT_TERMIOS version: 13 updated: 2023/12/03 19:38:54 +dnl CF_STRUCT_TERMIOS version: 15 updated: 2025/12/22 04:16:14 dnl ----------------- dnl Some machines require _POSIX_SOURCE to completely define struct termios. AC_DEFUN([CF_STRUCT_TERMIOS],[ AC_REQUIRE([CF_XOPEN_SOURCE]) -AC_CHECK_HEADERS( \ +AC_CHECK_HEADERS( sgtty.h \ termio.h \ termios.h \ unistd.h \ @@ -8401,13 +8602,13 @@ if test "$ac_cv_header_termios_h" = yes ; then esac if test "$termios_bad" = maybe ; then AC_MSG_CHECKING(whether termios.h needs _POSIX_SOURCE) - AC_TRY_COMPILE([#include ], - [struct termios foo; int x = (int)(foo.c_iflag = 1); (void)x], + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ], + [struct termios foo; int x = (int)(foo.c_iflag = 1); (void)x])], termios_bad=no, [ - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #define _POSIX_SOURCE #include ], - [struct termios foo; int x = (int)(foo.c_iflag = 2); (void)x], + [struct termios foo; int x = (int)(foo.c_iflag = 2); (void)x])], termios_bad=unknown, termios_bad=yes AC_DEFINE(_POSIX_SOURCE,1,[Define to 1 if we must define _POSIX_SOURCE])) ]) @@ -8487,7 +8688,7 @@ AC_SUBST(cf_cv_header_stdbool_h) AC_SUBST(cf_cv_type_of_bool)dnl ])dnl dnl --------------------------------------------------------------------------- -dnl CF_SYS_TIME_SELECT version: 6 updated: 2015/04/18 08:56:57 +dnl CF_SYS_TIME_SELECT version: 7 updated: 2025/12/24 12:27:29 dnl ------------------ dnl Check if we can include with ; this breaks on dnl older SCO configurations. @@ -8495,7 +8696,7 @@ AC_DEFUN([CF_SYS_TIME_SELECT], [ AC_MSG_CHECKING(if sys/time.h works with sys/select.h) AC_CACHE_VAL(cf_cv_sys_time_select,[ -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #ifdef HAVE_SYS_TIME_H #include @@ -8503,7 +8704,7 @@ AC_TRY_COMPILE([ #ifdef HAVE_SYS_SELECT_H #include #endif -],[],[cf_cv_sys_time_select=yes], +],[])],[cf_cv_sys_time_select=yes], [cf_cv_sys_time_select=no]) ]) AC_MSG_RESULT($cf_cv_sys_time_select) @@ -8519,7 +8720,7 @@ top_builddir=ifelse($1,,`pwd`,$1) AC_SUBST(top_builddir) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_TRY_PKG_CONFIG version: 6 updated: 2020/12/31 10:54:15 +dnl CF_TRY_PKG_CONFIG version: 7 updated: 2025/01/10 19:55:54 dnl ----------------- dnl This is a simple wrapper to use for pkg-config, for libraries which may be dnl available in that form. @@ -8536,6 +8737,7 @@ if test "$PKG_CONFIG" != none && "$PKG_CONFIG" --exists "$1"; then cf_pkgconfig_libs="`$PKG_CONFIG --libs "$1" 2>/dev/null`" CF_VERBOSE(package $1 CFLAGS: $cf_pkgconfig_incs) CF_VERBOSE(package $1 LIBS: $cf_pkgconfig_libs) + CF_REQUIRE_PKG($1) CF_ADD_CFLAGS($cf_pkgconfig_incs) CF_ADD_LIBS($cf_pkgconfig_libs) ifelse([$2],,:,[$2]) @@ -8546,17 +8748,17 @@ else fi ]) dnl --------------------------------------------------------------------------- -dnl CF_TRY_XOPEN_SOURCE version: 4 updated: 2022/09/10 15:16:16 +dnl CF_TRY_XOPEN_SOURCE version: 5 updated: 2025/12/14 17:40:20 dnl ------------------- dnl If _XOPEN_SOURCE is not defined in the compile environment, check if we dnl can define it successfully. AC_DEFUN([CF_TRY_XOPEN_SOURCE],[ AC_CACHE_CHECK(if we should define _XOPEN_SOURCE,cf_cv_xopen_source,[ - AC_TRY_COMPILE(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY, + AC_COMPILE_IFELSE([AC_LANG_PROGRAM(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY)], [cf_cv_xopen_source=no], [cf_save="$CPPFLAGS" CF_APPEND_TEXT(CPPFLAGS,-D_XOPEN_SOURCE=$cf_XOPEN_SOURCE) - AC_TRY_COMPILE(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY, + AC_COMPILE_IFELSE([AC_LANG_PROGRAM(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY)], [cf_cv_xopen_source=no], [cf_cv_xopen_source=$cf_XOPEN_SOURCE]) CPPFLAGS="$cf_save" @@ -8571,7 +8773,7 @@ if test "$cf_cv_xopen_source" != no ; then fi ]) dnl --------------------------------------------------------------------------- -dnl CF_TYPEOF_CHTYPE version: 11 updated: 2023/01/05 17:57:59 +dnl CF_TYPEOF_CHTYPE version: 12 updated: 2024/12/14 16:09:34 dnl ---------------- dnl Determine the type we should use for chtype (and attr_t, which is treated dnl as the same thing). We want around 32 bits, so on most machines want a @@ -8587,7 +8789,7 @@ $ac_includes_default int main(void) { FILE *fp = fopen("cf_test.out", "w"); - if (fp != 0) { + if (fp != NULL) { char *result = "long"; if (sizeof(unsigned long) > sizeof(unsigned int)) { int n; @@ -8623,23 +8825,23 @@ AC_SUBST(cf_cv_typeof_chtype) AC_DEFINE_UNQUOTED(TYPEOF_CHTYPE,$cf_cv_typeof_chtype,[Define to actual type if needed for chtype]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_TYPE_SIGACTION version: 5 updated: 2023/12/03 09:21:34 +dnl CF_TYPE_SIGACTION version: 6 updated: 2025/12/24 12:27:29 dnl ----------------- dnl AC_DEFUN([CF_TYPE_SIGACTION], [ AC_MSG_CHECKING([for type sigaction_t]) AC_CACHE_VAL(cf_cv_type_sigaction,[ - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include ], - [sigaction_t x; (void)x], + [sigaction_t x; (void)x])], [cf_cv_type_sigaction=yes], [cf_cv_type_sigaction=no])]) AC_MSG_RESULT($cf_cv_type_sigaction) test "$cf_cv_type_sigaction" = yes && AC_DEFINE(HAVE_TYPE_SIGACTION,1,[Define to 1 if we have the sigaction_t type]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_UNSIGNED_LITERALS version: 3 updated: 2023/12/03 10:02:17 +dnl CF_UNSIGNED_LITERALS version: 4 updated: 2025/12/24 12:27:29 dnl -------------------- dnl Test if the compiler supports 'U' and 'L' suffixes. Only old compilers dnl won't, but they're still there. @@ -8647,7 +8849,7 @@ AC_DEFUN([CF_UNSIGNED_LITERALS], [ AC_MSG_CHECKING([if unsigned literals are legal]) AC_CACHE_VAL(cf_cv_unsigned_literals,[ - AC_TRY_COMPILE([],[long x = 1L + 1UL + 1U + 1; (void)x], + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([],[long x = 1L + 1UL + 1U + 1; (void)x])], [cf_cv_unsigned_literals=yes], [cf_cv_unsigned_literals=no]) ]) @@ -8663,20 +8865,20 @@ AC_DEFUN([CF_UPPER], $1=`echo "$2" | sed y%abcdefghijklmnopqrstuvwxyz./-%ABCDEFGHIJKLMNOPQRSTUVWXYZ___%` ])dnl dnl --------------------------------------------------------------------------- -dnl CF_UTF8_LIB version: 10 updated: 2023/01/11 04:05:23 +dnl CF_UTF8_LIB version: 12 updated: 2025/12/22 04:16:14 dnl ----------- dnl Check for multibyte support, and if not found, utf8 compatibility library AC_DEFUN([CF_UTF8_LIB], [ -AC_HAVE_HEADERS(wchar.h) +AC_CHECK_HEADERS(wchar.h) AC_CACHE_CHECK(for multibyte character support,cf_cv_utf8_lib,[ cf_save_LIBS="$LIBS" - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ $ac_includes_default #ifdef HAVE_WCHAR_H #include #endif -],[putwc(0,0);], +],[putwc(0,0);])], [cf_cv_utf8_lib=yes], [CF_FIND_LINKAGE([ #include ],[putwc(0,0);],utf8, @@ -8694,19 +8896,19 @@ if test "$cf_cv_utf8_lib" = "add-on" ; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_VA_COPY version: 6 updated: 2018/12/04 18:14:25 +dnl CF_VA_COPY version: 7 updated: 2025/12/24 12:27:29 dnl ---------- dnl check for va_copy, part of stdarg.h starting with ISO C 1999. dnl Also, workaround for glibc's __va_copy, by checking for both. dnl Finally, try to accommodate pre-ISO C 1999 headers. AC_DEFUN([CF_VA_COPY],[ AC_CACHE_CHECK(for va_copy, cf_cv_have_va_copy,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ static va_list dst; static va_list src; - va_copy(dst, src)], + va_copy(dst, src)])], cf_cv_have_va_copy=yes, cf_cv_have_va_copy=no)]) @@ -8716,12 +8918,12 @@ then else # !cf_cv_have_va_copy AC_CACHE_CHECK(for __va_copy, cf_cv_have___va_copy,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ static va_list dst; static va_list src; - __va_copy(dst, src)], + __va_copy(dst, src)])], cf_cv_have___va_copy=yes, cf_cv_have___va_copy=no)]) @@ -8731,12 +8933,12 @@ then else # !cf_cv_have___va_copy AC_CACHE_CHECK(for __builtin_va_copy, cf_cv_have___builtin_va_copy,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ static va_list dst; static va_list src; - __builtin_va_copy(dst, src)], + __builtin_va_copy(dst, src)])], cf_cv_have___builtin_va_copy=yes, cf_cv_have___builtin_va_copy=no)]) @@ -8753,24 +8955,24 @@ case "${cf_cv_have_va_copy}${cf_cv_have___va_copy}${cf_cv_have___builtin_va_copy (*) AC_CACHE_CHECK(if we can simply copy va_list, cf_cv_pointer_va_list,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ va_list dst; va_list src; - dst = src], + dst = src])], cf_cv_pointer_va_list=yes, cf_cv_pointer_va_list=no)]) if test "$cf_cv_pointer_va_list" = no then AC_CACHE_CHECK(if we can copy va_list indirectly, cf_cv_array_va_list,[ -AC_TRY_LINK([ +AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ va_list dst; va_list src; - *dst = *src], + *dst = *src])], cf_cv_array_va_list=yes, cf_cv_array_va_list=no)]) test "$cf_cv_array_va_list" = yes && AC_DEFINE(ARRAY_VA_LIST,1,[Define to 1 if we can copy va_list indirectly]) @@ -8779,15 +8981,15 @@ AC_TRY_LINK([ esac ]) dnl --------------------------------------------------------------------------- -dnl CF_VERBOSE version: 3 updated: 2007/07/29 09:55:12 +dnl CF_VERBOSE version: 4 updated: 2025/12/14 17:51:46 dnl ---------- dnl Use AC_VERBOSE w/o the warnings AC_DEFUN([CF_VERBOSE], -[test -n "$verbose" && echo " $1" 1>&AC_FD_MSG +[test -n "$verbose" && echo " $1" 1>&AS_MESSAGE_FD CF_MSG_LOG([$1]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_VERSION_INFO version: 8 updated: 2021/01/01 13:31:04 +dnl CF_VERSION_INFO version: 11 updated: 2025/09/20 13:27:11 dnl --------------- dnl Define several useful symbols derived from the VERSION file. A separate dnl file is preferred to embedding the version numbers in various scripts. @@ -8865,17 +9067,19 @@ AC_SUBST(VERSION_PATCH) dnl if a package name is given, define its corresponding version info. We dnl need the package name to ensure that the defined symbols are unique. ifelse($1,,,[ - cf_PACKAGE=$1 + PROGRAM=$1 PACKAGE=ifelse($2,,$1,$2) AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE",[Define to the package-name]) + AC_SUBST(PROGRAM) AC_SUBST(PACKAGE) - CF_UPPER(cf_PACKAGE,$cf_PACKAGE) - AC_DEFINE_UNQUOTED(${cf_PACKAGE}_VERSION,"${VERSION_MAJOR}.${VERSION_MINOR}") - AC_DEFINE_UNQUOTED(${cf_PACKAGE}_PATCHDATE,${VERSION_PATCH}) + AH_TEMPLATE([AS_TR_CPP($1[_VERSION])],[version of package]) + AC_DEFINE_UNQUOTED(AS_TR_CPP($1[_VERSION]),"${VERSION_MAJOR}.${VERSION_MINOR}",[define to version of $1]) + AH_TEMPLATE([AS_TR_CPP($1[_PATCHDATE])],[patchdate of package]) + AC_DEFINE_UNQUOTED(AS_TR_CPP($1[_PATCHDATE]),${VERSION_PATCH},[define to patchdate of $1]) ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WCHAR_TYPE version: 5 updated: 2023/12/03 09:21:34 +dnl CF_WCHAR_TYPE version: 6 updated: 2025/12/24 12:27:29 dnl ------------- dnl Check if type wide-character type $1 is declared, and if so, which header dnl file is needed. The second parameter is used to set a shell variable when @@ -8885,16 +9089,16 @@ AC_DEFUN([CF_WCHAR_TYPE], [ # This is needed on Tru64 5.0 to declare $1 AC_CACHE_CHECK(if we must include wchar.h to declare $1,cf_cv_$1,[ -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #include #include #ifdef HAVE_LIBUTF8_H #include #endif], - [$1 state; (void)state], + [$1 state; (void)state])], [cf_cv_$1=no], - [AC_TRY_COMPILE([ + [AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #include #include @@ -8902,7 +9106,7 @@ AC_TRY_COMPILE([ #ifdef HAVE_LIBUTF8_H #include #endif], - [$1 value; (void) value], + [$1 value; (void) value])], [cf_cv_$1=yes], [cf_cv_$1=unknown])])]) @@ -8925,14 +9129,14 @@ fi ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WEAK_SYMBOLS version: 1 updated: 2008/08/16 19:18:06 +dnl CF_WEAK_SYMBOLS version: 2 updated: 2025/12/24 12:27:29 dnl --------------- dnl Check for compiler-support for weak symbols. dnl This works with "recent" gcc. AC_DEFUN([CF_WEAK_SYMBOLS],[ AC_CACHE_CHECK(if $CC supports weak symbols,cf_cv_weak_symbols,[ -AC_TRY_COMPILE([ +AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include ], [ #if defined(__GNUC__) @@ -8947,7 +9151,7 @@ AC_TRY_COMPILE([ #endif weak_symbol(fopen); -],[cf_cv_weak_symbols=yes],[cf_cv_weak_symbols=no]) +])],[cf_cv_weak_symbols=yes],[cf_cv_weak_symbols=no]) ]) ])dnl dnl --------------------------------------------------------------------------- @@ -9001,6 +9205,56 @@ $1_ABI=$cf_cv_abi_version cf_cv_abi_default=$cf_cv_abi_version ])dnl dnl --------------------------------------------------------------------------- +dnl CF_WITH_ADA version: 2 updated: 2024/11/09 18:07:29 +dnl ----------- +dnl Check for the Ada compiler (unless requested to not do this), which causes +dnl a further check for a C compiler which can work with the Ada compiler. +AC_DEFUN([CF_WITH_ADA],[ +AC_ARG_WITH(ada, + [ --without-ada suppress check for Ada compiler], + [cf_with_ada=$withval], + [cf_with_ada=yes]) + +cf_prog_cc="gcc cc" +if test "x$cf_with_ada" = xyes +then + CF_PROG_GNAT + if test "x$cf_cv_prog_gnat_correct" = xyes; then + # gcc's developers chose to deprecate gnatgcc before making gprconfig + # work. They replaced gnatgcc in gcc 13 with a script which spits out + # a warning offering advice which could never work. + # + # Here is a workaround. + AC_PATH_PROG(cf_cv_path_gnatgcc,gnatgcc,no) + if test "$cf_cv_path_gnatgcc" != no + then + AC_MSG_CHECKING(for improvement) + cf_file_gnatgcc=`file -L "$cf_cv_path_gnatgcc" 2>/dev/null` + case "x$cf_file_gnatgcc" in + (*script*) + cf_cv_path_gnatgcc=`sh -x "$cf_cv_path_gnatgcc" --version 2>&1 | grep -w exec | sed -e 's/^[[ ]]*+[[ ]]*//' -e 's/exec[[ ]]//' -e 's/ .*//'` + ;; + (*) + cf_cv_path_gnatgcc=no + ;; + esac + AC_MSG_RESULT($cf_cv_path_gnatgcc) + test "$cf_cv_path_gnatgcc" = no && cf_cv_path_gnatgcc=gnatgcc + cf_prog_cc="$cf_cv_path_gnatgcc $cf_prog_cc" + fi + fi +fi +case "$cf_prog_cc" in +(*/*) + CC="$cf_prog_cc" + AC_SUBST(CC) + ;; +(*) + CF_PROG_CC($cf_prog_cc) + ;; +esac +])dnl +dnl --------------------------------------------------------------------------- dnl CF_WITH_ADA_COMPILER version: 3 updated: 2023/10/28 11:59:01 dnl -------------------- dnl Command-line option to specify the Ada95 compiler. @@ -9201,7 +9455,7 @@ if test "$with_gpm" != no ; then fi ]) dnl --------------------------------------------------------------------------- -dnl CF_WITH_LIBTOOL version: 36 updated: 2021/01/01 13:31:04 +dnl CF_WITH_LIBTOOL version: 38 updated: 2025/10/01 18:05:23 dnl --------------- dnl Provide a configure option to incorporate libtool. Define several useful dnl symbols for the makefile rules. @@ -9285,7 +9539,7 @@ ifdef([AC_PROG_LIBTOOL],[ fi ])dnl LIB_CREATE='${LIBTOOL} --mode=link ${CC} -rpath ${libdir} ${LIBTOOL_VERSION} `cut -f1 ${top_srcdir}/VERSION` ${LIBTOOL_OPTS} ${LT_UNDEF} $(LIBS) -o' - LIB_OBJECT='${OBJECTS:.o=.lo}' + LIB_OBJECT='${OBJECTS:.${OBJEXT}=.lo}' LIB_SUFFIX=.la LIB_CLEAN='${LIBTOOL} --mode=clean' LIB_COMPILE='${LIBTOOL} --mode=compile' @@ -9565,7 +9819,7 @@ if test "x$with_pcre2" != xno ; then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WITH_PKG_CONFIG_LIBDIR version: 23 updated: 2023/11/22 20:48:30 +dnl CF_WITH_PKG_CONFIG_LIBDIR version: 25 updated: 2024/08/03 13:34:29 dnl ------------------------- dnl Allow the choice of the pkg-config library directory to be overridden. dnl @@ -9579,6 +9833,7 @@ dnl pkgconf (used with some systems such as FreeBSD in place of pkg-config) dnl optionally ignores $PKG_CONFIG_LIBDIR. Very old versions of pkg-config, dnl e.g., Solaris 10 also do not recognize $PKG_CONFIG_LIBDIR. AC_DEFUN([CF_WITH_PKG_CONFIG_LIBDIR],[ +AC_REQUIRE([CF_GLOB_FULLPATH])dnl case "$PKG_CONFIG" in (no|none|yes) @@ -9612,10 +9867,10 @@ case "x$cf_search_path" in ;; (x) ;; -(x/*\ *) +(x$GLOB_FULLPATH_POSIX\ *|x$GLOB_FULLPATH_OTHER\ *) PKG_CONFIG_LIBDIR= ;; -(x/*) +(x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) PKG_CONFIG_LIBDIR="$cf_search_path" AC_MSG_RESULT($PKG_CONFIG_LIBDIR) cf_search_path= @@ -9634,7 +9889,15 @@ case "x$cf_search_path" in pkg-config \ pkgconf do - cf_search_path=`"$PKG_CONFIG" --variable=pc_path "$cf_pkg_program" 2>/dev/null | tr : ' '` + cf_raw_search_path=`"$PKG_CONFIG" --variable=pc_path "$cf_pkg_program" 2>/dev/null` + case "$cf_raw_search_path" in + (*\\*) + cf_search_path=`echo "$cf_raw_search_path" | tr ';' ' ' | tr '\' '/'` + ;; + (*/*) + cf_search_path=`echo "$cf_raw_search_path" | tr : ' '` + ;; + esac test -n "$cf_search_path" && break done @@ -9707,7 +9970,7 @@ fi AC_SUBST(PKG_CONFIG_LIBDIR) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WITH_PTHREAD version: 7 updated: 2015/04/18 08:56:57 +dnl CF_WITH_PTHREAD version: 8 updated: 2025/12/24 12:27:29 dnl --------------- dnl Check for POSIX thread library. AC_DEFUN([CF_WITH_PTHREAD], @@ -9728,12 +9991,12 @@ if test "$with_pthread" != no ; then AC_MSG_CHECKING(if we can link with the $cf_lib_pthread library) cf_save_LIBS="$LIBS" CF_ADD_LIB($cf_lib_pthread) - AC_TRY_LINK([ + AC_LINK_IFELSE([AC_LANG_PROGRAM([ #include ],[ int rc = pthread_create(0,0,0,0); int r2 = pthread_mutexattr_settype(0, 0); -],[with_pthread=yes],[with_pthread=no]) +])],[with_pthread=yes],[with_pthread=no]) LIBS="$cf_save_LIBS" AC_MSG_RESULT($with_pthread) test "$with_pthread" = yes && break @@ -9775,7 +10038,7 @@ ifelse($1,,[ ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WITH_SYSMOUSE version: 3 updated: 2012/10/06 17:56:13 +dnl CF_WITH_SYSMOUSE version: 4 updated: 2025/12/24 12:27:29 dnl ---------------- dnl If we can compile with sysmouse, make it available unless it is not wanted. AC_DEFUN([CF_WITH_SYSMOUSE],[ @@ -9787,7 +10050,7 @@ AC_ARG_WITH(sysmouse, [cf_with_sysmouse=$withval], [cf_with_sysmouse=maybe]) if test "$cf_with_sysmouse" != no ; then - AC_TRY_COMPILE([ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([ #include #if (__FreeBSD_version >= 400017) #include @@ -9798,14 +10061,14 @@ AC_ARG_WITH(sysmouse, ],[ struct mouse_info the_mouse; ioctl(0, CONS_MOUSECTL, &the_mouse); -],[cf_with_sysmouse=yes],[cf_with_sysmouse=no]) +])],[cf_with_sysmouse=yes],[cf_with_sysmouse=no]) fi AC_MSG_RESULT($cf_with_sysmouse) test "$cf_with_sysmouse" = yes && AC_DEFINE(USE_SYSMOUSE,1,[Define to 1 if we can/should use the sysmouse interface]) fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WITH_SYSTYPE version: 1 updated: 2013/01/26 16:26:12 +dnl CF_WITH_SYSTYPE version: 2 updated: 2025/12/14 18:08:20 dnl --------------- dnl For testing, override the derived host system-type which is used to decide dnl things such as the linker commands used to build shared libraries. This is @@ -9816,7 +10079,7 @@ dnl This is different from the --host option: it is used only for testing parts dnl of the configure script which would not be reachable with --host since that dnl relies on the build environment being real, rather than mocked up. AC_DEFUN([CF_WITH_SYSTYPE],[ -CF_CHECK_CACHE([AC_CANONICAL_SYSTEM]) +CF_CHECK_CACHE([AC_CANONICAL_TARGET]) AC_ARG_WITH(system-type, [ --with-system-type=XXX test: override derived host system-type], [AC_MSG_WARN(overriding system type to $withval) @@ -9854,7 +10117,7 @@ CF_NO_LEAKS_OPTION(valgrind, [USE_VALGRIND]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_WITH_VERSIONED_SYMS version: 13 updated: 2023/12/03 09:24:04 +dnl CF_WITH_VERSIONED_SYMS version: 17 updated: 2025/12/16 04:01:46 dnl ---------------------- dnl Use this when building shared library with ELF, to markup symbols with the dnl version identifier from the given input file. Generally that identifier is @@ -9864,7 +10127,11 @@ dnl $1 = basename of the ".map" file (default $PACKAGE) AC_DEFUN([CF_WITH_VERSIONED_SYMS], [AC_REQUIRE([AC_PROG_FGREP])dnl AC_REQUIRE([AC_PROG_EGREP])dnl +AC_REQUIRE([CF_GLOB_FULLPATH])dnl +if test "$with_libtool" = "yes" ; then + : +elif test "$with_shared" = "yes" ; then AC_MSG_CHECKING(if versioned-symbols file should be used) AC_ARG_WITH(versioned-syms, [[ --with-versioned-syms[=MAP-FILE] version ELF shared library symbols per MAP-FILE]], @@ -9877,7 +10144,7 @@ case "x$with_versioned_syms" in ;; (xno) ;; -(x/*) +(x$GLOB_FULLPATH_POSIX|x$GLOB_FULLPATH_OTHER) test -f "$with_versioned_syms" || AC_MSG_ERROR(expected a filename: $with_versioned_syms) ;; (*) @@ -9899,11 +10166,13 @@ then VERSIONED_SYMS="-Wl,--version-script,\${RESULTING_SYMS}" MK_SHARED_LIB=`echo "$MK_SHARED_LIB" | sed -e "s%-Wl,%\\[$]{VERSIONED_SYMS} -Wl,%"` CF_VERBOSE(MK_SHARED_LIB: $MK_SHARED_LIB) + LIB_CREATE="[$]MK_SHARED_LIB" ;; (*-dy\ *) VERSIONED_SYMS="-Wl,-M,\${RESULTING_SYMS}" MK_SHARED_LIB=`echo "$MK_SHARED_LIB" | sed -e "s%-dy%\\[$]{VERSIONED_SYMS} -dy%"` CF_VERBOSE(MK_SHARED_LIB: $MK_SHARED_LIB) + LIB_CREATE="[$]MK_SHARED_LIB" ;; (*) AC_MSG_WARN(this system does not support versioned-symbols) @@ -9978,16 +10247,18 @@ conftest.so: conftest.$ac_cv_objext EOF # compile source, make library - if make -f conftest.mk 2>&AC_FD_CC >/dev/null + if make -f conftest.mk 2>&AS_MESSAGE_LOG_FD >/dev/null then # test for missing symbol in either Data or Text section - cf_missing="`nm -P conftest.so 2>&AC_FD_CC |${FGREP-fgrep} _ismissing | ${EGREP-egrep} '[[ ]][[DT]][[ ]]'`" + cf_missing="`nm -P conftest.so 2>&AS_MESSAGE_LOG_FD |${FGREP-fgrep} _ismissing | ${EGREP-egrep} '[[ ]][[DT]][[ ]]'`" test -n "$cf_missing" && WILDCARD_SYMS=yes fi AC_MSG_RESULT($WILDCARD_SYMS) rm -f conftest.* fi fi + +fi AC_SUBST(RESULTING_SYMS) AC_SUBST(VERSIONED_SYMS) AC_SUBST(WILDCARD_SYMS) @@ -10079,7 +10350,59 @@ fi AC_SUBST(no_x11_rgb) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_XOPEN_SOURCE version: 67 updated: 2023/09/06 18:55:27 +dnl CF_WITH_XTERM_KBS version: 3 updated: 2025/10/21 03:55:54 +dnl ----------------- +dnl Configure-option with platform-defaults for the "xterm+kbs" building block +dnl in the terminfo file. +dnl +dnl The terminfo "kbs" value corresponds to "stty erase", and is conventionally +dnl assigned to the key which has +dnl +dnl a "Backspace" label and/or +dnl a backarrow symbol. +dnl +dnl See XTerm FAQ "Why doesn't my delete key work?" +dnl https://invisible-island.net/xterm/xterm.faq.html#xterm_erase +AC_DEFUN([CF_WITH_XTERM_KBS],[ +case $host_os in +(linux*gnu*|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc|linux*musl|openbsd*|darwin*) + want_xterm_kbs=DEL + ;; +(*) + want_xterm_kbs=BS + ;; +esac + +AC_MSG_CHECKING(if xterm backspace-key sends BS or DEL) +AC_ARG_WITH(xterm-kbs, + [[ --with-xterm-kbs[=XXX] specify if xterm backspace-key sends BS or DEL]], + [with_xterm_kbs=$withval], + [with_xterm_kbs=auto]) +case x$with_xterm_kbs in +(xyes|xno|xBS|xbs|x8) + with_xterm_kbs=BS + ;; +(xDEL|xdel|x127) + with_xterm_kbs=DEL + ;; +(xauto) + with_xterm_kbs=$want_xterm_kbs + ;; +(*) + with_xterm_kbs=$withval + ;; +esac +AC_MSG_RESULT($with_xterm_kbs) +XTERM_KBS=$with_xterm_kbs +AC_SUBST(XTERM_KBS) + +if test "x$with_xterm_kbs" != "x$want_xterm_kbs" +then + AC_MSG_WARN([expected --with-xterm-kbs=$want_xterm_kbs for $host_os, have $with_xterm_kbs]) +fi +])dnl +dnl --------------------------------------------------------------------------- +dnl CF_XOPEN_SOURCE version: 71 updated: 2025/12/14 17:40:20 dnl --------------- dnl Try to get _XOPEN_SOURCE defined properly that we can use POSIX functions, dnl or adapt to the vendor's definitions to get equivalent functionality, @@ -10139,9 +10462,12 @@ case "$host_os" in cf_xopen_source="-D_SGI_SOURCE" cf_XOPEN_SOURCE= ;; -(linux*gnu|linux*gnuabi64|linux*gnuabin32|linux*gnueabi|linux*gnueabihf|linux*gnux32|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) +(linux*gnu*|uclinux*|gnu*|mint*|k*bsd*-gnu|cygwin|msys|mingw*|linux*uclibc) CF_GNU_SOURCE($cf_XOPEN_SOURCE) ;; +linux*musl) + cf_xopen_source="-D_BSD_SOURCE" + ;; (minix*) cf_xopen_source="-D_NETBSD_SOURCE" # POSIX.1-2001 features are ifdef'd with this... ;; @@ -10193,7 +10519,7 @@ case "$host_os" in # Some of these niche implementations use copy/paste, double-check... if test "$cf_cv_xopen_source" = no ; then CF_VERBOSE(checking if _POSIX_C_SOURCE interferes with _XOPEN_SOURCE) - AC_TRY_COMPILE(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY,,[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM(CF__XOPEN_SOURCE_HEAD,CF__XOPEN_SOURCE_BODY)],,[ AC_MSG_WARN(_POSIX_C_SOURCE definition is not usable) CPPFLAGS="$cf_save_xopen_cppflags"]) fi @@ -10209,19 +10535,19 @@ dnl which is still not guaranteed to provide all of the entrypoints that dnl _XOPEN_SOURCE would yield. if test -n "$cf_XOPEN_SOURCE" && test -z "$cf_cv_xopen_source" ; then AC_MSG_CHECKING(if _XOPEN_SOURCE really is set) - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #ifndef _XOPEN_SOURCE #error _XOPEN_SOURCE is not defined -#endif], +#endif])], [cf_XOPEN_SOURCE_set=yes], [cf_XOPEN_SOURCE_set=no]) AC_MSG_RESULT($cf_XOPEN_SOURCE_set) if test "$cf_XOPEN_SOURCE_set" = yes then - AC_TRY_COMPILE([#include ],[ + AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],[ #if (_XOPEN_SOURCE - 0) < $cf_XOPEN_SOURCE #error (_XOPEN_SOURCE - 0) < $cf_XOPEN_SOURCE -#endif], +#endif])], [cf_XOPEN_SOURCE_set_ok=yes], [cf_XOPEN_SOURCE_set_ok=no]) if test "$cf_XOPEN_SOURCE_set_ok" = no diff --git a/announce.html.in b/announce.html.in index 9889ef1..79ced53 100644 --- a/announce.html.in +++ b/announce.html.in @@ -1,7 +1,7 @@ -adacursesw6\-config 1 2024-04-20 ncurses 6.5 User commands +adacursesw6\-config 1 2025-04-05 ncurses 6.6 User commands -

adacursesw6\-config 1 2024-04-20 ncurses 6.5 User commands

+

adacursesw6\-config 1 2025-04-05 ncurses 6.6 User commands

 adacursesw6-config(1)            User commands           adacursesw6-config(1)
 
 
-
-

NAME

        adacursesw6-config - configuration helper for AdaCurses libraries
 
@@ -69,8 +67,8 @@
 
        --libs     reports the GNAT libraries needed to link with AdaCurses.
 
-       --version  reports  the  release  and  patch  date  information  of the
-                  ncurses libraries used to configure and build AdaCurses  and
+       --version  reports the  release  and  patch  date  information  of  the
+                  ncurses  libraries used to configure and build AdaCurses and
                   exits successfully.
 
        --help     issues a usage message and exits successfully.
@@ -112,7 +110,6 @@
               end loop;
 
               End_Windows;
-
            end Hello;
 
        Then, using
@@ -126,9 +123,7 @@

SEE ALSO

        curses(3x)
 
-
-
-ncurses 6.5                       2024-04-20             adacursesw6-config(1)
+ncurses 6.6                       2025-04-05             adacursesw6-config(1)
    diff --git a/doc/html/man/captoinfo.1m.html b/doc/html/man/captoinfo.1m.html index 92f9905..1c9ddca 100644 --- a/doc/html/man/captoinfo.1m.html +++ b/doc/html/man/captoinfo.1m.html @@ -1,7 +1,7 @@ -captoinfo 1m 2024-03-23 ncurses 6.5 User commands +captoinfo 1m 2025-11-11 ncurses 6.6 User commands -

    captoinfo 1m 2024-03-23 ncurses 6.5 User commands

    +

    captoinfo 1m 2025-11-11 ncurses 6.6 User commands

     captoinfo(1m)                    User commands                   captoinfo(1m)
 
 
-
-

    NAME

            captoinfo - convert a termcap description into a terminfo description
 
@@ -63,10 +61,10 @@
        equivalent terminfo description to the standard output stream.  termcap
        tc capabilities translate to terminfo "use" capabilities.
 
-       If no files are specified, captoinfo  interprets  the  content  of  the
-       environment  variable  TERMCAP  as  a  file name, and extracts only the
-       entry for the terminal named in the environment variable TERM from  it.
-       If  the  environment  variable  TERMCAP  is  not  set,  captoinfo reads
+       If  no  files  are  specified,  captoinfo interprets the content of the
+       environment variable TERMCAP as a file  name,  and  extracts  only  the
+       entry for the terminal type named in the environment variable TERM from
+       it.   If  the  environment variable TERMCAP is not set, captoinfo reads
        /etc/termcap.
 
        This utility is implemented as a link to tic(1m), with the latter's  -I
@@ -77,12 +75,11 @@

    Translations from Nonstandard Capabilities

            captoinfo  translates  some  obsolete,  nonstandard  capabilities  into
-       standard  (SVr4/XSI  Curses)  terminfo  capabilities.   It   issues   a
-       diagnostic  to the standard error stream for each, inviting the user to
-       check that it has not mistakenly  translated  an  unknown  or  mistyped
-       capability name.
+       standard terminfo capabilities.  It issues a diagnostic to the standard
+       error stream for each, inviting the user  to  check  that  it  has  not
+       mistakenly translated an unknown or mistyped capability name.
 
-                     Name
+                 termcap Code
               Obsolete   Standard    Origin      terminfo capability
               ---------------------------------------------------------
                  BO         mr        AT&T      enter_reverse_mode
@@ -111,14 +108,13 @@
                  KE         F4      Tektronix   key_f14
                  KF         F5      Tektronix   key_f15
                  BC         Sb      Tektronix   set_background
-
                  FC         Sf      Tektronix   set_foreground
                  HS         mh        IRIX      enter_dim_mode
 
        XENIX termcap had a set of extension capabilities, corresponding to box
        drawing characters of CCSID ("code page") 437, as follows.
 
-                      termcap Name            Graphic
+                      termcap Code            Graphic
                       -----------------------------------------
                            G2        upper left corner
                            G3        lower left corner
@@ -144,27 +140,28 @@
                            Gc        double intersection
                            GG        ACS magic cookie count
 
-       captoinfo composes single-line capabilities into an  acsc  string,  and
-       discards GG and double-line capabilities with a warning diagnostic.
+       captoinfo composes single-line box-drawing capabilities into a terminfo
+       acs_chars  (acsc)  string  capability,  and discards GG and double-line
+       capabilities with a warning diagnostic.
 
-       IBM's  AIX  has  a  terminfo facility descended from SVr1 terminfo, but
-       which is incompatible with the SVr4 format.  captoinfo  translates  the
-       following AIX extensions.
+       AIX has a terminfo facility descended from SVr2 terminfo, but which  is
+       incompatible  with the SVr4 format.  captoinfo translates the following
+       AIX extensions.
 
-                                     IBM    XSI
-                                    -------------
-                                    ksel    kslt
-                                    kbtab   kcbt
-                                    font0   s0ds
-                                    font1   s1ds
-                                    font2   s2ds
-                                    font3   s3ds
+                                    IBM    X/Open
+                                   ---------------
+                                   ksel    kslt
+                                   kbtab   kcbt
+                                   font0   s0ds
+                                   font1   s1ds
+                                   font2   s2ds
+                                   font3   s3ds
 
-       Additionally,  this  program  translates  the AIX box1 capability to an
-       acsc string.
+       It furthermore translates the  AIX  box1  capability  to  an  acs_chars
+       (acsc) string capability.
 
-       The  HP-UX  terminfo  library   supports   two   nonstandard   terminfo
-       capabilities,  meml  (memory lock) and memu (memory unlock).  captoinfo
+       The   HP-UX   terminfo   library   supports  two  nonstandard  terminfo
+       capabilities: memory_lock (meml) and memory_unlock  (memu).   captoinfo
        discards these with a warning message.
 
 
@@ -173,12 +170,15 @@
               default termcap terminal capability database
 
 
-

    PORTABILITY

    -       X/Open Curses, Issue 7 (2009) describes tic  briefly,  but  omits  this
-       program.
+

    EXTENSIONS

    +       This command is an SVr4 curses and ncurses extension.
 
-       SVr4 systems provide captoinfo as a separate application from tic.  Its
-       -v option does not accept a trace level argument n; repeat -v  n  times
+
+

    PORTABILITY

    +       X/Open Curses Issue 7 (2009) does not specify this command.
+
+       SVr4 systems provide captoinfo as a separate application from tic.  Its
+       -v  option  does not accept a trace level argument n; repeat -v n times
        instead.
 
        NetBSD does not provide this application.
@@ -192,9 +192,7 @@

    SEE ALSO

            infocmp(1m), tic(1m), curses(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-03-23                     captoinfo(1m)
+ncurses 6.6                       2025-11-11                     captoinfo(1m)
      @@ -206,6 +204,7 @@ ncurses 6.5 2024-03-23
    • FILES
      • +
    • EXTENSIONS
    • PORTABILITY
    • AUTHORS
    • SEE ALSO
      • diff --git a/doc/html/man/clear.1.html b/doc/html/man/clear.1.html index e7da4da..b47dca5 100644 --- a/doc/html/man/clear.1.html +++ b/doc/html/man/clear.1.html @@ -1,6 +1,6 @@ -clear 1 2024-03-16 ncurses 6.5 User commands +clear 1 2025-04-05 ncurses 6.6 User commands -

      clear 1 2024-03-16 ncurses 6.5 User commands

      +

      clear 1 2025-04-05 ncurses 6.6 User commands

       clear(1)                         User commands                        clear(1)
 
 
-
-

      NAME

              clear - clear the terminal screen
 
@@ -84,7 +82,7 @@

      PORTABILITY

      -       Neither IEEE Std 1003.1/The Open  Group  Base  Specifications  Issue  7
+       Neither IEEE Std 1003.1/The  Open  Group  Base  Specifications  Issue 7
        (POSIX.1-2008) nor X/Open Curses Issue 7 documents clear.
 
        The  latter documents tput, which could be used to replace this utility
@@ -96,14 +94,14 @@
        A clear command using the termcap database and library appeared in 2BSD
        (1979).  Eighth Edition Unix (1985) later included it.
 
-       The commercial Unix arm of AT&T adapted a different BSD program  (tset)
-       to  make  a  new  command,  tput, and replaced the clear program with a
+       The  commercial Unix arm of AT&T adapted a different BSD program (tset)
+       to make a new command, tput, and replaced  the  clear  program  with  a
        shell script that called "tput clear".
 
            /usr/bin/tput ${1:+-T$1} clear 2> /dev/null
            exit
 
-       In 1989, when Keith Bostic revised the BSD  tput  command  to  make  it
+       In  1989,  when  Keith  Bostic  revised the BSD tput command to make it
        similar to AT&T's tput, he added a clear shell script as well.
 
            exec tput clear
@@ -139,16 +137,14 @@
            to incorporate this extension.
 
        o   In 2013, the E3 capability was not exercised by "tput clear".  That
-           oversight was addressed in 2016 by reorganizing tput to  share  its
+           oversight  was  addressed in 2016 by reorganizing tput to share its
            logic with clear and tset.

      SEE ALSO

              tput(1), xterm(1), terminfo(5)
 
-
-
-ncurses 6.5                       2024-03-16                          clear(1)
+ncurses 6.6                       2025-04-05                          clear(1)
        diff --git a/doc/html/man/curs_add_wch.3x.html b/doc/html/man/curs_add_wch.3x.html index 64c645d..8d535da 100644 --- a/doc/html/man/curs_add_wch.3x.html +++ b/doc/html/man/curs_add_wch.3x.html @@ -1,7 +1,7 @@ -curs_add_wch 3x 2024-04-20 ncurses 6.5 Library calls +curs_add_wch 3x 2025-11-11 ncurses 6.6 Library calls -

        curs_add_wch 3x 2024-04-20 ncurses 6.5 Library calls

        +

        curs_add_wch 3x 2025-11-11 ncurses 6.6 Library calls

         curs_add_wch(3x)                 Library calls                curs_add_wch(3x)
 
 
-
-

        NAME

                add_wch, wadd_wch, mvadd_wch, mvwadd_wch, echo_wchar, wecho_wchar - add
-       a curses complex character to a window and advance the cursor
+       a curses complex character to a window, possibly advancing the cursor

        SYNOPSIS

                #include <curses.h>
 
-       int add_wch(const cchar_t *wch);
-       int wadd_wch(WINDOW *win, const cchar_t *wch);
-       int mvadd_wch(int y, int x, const cchar_t *wch);
-       int mvwadd_wch(WINDOW *win, int y, int x, const cchar_t *wch);
+       int add_wch(const cchar_t * wch);
+       int wadd_wch(WINDOW * win, const cchar_t * wch);
+       int mvadd_wch(int y, int x, const cchar_t * wch);
+       int mvwadd_wch(WINDOW * win, int y, int x, const cchar_t * wch);
 
-       int echo_wchar(const cchar_t *wch);
-       int wecho_wchar(WINDOW *win, const cchar_t *wch);
+       int echo_wchar(const cchar_t * wch);
+       int wecho_wchar(WINDOW * win, const cchar_t *wch);
+
+       /* (integer) constants */
+       /* ... */ WACS_BLOCK;
+       /* ... */ WACS_BOARD;
+       /* ... */ WACS_BTEE;
+       /* ... */ WACS_BULLET;
+       /* ... */ WACS_CKBOARD;
+       /* ... */ WACS_DARROW;
+       /* ... */ WACS_DEGREE;
+       /* ... */ WACS_DIAMOND;
+       /* ... */ WACS_HLINE;
+       /* ... */ WACS_LANTERN;
+       /* ... */ WACS_LARROW;
+       /* ... */ WACS_LLCORNER;
+       /* ... */ WACS_LRCORNER;
+       /* ... */ WACS_LTEE;
+       /* ... */ WACS_PLMINUS;
+       /* ... */ WACS_PLUS;
+       /* ... */ WACS_RARROW;
+       /* ... */ WACS_RTEE;
+       /* ... */ WACS_S1;
+       /* ... */ WACS_S9;
+       /* ... */ WACS_TTEE;
+       /* ... */ WACS_UARROW;
+       /* ... */ WACS_ULCORNER;
+       /* ... */ WACS_URCORNER;
+       /* ... */ WACS_VLINE;
+       /* extensions */
+       /* ... */ WACS_GEQUAL;
+       /* ... */ WACS_LEQUAL;
+       /* ... */ WACS_NEQUAL;
+       /* ... */ WACS_PI;
+       /* ... */ WACS_S3;
+       /* ... */ WACS_S7;
+       /* ... */ WACS_STERLING;
+       /* extensions for thick lines */
+       /* ... */ WACS_T_BTEE;
+       /* ... */ WACS_T_HLINE;
+       /* ... */ WACS_T_LLCORNER;
+       /* ... */ WACS_T_LRCORNER;
+       /* ... */ WACS_T_LTEE;
+       /* ... */ WACS_T_PLUS;
+       /* ... */ WACS_T_RTEE;
+       /* ... */ WACS_T_TTEE;
+       /* ... */ WACS_T_ULCORNER;
+       /* ... */ WACS_T_URCORNER;
+       /* ... */ WACS_T_VLINE;
+       /* extensions for double lines */
+       /* ... */ WACS_D_BTEE;
+       /* ... */ WACS_D_HLINE;
+       /* ... */ WACS_D_LLCORNER;
+       /* ... */ WACS_D_LRCORNER;
+       /* ... */ WACS_D_LTEE;
+       /* ... */ WACS_D_PLUS;
+       /* ... */ WACS_D_RTEE;
+       /* ... */ WACS_D_TTEE;
+       /* ... */ WACS_D_ULCORNER;
+       /* ... */ WACS_D_URCORNER;
+       /* ... */ WACS_D_VLINE;

        DESCRIPTION

         
-

        add_wch

        -       The add_wch, wadd_wch, mvadd_wch,  and  mvwadd_wch  functions  put  the
-       complex  character  wch  into the given window at its current position,
-       which is then advanced.  These functions perform wrapping and  special-
-       character processing as follows:
+

        wadd_wch

        +       wadd_wch  writes  the  curses  complex character wch to the window win,
+       then may advance the cursor position, analogously  to  the  standard  C
+       library's  putwchar(3).   ncurses(3x)  describes  the  variants of this
+       function.
 
-       o   If  wch  refers to a spacing character, then any previous character
-           at that location is removed.  A new character specified by  wch  is
-           placed  at  that  location  with  rendition  specified by wch.  The
-           cursor then advances after this spacing character, to  prepare  for
-           writing the next character on the screen.
+       Construct a curses complex character from a wchar_t with  setcchar(3x).
+       A  cchar_t  can  be  copied  from  place to place using win_wch(3x) and
+       wadd_wch.   curses  defines  constants  to  aid  the  manipulation   of
+       character  attributes;  see  curs_attr(3x).   A complex character whose
+       only character component is a wide space, and whose only  attribute  is
+       WA_NORMAL,  is  a  blank  character,  and  therefore  combines with the
+       window's background character; see curs_bkgrnd(3x).
 
-           The newly added spacing character is the base of the active complex
-           character.  Subsequent non-spacing characters can be combined  with
-           this base until another spacing character is written to the screen,
-           or the cursor is moved, e.g., using wmove.
+       Much behavior depends on whether the wide characters in wch are spacing
+       or non-spacing; see subsection "Complex Characters" below.
 
-       o   If wch refers to a non-spacing character, it  is  appended  to  the
-           active complex character, retaining the previous characters at that
-           location.  The rendition specified by wch is ignored.
+       o   If wch contains a spacing character,  then  any  character  at  the
+           cursor  is  first  removed.   The  complex  character wch, with its
+           attributes and color pair  identifier,  becomes  the  base  of  the
+           active complex character.
 
-           The cursor is not advanced after adding  a  non-spacing  character.
-           Subsequent calls to add non-spacing characters will update the same
-           position.
+       o   If wch contains only non-spacing characters, they are combined with
+           the  active  complex  character.  curses ignores its attributes and
+           color pair identifier, and does not advance the cursor.
 
-       o   If the character part of wch is a tab, newline, backspace or  other
-           control character, the window is updated and the cursor moves as if
-           addch were called.
+       Further non-spacing characters added with wadd_wch are not  written  at
+       the  new  cursor position but combine with the active complex character
+       until another spacing character is written to the window or the  cursor
+       is moved.
+
+       If  wch  is a backspace, carriage return, line feed, or tab, the cursor
+       moves appropriately within the window.
+
+       o   Backspace moves the cursor one character left; at the  left  margin
+           of a window, it does nothing.
+
+       o   Carriage  return  moves  the  cursor to the left margin on the same
+           line of the window.
+
+       o   Line feed does a clrtoeol(3x), then advances as if from  the  right
+           margin.
+
+       o   Tab  advances the cursor to the next tab stop (possibly on the next
+           line); these are placed at every eighth column by default.
+
+           Alter  the  tab  interval   with   the   TABSIZE   extension;   see
+           curs_variables(3x).
+
+       If  wch  is  any  other  nonprintable  character,  curses  draws  it in
+       printable form using  the  same  convention  as  wunctrl(3x).   Calling
+       win_wch(3x)  on  the  location  of  a  nonprintable  character does not
+       retrieve the character itself, but its wunctrl(3x) representation.
+
+       Adding spacing characters with wadd_wch causes it to wrap at the  right
+       margin of the window:
+
+       o   If  the  cursor  is  not  at the bottom of the scrolling region and
+           advancement occurs at the right margin,  the  cursor  automatically
+           wraps to the beginning of the next line.
+
+       o   If  the  cursor  is  at  the  bottom  of  the scrolling region when
+           advancement occurs at the right margin, and scrollok(3x) is enabled
+           for win, the scrolling region scrolls up one line  and  the  cursor
+           wraps as above.  Otherwise, advancement and scrolling do not occur,
+           and wadd_wch returns ERR.
+
+       A  window's  margins may coincide with the screen boundaries.  This may
+       be a problem when ncurses  updates  the  screen  to  match  the  curses
+       window.   When  their  right  and bottom margins coincide, ncurses uses
+       different strategies to handle the variations of scrolling and wrapping
+       at the lower-right corner by depending on the terminal capabilities:
+
+       o   If the terminal does not automatically wrap as characters are added
+           at the right margin (i.e., auto right margins), ncurses writes  the
+           character directly.
+
+       o   If  the  terminal has auto right margins, but also has capabilities
+           for turning auto margins off and on, ncurses turns the auto  margin
+           feature off temporarily when writing to the lower-right corner.
+
+       o   If  the  terminal has an insertion mode which can be turned off and
+           on, ncurses  writes  the  character  just  before  the  lower-right
+           corner,  and  then  inserts a character to push the update into the
+           corner.
 
 
-

        echo_wchar

        -       The echo_wchar function is functionally equivalent to a call to add_wch
-       followed  by  a  call  to  refresh(3x).   Similarly, the wecho_wchar is
-       functionally equivalent to a call to wadd_wch followed  by  a  call  to
-       wrefresh.   The  knowledge that only a single character is being output
-       is  taken  into  consideration  and,  for  non-control  characters,   a
-       considerable  performance  gain  might  be  seen  by  using  the *echo*
-       functions instead of their equivalents.
+

        wecho_wchar

        +       echo_wchar  and  wecho_wchar  are  equivalent  to  calling   (w)add_wch
+       followed  by  (w)refresh  on  stdscr  or  the specified window.  curses
+       interprets these functions as a  hint  that  only  a  single  (complex)
+       character  is  being output; for non-control characters, a considerable
+       performance gain may be enjoyed by employing them.
 
 
-

        Line Graphics

        -       Like addch(3x), addch_wch accepts symbols which make it simple to  draw
-       lines  and  other  frequently  used  special characters.  These symbols
-       correspond to the same VT100 line-drawing set as addch(3x).
+

        Forms-Drawing Characters

        +       curses defines macros  starting  with  WACS_  that  can  be  used  with
+       wadd_wch  to  write  line-drawing  and  other  symbols  to  the screen.
+       ncurses terms these forms-drawing  characters.   curses  uses  the  ACS
+       default  listed  below  if the terminal type lacks the acs_chars (acsc)
+       capability; that capability does  not  define  a  replacement  for  the
+       character;  or  if  the  terminal type and locale configuration require
+       Unicode to access these characters, but the library is  unable  to  use
+       Unicode.   The "acsc char" column corresponds to how the characters are
+       specified in the acs_chars (acsc) string capability, and the characters
+       in it may appear on the screen if the terminal  type's  database  entry
+       incorrectly  advertises  ACS support.  The name "ACS" originates in the
+       Alternate Character Set feature of the DEC VT100 terminal.
 
-                       Unicode   ASCII     acsc
-
-
-       ACS Name        Default   Default   Char   Glyph Name
+                       Unicode   ACS       acsc
+       Symbol          Default   Default   char   Glyph Name
        ------------------------------------------------------------------------
-       WACS_BLOCK      0x25ae    #         0      solid square block
-       WACS_BOARD      0x2592    #         h      board of squares
-       WACS_BTEE       0x2534    +         v      bottom tee
-       WACS_BULLET     0x00b7    o         ~      bullet
-       WACS_CKBOARD    0x2592    :         a      checker board (stipple)
-       WACS_DARROW     0x2193    v         .      arrow pointing down
-       WACS_DEGREE     0x00b0    '         f      degree symbol
-       WACS_DIAMOND    0x25c6    +         `      diamond
-       WACS_GEQUAL     0x2265    >         >      greater-than-or-equal-to
-       WACS_HLINE      0x2500    -         q      horizontal line
-       WACS_LANTERN    0x2603    #         i      lantern symbol
-       WACS_LARROW     0x2190    <         ,      arrow pointing left
-       WACS_LEQUAL     0x2264    <         y      less-than-or-equal-to
-       WACS_LLCORNER   0x2514    +         m      lower left-hand corner
-       WACS_LRCORNER   0x2518    +         j      lower right-hand corner
-       WACS_LTEE       0x2524    +         t      left tee
-       WACS_NEQUAL     0x2260    !         |      not-equal
-       WACS_PI         0x03c0    *         {      greek pi
-       WACS_PLMINUS    0x00b1    #         g      plus/minus
-       WACS_PLUS       0x253c    +         n      plus
-       WACS_RARROW     0x2192    >         +      arrow pointing right
-       WACS_RTEE       0x251c    +         u      right tee
-       WACS_S1         0x23ba    -         o      scan line 1
-       WACS_S3         0x23bb    -         p      scan line 3
-       WACS_S7         0x23bc    -         r      scan line 7
-       WACS_S9         0x23bd    _         s      scan line 9
-       WACS_STERLING   0x00a3    f         }      pound-sterling symbol
-       WACS_TTEE       0x252c    +         w      top tee
-       WACS_UARROW     0x2191    ^         -      arrow pointing up
-       WACS_ULCORNER   0x250c    +         l      upper left-hand corner
-       WACS_URCORNER   0x2510    +         k      upper right-hand corner
-       WACS_VLINE      0x2502    |         x      vertical line
+       WACS_BLOCK      U+25ae    #         0      solid square block
+       WACS_BOARD      U+2592    #         h      board of squares
+       WACS_BTEE       U+2534    +         v      bottom tee
+       WACS_BULLET     U+00b7    o         ~      bullet
+       WACS_CKBOARD    U+2592    :         a      checker board (stipple)
+       WACS_DARROW     U+2193    v         .      arrow pointing down
+       WACS_DEGREE     U+00b0    '         f      degree symbol
+       WACS_DIAMOND    U+25c6    +         `      diamond
+       WACS_GEQUAL     U+2265    >         >      greater-than-or-equal-to
+       WACS_HLINE      U+2500    -         q      horizontal line
+       WACS_LANTERN    U+2603    #         i      lantern symbol
+       WACS_LARROW     U+2190    <         ,      arrow pointing left
+       WACS_LEQUAL     U+2264    <         y      less-than-or-equal-to
+       WACS_LLCORNER   U+2514    +         m      lower left-hand corner
+       WACS_LRCORNER   U+2518    +         j      lower right-hand corner
+       WACS_LTEE       U+2524    +         t      left tee
+       WACS_NEQUAL     U+2260    !         |      not-equal
+       WACS_PI         U+03c0    *         {      greek pi
+       WACS_PLMINUS    U+00b1    #         g      plus/minus
+       WACS_PLUS       U+253c    +         n      plus
+       WACS_RARROW     U+2192    >         +      arrow pointing right
+       WACS_RTEE       U+251c    +         u      right tee
+       WACS_S1         U+23ba    -         o      scan line 1
+       WACS_S3         U+23bb    -         p      scan line 3
+       WACS_S7         U+23bc    -         r      scan line 7
+       WACS_S9         U+23bd    _         s      scan line 9
+       WACS_STERLING   U+00a3    f         }      pound-sterling symbol
+       WACS_TTEE       U+252c    +         w      top tee
+       WACS_UARROW     U+2191    ^         -      arrow pointing up
+       WACS_ULCORNER   U+250c    +         l      upper left-hand corner
+       WACS_URCORNER   U+2510    +         k      upper right-hand corner
+       WACS_VLINE      U+2502    |         x      vertical line
 
-       The wide-character configuration of ncurses also  defines  symbols  for
-       thick lines (acsc "J" to "V"):
+       The ncurses wide API also defines symbols for  thick  lines  (acsc  "J"
+       through "N", "T" through "X", and "Q"):
 
                          Unicode   ASCII     acsc
        ACS Name          Default   Default   Char   Glyph Name
        ------------------------------------------------------------------------
-       WACS_T_BTEE       0x253b    +         V      thick tee pointing up
-       WACS_T_HLINE      0x2501    -         Q      thick horizontal line
-       WACS_T_LLCORNER   0x2517    +         M      thick lower left corner
-       WACS_T_LRCORNER   0x251b    +         J      thick lower right corner
-       WACS_T_LTEE       0x252b    +         T      thick tee pointing right
-       WACS_T_PLUS       0x254b    +         N      thick large plus
-       WACS_T_RTEE       0x2523    +         U      thick tee pointing left
-       WACS_T_TTEE       0x2533    +         W      thick tee pointing down
-       WACS_T_ULCORNER   0x250f    +         L      thick upper left corner
-       WACS_T_URCORNER   0x2513    +         K      thick upper right corner
-       WACS_T_VLINE      0x2503    |         X      thick vertical line
+       WACS_T_BTEE       U+253b    +         V      thick tee pointing up
+       WACS_T_HLINE      U+2501    -         Q      thick horizontal line
+       WACS_T_LLCORNER   U+2517    +         M      thick lower left corner
+       WACS_T_LRCORNER   U+251b    +         J      thick lower right corner
+       WACS_T_LTEE       U+252b    +         T      thick tee pointing right
+       WACS_T_PLUS       U+254b    +         N      thick large plus
+       WACS_T_RTEE       U+2523    +         U      thick tee pointing left
+       WACS_T_TTEE       U+2533    +         W      thick tee pointing down
+       WACS_T_ULCORNER   U+250f    +         L      thick upper left corner
+       WACS_T_URCORNER   U+2513    +         K      thick upper right corner
+       WACS_T_VLINE      U+2503    |         X      thick vertical line
 
-       and for double-lines (acsc "A" to "I"):
+       and for double lines (acsc "A" through "I", plus "R" and "Y"):
 
                          Unicode   ASCII     acsc
        ACS Name          Default   Default   Char   Glyph Name
        ------------------------------------------------------------------------
-       WACS_D_BTEE       0x2569    +         H      double tee pointing up
-       WACS_D_HLINE      0x2550    -         R      double horizontal line
-       WACS_D_LLCORNER   0x255a    +         D      double lower left corner
-       WACS_D_LRCORNER   0x255d    +         A      double lower right corner
-       WACS_D_LTEE       0x2560    +         F      double tee pointing right
-       WACS_D_PLUS       0x256c    +         E      double large plus
-       WACS_D_RTEE       0x2563    +         G      double tee pointing left
-
-       WACS_D_TTEE       0x2566    +         I      double tee pointing down
-       WACS_D_ULCORNER   0x2554    +         C      double upper left corner
-       WACS_D_URCORNER   0x2557    +         B      double upper right corner
-       WACS_D_VLINE      0x2551    |         Y      double vertical line
+       WACS_D_BTEE       U+2569    +         H      double tee pointing up
+       WACS_D_HLINE      U+2550    -         R      double horizontal line
+       WACS_D_LLCORNER   U+255a    +         D      double lower left corner
+       WACS_D_LRCORNER   U+255d    +         A      double lower right corner
+       WACS_D_LTEE       U+2560    +         F      double tee pointing right
+       WACS_D_PLUS       U+256c    +         E      double large plus
+       WACS_D_RTEE       U+2563    +         G      double tee pointing left
+       WACS_D_TTEE       U+2566    +         I      double tee pointing down
+       WACS_D_ULCORNER   U+2554    +         C      double upper left corner
+       WACS_D_URCORNER   U+2557    +         B      double upper right corner
+       WACS_D_VLINE      U+2551    |         Y      double vertical line
 
        Unicode's  descriptions  for  these  characters  differs  slightly from
        ncurses, by introducing the term "light"  (along  with  less  important
@@ -198,75 +316,85 @@

        RETURN VALUE

        -       All routines return the integer ERR upon failure and OK on success.
+       These functions return OK on success and ERR on failure.
 
-       X/Open  Curses  does  not   specify   any   error   conditions.    This
-       implementation returns an error
+       In ncurses, these functions fail if
 
-       o   if the window pointer is null or
+       o   the curses screen has not been initialized,
 
-       o   if it is not possible to add a complete character in the window.
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer,
 
-       The latter may be due to different causes:
+       o   wrapping  to  a new line is impossible because scrollok(3x) has not
+           been called on win (or stdscr, as applicable) when writing  to  its
+           bottom right location is attempted, or
 
-       o   If  scrollok(3x)  is  not enabled, writing a character at the lower
-           right margin succeeds.  However, an error is returned because it is
-           not possible to wrap to a new line.
+       o   it  is  not  possible  to  add  a  complete character at the cursor
+           position.
 
-       o   If  an error is detected when converting a multibyte character to a
-           sequence of bytes, or if it is not  possible  to  add  all  of  the
-           resulting bytes in the window, an error is returned.
-
-       Functions  prefixed with "mv" first perform cursor movement and fail if
+       Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

        NOTES

        -       Note that add_wch, mvadd_wch, mvwadd_wch, and echo_wchar may be macros.
+       add_wch,  mvadd_wch,  mvwadd_wch,  and echo_wchar may be implemented as
+       macros.
+
+
+

        EXTENSIONS

        +       The  symbols  WACS_S3,  WACS_S7,  WACS_LEQUAL,  WACS_GEQUAL,   WACS_PI,
+       WACS_NEQUAL,   and  WACS_STERLING  are  not  standard.   However,  many
+       publicly  available   terminfo   entries   include   acs_chars   (acsc)
+       capabilities  in which their key characters (pryz{|}) are embedded, and
+       a second-hand list of their character descriptions has come  to  light.
+       The ncurses developers invented WACS-prefixed names for them.

        PORTABILITY

        -       These functions are described in X/Open Curses, Issue 4.  The  defaults
-       specified for line-drawing characters apply in the POSIX locale.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
+       These  functions  are described in X/Open Curses Issue 4.  It specifies
+       no error conditions for them.
 
-

        WACS Symbols

        -       X/Open  Curses  makes it clear that the WACS_ symbols should be defined
-       as a pointer to cchar_t data, e.g., in the discussion of border_set.  A
-       few implementations are problematic:
+       The defaults specified for forms-drawing characters apply in the  POSIX
+       locale.   X/Open Curses makes it clear that the WACS_ symbols should be
+       defined as a pointer to  cchar_t  data,  e.g.,  in  the  discussion  of
+       border_set.  A few implementations are problematic:
 
-       o   NetBSD curses defines the symbols as a wchar_t within a cchar_t.
+       o   NetBSD curses defines the symbols as a wchar_t within a cchar_t.
 
-       o   HP-UX  curses  equates  some  of  the ACS_ symbols to the analogous
-           WACS_ symbols as if the ACS_ symbols  were  wide  characters.   The
+       o   HP-UX  curses  equates  some  of  the ACS_ symbols to the analogous
+           WACS_ symbols as if the ACS_ symbols  were  wide  characters.   The
            misdefined  symbols  are the arrows and other symbols which are not
            used for line-drawing.
 
        X/Open Curses does not specify  symbols  for  thick-  or  double-lines.
-       SVr4 curses implementations defined their line-drawing symbols in terms
-       of intermediate symbols.  This implementation  extends  those  symbols,
-       providing new definitions which are not in the SVr4 implementations.
+       SVr4 curses implementations defined their line-drawing symbols in terms
+       of  intermediate symbols.  ncurses extends those symbols, providing new
+       definitions not found in SVr4 implementations.
 
-       Not  all  Unicode-capable  terminals  provide  support  for VT100-style
-       alternate character  sets  (i.e.,  the  acsc  capability),  with  their
-       corresponding  line-drawing  characters.  X/Open Curses did not address
-       the  aspect  of  integrating  Unicode  with  line-drawing   characters.
-       Existing  implementations of Unix curses (AIX, HP-UX, Solaris) use only
-       the acsc character-mapping to provide this feature.  As a result, those
-       implementations  can  only  use  single-byte  line-drawing  characters.
-       ncurses 5.3 (2002) provided a table of Unicode values  to  solve  these
-       problems.  NetBSD curses incorporated that table in 2010.
+       Not all  Unicode-capable  terminals  provide  support  for  VT100-style
+       alternate character sets (i.e., the acsc_chars (acsc) capability), with
+       their  corresponding  line-drawing  characters.   X/Open Curses did not
+       address the aspect of integrating Unicode with line-drawing characters.
+       Existing implementations of System V curses (AIX, HP-UX,  Solaris)  use
+       only  the  acsc_chars (acsc) character-mapping to provide this feature.
+       As a result, those  implementations  can  use  only  single-byte  line-
+       drawing  characters.   ncurses  5.3  (2002) provided a table of Unicode
+       values to solve these problems.  NetBSD curses incorporated that  table
+       in 2010.
 
-       In  this  implementation,  the  Unicode  values are used instead of the
-       terminal description's acsc mapping as discussed in ncurses(3x) for the
-       environment  variable  NCURSES_NO_UTF8_ACS.   In contrast, for the same
-       cases, the line-drawing characters described in addch(3x) will use only
-       the ASCII default values.
+       ncurses   uses   the  Unicode  values  instead  of  the  terminal  type
+       description's acsc_chars (acsc) mapping as discussed in ncurses(3x) for
+       the environment variable NCURSES_NO_UTF8_ACS.   In  contrast,  for  the
+       same cases, the line-drawing characters described in addch(3x) will use
+       only the ASCII default values.
 
        Having  Unicode available does not solve all of the problems with line-
-       drawing for curses:
+       drawing for curses:
 
-       o   The closest Unicode equivalents to the VT100 graphics  S1,  S3,  S7
+       o   The closest Unicode equivalents to the VT100 graphics S1,  S3,  S7,
            and  S9 frequently are not displayed at the regular intervals which
            the terminal used.
 
@@ -277,45 +405,58 @@
            Lacking documentation, most readers assume that a storm lantern was
            intended.  But there are several possibilities, all with problems.
 
-           Unicode  6.0  (2010)  does provide two lantern symbols: U+1F383 and
-           U+1F3EE.  Those were not available  in  2002,  and  are  irrelevant
-           since  they  lie  outside the BMP and as a result are not generally
-           available in terminals.  They are not storm lanterns, in any case.
+           Unicode 6.0 (2010) does provide two lantern  symbols:  U+1F383  and
+           U+1F3EE.   Those  were  not  available  in 2002, and are irrelevant
+           since they lie outside the Basic Multilingual Plane and as a result
+           are unavailable on many terminals.  They are not storm lanterns, in
+           any case.
 
            Most storm lanterns have a tapering glass chimney (to guard against
            tipping); some have a wire grid protecting the chimney.
 
-           For  the  tapering  appearance,   U+2603 was adequate.  In use on a
+           For the tapering appearance,  U+2603 was adequate.   In  use  on  a
            terminal, no one can tell what the image represents.  Unicode calls
            it a snowman.
 
            Others have suggested these alternatives: <section> U+00A7 (section
-           mark), <Theta> U+0398 (theta), <Phi> U+03A6 (phi),  <delta>  U+03B4
+           mark),  <Theta>  U+0398 (theta), <Phi> U+03A6 (phi), <delta> U+03B4
            (delta),  U+2327 (x in a rectangle),  U+256C (forms double vertical
            and horizontal), and  U+2612 (ballot box with x).

        Complex Characters

        -       The complex character  type  cchar_t  can  store  more  than  one  wide
-       character  (wchar_t).   The  X/Open Curses description does not mention
-       this possibility, describing only the cases  where  wch  is  a  spacing
-       character or a non-spacing character.
+       The complex character  type  cchar_t  can  store  more  than  one  wide
+       character  (wchar_t).  X/Open Curses does not mention this possibility,
+       specifying behavior only  where  wch  is  a  single  character,  either
+       spacing or non-spacing.
 
-       This implementation assumes that wch is constructed using setcchar(3x),
-       and in turn that the result
+       ncurses assumes that wch is constructed using setcchar(3x), and in turn
+       that the result
 
-       o   contains at most one spacing character in the beginning of its list
-           of wide characters, and zero or more non-spacing characters or
+       o   contains at most one spacing character at the beginning of its list
+           of wide characters, and zero or more non-spacing characters, or
 
-       o   may hold one non-spacing character.
+       o   holds one non-spacing character.
 
        In  the  latter  case,  ncurses  adds  the non-spacing character to the
-       active (base) spacing character.
+       active complex character.
 
 
-

        TABSIZE

        -       The TABSIZE variable is implemented  in  SVr4  and  other  versions  of
-       curses, but is not specified by X/Open Curses (see curs_variables(3x)).
+

        HISTORY

        +       X/Open Curses Issue 4 (1995) initially specified these functions.   The
+       System V  Interface  Definition  (SVID)  Version 4  of  the  same  year
+       specified functions named waddwch (and the usual variants),  echowchar,
+       and wechowchar.  These were later additions to SVr4.x, not appearing in
+       the  first SVr4 (1989).  They differed from X/Open's later wadd_wch and
+       wecho_wchar in that they each took an argument of type wchar_t  instead
+       of cchar_t.  SVID defined no  WACS_ symbols.
+
+       X/Open  Curses  Issue 4  also  defined  many  of  the  WACS_ constants,
+       excepting  WACS_GEQUAL,  WACS_LEQUAL,  WACS_NEQUAL,  WACS_PI,  WACS_S3,
+       WACS_S7,  and  WACS_STERLING;  and  those  for drawing thick and double
+       lines.
+
+       ncurses 5.3 (2002) furnished the remaining WACS_ constants.

        SEE ALSO

        @@ -323,12 +464,10 @@
        its non-wide-character configuration.
 
        curses(3x),   curs_addwstr(3x),   curs_add_wchstr(3x),   curs_attr(3x),
-       curs_clear(3x),  curs_getcchar(3x), curs_outopts(3x), curs_refresh(3x),
-       curs_variables(3x), putwc(3)
+       curs_bkgrnd(3x),  curs_clear(3x),  curs_getcchar(3x), curs_outopts(3x),
+       curs_refresh(3x), curs_variables(3x), putwc(3)
 
-
-
-ncurses 6.5                       2024-04-20                  curs_add_wch(3x)
+ncurses 6.6                       2025-11-11                  curs_add_wch(3x)
        diff --git a/doc/html/man/curs_add_wchstr.3x.html b/doc/html/man/curs_add_wchstr.3x.html index f554061..46d4785 100644 --- a/doc/html/man/curs_add_wchstr.3x.html +++ b/doc/html/man/curs_add_wchstr.3x.html @@ -1,6 +1,6 @@ -curs_add_wchstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_add_wchstr 3x 2025-10-20 ncurses 6.6 Library calls -

        curs_add_wchstr 3x 2024-04-20 ncurses 6.5 Library calls

        +

        curs_add_wchstr 3x 2025-10-20 ncurses 6.6 Library calls

         curs_add_wchstr(3x)              Library calls             curs_add_wchstr(3x)
 
 
-
-

        NAME

        -       add_wchstr,   add_wchnstr,   wadd_wchstr,  wadd_wchnstr,  mvadd_wchstr,
-       mvadd_wchnstr, mvwadd_wchstr, mvwadd_wchnstr -  add  a  curses  complex
+       add_wchstr,   wadd_wchstr,  mvadd_wchstr,  mvwadd_wchstr,  add_wchnstr,
+       wadd_wchnstr, mvadd_wchnstr, mvwadd_wchnstr  -  add  a  curses  complex
        character string to a window

        SYNOPSIS

                #include <curses.h>
 
-       int add_wchstr(const cchar_t *wchstr);
-       int wadd_wchstr(WINDOW * win, const cchar_t *wchstr);
-       int mvadd_wchstr(int y, int x, const cchar_t *wchstr);
-       int mvwadd_wchstr(WINDOW *win, int y, int x, const cchar_t *wchstr);
+       int add_wchstr(const cchar_t * wchstr);
+       int wadd_wchstr(WINDOW *  win, const cchar_t * wchstr);
+       int mvadd_wchstr(int y, int x, const cchar_t * wchstr);
+       int mvwadd_wchstr(WINDOW * win, int y, int x, const cchar_t * wchstr);
 
-       int add_wchnstr(const cchar_t *wchstr, int n);
-       int wadd_wchnstr(WINDOW * win, const cchar_t *wchstr, int n);
-       int mvadd_wchnstr(int y, int x, const cchar_t *wchstr, int n);
-       int mvwadd_wchnstr(WINDOW *win, int y, int x, const cchar_t *wchstr, int n);
+       int add_wchnstr(const cchar_t * wchstr, int n);
+       int wadd_wchnstr(WINDOW *  win, const cchar_t * wchstr, int n);
+       int mvadd_wchnstr(int y, int x, const cchar_t * wchstr, int n);
+       int mvwadd_wchnstr(WINDOW * win, int y, int x,
+             const cchar_t * wchstr, int n);

        DESCRIPTION

        -       These  functions copy the (null-terminated) array of complex characters
-       wchstr into the window image structure starting at the  current  cursor
-       position.
+       wadd_wchstr  copies  the  string  of  complex  characters wchstr to the
+       window win.  A null complex character  terminates  the  string.   If  a
+       complex  character  does  not  completely  fit  at the end of the line,
+       curses  fills  its  remaining  cells  with  the   window's   background
+       character;  see  bkgrnd(3x).  wadd_wchnstr does the same, but copies at
+       most n characters, or as many as possible  if  n  is  -1.   ncurses(3x)
+       describes the variants of these functions.
 
-       The four functions with n as the last argument copy at most n elements,
-       but no more than will fit on the line.  If n=-1 then the whole array is
-       copied, to the maximum number of characters that will fit on the line.
+       Because  these  functions do not call wadd_wch(3x) internally, they are
+       faster than waddwstr(3x) and waddnwstr(3x).  On the other hand, they
 
-       The  window  cursor  is  not advanced.  These functions are faster than
-       waddnstr.  On the other hand:
+       o   do  not  treat  the  backspace,  carriage  return,  or  line   feed
+           characters specially;
 
-       o   they do not perform checking (such as for the  newline,  backspace,
-           or carriage return characters),
+       o   do not represent unprintable characters with wunctrl(3x);
 
-       o   they do not advance the current cursor position,
+       o   do  not  update  the  cursor  position to follow the last character
+           written; and
 
-       o   they do not expand other control characters to ^-escapes, and
-
-       o   they  truncate  the  string  if it crosses the right margin, rather
-           than wrapping it around to the new line.
-
-       These functions end successfully on encountering  a  null  cchar_t,  or
-       when  they have filled the current line.  If a complex character cannot
-       completely fit at the end of the current line,  the  remaining  columns
-       are filled with the background character and rendition.
+       o   truncate the string at  the  window's  right  margin,  rather  than
+           wrapping it to the next line and potentially scrolling.

        RETURN VALUE

        -       All functions return the integer ERR upon failure and OK on success.
+       These functions return OK on success and ERR on failure.
 
-       X/Open   Curses   does   not   specify   any  error  conditions.   This
-       implementation returns an error
+       In ncurses, these functions fail if
 
-       o   if the win parameter is null or
+       o   the curses screen has not been initialized,
 
-       o   if the wchstr parameter is null.
+       o   wchstr is a null pointer, or
+
+       o   (for  functions  taking  a  WINDOW  pointer argument) win is a null
+           pointer.
 
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

        NOTES

        -       All functions except wadd_wchnstr may be macros.
+       All  of  these  functions  except  wadd_wchnstr  may  be implemented as
+       macros.

        PORTABILITY

        -       These functions are described in X/Open Curses, Issue 4.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+
+

        HISTORY

        +       X/Open Curses Issue 4 (1995) initially specified these functions.   The
+       System V  Interface  Definition  Version 4  of  the same year specified
+       functions named waddwchstr and waddwchnstr (and  the  usual  variants).
+       These  were  later additions to SVr4.x, not appearing in the first SVr4
+       (1989).  They differed from X/Open's later wadd_wchstr and wadd_wchnstr
+       in that they each took an argument of type wchar_t instead of cchar_t.

        SEE ALSO

        @@ -122,9 +130,7 @@
 
        curses(3x), curs_addwstr(3x), curs_add_wch(3x)
 
-
-
-ncurses 6.5                       2024-04-20               curs_add_wchstr(3x)
+ncurses 6.6                       2025-10-20               curs_add_wchstr(3x)
        diff --git a/doc/html/man/curs_addch.3x.html b/doc/html/man/curs_addch.3x.html index 0a0622e..c8227c4 100644 --- a/doc/html/man/curs_addch.3x.html +++ b/doc/html/man/curs_addch.3x.html @@ -1,7 +1,7 @@ -curs_addch 3x 2024-04-20 ncurses 6.5 Library calls +curs_addch 3x 2025-11-11 ncurses 6.6 Library calls -

        curs_addch 3x 2024-04-20 ncurses 6.5 Library calls

        +

        curs_addch 3x 2025-11-11 ncurses 6.6 Library calls

         curs_addch(3x)                   Library calls                  curs_addch(3x)
 
 
-
-

        NAME

                addch,  waddch,  mvaddch,  mvwaddch, echochar, wechochar - add a curses
        character to a window and advance the cursor
@@ -56,28 +54,68 @@
        #include <curses.h>
 
        int addch(const chtype ch);
-       int waddch(WINDOW *win, const chtype ch);
+       int waddch(WINDOW * win, const chtype ch);
        int mvaddch(int y, int x, const chtype ch);
-       int mvwaddch(WINDOW *win, int y, int x, const chtype ch);
+       int mvwaddch(WINDOW * win, int y, int x, const chtype ch);
 
        int echochar(const chtype ch);
-       int wechochar(WINDOW *win, const chtype ch);
+       int wechochar(WINDOW * win, const chtype ch);
+
+       /* (integer) constants */
+       /* ... */ ACS_BLOCK;
+       /* ... */ ACS_BOARD;
+       /* ... */ ACS_BTEE;
+       /* ... */ ACS_BULLET;
+       /* ... */ ACS_CKBOARD;
+       /* ... */ ACS_DARROW;
+       /* ... */ ACS_DEGREE;
+       /* ... */ ACS_DIAMOND;
+       /* ... */ ACS_HLINE;
+       /* ... */ ACS_LANTERN;
+       /* ... */ ACS_LARROW;
+       /* ... */ ACS_LLCORNER;
+       /* ... */ ACS_LRCORNER;
+       /* ... */ ACS_LTEE;
+       /* ... */ ACS_PLMINUS;
+       /* ... */ ACS_PLUS;
+       /* ... */ ACS_RARROW;
+       /* ... */ ACS_RTEE;
+       /* ... */ ACS_S1;
+       /* ... */ ACS_S9;
+       /* ... */ ACS_TTEE;
+       /* ... */ ACS_UARROW;
+       /* ... */ ACS_ULCORNER;
+       /* ... */ ACS_URCORNER;
+       /* ... */ ACS_VLINE;
+       /* extensions */
+       /* ... */ ACS_GEQUAL;
+       /* ... */ ACS_LEQUAL;
+       /* ... */ ACS_NEQUAL;
+       /* ... */ ACS_PI;
+       /* ... */ ACS_S3;
+       /* ... */ ACS_S7;
+       /* ... */ ACS_STERLING;

        DESCRIPTION

         
-

        Adding Characters

        -       waddch puts the character ch at the cursor position of window win, then
-       advances  the  cursor position, analogously to the standard C library's
+

        waddch

        +       waddch writes the curses character ch to the window win, then  advances
+       the   cursor   position,   analogously  to  the  standard  C  library's
        putchar(3).  ncurses(3x) describes the variants of this function.
 
-       If advancement occurs at the right margin,
+       Construct a curses character from a char  by  assignment  or  typecast.
+       Subsection "Video Attributes" of attron(3x) describes how to manipulate
+       its  attributes and color pair.  (A color pair selection is not honored
+       unless initialized; see start_color(3x).)
 
-       o   the cursor automatically wraps to the beginning of the  next  line;
-           and
-
-       o   at  the bottom of the current scrolling region, and if scrollok(3x)
-           is enabled for win, the scrolling region scrolls up one line.
+       The object or expression ch may contain attributes and/or a color  pair
+       identifier.   (A  chtype  can  be  copied  from  place  to  place using
+       winch(3x)  and  waddch.)   curses  defines   constants   to   aid   the
+       manipulation  of  character  attributes; see curs_attr(3x).  A ch whose
+       character component is a space, and whose only attribute  is  A_NORMAL,
+       is  a  blank  character,  and  therefore  combines  with  the  window's
+       background character; see curs_bkgd(3x).
 
        If ch is a backspace, carriage return, line feed, or  tab,  the  cursor
        moves appropriately within the window.
@@ -85,52 +123,78 @@
        o   Backspace  moves  the cursor one character left; at the left margin
            of a window, it does nothing.
 
-       o   Carriage return moves the cursor to the left margin on the  current
+       o   Carriage return moves the cursor to the left  margin  on  the  same
            line of the window.
 
-       o   Line  feed  does  a clrtoeol(3x), then moves the cursor to the left
-           margin on the next line of  the  window,  and  if  scrollok(3x)  is
-           enabled  for  win,  scrolls the window if the cursor was already on
-           the last line.
+       o   Line  feed  does a clrtoeol(3x), then advances as if from the right
+           margin.
 
        o   Tab advances the cursor to the next tab stop (possibly on the  next
-           line);  these  are placed at every eighth column by default.  Alter
-           the   tab   interval    with    the    TABSIZE    extension;    see
+           line); these are placed at every eighth column by default.
+
+           Alter   the   tab   interval   with   the  TABSIZE  extension;  see
            curs_variables(3x).
 
-       If  ch  is  any  other nonprintable character, it is drawn in printable
-       form, using the same convention as unctrl(3x).
+       If ch is any other nonprintable character, curses draws it in printable
+       form using the same convention as unctrl(3x).  Calling winch(3x) on the
+       location of a nonprintable character  does  not  return  the  character
+       itself, but its unctrl(3x) representation.
 
-       Calling winch(3x) on the location of a nonprintable character does  not
-       return the character itself, but its unctrl(3x) representation.
+       Adding  printable characters with waddch causes it to wrap at the right
+       margin of the window:
 
-       ch  may  contain  rendering  and/or color attributes, and others can be
-       combined with the parameter by logically "or"ing with it.  (A character
-       with  its  attributes can be copied from place to place using winch(3x)
-       and  waddch.)   See  curs_attr(3x)  for  values  of  predefined   video
-       attribute constants that can be usefully "or"ed with characters.
+       o   If the cursor is not at the bottom  of  the  scrolling  region  and
+           advancement  occurs  at  the right margin, the cursor automatically
+           wraps to the beginning of the next line.
+
+       o   If the cursor is  at  the  bottom  of  the  scrolling  region  when
+           advancement occurs at the right margin, and scrollok(3x) is enabled
+           for  win,  the  scrolling region scrolls up one line and the cursor
+           wraps as above.  Otherwise, advancement and scrolling do not occur,
+           and waddch returns ERR.
+
+       A window's margins may coincide with the screen boundaries.   This  may
+       be  a  problem  when  ncurses  updates  the  screen to match the curses
+       window.  When their right and bottom  margins  coincide,  ncurses  uses
+       different strategies to handle the variations of scrolling and wrapping
+       at the lower-right corner by depending on the terminal capabilities:
+
+       o   If the terminal does not automatically wrap as characters are added
+           at  the right margin (i.e., auto right margins), ncurses writes the
+           character directly.
+
+       o   If the terminal has auto right margins, but also  has  capabilities
+           for  turning auto margins off and on, ncurses turns the auto margin
+           feature off temporarily when writing to the lower-right corner.
+
+       o   If the terminal has an insertion mode which can be turned  off  and
+           on,  ncurses  writes  the  character  just  before  the lower-right
+           corner, and then inserts a character to push the  update  into  the
+           corner.
 
 
-

        Echoing Characters

        +

        wechochar

                echochar  and  wechochar are equivalent to calling (w)addch followed by
-       (w)refresh.  curses interprets these functions as a hint  that  only  a
-       single  character  is  being  output;  for  non-control  characters,  a
-       considerable performance gain may be enjoyed by employing them.
+       (w)refresh on stdscr or the specified window.  curses interprets  these
+       functions  as a hint to its optimizer that only a single character cell
+       in the window is  being  altered  between  refreshes;  for  non-control
+       characters, a considerable performance gain may be enjoyed by employing
+       them.

        Forms-Drawing Characters

        -       curses defines macros starting with ACS_ that can be used  with  waddch
-       to  write  line-drawing  and  other  special  characters to the screen.
-       ncurses terms these forms-drawing characters.  The ACS  default  listed
-       below  is  used  if  the  acs_chars (acsc) terminfo capability does not
-       define a terminal-specific replacement for it, or if the  terminal  and
-       locale  configuration  requires  Unicode to access these characters but
-       the  library  is  unable  to  use  Unicode.   The  "acsc  char"  column
-       corresponds to how the characters are specified in the acs_chars string
-       capability, and the characters in it may appear on the  screen  if  the
-       terminal's database entry incorrectly advertises ACS support.  The name
-       "ACS" originates in the Alternate Character  Set  feature  of  the  DEC
-       VT100 terminal.
+       curses  defines  macros starting with ACS_ that can be used with waddch
+       to write line-drawing and other symbols to the screen.   ncurses  terms
+       these  forms-drawing  characters.   curses  uses the ACS default listed
+       below if the terminal type lacks the acs_chars (acsc) capability;  that
+       capability  does  not define a replacement for the character; or if the
+       terminal type and locale configuration require Unicode to access  these
+       characters,  but the library is unable to use Unicode.  The "acsc char"
+       column corresponds to how the characters are specified in the acs_chars
+       (acsc) string capability, and the characters in it may  appear  on  the
+       screen if the terminal type's database entry incorrectly advertises ACS
+       support.   The  name  "ACS"  originates  in the Alternate Character Set
+       feature of the DEC VT100 terminal.
 
                       ACS       acsc
        Symbol         Default   char   Glyph Name
@@ -172,16 +236,29 @@

        RETURN VALUE

                These functions return OK on success and ERR on failure.
 
-       In  ncurses, waddch returns ERR if it is not possible to add a complete
-       character at the cursor position, as when  conversion  of  a  multibyte
-       character  to  a  byte sequence fails, or at least one of the resulting
-       bytes cannot be added to the window.  See section  "PORTABILITY"  below
-       regarding the use of waddch with multibyte characters.
+       In ncurses, these functions fail if
 
-       waddch  can successfully write a character at the bottom right location
-       of the window.  However, ncurses returns ERR  if  scrollok(3x)  is  not
-       enabled  in  that  event,  because  it is not possible to wrap to a new
-       line.
+       o   the curses screen has not been initialized,
+
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer,
+
+       o   wrapping  to  a new line is impossible because scrollok(3x) has not
+           been called on win (or stdscr, as applicable) when a write  to  its
+           bottom right location is attempted, or
+
+       o   it  is  not  possible  to  add  a  complete character at the cursor
+           position.
+
+       The last may be due to different causes:
+
+       o   conversion of a wide character to a  multibyte  character  sequence
+           can fail, or
+
+       o   at  least one of the bytes resulting from wide character conversion
+           to a multibyte character sequence cannot be added  to  the  window.
+           See  section  "PORTABILITY"  below regarding the use of waddch with
+           wide characters.
 
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.
@@ -191,36 +268,92 @@
        addch, mvaddch, mvwaddch, and echochar may be implemented as macros.
 
 
+

        EXTENSIONS

        +       The symbols ACS_S3, ACS_S7, ACS_LEQUAL, ACS_GEQUAL, ACS_PI, ACS_NEQUAL,
+       and  ACS_STERLING were not documented in any publicly released System V
+       and are  not  standard.   However,  many  publicly  available  terminfo
+       entries  include  acs_chars  (acsc)  capabilities  in  which  their key
+       characters (pryz{|}) are embedded, and  a  second-hand  list  of  their
+       character  descriptions  has  come  to  light, which identifies them as
+       VT100 special characters.
+
+       The DEC Special Character and Line Drawing Set (VT100) is indexed by an
+       ASCII character in the range 96 (`) to 126 (~).  That  index  character
+       is  part  of  the  definition  for  the curses ACS_ symbols.  The VT100
+       special characters can be categorized in three groups:
+
+       o   useful graphic symbols with a  standard  ACS_  symbol,  (e.g.,  the
+           line-drawing symbols),
+
+       o   possibly useful characters (these non-standard symbols),
+
+       o   representations  of  control characters (e.g., newline and vertical
+           tabulation).
+
+       A few ACS_ symbols do not  fit  into  DEC's  VT100  scheme.   The  AT&T
+       Teletype  5410v1  arrow  symbols  and ACS_BLOCK use indices outside the
+       range 96 to 126.  Two of the  Teletype  symbols  use  indices  in  that
+       range, with different meaning versus the VT100:
+
+       o   ACS_BOARD corresponds to the VT100 symbol for newline
+
+       o   ACS_LANTERN corresponds to the VT100 symbol for vertical tabulation
+
+       AT&T defined ACS_ names for the most useful graphic symbols, as well as
+       for its own.  Its header file commented:
+
+       /*
+        * Standard alternate character set.  The current ACS world is
+        * evolving, so we support only a widely available subset: the
+        * line drawing characters from the VT100, plus a few from the
+        * Teletype 5410v1.  Eventually there may be support of more
+        * sophisticated ACS line drawing, such as that in the Teletype
+        * 5410, the HP line drawing set, and the like.  There may be
+        * support for some non line oriented characters as well.
+        *
+        * Line drawing ACS names are of the form ACS_trbl, where t is
+        * the top, r is the right, b is the bottom, and l is the left.
+        * t, r, b, and l might be B (blank), S (single), D (double), or
+        * T (thick).  The subset defined here only uses B and S.
+        */
+
+       Although  these  less-useful graphic symbols were not given names, they
+       were used in terminfo entries.  The ncurses  developers  invented  ACS-
+       prefixed names for them.
+
+

        PORTABILITY

        -       X/Open  Curses,  Issue  4  describes  these functions.  It specifies no
-       error conditions for them.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
-       SVr4 curses describes a successful return value  only  as  "an  integer
-       value other than ERR".
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       The  defaults specified for forms-drawing characters apply in the POSIX
+       SVr4  describes  a  successful  return  value only as "an integer value
+       other than ERR".
+
+       The defaults specified for forms-drawing characters apply in the  POSIX
        locale.

        ACS Symbols

        -       X/Open Curses states that the ACS_ definitions are char constants.
-
+       X/Open  Curses  states  that  the  ACS_ definitions are char constants.
        Some implementations are problematic.
 
-       o   Solaris curses, for example, define the ACS symbols  as  constants;
+       o   Solaris curses, for example, defines the ACS symbols as  constants;
            others define them as elements of an array.
 
-           This  implementation  uses  an  array, acs_map, as did SVr4 curses.
-           NetBSD also uses an array, actually named _acs_char, with a #define
-           for compatibility.
+           SVr4  used  an array, acs_map, as does ncurses.  NetBSD curses also
+           uses an array, actually  named  _acs_char,  with  a  "#define"  for
+           compatibility.
 
-       o   HP-UX  curses  equates  some  of  the ACS_ symbols to the analogous
-           WACS_ symbols as if the ACS_  symbols  were  wide  characters  (see
+       o   HP-UX  curses  equates  some  of  the ACS_ symbols to the analogous
+           WACS_ symbols as if the ACS_  symbols  were  wide  characters  (see
            curs_add_wch(3x)).   The  misdefined  symbols  are  the  arrows and
            others that are not used for line drawing.
 
        o   X/Open Curses (Issues 2 through 7) has a  typographical  error  for
-           the  ACS_LANTERN  symbol,  equating  its  "VT100+ Character" to "I"
+           the  ACS_LANTERN  symbol,  equating  its  "VT100+ Character" to "I"
            (capital I), while the header  files  for  SVr4  curses  and  other
            implementations use "i" (small i).
 
@@ -230,17 +363,9 @@
            other hand, its gs6300 (AT&T PC6300 with EMOTS  Terminal  Emulator)
            description uses lowercase i.
 
-       Some  ACS  symbols  (ACS_S3,  ACS_S7,  ACS_LEQUAL,  ACS_GEQUAL, ACS_PI,
-       ACS_NEQUAL, and ACS_STERLING)  were  not  documented  in  any  publicly
-       released  System V.   However, many publicly available terminfo entries
-       include acsc strings  in  which  their  key  characters  (pryz{|})  are
-       embedded,  and  a  second-hand list of their character descriptions has
-       come to light.  The ncurses developers invented ACS-prefixed names  for
-       them.
+       The displayed values of ACS_ constants depend on
 
-       The displayed values of ACS_ constants depend on
-
-       o   the  ncurses  ABI--for  example,  wide-character  versus  non-wide-
+       o   the  ncurses  ABI  --  for example, wide-character versus non-wide-
            character configurations  (the  former  is  capable  of  displaying
            Unicode while the latter is not), and
 
@@ -248,59 +373,61 @@
 
        In  certain  cases,  the  terminal  is  unable to display forms-drawing
        characters  except  by  using  UTF-8;  see  the   discussion   of   the
-       NCURSES_NO_UTF8_ACS environment variable in ncurses(3x)).
+       NCURSES_NO_UTF8_ACS environment variable in ncurses(3x).

        Character Set

        -       X/Open  Curses  assumes  that the parameter passed to waddch contains a
-       single character.  As discussed in curs_attr(3x),  that  character  may
-       have  been more than eight bits wide in an SVr3 or SVr4 implementation,
-       but in the X/Open  Curses  model,  the  details  are  not  given.   The
-       important distinction between SVr4 curses and X/Open Curses is that the
-       latter separates non-character information (attributes and color)  from
-       the  character  code,  which  SVr4  packs  into a chtype for passage to
-       waddch.
+       X/Open  Curses  assumes  that the parameter passed to waddch contains a
+       single character.  That character may have been more  than  eight  bits
+       wide  in  an  SVr3 or SVr4 implementation, but X/Open Curses leaves the
+       width of a non-wide character code unspecified.  The  standard  further
+       does  not specify the internal structure of a chtype, though the use of
+       bitwise operators to combine the character code with attributes  and  a
+       color pair identifier into a chtype for passage to waddch is common.  A
+       portable application uses only the macros discussed in curs_attr(3x) to
+       manipulate a chtype.
 
-       In ncurses, chtype holds  an  eight-bit  character.   But  the  library
-       allows  a  multibyte character to be passed in a succession of calls to
-       waddch.  Other implementations do not; a waddch call transmits  exactly
-       one  character,  which  may be rendered in one or more screen locations
-       depending on whether it is printable.
+       In ncurses, chtype holds an eight-bit character, but the library allows
+       a  multibyte  character sequence to be passed via a succession of calls
+       to waddch.  Other implementations  do  not;  a  waddch  call  transmits
+       exactly  one  character,  which  may  be rendered in one or more screen
+       locations depending  on  whether  it  is  printable  (see  unctrl(3x)).
+       Depending  on  the  locale,  ncurses  inspects  the byte passed in each
+       waddch call and checks whether the latest call  continues  a  multibyte
+       character.    When  a  character  is  complete,  ncurses  displays  the
+       character  and  advances  the  cursor.   If  the  calling   application
+       interrupts the succession of bytes in a multibyte character sequence by
+       changing the current location -- for example, with wmove(3x) -- ncurses
+       discards the incomplete character.
 
-       Depending on the locale settings, ncurses inspects the byte  passed  in
-       each  waddch  call,  and  checks  whether  the  latest call continues a
-       multibyte sequence.  When a character is complete, ncurses displays the
-       character and advances the cursor.
+       For  portability  to  other  implementations,  do  not  rely  upon  the
+       foregoing behavior.  Check whether a character can be represented as  a
+       single byte in the current locale.
 
-       If  the  calling  application  interrupts  the succession of bytes in a
-       multibyte character sequence  by  changing  the  current  location--for
-       example, with wmove(3x)--ncurses discards the incomplete character.
+       o   If it can, call either waddch or wadd_wch.
 
-       For  portability  to  other  implementations,  do  not  rely  upon this
-       behavior.  Check whether a character can be  represented  as  a  single
-       byte in the current locale.
-
-       o   If it can, call either waddch or wadd_wch(3x).
-
-       o   If it cannot, use only wadd_wch(3x).
+       o   If it cannot, use only wadd_wch.
 
 
-

        TABSIZE

        -       SVr4  and  other versions of curses implement the TABSIZE variable, but
-       X/Open Curses does not specify it (see curs_variables(3x)).
+

        HISTORY

        +       4BSD (1980) introduced waddch and its variants.
+
+       SVr3  (1987) added the echochar and wechochar functions and most of the
+       ACS_ constants, except for ACS_GEQUAL, ACS_LEQUAL, ACS_NEQUAL,  ACS_PI,
+       ACS_S3, ACS_S7, and ACS_STERLING.
+
+       ncurses 1.9.6 (1995) furnished the remaining ACS_ constants.

        SEE ALSO

        -       curs_add_wch(3x) describes comparable functions of the ncurses  library
+       curs_add_wch(3x)  describes comparable functions of the ncurses library
        in its wide-character configuration (ncursesw).
 
        curses(3x),    curs_addchstr(3x),    curs_addstr(3x),    curs_attr(3x),
-       curs_clear(3x),  curs_inch(3x),   curs_outopts(3x),   curs_refresh(3x),
-       curs_variables(3x), putchar(3)
+       curs_bkgd(3x),    curs_clear(3x),    curs_inch(3x),   curs_outopts(3x),
+       curs_refresh(3x), curs_variables(3x), putchar(3)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_addch(3x)
+ncurses 6.6                       2025-11-11                    curs_addch(3x)
        diff --git a/doc/html/man/curs_addchstr.3x.html b/doc/html/man/curs_addchstr.3x.html index a3441e6..8aa4080 100644 --- a/doc/html/man/curs_addchstr.3x.html +++ b/doc/html/man/curs_addchstr.3x.html @@ -1,6 +1,6 @@ -curs_addchstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_addchstr 3x 2025-08-16 ncurses 6.6 Library calls -

        curs_addchstr 3x 2024-04-20 ncurses 6.5 Library calls

        +

        curs_addchstr 3x 2025-08-16 ncurses 6.6 Library calls

         curs_addchstr(3x)                Library calls               curs_addchstr(3x)
 
 
-
-

        NAME

        -       addchstr,  addchnstr,  waddchstr,  waddchnstr, mvaddchstr, mvaddchnstr,
-       mvwaddchstr, mvwaddchnstr - add a curses character string to a window
+       addchstr,  waddchstr,  mvaddchstr,  mvwaddchstr, addchnstr, waddchnstr,
+       mvaddchnstr, mvwaddchnstr - add a curses character string to a window

        SYNOPSIS

                #include <curses.h>
 
-       int addchstr(const chtype *chstr);
-       int waddchstr(WINDOW *win, const chtype *chstr);
-       int mvaddchstr(int y, int x, const chtype *chstr);
-       int mvwaddchstr(WINDOW *win, int y, int x, const chtype *chstr);
+       int addchstr(const chtype * chstr);
+       int waddchstr(WINDOW * win, const chtype * chstr);
+       int mvaddchstr(int y, int x, const chtype * chstr);
+       int mvwaddchstr(WINDOW * win, int y, int x,
+             const chtype * chstr);
 
-       int addchnstr(const chtype *chstr, int n);
-       int waddchnstr(WINDOW *win, const chtype *chstr, int n);
-       int mvaddchnstr(int y, int x, const chtype *chstr, int n);
-       int mvwaddchnstr(WINDOW *win, int y, int x, const chtype *chstr, int n);
+       int addchnstr(const chtype * chstr, int n);
+       int waddchnstr(WINDOW * win, const chtype * chstr, int n);
+       int mvaddchnstr(int y, int x, const chtype * chstr, int n);
+       int mvwaddchnstr(WINDOW * win, int y, int x,
+             const chtype * chstr, int n);

        DESCRIPTION

        -       These functions copy the (null-terminated) chstr array into the  window
-       image structure starting at the current cursor position.
+       waddchstr copies the string of curses characters chstr  to  the  window
+       win.   A  null curses character terminates the string.  waddchnstr does
+       the same, but copies at most n characters, or as many as possible if  n
+       is -1.  ncurses(3x) describes the variants of these functions.
 
-       The four functions with n as the last argument copy at most n elements,
-       but no more than will fit on the line.  If n=-1 then the whole array is
-       copied, to the maximum number of characters that will fit on the line.
+       Because  these  functions  do  not call waddch(3x) internally, they are
+       faster than waddstr(3x) and waddnstr(3x).  On the other hand, they
 
-       The  window  cursor  is  not advanced.  These functions are faster than
-       waddnstr.  On the other hand:
+       o   do  not  treat  the  backspace,  carriage  return,  or  line   feed
+           characters specially;
 
-       o   they do not perform checking (such as for the  newline,  backspace,
-           or carriage return characters),
+       o   do not represent unprintable characters with unctrl(3x);
 
-       o   they do not advance the current cursor position,
+       o   do  not  update  the  cursor  position to follow the last character
+           written; and
 
-       o   they do not expand other control characters to ^-escapes, and
-
-       o   they  truncate  the  string  if it crosses the right margin, rather
-           than wrapping it around to the new line.
+       o   truncate the string at  the  window's  right  margin,  rather  than
+           wrapping it to the next line and potentially scrolling.

        RETURN VALUE

        -       All functions return the integer ERR upon failure and OK on success.
+       These functions return OK on success and ERR on failure.
 
-       X/Open  Curses  does  not   specify   any   error   conditions.    This
-       implementation returns an error
+       In ncurses, these functions fail if
 
-       o   if the win parameter is null or
+       o   the curses screen has not been initialized,
 
-       o   if the wchstr parameter is null.
+       o   chstr is a null pointer, or
 
-       Functions  prefixed with "mv" first perform cursor movement and fail if
+       o   (for  functions  taking  a  WINDOW  pointer argument) win is a null
+           pointer.
+
+       Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

        NOTES

        -       All functions except waddchnstr may be macros.
+       All of these functions except waddchnstr may be implemented as macros.

        PORTABILITY

        -       These functions are described in X/Open Curses, Issue 4.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       SVr4  describes  a  successful  return  value only as "an integer value
+       other than ERR".
+
+
+

        HISTORY

        +       SVr3.1 (1987) introduced these functions.

        SEE ALSO

        @@ -115,9 +124,7 @@
 
        curses(3x), curs_addch(3x), curs_addstr(3x)
 
-
-
-ncurses 6.5                       2024-04-20                 curs_addchstr(3x)
+ncurses 6.6                       2025-08-16                 curs_addchstr(3x)
        diff --git a/doc/html/man/curs_addstr.3x.html b/doc/html/man/curs_addstr.3x.html index b7f1c68..27c03f0 100644 --- a/doc/html/man/curs_addstr.3x.html +++ b/doc/html/man/curs_addstr.3x.html @@ -1,6 +1,6 @@ -curs_addstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_addstr 3x 2025-10-20 ncurses 6.6 Library calls -

        curs_addstr 3x 2024-04-20 ncurses 6.5 Library calls

        +

        curs_addstr 3x 2025-10-20 ncurses 6.6 Library calls

         curs_addstr(3x)                  Library calls                 curs_addstr(3x)
 
 
-
-

        NAME

        -       addstr,  addnstr,  waddstr,  waddnstr,  mvaddstr, mvaddnstr, mvwaddstr,
+       addstr,  waddstr,  mvaddstr,  mvwaddstr,  addnstr, waddnstr, mvaddnstr,
        mvwaddnstr - add a string to a curses window and advance the cursor

        SYNOPSIS

                #include <curses.h>
 
-       int addstr(const char *str);
-       int mvaddstr(int y, int x, const char *str);
-       int mvwaddstr(WINDOW *win, int y, int x, const char *str);
-       int waddstr(WINDOW *win, const char *str);
+       int addstr(const char * str);
+       int waddstr(WINDOW * win, const char * str);
+       int mvaddstr(int y, int x, const char * str);
+       int mvwaddstr(WINDOW * win, int y, int x, const char * str);
 
-       int addnstr(const char *str, int n);
-       int mvaddnstr(int y, int x, const char *str, int n);
-       int mvwaddnstr(WINDOW *win, int y, int x, const char *str, int n);
-       int waddnstr(WINDOW *win, const char *str, int n);
+       int addnstr(const char * str, int n);
+       int waddnstr(WINDOW * win, const char * str, int n);
+       int mvaddnstr(int y, int x, const char * str, int n);
+       int mvwaddnstr(WINDOW * win, int y, int x, const char * str, int n);

        DESCRIPTION

                waddstr writes the characters of the (null-terminated)  string  str  to
-       the  window win.  Its process is similar to calling waddch(3x) for each
-       char in str.  Control characters are processed as in waddch(3x).
-
-       waddnstr writes at most n  characters,  or  until  a  terminating  null
-       character  occurs  in  str.   If  n  is  -1, waddnstr writes the entire
-       string.
-
-       ncurses(3x) describes the variants of these functions.
+       the  window  win,  as  if  by  calling waddch(3x) for each char in str.
+       waddnstr is similar, but writes at most n  characters.   If  n  is  -1,
+       waddnstr  writes the entire string.  ncurses(3x) describes the variants
+       of these functions.

        RETURN VALUE

                These functions return OK on success and ERR on failure.
 
-       X/Open Curses does not specify any error conditions.   ncurses  returns
-       an error
+       In ncurses, these functions fail if
 
-       o   if the window pointer is NULL,
+       o   the curses screen has not been initialized,
 
-       o   if the string pointer is NULL, or
+       o   str is a null pointer,
 
-       o   if an internal waddch(3x) call returns an error.
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer, or
+
+       o   an internal waddch(3x) call returns ERR.
 
        Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.

        NOTES

        -       All of these functions except waddnstr may be macros.
+       All of these functions except waddnstr may be implemented as macros.

        PORTABILITY

        -       X/Open Curses, Issue 4 describes these functions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+
+
+

        HISTORY

        +       4BSD  (1980)  introduced  waddstr  along  with its variants, the latter
+       defined as macros.
+
+       SVr3.1 (1987) added waddnstr (and its variants) redefining waddstr as a
+       macro wrapping it.

        SEE ALSO

        @@ -107,9 +115,7 @@
 
        curses(3x), curs_addch(3x), curs_addchstr(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_addstr(3x)
+ncurses 6.6                       2025-10-20                   curs_addstr(3x)
        diff --git a/doc/html/man/curs_addwstr.3x.html b/doc/html/man/curs_addwstr.3x.html index ce3229a..8fe360b 100644 --- a/doc/html/man/curs_addwstr.3x.html +++ b/doc/html/man/curs_addwstr.3x.html @@ -1,6 +1,6 @@ -curs_addwstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_addwstr 3x 2025-03-15 ncurses 6.6 Library calls -

        curs_addwstr 3x 2024-04-20 ncurses 6.5 Library calls

        +

        curs_addwstr 3x 2025-03-15 ncurses 6.6 Library calls

         curs_addwstr(3x)                 Library calls                curs_addwstr(3x)
 
 
-
-

        NAME

        -       addwstr,   addnwstr,   waddwstr,   waddnwstr,   mvaddwstr,  mvaddnwstr,
-       mvwaddwstr, mvwaddnwstr - add  a  wide-character  string  to  a  curses
+       addwstr,   waddwstr,   mvaddwstr,   mvwaddwstr,   addnwstr,  waddnwstr,
+       mvaddnwstr, mvwaddnwstr - add  a  wide-character  string  to  a  curses
        window and advance the cursor

        SYNOPSIS

                #include <curses.h>
 
-       int addwstr(const wchar_t *wstr);
-       int mvaddwstr(int y, int x, const wchar_t *wstr);
-       int mvwaddwstr(WINDOW *win, int y, int x, const wchar_t *wstr);
-       int waddwstr(WINDOW *win, const wchar_t *wstr);
+       int addwstr(const wchar_t * wstr);
+       int waddwstr(WINDOW * win, const wchar_t * wstr);
+       int mvaddwstr(int y, int x, const wchar_t * wstr);
+       int mvwaddwstr(WINDOW * win, int y, int x,
+             const wchar_t * wstr);
 
-       int addnwstr(const wchar_t *wstr, int n);
-       int mvaddnwstr(int y, int x, const wchar_t *wstr, int n);
-       int mvwaddnwstr(WINDOW *win, int y, int x, const wchar_t *wstr, int n);
-       int waddnwstr(WINDOW *win, const wchar_t *wstr, int n);
+       int addnwstr(const wchar_t * wstr, int n);
+       int waddnwstr(WINDOW * win, const wchar_t * wstr, int n);
+       int mvaddnwstr(int y, int x, const wchar_t * wstr, int n);
+       int mvwaddnwstr(WINDOW * win, int y, int x,
+             const wchar_t * wstr, int n);

        DESCRIPTION

                waddwstr  writes  the  characters  of  the (wide-null-terminated) wide-
-       character string wstr to the window win.  Its  process  is  similar  to
-       constructing   a  cchar_t  for  each  wchar_t  in  wstr,  then  calling
-       wadd_wch(3x) with the resulting cchar_t.
-
-       o   Spacing and non-spacing characters in the string are processed  one
-           at a time, and
-
-       o   control characters are processed as in wadd_wch(3x).
-
-       waddnwstr writes at most n wide characters, or until a terminating wide
-       null character occurs in wstr.  If n is -1, waddnwstr writes the entire
-       wide string.
-
+       character string wstr to the  window  win,  as  if  by  constructing  a
+       cchar_t  for  each  wchar_t in wstr, then calling wadd_wch(3x) with the
+       resulting cchar_t.  curses processes spacing and non-spacing characters
+       in wstr one at a time.  waddnwstr is similar, but writes at most n wide
+       characters.  If n is -1,  waddnwstr  writes  the  entire  wide  string.
        ncurses(3x) describes the variants of these functions.

        RETURN VALUE

                These functions return OK on success and ERR on failure.
 
-       X/Open  Curses  does not specify any error conditions.  ncurses returns
-       an error
+       In ncurses, these functions fail if
 
-       o   if the window pointer is NULL,
+       o   the curses screen has not been initialized,
 
-       o   if the string pointer is NULL, or
+       o   wstr is a null pointer,
 
-       o   if an internal wadd_wch(3x) call returns an error.
+       o   (for  functions  taking  a  WINDOW  pointer argument) win is a null
+           pointer, or
+
+       o   an internal wadd_wch(3x) call returns ERR.
 
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.
@@ -105,18 +99,26 @@

        PORTABILITY

        -       X/Open Curses, Issue 4 describes these functions.
+       X/Open Curses Issue 4 describes these functions.
+
+       SVr4  describes  a  successful  return  value only as "an integer value
+       other than ERR".
+
+
+

        HISTORY

        +       X/Open Curses Issue 4 (1995) initially specified these functions.   The
+       System V  Interface  Definition  Version 4  of  the same year specified
+       functions named waddwstr and waddnwstr (and the usual variants).  These
+       were later additions to SVr4.x, not appearing in the first SVr4 (1989).

        SEE ALSO

        -       curs_addstr(3x)  describes  comparable functions of the ncurses library
+       curs_addstr(3x) describes comparable functions of the  ncurses  library
        in its non-wide-character configuration.
 
        curses(3x), curs_add_wch(3x), curs_add_wchstr(3x)
 
-
-
-ncurses 6.5                       2024-04-20                  curs_addwstr(3x)
+ncurses 6.6                       2025-03-15                  curs_addwstr(3x)
        diff --git a/doc/html/man/curs_attr.3x.html b/doc/html/man/curs_attr.3x.html index bc1fd85..640e866 100644 --- a/doc/html/man/curs_attr.3x.html +++ b/doc/html/man/curs_attr.3x.html @@ -1,7 +1,7 @@ -curs_attr 3x 2024-04-27 ncurses 6.5 Library calls +curs_attr 3x 2025-11-11 ncurses 6.6 Library calls -

        curs_attr 3x 2024-04-27 ncurses 6.5 Library calls

        +

        curs_attr 3x 2025-11-11 ncurses 6.6 Library calls

         curs_attr(3x)                    Library calls                   curs_attr(3x)
 
 
-
-

        NAME

                attr_get, wattr_get, attr_set, wattr_set, attr_off, wattr_off, attr_on,
        wattr_on, attroff, wattroff, attron, wattron, attrset, wattrset, chgat,
@@ -121,24 +119,25 @@
        Use wattr_get to retrieve attributes for the given window.
 
        Use attr_on and wattr_on to turn on  window  attributes,  i.e.,  values
-       OR'd  together  in  attr,  without  affecting  other  attributes.   Use
-       attr_off and wattr_off to turn off window attributes, again values OR'd
-       together in attr, without affecting other attributes.
+       logically "or"-ed together in attr, without affecting other attributes.
+       Use  attr_off and wattr_off to turn off window attributes, again values
+       logically "or"-ed together in attr, without affecting other attributes.

        Legacy Window Attributes

        -       The  X/Open  window attribute routines which set or get, turn on or off
-       are extensions of older routines which assume that color pairs are OR'd
-       into  the attribute parameter.  These newer routines use similar names,
-       because X/Open simply added an underscore (_) for the newer names.
+       The X/Open window attribute routines which set or get, turn on  or  off
+       are  extensions  of  older  routines  which assume that color pairs are
+       logically "or"-ed into the attribute parameter.  These  newer  routines
+       use  similar  names,  because X/Open simply added an underscore (_) for
+       the newer names.
 
-       The int datatype used in the legacy routines is treated as if it is the
-       same  size  as  chtype  (used by addch(3x)).  It holds the common video
-       attributes (such as bold, reverse), as well as a few  bits  for  color.
-       Those  bits  correspond  to  the  A_COLOR symbol.  The COLOR_PAIR macro
-       provides a value which can be OR'd into the attribute  parameter.   For
-       example,  as  long as that value fits into the A_COLOR mask, then these
-       calls produce similar results:
+       The int datatype used in the legacy routines is treated as if it is the
+       same size as chtype (used by addch(3x)).  It  holds  the  common  video
+       attributes  (such  as  bold, reverse), as well as a few bits for color.
+       Those bits correspond to the  A_COLOR  symbol.   The  COLOR_PAIR  macro
+       provides  a  value  which  can  be logically "or"-ed into the attribute
+       parameter.  For example, as long as that value fits  into  the  A_COLOR
+       mask, then these calls produce similar results:
 
            attrset(A_BOLD | COLOR_PAIR(pair));
            attr_set(A_BOLD, pair, NULL);
@@ -148,28 +147,28 @@
        (8) bits, then COLOR_PAIR(259) is 4 (i.e., 259 is 4 more than the limit
        255).
 
-       The  PAIR_NUMBER  macro extracts a pair number from an int (or chtype).
-       For example, the input and output values in these statements  would  be
+       The PAIR_NUMBER macro extracts a pair number from an int  (or  chtype).
+       For  example,  the input and output values in these statements would be
        the same:
 
            int value = A_BOLD | COLOR_PAIR(input);
            int output = PAIR_NUMBER(value);
 
-       The  attrset routine is a legacy feature predating SVr4 curses but kept
-       in X/Open Curses  for  the  same  reason  that  SVr4  curses  kept  it:
+       The attrset routine is a legacy feature predating SVr4 curses but  kept
+       in  X/Open  Curses  for  the  same  reason  that  SVr4  curses kept it:
        compatibility.
 
-       The  remaining  attr*  functions operate exactly like the corresponding
-       attr_* functions, except that they take arguments of  type  int  rather
-       than attr_t.
+       The remaining attr* functions operate exactly  like  the  corresponding
+       attr_*  functions,  except  that they take arguments of type int rather
+       than attr_t.
 
-       There  is  no  corresponding attrget function as such in X/Open Curses,
+       There is no corresponding attrget function as such  in  X/Open  Curses,
        although ncurses provides getattrs (see curs_legacy(3x)).

        Change Character Rendition

                The  routine  chgat  changes  the  attributes  of  a  given  number  of
-       characters  starting at the current cursor location of stdscr.  It does
+       characters starting at the current cursor location of stdscr.  It  does
        not update the cursor and does not perform wrapping.  A character count
        of  -1  or  greater  than  the  remaining  window width means to change
        attributes all the way to the end of  the  current  line.   The  wchgat
@@ -182,32 +181,32 @@

        Change Window Color

                The routine color_set sets the current color of the given window to the
-       foreground/background  combination  described   by   the   color   pair
+       foreground/background   combination   described   by   the  color  pair
        parameter.

        Standout

        -       The  routine  standout  is the same as attron(A_STANDOUT).  The routine
-       standend is the same as attrset(A_NORMAL) or attrset(0),  that  is,  it
+       The routine standout is the same as  attron(A_STANDOUT).   The  routine
+       standend  is  the  same as attrset(A_NORMAL) or attrset(0), that is, it
        turns off all attributes.
 
        X/Open Curses does not mark these "restricted", because
 
        o   they have well established legacy use, and
 
-       o   there  is  no  ambiguity  about  the  way  the  attributes might be
+       o   there is no  ambiguity  about  the  way  the  attributes  might  be
            combined with a color pair.

        Video Attributes

        -       The following video attributes, defined in <curses.h>, can be passed to
-       the  routines attron, attroff, and attrset, or OR'd with the characters
-       passed to addch (see curs_addch(3x)).
+       The  following  video attributes, defined in curses.h, can be passed to
+       attron, attroff, attrset, and logically "or"-ed with characters  passed
+       to addch(3x).
 
               Name           Description
               -----------------------------------------------------------------
               A_NORMAL       Normal display (no highlight)
-              A_STANDOUT     Best highlighting mode of the terminal
+              A_STANDOUT     Best highlighting mode available
               A_UNDERLINE    Underlining
               A_REVERSE      Reverse video
               A_BLINK        Blinking
@@ -217,11 +216,12 @@
               A_INVIS        Invisible or blank mode
               A_ALTCHARSET   Alternate character set
               A_ITALIC       Italics (non-X/Open extension)
-              A_CHARTEXT     Bit-mask to extract a character
-              A_COLOR        Bit-mask to extract a color (legacy routines)
+              A_ATTRIBUTES   Mask to extract character code
+              A_CHARTEXT     Mask to extract attributes
+              A_COLOR        Mask to extract color pair identifier
 
-       These video attributes are supported by attr_on and  related  functions
-       (which also support the attributes recognized by attron, etc.):
+       attr_on,  attr_off,  and  attr_set support the foregoing as well as the
+       following additional attributes.
 
               Name            Description
               -----------------------------------------------------------------
@@ -232,42 +232,33 @@
               WA_TOP          Top highlight
               WA_VERTICAL     Vertical highlight
 
-       The  return  values  of many of these routines are not meaningful (they
-       are implemented as macro-expanded assignments and simply  return  their
-       argument).   The  SVr4 manual page claims (falsely) that these routines
-       always return 1.
-

        RETURN VALUE

        -       All routines return the integer OK on success, or ERR on failure.
+       These functions return OK on success and ERR on failure.
 
-       X/Open Curses does not specify any error conditions.
+       In ncurses, they return ERR if win is NULL.
 
-       This implementation
+       wcolor_set returns ERR if pair is outside the range 0..COLOR_PAIRS-1.
 
-       o   returns an error if the window pointer is null.
-
-       o   returns an error if the color  pair  parameter  for  wcolor_set  is
-           outside the range 0..COLOR_PAIRS-1.
-
-       o   does  not  return an error if either of the parameters of wattr_get
-           used for retrieving attribute or color pair values is NULL.
+       wattr_get does not fail if its attrs or pair parameter is NULL.
 
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

        NOTES

        -       These functions may be macros:
+       attr_on,  attr_off,  attr_set,  wattr_set,  chgat,  mvchgat,  mvwchgat,
+       wchgat, and color_set are part of ncurses's wide-character API, and are
+       not available in its non-wide-character configuration.
 
-              attroff,  wattroff, attron, wattron, attrset, wattrset, standend
-              and standout.
+       attron, wattron, attroff, wattroff, attrset,  wattrset,  standout,  and
+       standend may be implemented as macros.
 
-       Color pair values can only be OR'd with attributes if the  pair  number
-       is less than 256.  The alternate functions such as color_set can pass a
-       color pair value directly.  However, ncurses ABI 4 and 5 simply OR this
-       value  within  the  alternate functions.  You must use ncurses ABI 6 to
-       support more than 256 color pairs.
+       Color  pair values may be logically "or"-ed with attributes if the pair
+       number is less than 256.  The alternate functions such as color_set can
+       pass a color pair value directly.  However, ncurses ABI 4 and 5  simply
+       logically "or" this value within the alternate functions.  You must use
+       ncurses ABI 6 to support more than 256 color pairs.

        EXTENSIONS

        @@ -280,28 +271,33 @@
 
        Each  of  the functions added by XSI Curses has a parameter opts, which
        X/Open Curses  still  (after  more  than  twenty  years)  documents  as
-       reserved  for  future  use,  saying  that  it  should  be  NULL.   This
+       reserved  for  future  use,  saying  that  it  should  be  NULL.   This
        implementation uses that parameter in ABI 6  for  the  functions  which
        have a color pair parameter to support extended color pairs:
 
        o   For functions which modify the color, e.g., wattr_set and wattr_on,
-           if opts is set it is treated as a pointer to int, and used  to  set
-           the color pair instead of the short pair parameter.
+           if  opts  is set it is treated as a pointer to int, and used to set
+           the color pair instead of the short pair parameter.
 
        o   For functions which retrieve the color, e.g., wattr_get, if opts is
-           set it is treated as a pointer to int, and  used  to  retrieve  the
-           color  pair  as  an int value, in addition to retrieving it via the
-           standard pointer to short parameter.
+           set it is treated as a pointer to int, and  used  to  retrieve  the
+           color  pair  as  an int value, in addition to retrieving it via the
+           standard pointer to short parameter.
 
        o   For functions which turn attributes off, e.g., wattr_off, the  opts
-           parameter is ignored except except to check that it is NULL.
+           parameter is ignored except to check that it is NULL.

        PORTABILITY

        -       These  functions are described in X/Open Curses, Issue 4.  The standard
-       defined the dedicated  type  for  highlights,  attr_t,  which  was  not
-       defined in SVr4 curses.  The functions taking attr_t arguments were not
-       supported under SVr4.
+       These  functions  are described in X/Open Curses Issue 4.  It specifies
+       no error conditions for them.
+
+       The standard defined the dedicated type for highlights,  attr_t,  which
+       was  not defined in SVr4 curses.  The functions taking attr_t arguments
+       were not supported under SVr4.
+
+       SVr4 describes the functions not taking attr_t  or  pair  arguments  as
+       always returning 1.
 
        Very old versions of this library did not force an update of the screen
        when  changing  the  attributes.   Use  touchwin to force the screen to
@@ -310,7 +306,7 @@
        X/Open  Curses  states   that   whether   the   traditional   functions
        attron/attroff/attrset  can  manipulate  attributes other than A_BLINK,
        A_BOLD, A_DIM, A_REVERSE, A_STANDOUT, or A_UNDERLINE is  "unspecified".
-       Under  this  implementation  as  well  as  SVr4 curses, these functions
+       Under  this  implementation  as  well  as  SVr4 curses, these functions
        correctly manipulate all other highlights (specifically,  A_ALTCHARSET,
        A_PROTECT, and A_INVIS).
 
@@ -324,102 +320,99 @@
        the newer set of names:
 
               Name            Description
-              -----------------------------------------------------------------
+              -------------------------------------------------
               WA_NORMAL       Normal display (no highlight)
-              WA_STANDOUT     Best highlighting mode of the terminal
+              WA_STANDOUT     Best highlighting mode available
               WA_UNDERLINE    Underlining
               WA_REVERSE      Reverse video
               WA_BLINK        Blinking
               WA_DIM          Half bright
               WA_BOLD         Extra bright or bold
-
               WA_ALTCHARSET   Alternate character set
 
-       X/Open Curses does not assign values to  these  symbols,  nor  does  it
-       state  whether or not they are related to the similarly-named A_NORMAL,
+       X/Open  Curses  does  not  assign  values to these symbols, nor does it
+       state whether or not they are related to the similarly-named  A_NORMAL,
        etc.:
 
-       o   X/Open Curses specifies that each  pair  of  corresponding  A_  and
-           WA_-using   functions   operates   on  the  same  current-highlight
+       o   X/Open  Curses  specifies  that  each  pair of corresponding A_ and
+           WA_-using  functions  operates  on   the   same   current-highlight
            information.
 
-       o   However, in some  implementations,  those  symbols  have  unrelated
+       o   However,  in  some  implementations,  those  symbols have unrelated
            values.
 
-           For example, the Solaris xpg4 (X/Open) curses declares attr_t to be
-           an unsigned short integer (16-bits), while  chtype  is  a  unsigned
+           For example, the Solaris xpg4 (X/Open) curses declares attr_t to be
+           an unsigned short integer (16-bits), while  chtype  is  a  unsigned
            integer (32-bits).  The WA_ symbols in this case are different from
-           the A_ symbols because they are used for a smaller  datatype  which
+           the  A_  symbols because they are used for a smaller datatype which
            does not represent A_CHARTEXT or A_COLOR.
 
            In this implementation (as in many others), the values happen to be
-           the same because it simplifies copying information  between  chtype
-           and cchar_t variables.
+           the same because it simplifies copying information  between  chtype
+           and cchar_t variables.
 
-       o   Because  ncurses's  attr_t  can  hold  a color pair (in the A_COLOR
+       o   Because  ncurses's  attr_t  can  hold  a color pair (in the A_COLOR
            field), a call to wattr_on, wattr_off, or wattr_set may  alter  the
            window's  color.   If  the  color pair information in the attribute
            parameter is zero, no change is made to the window's color.
 
-           This is consistent with SVr4 curses; X/Open Curses does not specify
+           This is consistent with SVr4 curses; X/Open Curses does not specify
            this.
 
-       The  X/Open  Curses  extended  conformance  level  adds  new highlights
-       A_HORIZONTAL,  A_LEFT,   A_LOW,   A_RIGHT,   A_TOP,   A_VERTICAL   (and
-       corresponding  WA_  macros  for  each).   As  of  August 2013, no known
+       The X/Open  Curses  extended  conformance  level  adds  new  highlights
+       A_HORIZONTAL,   A_LEFT,   A_LOW,   A_RIGHT,   A_TOP,   A_VERTICAL  (and
+       corresponding WA_ macros for  each).   As  of  August  2013,  no  known
        terminal provides these highlights (i.e., via the sgr1 capability).

        HISTORY

        -       X/Open Curses is largely based  on  SVr4  curses,  adding  support  for
-       "wide-characters"  (not  specific  to  Unicode).   Some  of  the X/Open
-       differences from SVr4 curses address the way video  attributes  can  be
-       applied  to wide-characters.  But aside from that, attrset and attr_set
-       are similar.  SVr4 curses provided the basic features for  manipulating
-       video  attributes.  However, earlier versions of curses provided a part
-       of these features.
+       4BSD  (1980) used a char to represent each cell of the terminal screen.
+       It assumed 7-bit character codes, employing the eighth bit of a byte to
+       represent a  standout  attribute  (often  implemented  as  bold  and/or
+       reverse  video).   It  introduced  standout,  standend,  wstandout, and
+       wstandend  functions   to   manipulate   this   bit.    Despite   their
+       inflexibility,  they  carried  over into System V curses and ultimately
+       X/Open Curses due to their pervasive use in legacy applications.  While
+       some 1980s terminals supported  a  variety  of  video  attributes,  BSD
+       curses could do nothing with them.
 
-       As seen in 2.8BSD, curses assumed 7-bit characters,  using  the  eighth
-       bit  of  a byte to represent the standout feature (often implemented as
-       bold and/or reverse video).  The BSD curses library provided  functions
-       standout  and  standend which were carried along into X/Open Curses due
-       to their pervasive use in legacy applications.
+       SVr2  (1984) provided an improved curses library, introducing chtype to
+       create the abstract notion of a curses character; this was  by  default
+       an  unsigned  short,  with a provision for compile-time redefinition to
+       other integral types (a freedom not necessarily available to  users  of
+       shared  libraries,  and  in any event a source license was necessary to
+       exercise  it).   It  added  the  functions  attron,  attroff,  attrset,
+       wattron, wattroff, and wattrset, and defined the A_ macros listed above
+       (except for A_ITALIC and A_COLOR) for use by applications to manipulate
+       other  attributes.  The values of these macros were not necessarily the
+       same in different systems, even among those certified as System V.
 
-       Some  terminals  in  the  1980s  could  support  a  variety  of   video
-       attributes,  although  the  BSD  curses  library  could do nothing with
-       those.  System V  (1983)  provided  an  improved  curses  library.   It
-       defined  the A_ symbols for use by applications to manipulate the other
-       attributes.  There are few useful references for the chronology.
+       SVr3.2 (1988) added the A_COLOR macro along with a  color  system;  see
+       curs_color(3x).
 
-       Goodheart's book UNIX Curses Explained (1991)  describes  SVr3  (1987),
-       commenting on several functions:
+       X/Open  Curses  Issue 4  (1995)  is  largely  based on SVr4 curses, but
+       recognized that the wchar_t type of ISO C95 was intended to house  only
+       a  single character code, not a sequence of codes combining with a base
+       character, let alone could it reliably offer  room  for  a  color  pair
+       identifier  and  a  set  of attribute bits with a potential for further
+       growth -- thus the standard invented the curses complex character  type
+       cchar_t  and a separate type attr_t for storage of attribute bits.  The
+       new types brought along several new functions to manipulate them,  some
+       corresponding  to  existing  chtype-based functions (attr_on, attr_off,
+       attr_set, wattr_on, wattr_off, and wattr_set), and some new (chgat  and
+       its variants, color_set, and wcolor_set).
 
-       o   the  attron,  attroff, attrset functions (and most of the functions
-           found in SVr4 but not in BSD curses) were introduced by System V,
+       Different  Unix systems used differently sized bit fields in chtype for
+       the character code and the color pair identifier, and took into account
+       platforms' different integer sizes (32- versus 64-bit).
 
-       o   the alternate character set feature with A_ALTCHARSET was added  in
-           SVr2 and improved in SVr3 (by adding acs_map[]),
-
-       o   start_color  and  related color-functions were introduced by System
-           V.3.2,
-
-       o   pads, soft-keys were added in SVr3, and
-
-       Goodheart did not mention the background character or the cchar_t type.
-       Those are respectively SVr4 and X/Open features.  He did mention the A_
-       constants, but did not indicate their values.  Those were not the  same
-       in different systems, even for those marked as System V.
-
-       Different  Unix  systems  used  different  sizes  for the bit-fields in
-       chtype for characters and colors, and took into account  the  different
-       integer sizes (32-bit versus 64-bit).
-
-       This  table  showing  the number of bits for A_COLOR and A_CHARTEXT was
-       gleaned from the curses header files for various operating systems  and
-       architectures.   The inferred architecture and notes reflect the format
-       and size of the  defined  constants  as  well  as  clues  such  as  the
-       alternate  character  set implementation.  A 32-bit library can be used
-       on a 64-bit system, but not necessarily the reverse.
+       The following  table  showing  the  number  of  bits  for  A_COLOR  and
+       A_CHARTEXT  was  gleaned  from  the  curses  header  files  for various
+       operating systems and architectures.   The  inferred  architecture  and
+       notes  reflect  the format and size of the defined constants as well as
+       clues such as the alternate character  set  implementation.   A  32-bit
+       library  can  be  used  on  a  64-bit  system,  but not necessarily the
+       converse.
 
                                      Bits
        Year  System        Arch   Color  Char  Notes
@@ -434,7 +427,7 @@
        1996  AIX 4.2       32     7      16    X/Open curses
        1996  OSF/1 r4      32     6      16    X/Open curses
        1997  HP-UX 11.00   32     6      8     X/Open curses
-       2000  U/Win         32/64  7/31   16    uses chtype
+       2000  UWIN          32/64  7/31   16    uses chtype
 
        Notes:
 
@@ -444,60 +437,59 @@
               in 1996.
 
           o   HP-UX  10.30 (1997) marked "curses_colr" obsolete.  That version
-              of curses was dropped with HP-UX 11.30 in 2006.
+              of curses was dropped with HP-UX 11.30 in 2006.
 
           Regarding OSF/1 (and Tru64),
 
-          o   These used 64-bit hardware.   Like  ncurses,  the  OSF/1  curses
+          o   These used 64-bit hardware.   Like  ncurses,  the  OSF/1  curses
               interface is not customized for 32-bit and 64-bit versions.
 
           o   Unlike  other  systems  which  evolved  from  AT&T  code,  OSF/1
-              provided a new implementation for X/Open curses.
+              provided a new implementation for X/Open Curses.
 
           Regarding Solaris,
 
           o   The initial release of Solaris was in 1992.
 
-          o   The xpg4 (X/Open) curses was developed by MKS from 1990 to 1995.
-              Sun's copyright began in 1996.
+          o   Its  XPG4  (X/Open  Curses-conforming)   xcurses   library   was
+              developed  by  Mortice  Kern  Systems  from 1990 to 1995.  Sun's
+              copyright began in 1996.
 
-          o   Sun updated the X/Open curses interface after 64-bit support was
-              introduced  in  1997,  but  did  not  modify  the  SVr4   curses
+          o   Sun updated the X/Open Curses interface after 64-bit support was
+              introduced  in  1997,  but  did  not  modify  the  SVr4   curses
               interface.
 
-          Regarding U/Win,
+          Regarding UWIN,
 
-          o   Development  of  the  curses  library  began in 1991, stopped in
+          o   Development  of  the  curses  library  began in 1991, stopped in
               2000.
 
           o   Color support was added in 1998.
 
-          o   The library uses only chtype (no cchar_t).
+          o   The library uses only chtype (not cchar_t).
 
-       Once X/Open curses was adopted in the mid-1990s, the  constraint  of  a
-       32-bit interface with many colors and wide-characters for chtype became
-       a moot point.  The cchar_t structure (whose size and  members  are  not
+       Once X/Open Curses was adopted in the mid-1990s, the  constraint  of  a
+       32-bit interface with many colors and wide-characters for chtype became
+       a  moot  point.   The cchar_t structure (whose size and members are not
        specified in X/Open Curses) could be extended as needed.
 
-       Other interfaces are rarely used now:
+       Other interfaces are rarely used now.
 
-       o   BSD  curses was improved slightly in 1993/1994 using Keith Bostic's
-           modification to make the library 8-bit clean for nvi(1).  He  moved
-           standout attribute to a structure member.
+       o   BSD curses was improved slightly in 1993/1994 using Keith  Bostic's
+           modification  to make the library 8-bit clean for nvi(1).  He moved
+           the standout attribute to a structure member.  The resulting 4.4BSD
+           curses was replaced by ncurses over the next ten years.
 
-           The  resulting  4.4BSD curses was replaced by ncurses over the next
-           ten years.
+       o   UWIN has been defunct since 2012.
 
-       o   U/Win is rarely used now.
+       ncurses 6.0 (2015) added the A_ITALIC macro.

        SEE ALSO

                curses(3x),     curs_addch(3x),     curs_addstr(3x),     curs_bkgd(3x),
        curs_printw(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-27                     curs_attr(3x)
+ncurses 6.6                       2025-11-11                     curs_attr(3x)
          diff --git a/doc/html/man/curs_beep.3x.html b/doc/html/man/curs_beep.3x.html index e3d6c81..76f78a4 100644 --- a/doc/html/man/curs_beep.3x.html +++ b/doc/html/man/curs_beep.3x.html @@ -1,6 +1,6 @@ -curs_beep 3x 2024-04-20 ncurses 6.5 Library calls +curs_beep 3x 2025-02-01 ncurses 6.6 Library calls -

          curs_beep 3x 2024-04-20 ncurses 6.5 Library calls

          +

          curs_beep 3x 2025-02-01 ncurses 6.6 Library calls

           curs_beep(3x)                    Library calls                   curs_beep(3x)
 
 
-
-

          NAME

                  beep, flash - ring the (visual) bell of the terminal with curses
 
@@ -58,35 +56,45 @@

          DESCRIPTION

          -       The  beep  and flash routines are used to alert the terminal user.  The
-       routine beep sounds an audible alarm  on  the  terminal,  if  possible;
-       otherwise  it  flashes  the  screen  (visible bell).  The routine flash
-       flashes the screen, and if that is not possible, sounds the alert.   If
-       neither  alert is possible, nothing happens.  Nearly all terminals have
-       an audible alert (bell or beep), but only some can flash the screen.
+       beep  and  flash  alert  the  terminal user: the former by sounding the
+       terminal's  audible  alarm,  and  the  latter  by  visibly   attracting
+       attention.    Commonly,   a   terminal  implements  a  visual  bell  by
+       momentarily reversing the character foreground and background colors on
+       the entire display; even  a  monochrome  device  can  do  this.   These
+       functions  each  attempt  the  other alert type if the one requested is
+       unavailable.  If neither  is  available,  curses  performs  no  action.
+       Nearly  all terminals have an audible alert mechanism such as a bell or
+       piezoelectric buzzer, but only some can flash the screen.

          RETURN VALUE

          -       These routines return OK if they succeed in beeping  or  flashing,  ERR
-       otherwise.
+       These functions return OK on success and ERR on failure.
+
+       In ncurses, beep and flash return OK if the terminal type supports  the
+       corresponding  capability: bell (bel) for beep and flash_screen (flash)
+       for flash.  Otherwise they return ERR.

          EXTENSIONS

          -       SVr4's  beep  and  flash  routines  always  returned  OK, so it was not
-       possible to tell when the beep or flash failed.
+       In ncurses, these functions can return ERR.

          PORTABILITY

          -       These functions are described in X/Open Curses, Issue 4.  Like SVr4, it
-       specifies that they always return OK.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       On SVr4 curses, they always return OK, and X/Open Curses specifies them
+       as doing so.
+
+
+

          HISTORY

          +       SVr2 (1984) introduced beep and flash.

          SEE ALSO

          -       curses(3x)
+       curses(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-04-20                     curs_beep(3x)
+ncurses 6.6                       2025-02-01                     curs_beep(3x)
          diff --git a/doc/html/man/curs_bkgd.3x.html b/doc/html/man/curs_bkgd.3x.html index 47d2e13..a4d2a2e 100644 --- a/doc/html/man/curs_bkgd.3x.html +++ b/doc/html/man/curs_bkgd.3x.html @@ -1,6 +1,6 @@ -curs_bkgd 3x 2024-04-20 ncurses 6.5 Library calls +curs_bkgd 3x 2025-08-23 ncurses 6.6 Library calls -

          curs_bkgd 3x 2024-04-20 ncurses 6.5 Library calls

          +

          curs_bkgd 3x 2025-08-23 ncurses 6.6 Library calls

           curs_bkgd(3x)                    Library calls                   curs_bkgd(3x)
 
 
-
-

          NAME

                  bkgdset,  wbkgdset,  bkgd,  wbkgd, getbkgd - manipulate background of a
        curses window of characters
@@ -64,24 +62,29 @@

          DESCRIPTION

          -       The  background  of  a  curses  window  (in  the  library's  non-"wide"
-       configuration)   is  a  chtype  combining  a  set  of  attributes  (see
-       curs_attr(3x)) with a character called the blank character.
+       Every curses  window  has  a  background  character  property:  in  the
+       library's  non-wide-character  configuration,  it is a curses character
+       (chtype) that combines a set of attributes (and, if colors are enabled,
+       a color pair identifier) with a character code.   When  erasing  (parts
+       of)  a  window,  curses  replaces  the erased cells with the background
+       character.
 
-       The blank character is a spacing character that  populates  a  window's
-       character  cells  when  their  contents are erased without replacement.
-       The background's attributes are combined with all non-blank  characters
-       written  to  the window, as with the waddch(3x) and winsch(3x) families
-       of functions.
+       curses also uses the background character when writing characters to  a
+       populated window.
 
-       The blank character and  attributes  of  the  background  combine  with
-       characters  written  to  the window as described below.  The background
-       becomes a property of the character  and  moves  with  it  through  any
-       scrolling and insert/delete line/character operations.
+       o   The  attribute  part  of the background character combines with all
+           non-blank character cells  in  the  window,  as  populated  by  the
+           waddch(3x)  and  winsch(3x)  families  of functions (and those that
+           call them).
 
-       To  the  extent possible on a given terminal, the attribute part of the
-       background is displayed as the graphic rendition of the  character  put
-       on the screen.
+       o   Both the character code and attributes of the background  character
+           combine with blank character cells in the window.
+
+       The  background character's set of attributes becomes a property of the
+       character cell and move with it through any scrolling and insert/delete
+       line/character operations.  To the  extent  possible  on  the  terminal
+       type, curses displays the attributes of the background character as the
+       graphic rendition of a character cell on the display.

          bkgd, wbkgd

          @@ -95,38 +98,40 @@
        o   Wherever the former background character appears, it changes to the
            new background character.
 
-       ncurses  updates  the rendition of each character cell by comparing the
-       character, non-color attributes, and colors.  The  library  applies  to
-       following  procedure  to  each cell in the window, whether or not it is
-       blank.
+       ncurses updates the rendition of each character cell by  comparing  the
+       character, non-color attributes, and color pair selection.  The library
+       applies  the following procedure to each cell in the window, whether or
+       not it is blank.
 
        o   ncurses first compares  the  cell's  character  to  the  previously
-           specified  blank  character;  if they match, ncurses writes the new
-           blank character to the cell.
+           specified  background  character; if they match, ncurses writes the
+           new background character to the cell.
 
-       o   ncurses then checks if the cell uses color, that is, its color pair
-           value  is  nonzero.   If not, it simply replaces the attributes and
-           color  pair  in  the  cell  with  those  from  the  new  background
+       o   ncurses then checks whether the cell uses color; that is, its color
+           pair value is nonzero.  If not, it simply replaces  the  attributes
+           and  color  pair  in  the  cell  with those from the new background
            character.
 
-       o   If  the  cell  uses color, and its background color matches that of
-           the current window background, ncurses removes attributes that  may
-           have  come  from the current background and adds those from the new
-           background.  It finishes by setting the cell's  background  to  use
+       o   If the cell uses color, and its background color  matches  that  of
+           the  current window background, ncurses removes attributes that may
+           have come from the current background and adds those from  the  new
+           background.   It  finishes  by setting the cell's background to use
            the new window background color.
 
-       o   If  the  cell  uses  color, and its background color does not match
-           that of the current window background,  ncurses  updates  only  the
-           non-color  attributes, first removing those that may have come from
-           the current background, and then adding  attributes  from  the  new
+       o   If the cell uses color, and its background  color  does  not  match
+           that  of  the  current  window background, ncurses updates only the
+           non-color attributes, first removing those that may have come  from
+           the  current  background,  and  then adding attributes from the new
            background.
 
-       ncurses  treats  a  background  character  value of zero (0) as a blank
-       character.
+       If the new background's character is non-spacing (for example, if it is
+       a  control  character),  ncurses  retains   the   existing   background
+       character,  except  for  one  special case: ncurses treats a background
+       character code of zero (0) as a space.
 
        If the terminal does not support  color,  or  if  color  has  not  been
        initialized  with  start_color(3x),  ncurses ignores the new background
-       character's color attribute.
+       character's color pair selection.

          bkgdset, wbkgdset

          @@ -136,19 +141,21 @@

          getbkgd

          -       getbkgd obtains the given window's background character  and  attribute
-       combination.
+       getbkgd  returns  the  given window's background character, attributes,
+       and color pair as a chtype.

          RETURN VALUE

          -       Functions  returning  an int return OK on success.  bkgd returns ERR if
-       the library has not been initialized.  wbkgd and getbkgd return ERR  if
-       a WINDOW pointer argument is null.
-
        bkgdset and wbkgdset do not return a value.
 
-       getbkgd   returns   a   window's  background  character  and  attribute
-       combination.
+       Functions returning an int return ERR upon failure and OK upon success.
+       In ncurses, failure occurs if
+
+       o   the curses screen has not been initialized, or
+
+       o   win is NULL.
+
+       getbkgd's return value is as described above.

          NOTES

          @@ -159,37 +166,39 @@
 
        X/Open  Curses  mentions that the character part of the background must
        be a single-byte value.  ncurses, like SVr4 curses,  checks  to  ensure
-       that, and will reuse the old background character if the check fails.
+       that  it is, and retains the existing background character if the check
+       fails.

          PORTABILITY

          -       X/Open  Curses,  Issue  4 describes these functions.  It specifies that
-       bkgd, wbkgd, and getbkgd return ERR on failure  (in  the  case  of  the
-       last,  this  value  is  cast  to  chtype),  but  describes  no  failure
-       conditions.
+       X/Open Curses Issue 4 describes these  functions.   It  indicates  that
+       bkgd,  wbkgd,  and  getbkgd  return  ERR on failure (in the case of the
+       last, this value is cast to chtype), but specifies no error  conditions
+       for them.
 
-       The SVr4.0 manual says that bkgd and wbkgd may return  OK  "or  a  non-
-       negative  integer  if immedok is set", which refers to the return value
-       from wrefresh(3x), used to implement the  immediate  repainting.   SVr4
-       curses's  wrefresh  returns  the  number  of  characters written to the
-       screen during the refresh.  ncurses does not do that.
+       SVr4  documentation  says  that  bkgd  and  wbkgd  return OK "or a non-
+       negative integer if immedok() is set", referring to  the  return  value
+       from  wrefresh,  which in SVr4 returns a count of characters written to
+       the window if its immedok property is set; in ncurses, it does not.
 
        Neither X/Open  Curses  nor  the  SVr4  manual  pages  detail  how  the
-       rendition  of  characters  on  the  screen  updates  when bkgd or wbkgd
+       rendition  of  characters  in  the  window  updates  when bkgd or wbkgd
        changes the background character.  ncurses, like SVr4 curses, does  not
-       (in  its  non-"wide"  configuration)  store  the  background and window
-       attribute contributions to each character cell separately.
+       (in  its  non-wide-character  configuration)  store  the background and
+       window attribute contributions to each character cell separately.
+
+
+

          HISTORY

          +       SVr3.1 (1987) introduced these functions.

          SEE ALSO

          -       curs_bkgrnd(3x) describes the corresponding  functions  in  the  "wide"
+       curs_bkgrnd(3x) describes  the  corresponding  functions  in  the  wide
        configuration of ncurses.
 
        curses(3x), curs_addch(3x), curs_attr(3x)
 
-
-
-ncurses 6.5                       2024-04-20                     curs_bkgd(3x)
+ncurses 6.6                       2025-08-23                     curs_bkgd(3x)
          diff --git a/doc/html/man/curs_bkgrnd.3x.html b/doc/html/man/curs_bkgrnd.3x.html index a11a68c..b0a04b6 100644 --- a/doc/html/man/curs_bkgrnd.3x.html +++ b/doc/html/man/curs_bkgrnd.3x.html @@ -1,6 +1,6 @@ -curs_bkgrnd 3x 2024-04-20 ncurses 6.5 Library calls +curs_bkgrnd 3x 2025-08-23 ncurses 6.6 Library calls -

          curs_bkgrnd 3x 2024-04-20 ncurses 6.5 Library calls

          +

          curs_bkgrnd 3x 2025-08-23 ncurses 6.6 Library calls

           curs_bkgrnd(3x)                  Library calls                 curs_bkgrnd(3x)
 
 
-
-

          NAME

                  bkgrnd,   wbkgrnd,   bkgrndset,  wbkgrndset,  getbkgrnd,  wgetbkgrnd  -
        manipulate background of a curses window of wide characters
@@ -65,24 +63,29 @@

          DESCRIPTION

          -       The  background  of  a  curses  window   (in   the   library's   "wide"
-       configuration)  is  a  cchar_t  combining  a  set  of  attributes  (see
-       curs_attr(3x)) with a complex character called the blank character.
+       Every curses  window  has  a  background  character  property:  in  the
+       library's   wide  configuration,  it  is  a  curses  complex  character
+       (cchar_t) that combines  a  set  of  attributes  (and,  if  colors  are
+       enabled,  a color pair identifier) with a character code.  When erasing
+       (parts of)  a  window,  curses  replaces  the  erased  cells  with  the
+       background character.
 
-       The blank character is a spacing character that  populates  a  window's
-       character  cells  when  their  contents are erased without replacement.
-       The background's attributes are combined with all non-blank  characters
-       written  to  the  window,  as  with  the  wadd_wch(3x) and wins_wch(3x)
-       families of functions.
+       curses  also uses the background character when writing characters to a
+       populated window.
 
-       The blank character and  attributes  of  the  background  combine  with
-       characters  written  to  the window as described below.  The background
-       becomes a property of the character  and  moves  with  it  through  any
-       scrolling and insert/delete line/character operations.
+       o   The attribute part of the background character  combines  with  all
+           non-blank  character  cells  in  the  window,  as  populated by the
+           wadd_wch(3x) and wins_wch(3x) families of functions (and those that
+           call them).
 
-       To  the  extent possible on a given terminal, the attribute part of the
-       background is displayed as the graphic rendition of the  character  put
-       on the screen.
+       o   Both the character code and attributes of the background  character
+           combine with blank character cells in the window.
+
+       The  background character's set of attributes becomes a property of the
+       character cell and move with it through any scrolling and insert/delete
+       line/character operations.  To the  extent  possible  on  the  terminal
+       type, curses displays the attributes of the background character as the
+       graphic rendition of a character cell on the display.

          bkgrnd, wbkgrnd

          @@ -90,24 +93,24 @@
        specified window and then apply this setting to every character cell in
        that window.
 
-       o   The  rendition  of every character in the window changes to the new
+       o   The rendition of every character in the window changes to  the  new
            background rendition.
 
        o   Wherever the former background character appears, it changes to the
            new background character.
 
        ncurses  updates  the rendition of each character cell by comparing the
-       character, non-color attributes, and colors.  The  library  applies  to
-       following  procedure  to  each cell in the window, whether or not it is
-       blank.
+       character, non-color attributes, and color pair selection.  The library
+       applies to following procedure to each cell in the window,  whether  or
+       not it is blank.
 
-       o   ncurses first compares  the  cell's  character  to  the  previously
-           specified  blank  character;  if they match, ncurses writes the new
-           blank character to the cell.
+       o   ncurses  first  compares  the  cell's  character  to the previously
+           specified background character; if they match, ncurses  writes  the
+           new background character to the cell.
 
-       o   ncurses then checks if the cell uses color, that is, its color pair
-           value  is  nonzero.   If not, it simply replaces the attributes and
-           color  pair  in  the  cell  with  those  from  the  new  background
+       o   ncurses then checks whether the cell uses color; that is, its color
+           pair  value  is nonzero.  If not, it simply replaces the attributes
+           and color pair in the cell  with  those  from  the  new  background
            character.
 
        o   If  the  cell  uses color, and its background color matches that of
@@ -122,12 +125,13 @@
            the current background, and then adding  attributes  from  the  new
            background.
 
-       ncurses  treats  a  background  character  value of zero (0) as a blank
-       character.
+       If  the  new  background's character is non-spacing, ncurses reuses the
+       old background character, except for one special case: ncurses treats a
+       background character code of zero (0) as a space.
 
        If the terminal does not support  color,  or  if  color  has  not  been
        initialized  with  start_color(3x),  ncurses ignores the new background
-       character's color attribute.
+       character's color pair selection.

          bkgrndset, wbkgrndset

          @@ -137,47 +141,53 @@

          getbkgrnd, wgetbkgrnd

          -       The getbkgrnd and wgetbkgrnd functions obtain the background  character
-       and  attribute  pair of stdscr or the specified window and store it via
-       the wch pointer.
+       getbkgrnd and wgetbkgrnd respectively  obtain  stdscr's  or  the  given
+       window's background character, attributes, and color pair, and store it
+       in their wch argument.

          RETURN VALUE

                  bkgrndset and wbkgrndset do not return a value.
 
-       The other functions return ERR upon failure and OK  upon  success.   In
-       ncurses, failure occurs if
+       Functions returning an int return ERR upon failure and OK upon success.
+       In ncurses, failure occurs if
 
-       o   a WINDOW pointer win is null, or
+       o   the curses screen has not been initialized,
 
-       o   a cchar_t pointer wch is null.
+       o   win is NULL, or
+
+       o   wch is NULL.

          NOTES

                  bkgrnd, bkgrndset, and getbkgrnd may be implemented as macros.
 
-       Unlike  their  counterparts in the non-"wide" configuration of ncurses,
-       getbkgrnd and wgetbkgrnd supply the background character and  attribute
-       in a modifiable cchar_t parameter, not as the return value.
+       Unlike  their  counterparts  in the non-wide-character configuration of
+       ncurses, getbkgrnd and wgetbkgrnd store the background character  in  a
+       modifiable  cchar_t  parameter,  rather than supplying it as the return
+       value.

          PORTABILITY

          -       X/Open  Curses,  Issue  4  describes  these functions.  It specifies no
-       error conditions for them.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
        X/Open Curses does not provide details of how the rendition is updated.
-       This implementation follows the approach used in SVr4 curses.
+       ncurses follows the approach used in SVr4 curses's  non-wide  functions
+       for manipulating the window background.
+
+
+

          HISTORY

          +       X/Open Curses Issue 4 (1995) initially specified these functions.

          SEE ALSO

          -       curs_bkgd(3x)  describes  the corresponding functions in the non-"wide"
-       configuration of ncurses.
+       curs_bkgd(3x)  describes  the  corresponding functions in the non-wide-
+       character configuration of ncurses.
 
        curses(3x), curs_add_wch(3x), curs_attr(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_bkgrnd(3x)
+ncurses 6.6                       2025-08-23                   curs_bkgrnd(3x)
          diff --git a/doc/html/man/curs_border.3x.html b/doc/html/man/curs_border.3x.html index d310dad..ef90c8e 100644 --- a/doc/html/man/curs_border.3x.html +++ b/doc/html/man/curs_border.3x.html @@ -1,6 +1,6 @@ -curs_border 3x 2024-04-20 ncurses 6.5 Library calls +curs_border 3x 2025-10-20 ncurses 6.6 Library calls -

          curs_border 3x 2024-04-20 ncurses 6.5 Library calls

          +

          curs_border 3x 2025-10-20 ncurses 6.6 Library calls

           curs_border(3x)                  Library calls                 curs_border(3x)
 
 
-
-

          NAME

                  border,  wborder, box, hline, whline, vline, wvline, mvhline, mvwhline,
        mvvline, mvwvline - draw borders  and  lines  in  a  curses  window  of
@@ -56,29 +54,28 @@
        #include <curses.h>
 
        int border(chtype ls, chtype rs, chtype ts, chtype bs,
-                  chtype tl, chtype tr, chtype bl, chtype br);
+             chtype tl, chtype tr, chtype bl, chtype br);
        int wborder(WINDOW *win, chtype ls, chtype rs,
-                   chtype ts, chtype bs, chtype tl, chtype tr,
-                   chtype bl, chtype br);
+             chtype ts, chtype bs, chtype tl, chtype tr,
+             chtype bl, chtype br);
 
        int box(WINDOW *win, chtype verch, chtype horch);
 
        int hline(chtype ch, int n);
        int whline(WINDOW *win, chtype ch, int n);
-       int vline(chtype ch, int n);
-       int wvline(WINDOW *win, chtype ch, int n);
-
        int mvhline(int y, int x, chtype ch, int n);
        int mvwhline(WINDOW *win, int y, int x, chtype ch, int n);
+
+       int vline(chtype ch, int n);
+       int wvline(WINDOW *win, chtype ch, int n);
        int mvvline(int y, int x, chtype ch, int n);
        int mvwvline(WINDOW *win, int y, int x, chtype ch, int n);

          DESCRIPTION

          -       The  border,  wborder and box routines draw a box around the edges of a
-       window.  Other than the window,  each  argument  is  a  character  with
-       attributes:
-
+       wborder  and  border draw a box at the edges of the specified window or
+       stdscr, respectively.  Each chtype argument corresponds to a  geometric
+       component of the border as follows:
               ls - left side,
               rs - right side,
               ts - top side,
@@ -88,60 +85,76 @@
               bl - bottom left-hand corner, and
               br - bottom right-hand corner.
 
-       If  any  of  these  arguments  is  zero, then the corresponding default
-       values (defined in curses.h) are used instead:
-
+       If  any chtype argument is 0, then curses uses forms-drawing characters
+       (see addch(3x)) in the following correspondence:
               ACS_VLINE,
               ACS_VLINE,
               ACS_HLINE,
               ACS_HLINE,
               ACS_ULCORNER,
               ACS_URCORNER,
-              ACS_LLCORNER,
+              ACS_LLCORNER, and
               ACS_LRCORNER.
 
-       box(win,  verch,  horch)  is  a  shorthand  for  the  following   call:
-       wborder(win, verch, verch, horch, horch, 0, 0, 0, 0).
+       box(win, verch, horch) is shorthand  for  "wborder(win,  verch,  verch,
+       horch, horch, 0, 0, 0, 0)".
 
-       The  hline  and whline functions draw a horizontal (left to right) line
-       using ch starting at the current cursor position in  the  window.   The
-       current  cursor  position  is  not  changed.   The  line  is  at most n
-       characters long, or as many as fit into the window.
-
-       The vline and wvline functions draw a vertical  (top  to  bottom)  line
-       using  ch  starting  at the current cursor position in the window.  The
-       current cursor position  is  not  changed.   The  line  is  at  most  n
-       characters long, or as many as fit into the window.
+       whline  draws  a horizontal line of ch from left to right, and wvline a
+       vertical one from top to bottom, stopping once n characters  have  been
+       drawn  or  upon  reaching  the boundary of win.  These functions do not
+       update the cursor position (beyond any motion directed  by  their  "mv"
+       variants).  ncurses(3x) describes the variants of these functions.

          RETURN VALUE

          -       All  routines return the integer OK.  The SVr4.0 manual says "or a non-
-       negative integer if immedok is set", but this appears to be an error.
+       These functions return OK on success and ERR on failure.
 
-       X/Open  Curses  does  not   specify   any   error   conditions.    This
-       implementation returns an error if the window pointer is null.
+       In ncurses,
 
-       Functions  prefixed with "mv" first perform cursor movement and fail if
+       o   these functions fail if the screen is not initialized; and
+
+       o   functions  taking  a  WINDOW pointer argument fail if win is a null
+           pointer.
+
+       Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

          NOTES

          -       The borders generated by these functions are inside  borders  (this  is
-       also true of SVr4 curses, though the fact is not documented).
+       Unusually,  there  is no wbox function; box behaves as one would expect
+       wbox to, accepting a WINDOW pointer argument.
 
-       Note that border and box may be macros.
+       border, box, hline, mvhline, mvwhline, vline, mvvline, and mvwvline may
+       be implemented as macros.
+
+       Borders drawn by these functions are interior borders.

          PORTABILITY

          -       These functions are described in X/Open Curses, Issue 4.
+       These functions are described in X/Open Curses Issue 4.   It  specifies
+       no error conditions for them.
+
+       SVr4  documentation  says  that  these  functions  return OK "or a non-
+       negative integer if immedok() is set", referring to  the  return  value
+       from  wrefresh,  which in SVr4 returns a count of characters written to
+       the window if its immedok property is set; in ncurses, it does not.
+
+       BSD curses drew boxes with horch in every character cell of the top and
+       bottom lines of the window, whereas SVr3.1 and  later  curses,  because
+       its box wrapped wborder, used the default corner characters.
+
+
+

          HISTORY

          +       4BSD (1980) introduced box, defining it as a function.
+
+       SVr3.1  (1987)  added  whline and wvline and their variants, as well as
+       border and wborder, redefining box as a macro wrapping the latter.

          SEE ALSO

                  curses(3x), curs_outopts(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_border(3x)
+ncurses 6.6                       2025-10-20                   curs_border(3x)
          diff --git a/doc/html/man/curs_border_set.3x.html b/doc/html/man/curs_border_set.3x.html index e687aa6..a75ac0c 100644 --- a/doc/html/man/curs_border_set.3x.html +++ b/doc/html/man/curs_border_set.3x.html @@ -1,6 +1,6 @@ -curs_border_set 3x 2024-04-20 ncurses 6.5 Library calls +curs_border_set 3x 2025-10-20 ncurses 6.6 Library calls -

          curs_border_set 3x 2024-04-20 ncurses 6.5 Library calls

          +

          curs_border_set 3x 2025-10-20 ncurses 6.6 Library calls

           curs_border_set(3x)              Library calls             curs_border_set(3x)
 
 
-
-

          NAME

                  border_set,  wborder_set,  box_set, hline_set, whline_set, mvhline_set,
        mvwhline_set, vline_set, wvline_set, mvvline_set, mvwvline_set  -  draw
@@ -55,53 +53,38 @@

          SYNOPSIS

                  #include <curses.h>
 
-       int border_set(
-          const cchar_t *ls, const cchar_t *rs,
-          const cchar_t *ts, const cchar_t *bs,
-          const cchar_t *tl, const cchar_t *tr,
-          const cchar_t *bl, const cchar_t *br);
-       int wborder_set(
-          WINDOW *win,
-          const cchar_t *ls, const cchar_t *rs,
-          const cchar_t *ts, const cchar_t *bs,
-          const cchar_t *tl, const cchar_t *tr,
-          const cchar_t *bl, const cchar_t *br);
-       int box_set(
-          WINDOW *win,
-          const cchar_t *verch,
-          const cchar_t *horch);
-       int hline_set(
-          const cchar_t *wch, int n);
-       int whline_set(
-          WINDOW *win,
-          const cchar_t *wch, int n);
-       int mvhline_set(
-          int y, int x,
-          const cchar_t *wch, int n);
-       int mvwhline_set(
-          WINDOW *win,
-          int y, int x,
-          const cchar_t *wch, int n);
-       int vline_set(
-          const cchar_t *wch, int n);
-       int wvline_set(
-          WINDOW *win,
-          const cchar_t *wch, int n);
-       int mvvline_set(
-          int y, int x,
-          const cchar_t *wch, int n);
-       int mvwvline_set(
-          WINDOW *win,
-          int y, int x,
-          const cchar_t *wch, int n);
+       int border_set(const cchar_t *ls, const cchar_t *rs,
+             const cchar_t *ts, const cchar_t *bs,
+             const cchar_t *tl, const cchar_t *tr,
+             const cchar_t *bl, const cchar_t *br);
+       int wborder_set(WINDOW *win,
+             const cchar_t *ls, const cchar_t *rs,
+             const cchar_t *ts, const cchar_t *bs,
+             const cchar_t *tl, const cchar_t *tr,
+             const cchar_t *bl, const cchar_t *br);
+
+       int box_set(WINDOW *win, const cchar_t *verch,
+             const cchar_t *horch);
+
+       int hline_set(const cchar_t *wch, int n);
+       int whline_set(WINDOW *win, const cchar_t *wch, int n);
+       int mvhline_set(int y, int x, const cchar_t *wch, int n);
+       int mvwhline_set(WINDOW *win, int y, int x,
+             const cchar_t *wch, int n);
+
+       int vline_set(const cchar_t *wch, int n);
+       int wvline_set(WINDOW *win, const cchar_t *wch, int n);
+       int mvvline_set(int y, int x, const cchar_t *wch, int n);
+       int mvwvline_set(WINDOW *win, int y, int x,
+             const cchar_t *wch, int n);

          DESCRIPTION

                  The border_set and wborder_set functions draw a border around the edges
-       of the current or specified window.  These functions do not change  the
+       of  the current or specified window.  These functions do not change the
        cursor position, and do not wrap.
 
-       Other  than  the  window,  each  argument  is  a complex character with
+       Other than the window,  each  argument  is  a  complex  character  with
        attributes:
               ls - left side,
               rs - right side,
@@ -112,7 +95,7 @@
               bl - bottom left-hand corner, and
               br - bottom right-hand corner.
 
-       If any of these arguments  is  zero,  then  the  corresponding  default
+       If  any  of  these  arguments  is  zero, then the corresponding default
        values (defined in curses.h) are used instead:
               WACS_VLINE,
               WACS_VLINE,
@@ -128,9 +111,9 @@
        wborder_set(win, verch, verch,
            horch, horch, NULL, NULL, NULL, NULL);
 
-       The  *line_set functions use wch to draw a line starting at the current
-       cursor position in the window.  The line is at most n  characters  long
-       or  as many as fit into the window.  The current cursor position is not
+       The *line_set functions use wch to draw a line starting at the  current
+       cursor  position  in the window.  The line is at most n characters long
+       or as many as fit into the window.  The current cursor position is  not
        changed.
 
        The hline_set, mvhline_set, mvwhline_set, and whline_set functions draw
@@ -144,27 +127,30 @@
        Upon successful completion, these functions return OK.  Otherwise, they
        return ERR.
 
-       Functions using a window parameter return an error if it is null.
+       Functions using a window parameter return ERR if it is null.
 
        Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.

          NOTES

          -       Note   that   border_set,    hline_set,    mvhline_set,    mvvline_set,
-       mvwhline_set, mvwvline_set, and vline_set may be macros.
+       border_set,   hline_set,   mvhline_set,   mvvline_set,    mvwhline_set,
+       mvwvline_set, and vline_set may be implemented as macros.

          PORTABILITY

          -       These functions are described in X/Open Curses, Issue 4.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+
+

          HISTORY

          +       X/Open Curses Issue 4 (1995) initially specified these functions.

          SEE ALSO

                  curses(3x), curs_add_wch(3x), curs_border(3x), curs_outopts(3x)
 
-
-
-ncurses 6.5                       2024-04-20               curs_border_set(3x)
+ncurses 6.6                       2025-10-20               curs_border_set(3x)
          diff --git a/doc/html/man/curs_clear.3x.html b/doc/html/man/curs_clear.3x.html index 058689b..d4a63c0 100644 --- a/doc/html/man/curs_clear.3x.html +++ b/doc/html/man/curs_clear.3x.html @@ -1,6 +1,6 @@ -curs_clear 3x 2024-04-20 ncurses 6.5 Library calls +curs_clear 3x 2025-01-18 ncurses 6.6 Library calls -

          curs_clear 3x 2024-04-20 ncurses 6.5 Library calls

          +

          curs_clear 3x 2025-01-18 ncurses 6.6 Library calls

           curs_clear(3x)                   Library calls                  curs_clear(3x)
 
 
-
-

          NAME

                  erase,  werase, clear, wclear, clrtobot, wclrtobot, clrtoeol, wclrtoeol
        - clear all or part of a curses window
@@ -78,8 +76,8 @@

          clear, wclear

          -       The clear and wclear routines are like erase and werase, but they  also
-       call  clearok(3x), so that the screen is cleared completely on the next
+       The  clear and wclear routines are like erase and werase, but they also
+       call clearok(3x), so that the screen is cleared completely on the  next
        call to wrefresh for that window and repainted from scratch.
 
 
@@ -98,34 +96,34 @@

          RETURN VALUE

                  All routines return the integer OK on success and ERR on failure.
 
-       X/Open defines no error conditions.  In this implementation,
+       In this implementation,
 
-       o   functions using a window pointer parameter return an error if it is
-           null
+       o   functions using a window pointer parameter return ERR if it is null
 
        o   wclrtoeol returns an error if the cursor position is about to wrap.

          NOTES

          -       Note  that  erase, werase, clear, wclear, clrtobot, and clrtoeol may be
-       macros.
+       erase, werase, clear, wclear, clrtobot, and clrtoeol may be implemented
+       as macros.

          PORTABILITY

          -       These functions are described in X/Open Curses, Issue 4.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       The SVr4.0 manual says that these functions could  return  "or  a  non-
-       negative  integer  if immedok is set", referring to the return-value of
-       wrefresh.  In that implementation, wrefresh would return a count of the
-       number of characters written to the terminal.
+       SVr4  documentation  says  that  these  functions  return OK "or a non-
+       negative integer if immedok() is set", referring to  the  return  value
+       from  wrefresh,  which in SVr4 returns a count of characters written to
+       the window if its immedok property is set; in ncurses, it does not.
 
-       Some  historic  curses implementations had, as an undocumented feature,
+       Some historic curses implementations had, as an  undocumented  feature,
        the  ability  to  do  the  equivalent  of  clearok(...,  1)  by  saying
        touchwin(stdscr) or clear(stdscr).  This will not work under ncurses.
 
-       This  implementation,  and  others  such  as  Solaris, sets the current
-       position to 0,0 after erasing via werase and wclear.  That fact is  not
-       documented   in   other   implementations,  and  may  not  be  true  of
+       This implementation, and others  such  as  Solaris,  sets  the  current
+       position  to 0,0 after erasing via werase and wclear.  That fact is not
+       documented  in  other  implementations,  and  may  not   be   true   of
        implementations which were not derived from SVr4 source.
 
        Not obvious from the description, most implementations clear the screen
@@ -136,9 +134,7 @@

          SEE ALSO

                  curses(3x), curs_outopts(3x), curs_refresh(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_clear(3x)
+ncurses 6.6                       2025-01-18                    curs_clear(3x)
            diff --git a/doc/html/man/curs_color.3x.html b/doc/html/man/curs_color.3x.html index d84a573..03d533d 100644 --- a/doc/html/man/curs_color.3x.html +++ b/doc/html/man/curs_color.3x.html @@ -1,6 +1,6 @@ -curs_color 3x 2024-04-20 ncurses 6.5 Library calls +curs_color 3x 2025-08-23 ncurses 6.6 Library calls -

            curs_color 3x 2024-04-20 ncurses 6.5 Library calls

            +

            curs_color 3x 2025-08-23 ncurses 6.6 Library calls

             curs_color(3x)                   Library calls                  curs_color(3x)
 
 
-
-

            NAME

                    start_color,   has_colors,   can_change_color,  init_pair,  init_color,
        init_extended_pair, init_extended_color,  color_content,  pair_content,
        extended_color_content,    extended_pair_content,    reset_color_pairs,
        COLOR_PAIR, PAIR_NUMBER, COLORS, COLOR_PAIRS,  COLOR_BLACK,  COLOR_RED,
        COLOR_GREEN,   COLOR_YELLOW,   COLOR_BLUE,  COLOR_MAGENTA,  COLOR_CYAN,
-       COLOR_WHITE - manipulate terminal colors with curses
+       COLOR_WHITE, A_COLOR - manipulate terminal colors with curses

            SYNOPSIS

            @@ -82,8 +80,18 @@
        /* extension */
        void reset_color_pairs(void);
 
+       /* macros */
        int COLOR_PAIR(int n);
        PAIR_NUMBER(int attr);
+       COLOR_BLACK
+       COLOR_RED
+       COLOR_GREEN
+       COLOR_YELLOW
+       COLOR_BLUE
+       COLOR_MAGENTA
+       COLOR_CYAN
+       COLOR_WHITE
+       A_COLOR

            DESCRIPTION

            @@ -99,39 +107,37 @@
 
        If  a  terminal  has  the  relevant  capability,   init_color   permits
        (re)definition of a color.  has_colors and can_change_color return TRUE
-       or FALSE, depending on whether the terminal has  color  capability  and
-       whether  the  programmer  can change the colors.  color_content permits
-       extraction of the red, green, and blue  components  of  an  initialized
-       color.   pair_content  permits  discovery  of  a  color  pair's current
+       or  FALSE,  depending  on whether the terminal has color capability and
+       whether the programmer can change the  colors.   color_content  permits
+       extraction  of  the  red,  green, and blue components of an initialized
+       color.  pair_content  permits  discovery  of  a  color  pair's  current
        definition.

            Rendering

            -       curses combines the following data to render a character cell.  Any  of
+       curses  combines the following data to render a character cell.  Any of
        them can include color information.
 
        o   curses character attributes, as from waddch(3x) or wadd_wch(3x)
 
        o   window attributes, as from wattrset(3x) or wattr_set(3x)
 
-       o   window  background  character  attributes,  as from wbkgdset(3x) or
+       o   window background character attributes,  as  from  wbkgdset(3x)  or
            wbkgrndset(3x)
 
-       Per-character and window attributes are usually set through a  function
-       parameter  containing  attributes  including  a color pair value.  Some
+       Per-character  and window attributes are usually set through a function
+       parameter containing attributes including a  color  pair  value.   Some
        functions,  such  as  wattr_set,  use  a  separate  color  pair  number
        parameter.
 
-       The  background  character  is  a special case: it includes a character
+       The background character is a special case:  it  includes  a  character
        code, just as if it were passed to waddch.
 
-       The curses library does the actual work of combining these color  pairs
+       The  curses library does the actual work of combining these color pairs
        in an internal function called from waddch:
 
        o   If the parameter passed to waddch is blank, and it uses the special
-           color pair 0,
-
-           o   curses next checks the window attribute.
+           color pair 0, curses next checks the window attribute.
 
            o   If the window attribute does not use color pair 0, curses  uses
                the color pair from the window attribute.
@@ -149,32 +155,27 @@

            CONSTANTS

            -       In <curses.h> the following macros are defined.  These are the standard
-       colors (ISO-6429).  curses also assumes that COLOR_BLACK is the default
-       background color for all terminals.
+       ISO 6429 and ECMA-48 define eight standard colors (also known as "ANSI"
+       colors).  curses.h defines object-like macros  COLOR_BLACK,  COLOR_RED,
+       COLOR_GREEN,  COLOR_YELLOW,  COLOR_BLUE, COLOR_MAGENTA, COLOR_CYAN, and
+       COLOR_WHITE  accordingly.   curses  assumes  that  COLOR_BLACK  is  the
+       default   background  color  for  all  terminals.   ncurses  offers  an
+       extension to override that assumption;  see  assume_default_colors(3x).
+       Some terminals support additional colors that lack standard names.
 
-             COLOR_BLACK
-             COLOR_RED
-             COLOR_GREEN
-             COLOR_YELLOW
-             COLOR_BLUE
-             COLOR_MAGENTA
-             COLOR_CYAN
-             COLOR_WHITE
-
-       Some terminals support more than the eight (8)  "ANSI"  colors.   There
-       are no standard names for those additional colors.
+       A_COLOR  is  a  bit  mask  that,  when  bitwise "and"-ed with a chtype,
+       extracts its color pair identifier.

            VARIABLES

            COLORS

            -       is  initialized  by  start_color  to  the  maximum number of colors the
+       is initialized by start_color to  the  maximum  number  of  colors  the
        terminal can support.

            COLOR_PAIRS

            -       is initialized by start_color to the maximum number of color pairs  the
+       is  initialized by start_color to the maximum number of color pairs the
        terminal can support.  Often, its value is the product COLORS x COLORS,
        but this is not always true.
 
@@ -197,14 +198,14 @@
            (respectively defining the maximum number of colors and color pairs
            the terminal can support).
 
-       o   It  initializes  the special color pair 0 to the default foreground
+       o   It initializes the special color pair 0 to the  default  foreground
            and background colors.  No other color pairs are initialized.
 
-       o   It restores the colors on the terminal to the values they had  when
+       o   It  restores the colors on the terminal to the values they had when
            the terminal was just turned on.
 
-       o   If  the  terminal supports the initc (initialize_color) capability,
-           start_color initializes its internal table  representing  the  red,
+       o   If the terminal supports the initc  (initialize_color)  capability,
+           start_color  initializes  its  internal table representing the red,
            green, and blue components of the color palette.
 
            The components depend on whether the terminal uses CGA (aka "ANSI")
@@ -212,55 +213,65 @@
            set).   The  table  is  initialized  first  for  eight basic colors
            (black, red, green, yellow, blue, magenta, cyan, and white),  using
            weights that depend upon the CGA/HLS choice.  For "ANSI" colors the
-           weights are 680 or 0 depending on whether  the  corresponding  red,
-           green,  or  blue component is used or not.  That permits using 1000
-           to represent bold/bright colors.  After the  initial  eight  colors
-           (if  the  terminal  supports more than eight colors) the components
-           are initialized using the same pattern, but with weights  of  1000.
+           weights  are  680  or 0 depending on whether the corresponding red,
+           green, or blue component is used or not.  That permits  using  1000
+           to  represent  bold/bright  colors.  After the initial eight colors
+           (if the terminal supports more than eight  colors)  the  components
+           are  initialized  using the same pattern, but with weights of 1000.
            SVr4 uses a similar scheme, but uses 1000 for the components of the
            initial eight colors.
 
            start_color does not attempt to set the terminal's color palette to
-           match  its  built-in  table.   An application may use init_color to
+           match its built-in table.  An application  may  use  init_color  to
            alter the internal table along with the terminal's color.
 
-       These limits apply to color values and  color  pairs.   Values  outside
+       These  limits  apply  to  color values and color pairs.  Values outside
        these limits are not valid, and may result in a runtime error:
 
-       o   COLORS   corresponds   to   the   terminal   database's  max_colors
+       o   COLORS  corresponds   to   the   terminal   database's   max_colors
            capability, (see terminfo(5)).
 
-       o   color values are expected  to  be  in  the  range  0  to  COLORS-1,
+       o   color  values  are  expected  to  be  in  the  range 0 to COLORS-1,
            inclusive (including 0 and COLORS-1).
 
-       o   a  special  color value -1 is used in certain extended functions to
+       o   a special color value -1 is used in certain extended  functions  to
            denote the default color (see use_default_colors(3x)).
 
-       o   COLOR_PAIRS  corresponds  to  the  terminal  database's   max_pairs
+       o   COLOR_PAIRS   corresponds  to  the  terminal  database's  max_pairs
            capability, (see terminfo(5)).
 
-       o   valid  color  pair  values  are  in  the  range 1 to COLOR_PAIRS-1,
+       o   valid color pair values  are  in  the  range  1  to  COLOR_PAIRS-1,
            inclusive.
 
        o   color pair 0 is special; it denotes "no color".
 
-           Color pair 0 is assumed to be  white  on  black,  but  is  actually
-           whatever  the  terminal implements before color is initialized.  It
+           Color  pair  0  is  assumed  to  be white on black, but is actually
+           whatever the terminal implements before color is  initialized.   It
            cannot be modified by the application.

            has_colors

            -       The has_colors routine requires no arguments.  It returns TRUE  if  the
-       terminal  can  manipulate  colors;  otherwise,  it returns FALSE.  This
-       routine  facilitates  writing   terminal-independent   programs.    For
-       example, a programmer can use it to decide whether to use color or some
-       other video attribute.
+       has_colors returns TRUE if the terminal supports colors and FALSE if it
+       does  not.   initscr(3x)  or  newterm(3x)  must  be  called  first, but
+       start_color need not be.   An  application  might  call  has_colors  to
+       decide  whether to use color or a video attribute like A_BOLD to render
+       text.
+
+       Color support in curses requires that  the  terminal  type  description
+       support  the  capabilities  max_colors (colors), max_pairs (pairs), and
+       any of
+
+       o   set_foreground (setf) and set_background (setb);
+
+       o   set_a_foreground (setaf) and set_a_background (setab); or
+
+       o   set_color_pair (scp).

            can_change_color

                    The can_change_color routine requires no arguments.  It returns TRUE if
-       the  terminal  supports colors and can change their definitions; other,
-       it  returns  FALSE.   This  routine   facilitates   writing   terminal-
+       the terminal supports colors and can change their  definitions;  other,
+       it   returns   FALSE.    This  routine  facilitates  writing  terminal-
        independent programs.
 
 
@@ -270,19 +281,19 @@
        foreground color number, and the background color number.  For portable
        applications:
 
-       o   The first argument must be a valid color pair  value.   If  default
-           colors  are  used  (see  use_default_colors(3x)) the upper limit is
-           adjusted to allow for extra pairs which  use  a  default  color  in
+       o   The  first  argument  must be a valid color pair value.  If default
+           colors are used (see use_default_colors(3x))  the  upper  limit  is
+           adjusted  to  allow  for  extra  pairs which use a default color in
            foreground and/or background.
 
        o   The second and third arguments must be valid color values.
 
-       If  the  color pair was previously initialized, the screen is refreshed
-       and all  occurrences  of  that  color  pair  are  changed  to  the  new
+       If the color pair was previously initialized, the screen  is  refreshed
+       and  all  occurrences  of  that  color  pair  are  changed  to  the new
        definition.
 
-       As  an  extension,  ncurses  allows  you  to  set  color pair 0 via the
-       assume_default_colors(3x) routine, or to specify  the  use  of  default
+       As an extension, ncurses allows  you  to  set  color  pair  0  via  the
+       assume_default_colors(3x)  routine,  or  to  specify the use of default
        colors (color number -1) if you first invoke the use_default_colors(3x)
        routine.
 
@@ -299,22 +310,22 @@
        four arguments: the number of the color to be changed followed by three
        RGB values (for the amounts of red, green, and blue components).
 
-       o   The  first argument must be a valid color value; default colors are
-           not allowed here.  (See the section Colors for  the  default  color
+       o   The first argument must be a valid color value; default colors  are
+           not  allowed  here.   (See the section Colors for the default color
            index.)
 
-       o   Each  of  the  last  three arguments must be a value in the range 0
+       o   Each of the last three arguments must be a value  in  the  range  0
            through 1000.
 
-       When init_color is used, all occurrences of that color  on  the  screen
+       When  init_color  is  used, all occurrences of that color on the screen
        immediately change to the new definition.

            init_extended_color

            -       Because  init_color  uses signed shorts for its parameters, that limits
-       color-values and their red, green, and  blue  components  to  32767  on
-       modern  hardware.   The extension init_extended_color uses ints for the
-       color value and for  setting  the  red,  green,  and  blue  components,
+       Because init_color uses signed shorts for its parameters,  that  limits
+       color-values  and  their  red,  green,  and blue components to 32767 on
+       modern hardware.  The extension init_extended_color uses ints  for  the
+       color  value  and  for  setting  the  red,  green, and blue components,
        allowing a larger number of colors to be supported.
 
 
@@ -337,13 +348,13 @@
        Because color_content uses  signed  shorts  for  its  parameters,  that
        limits  color-values and their red, green, and blue components to 32767
        on modern hardware.  The extension extended_color_content uses ints for
-       the  color value and for returning the red, green, and blue components,
+       the color value and for returning the red, green, and blue  components,
        allowing a larger number of colors to be supported.

            pair_content

            -       The pair_content routine allows programmers to find out what  colors  a
-       given  color  pair consists of.  It requires three arguments: the color
+       The  pair_content  routine allows programmers to find out what colors a
+       given color pair consists of.  It requires three arguments:  the  color
        pair number, and two addresses of shorts for storing the foreground and
        the background color numbers.
 
@@ -372,174 +383,177 @@

            COLOR_PAIR

                    COLOR_PAIR(n) converts a color pair number to an attribute.  Attributes
-       can hold color pairs in the range 0 to 255.  If you need a  color  pair
-       larger  than  that, you must use functions such as attr_set (which pass
-       the color  pair  as  a  separate  parameter)  rather  than  the  legacy
+       can  hold  color pairs in the range 0 to 255.  If you need a color pair
+       larger than that, you must use functions such as attr_set  (which  pass
+       the  color  pair  as  a  separate  parameter)  rather  than  the legacy
        functions such as attrset.

            PAIR_NUMBER

            -       PAIR_NUMBER(attr)   extracts   the  color  information  from  its  attr
-       parameter and returns it as a color pair  number;  it  is  the  inverse
+       PAIR_NUMBER(attr)  extracts  the  color  information  from   its   attr
+       parameter  and  returns  it  as  a color pair number; it is the inverse
        operation of COLOR_PAIR.

            RETURN VALUE

            -       The routines can_change_color and has_colors return TRUE or FALSE.
+       can_change_color and  has_colors  return  TRUE  or  FALSE.   The  other
+       functions return OK on success and ERR on failure.
 
-       All  other routines return the integer ERR upon failure and an OK (SVr4
-       specifies only "an integer  value  other  than  ERR")  upon  successful
-       completion.
+       In   ncurses,  functions  returning  an  int  recognize  several  error
+       conditions.
 
-       X/Open  defines  no  error  conditions.   SVr4 does document some error
-       conditions which apply in general:
+       o   All return  ERR  if  the  screen  has  not  been  initialized;  see
+           initscr(3x) or newterm(3x).
 
-       o   This implementation will return ERR on attempts to use color values
-           outside  the  range  0  to  COLORS-1 (except for the default colors
-           extension),  or  use  color  pairs   outside   the   range   0   to
-           COLOR_PAIRS-1.
+       o   All  except  start_color  return  ERR  if  start_color has not been
+           called, or itself returned ERR.
 
-           Color values used in init_color must be in the range 0 to 1000.
+       o   start_color returns ERR if it cannot allocate memory for its  color
+           pair table.
 
-           An  error  is  returned  from all functions if the terminal has not
-           been initialized.
+       o   init_color  returns  ERR  if  the  terminal  type  does not support
+           assignable color values; that is, if the  initialize_color  (initc)
+           capability is absent from its description.
 
-           An error is returned from secondary functions such as init_pair  if
-           start_color was not called.
+       o   init_color  returns  ERR if any of its r, g, b arguments is outside
+           the range 0-1000 inclusive.
 
-       o   SVr4   does  much  the  same,  except  that  it  returns  ERR  from
-           pair_content if the pair was not initialized using  init_pairs  and
-           it  returns ERR from color_content if the terminal does not support
-           changing colors.
+       o   init_pair,  init_color,  init_extended_pair,   init_extended_color,
+           color_content,     pair_content,     extended_color_content,    and
+           extended_pair_content return ERR on attempts to use
 
-           This implementation does not return ERR for either case.
+           o   color identifiers outside the range 0-COLORS-1  inclusive,  the
+               default colors extension notwithstanding, or
 
-       Specific functions make additional checks:
-
-          init_color
-               returns an error if the terminal does not support this feature,
-               e.g.,  if  the  initialize_color  capability is absent from the
-               terminal description.
-
-          start_color
-               returns an error if the color table cannot be allocated.
+           o   color   pair  identifiers  outside  the  range  0-COLOR_PAIRS-1
+               inclusive.

            NOTES

            -       In the ncurses implementation, there is  a  separate  color  activation
-       flag,  color  palette,  color  pairs  table,  and associated COLORS and
-       COLOR_PAIRS counts for  each  screen;  the  start_color  function  only
-       affects  the  current  screen.   The  SVr4/XSI  interface is not really
-       designed with this in mind, and historical implementations  may  use  a
-       single shared color palette.
+       In ncurses, init_pair accepts negative foreground and background  color
+       arguments  to  support  its  use_default_colors(3x) extension, but only
+       after the latter function has been called.
 
-       Setting  an  implicit  background  color  via a color pair affects only
-       character cells that a character write  operation  explicitly  touches.
-       To  change the background color used when parts of a window are blanked
+       The assumption that COLOR_BLACK is the  terminal's  default  background
+       color  can  be  overridden  using  ncurses's  assume_default_colors(3x)
+       extension.
+
+       In ncurses, each pointer passed to color_content and  pair_content  can
+       be  null,  in  which  case  the  library  ignores  it,  permitting  the
+       application to disregard unnecessary information.
+
+       In ncurses, each screen has a color  activation  flag,  color  palette,
+       color  pair  table,  and  associated  COLORS  and  COLOR_PAIRS  values;
+       start_color affects only the  current  screen.   The  SVr4  and  X/Open
+       Curses  interface was not really designed with this in mind; historical
+       implementations may use a single shared color palette.
+
+       Setting an implicit background color via  a  color  pair  affects  only
+       character  cells  that  a character write operation explicitly touches.
+       To change the background color used when parts of a window are  blanked
        by erasing or scrolling operations, see curs_bkgd(3x).
 
-       Several caveats apply on older x86 machines  (e.g.,  i386,  i486)  with
-       VGA-compatible graphics:
+       Several  caveats  apply  to IBM PC-compatible machines of the 80486 era
+       and earlier with CGA/EGA/VGA video.
 
-       o   COLOR_YELLOW  is  actually  brown.  To get yellow, use COLOR_YELLOW
-           combined with the A_BOLD attribute.
+       o   COLOR_YELLOW was frequently converted, in the analog domain,  to  a
+           shade  of brown if the intensity bit was not set.  To get yellow on
+           such devices,  one  would  combine  COLOR_YELLOW  with  the  A_BOLD
+           attribute.
 
-       o   The A_BLINK attribute should in theory cause the background  to  go
-           bright.  This often fails to work, and even some cards for which it
-           mostly works (such as the Paradise and compatibles)  do  the  wrong
-           thing  when  you try to set a bright "yellow" background (you get a
-           blinking yellow foreground instead).
+       o   The  A_BLINK attribute should in theory make the background bright.
+           This often fails to work, and even VGA  controllers  for  which  it
+           mostly  works,  such as those from Paradise and compatibles, do the
+           wrong thing when you try to set a bright "yellow" background -- you
+           get a blinking yellow foreground instead.
 
-       o   Color RGB values are not settable.
+       o   Color RGB values are not configurable on  these  devices  (in  text
+           mode).

            EXTENSIONS

            -       The functions marked as extensions were designed for  ncurses(3x),  and
-       are  not  found  in  SVr4  curses, 4.4BSD curses, or any other previous
-       curses implementation.
+       The  functions  marked as extensions originated in ncurses, and are not
+       found in SVr4 curses, 4.4BSD  curses,  or  any  other  previous  curses
+       implementation.

            PORTABILITY

                    Applications employing ncurses extensions should condition their use on
        the visibility of the NCURSES_VERSION preprocessor macro.
 
-       This  implementation  satisfies  X/Open  Curses's  minimum maximums for
-       COLORS and COLOR_PAIRS.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       The  init_pair  routine  accepts  negative  values  of  foreground  and
-       background  color  to support the use_default_colors(3x) extension, but
-       only if that routine has been first invoked.
-
-       The assumption that COLOR_BLACK is the default background color for all
-       terminals   can   be   modified   using  the  assume_default_colors(3x)
-       extension.
-
-       This implementation checks the pointers, e.g., for the values  returned
-       by  color_content  and  pair_content,  and will treat those as optional
-       parameters when null.
+       ncurses  satisfies  X/Open  Curses's  minimum  maximums  for COLORS and
+       COLOR_PAIRS.
 
        X/Open Curses does not specify a limit for the  number  of  colors  and
-       color pairs which a terminal can support.  However, in its use of short
-       for the parameters, it carries over SVr4's  implementation  detail  for
-       the compiled terminfo database, which uses signed 16-bit numbers.  This
-       implementation provides extended versions of those functions which  use
-       short  parameters, allowing applications to use larger color- and pair-
-       numbers.
+       color pairs which a terminal can support.  However, in its use of short
+       for  the  parameters,  it carries over SVr4's implementation detail for
+       the compiled terminfo  database,  which  uses  signed  16-bit  numbers.
+       ncurses  provides  extended  versions  of  the  functions  using  short
+       parameters,  allowing  applications  to  use  larger  color  and   pair
+       identifiers.
 
-       The reset_color_pairs function is an extension of ncurses.
+       SVr4  curses returns ERR from pair_content if its pair argument was not
+       initialized using init_pairs, and from color_content  if  the  terminal
+       does not support changing colors.  ncurses does neither.

            HISTORY

            -       SVr3.2 introduced color support to curses in 1987.
+       SVr3.2  (1987)  introduced  color  support  to  curses  with all of the
+       symbols in the synopsis above except those marked  as  extensions.   It
+       reserved color pair 0 as the terminal's initial, "uncolored" state, and
+       limited  the  number  of  possible color pairs to 64, because the color
+       pair datum was encoded in six bits of a chtype.
 
-       SVr4 made internal changes, e.g., moving  the  storage  for  the  color
-       state  from  SP  (the  SCREEN  structure)  to  cur_term  (the  TERMINAL
-       structure), but provided the same set of library functions.
+       SVr4 made only internal changes, such as moving the  storage  of  color
+       state  from  the  SCREEN  structure  (pointed to by SP) to the TERMINAL
+       structure (pointed to by cur_term).
 
-       SVr4 curses limits the number of color pairs  to  64,  reserving  color
-       pair  zero  (0)  as the terminal's initial uncolored state.  This limit
-       arises because the color pair information is a bitfield in  the  chtype
-       data type (denoted by A_COLOR).
+       Other curses implementations impose different limits on the  number  of
+       colors and color pairs.
 
-       Other implementations of curses had different limits:
+       o   PCCurses  (1987-1990)  provided  for  only  8 colors (and therefore
+           required at most 8x8 = 64 color pairs).
 
-       o   PCCurses (1987-1990) provided for only eight (8) colors.
+       o   PDCurses  (1992-present)  inherited  the  8-color  limitation  from
+           PCCurses,  but  changed  this  to  256  in  version 2.5 (2001), and
+           widened its chtype from 16 to 32 bits.
 
-       o   PDCurses  (1992-present)  inherited  the  8-color  limitation  from
-           PCCurses, but changed this to 256 in version 2.5 (2001), along with
-           changing chtype from 16-bits to 32-bits.
+       o   X/Open  Curses  (1992-present)  specified  a  new  structure  type,
+           cchar_t,  to  store  the character code, attribute flags, and color
+           pair identifier, allowing an increased range of  color  pairs.   It
+           specifies  a  short  as  storing  identifiers  for colors and color
+           pairs, limiting portable values to 15  bits;  negative  values  are
+           invalid in System V.
 
-       o   X/Open Curses (1992-present) added a new structure cchar_t to store
-           the character, attributes and color pair values, allowing increased
-           range  of  color  pairs.   Both color pairs and color-values used a
-           signed short, limiting values to 15 bits.
+       o   ncurses  (1992-present),  in  its non-wide-character configuration,
+           uses 8 bits of chtype for the color pair identifier.
 
-       o   ncurses (1992-present)  uses  eight  bits  for  A_COLOR  in  chtype
-           values.
+           Version 5.3 (2002) offered a wide-character interface, but  encoded
+           the color pair identifier with attributes in the character type.
 
-           Version  5.3  provided  a wide-character interface (2002), but left
-           color pairs as part of the attributes-field.
+           Since  version  6 (2015), ncurses uses a separate int for the color
+           pair identifier in a cchar_t, introducing  extension  functions  to
+           manage  the  wider  type.   When a color pair value fits in 8 bits,
+           ncurses permits color pair data to be manipulated via the functions
+           taking chtype arguments, even  when  a  curses  window  uses  wide-
+           character cells.
 
-           Since version 6 (2015), ncurses uses a separate int for color pairs
-           in the cchar_t values.  When those color pair values fit in 8 bits,
-           ncurses allows color pairs to  be  manipulated  via  the  functions
-           using chtype values.
-
-       o   NetBSD  curses  used  6  bits  from  2000  (when  colors were first
-           supported) until 2004.  At that point, NetBSD  changed  to  use  10
-           bits.   As  of  2021,  that size is unchanged.  Like ncurses before
-           version 6, the NetBSD color  pair  information  is  stored  in  the
-           attributes  field of cchar_t, limiting the number of color pairs by
-           the size of the bitfield.
+       o   NetBSD  curses  used 6 bits for the color pair identifier from 2000
+           (when it first added color support) until  2004.   At  that  point,
+           NetBSD  widened  the  color  pair  identifier to use 9 bits.  As of
+           2025, that size is unchanged.  Like ncurses before version  6,  the
+           NetBSD  color  pair  datum  is  stored  in  the attributes field of
+           cchar_t, limiting the number of color pairs.

            SEE ALSO

                    curses(3x),   curs_attr(3x),   curs_initscr(3x),    curs_variables(3x),
        default_colors(3x)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_color(3x)
+ncurses 6.6                       2025-08-23                    curs_color(3x)
              diff --git a/doc/html/man/curs_delch.3x.html b/doc/html/man/curs_delch.3x.html index ca638df..7e26882 100644 --- a/doc/html/man/curs_delch.3x.html +++ b/doc/html/man/curs_delch.3x.html @@ -1,6 +1,6 @@ -curs_delch 3x 2024-04-20 ncurses 6.5 Library calls +curs_delch 3x 2025-04-05 ncurses 6.6 Library calls -

              curs_delch 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_delch 3x 2025-04-05 ncurses 6.6 Library calls

               curs_delch(3x)                   Library calls                  curs_delch(3x)
 
 
-
-

              NAME

                      delch,  wdelch,  mvdelch,  mvwdelch  - delete a character from a curses
        window
@@ -55,51 +53,58 @@
        #include <curses.h>
 
        int delch(void);
-       int wdelch(WINDOW *win);
+       int wdelch(WINDOW * win);
        int mvdelch(int y, int x);
-       int mvwdelch(WINDOW *win, int y, int x);
+       int mvwdelch(WINDOW * win, int y, int x);

              DESCRIPTION

              -       wdelch  deletes  the  character  at  the  cursor   position   in   win.
-       ncurses(3x) describes the variants of this function.
-
-       wdelch moves all characters to the right of the cursor on the same line
-       to the left one position and replaces the  contents  of  the  rightmost
-       position  on  the  line with the window's blank character; see bkgd(3x)
-       (wide-character API users may consult bkgrnd(3x) instead).  The  cursor
-       position does not change (after moving to (y, x), if specified).
+       wdelch deletes the character at the cursor position in win.   It  moves
+       all  characters to the right of the cursor on the same line to the left
+       one position and replaces the contents of the rightmost position on the
+       line with  the  window's  background  character;  see  bkgd(3x)  (wide-
+       character  API users: bkgrnd(3x)).  The cursor position does not change
+       (after moving to (y, x),  if  specified).   ncurses(3x)  describes  the
+       variants of this function.

              RETURN VALUE

                      These functions return OK on success and ERR on failure.
 
-       Functions taking a WINDOW pointer argument fail if the pointer is NULL.
+       In ncurses, these functions fail if
 
-       Functions  prefixed with "mv" first perform cursor movement and fail if
+       o   the curses screen has not been initialized, or
+
+       o   (for  functions  taking  a  WINDOW  pointer argument) win is a null
+           pointer.
+
+       Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

              NOTES

                      delch, mvdelch, and mvwdelch may be implemented as macros.
 
-       A terminal's delete_character  (dch1)  capability  is  not  necessarily
+       A  terminal's  delete_character  (dch1)  capability  is not necessarily
        employed.

              PORTABILITY

              -       X/Open Curses, Issue 4 describes these functions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       SVr4  curses  describes  a  successful return value only as "an integer
-       value other than ERR".
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+
+
+

              HISTORY

              +       SVr2 (1984) introduced wdelch.

              SEE ALSO

                      curses(3x)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_delch(3x)
+ncurses 6.6                       2025-04-05                    curs_delch(3x)
              diff --git a/doc/html/man/curs_deleteln.3x.html b/doc/html/man/curs_deleteln.3x.html index c9c5001..58b20ea 100644 --- a/doc/html/man/curs_deleteln.3x.html +++ b/doc/html/man/curs_deleteln.3x.html @@ -1,6 +1,6 @@ -curs_deleteln 3x 2024-04-20 ncurses 6.5 Library calls +curs_deleteln 3x 2025-07-05 ncurses 6.6 Library calls -

              curs_deleteln 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_deleteln 3x 2025-07-05 ncurses 6.6 Library calls

               curs_deleteln(3x)                Library calls               curs_deleteln(3x)
 
 
-
-

              NAME

              -       deleteln,  wdeleteln, insdelln, winsdelln, insertln, winsertln - delete
+       deleteln,  wdeleteln, insertln, winsertln, insdelln, winsdelln - delete
        or insert lines in a curses window
 
 
@@ -55,61 +53,63 @@
        #include <curses.h>
 
        int deleteln(void);
-       int wdeleteln(WINDOW *win);
-
-       int insdelln(int n);
-       int winsdelln(WINDOW *win, int n);
+       int wdeleteln(WINDOW * win);
 
        int insertln(void);
-       int winsertln(WINDOW *win);
+       int winsertln(WINDOW * win);
+
+       int insdelln(int n);
+       int winsdelln(WINDOW * win, int n);

              DESCRIPTION

              -       The deleteln and wdeleteln routines delete the line under the cursor in
-       the  window;  all  lines  below the current line are moved up one line.
-       The bottom line of the window is cleared.  The cursor position does not
-       change.
+       wdeleteln deletes the line at the cursor in win;  all  lines  below  it
+       move  up  one  line.  curses then fills the bottom line of win with the
+       background character configured  by  wbkgdset(3x)  (wide-character  API
+       users: wbkgrndset(3x)).  The cursor position does not change.
 
-       The  insdelln  and  winsdelln  routines, for positive n, insert n lines
-       into the specified window above the current line.  The n  bottom  lines
-       are  lost.  For negative n, delete n lines (starting with the one under
-       the cursor), and move the remaining lines up.  The bottom n  lines  are
-       cleared.  The current cursor position remains the same.
+       winsertln inserts a new, empty line of characters above the line at the
+       cursor in win, shifting the existing lines down by one.  The content of
+       the  window's  bottom  line is lost; curses fills the new line with the
+       background character.  The cursor position does not change.
 
-       The  insertln  and  winsertln  routines  insert  a blank line above the
-       current line and the bottom line is lost.
+       winsdelln inserts or deletes  n lines  in  win  as  n  is  positive  or
+       negative,  respectively,  as  if  by  repeatedly  calling  winsertln or
+       wdeleteln.  winsdelln(..., 0) performs no operation.

              RETURN VALUE

              -       These routines return the integer ERR upon  failure  and  an  OK  (SVr4
-       specifies  only  "an  integer  value  other  than ERR") upon successful
-       completion.
+       These functions return OK on success and ERR on failure.
 
-       X/Open defines no error conditions.  In  this  implementation,  if  the
-       window parameter is null, an error is returned.
+       In ncurses, they fail if win is NULL.

              NOTES

              -       Note that all but winsdelln may be macros.
+       All of these functions except winsdelln may be implemented as macros.
 
-       These  routines do not require a hardware line delete or insert feature
-       in  the  terminal.   In  fact,  they  will  not   use   hardware   line
-       delete/insert  unless  idlok(...,  TRUE)  has  been  set on the current
-       window.
+       These functions do not require the terminal to  possess  hardware  line
+       deletion  or  insertion  capabilities.   Even  if available, by default
+       curses does not use them; see idlok(3x).

              PORTABILITY

              -       These functions are described in X/Open Curses, Issue 4.  The  standard
-       specifies  that  they  return  ERR  on  failure, but specifies no error
-       conditions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+
+
+

              HISTORY

              +       4BSD (1980) introduced deleteln, wdeleteln, insertln, and winsertln.
+
+       SVr3.1 (1987) added insdelln and winsdelln.

              SEE ALSO

                      curses(3x)
 
-
-
-ncurses 6.5                       2024-04-20                 curs_deleteln(3x)
+ncurses 6.6                       2025-07-05                 curs_deleteln(3x)
              diff --git a/doc/html/man/curs_extend.3x.html b/doc/html/man/curs_extend.3x.html index e8b3a46..9c163a0 100644 --- a/doc/html/man/curs_extend.3x.html +++ b/doc/html/man/curs_extend.3x.html @@ -1,6 +1,6 @@ -curs_extend 3x 2024-03-16 ncurses 6.5 Library calls +curs_extend 3x 2025-11-11 ncurses 6.6 Library calls -

              curs_extend 3x 2024-03-16 ncurses 6.5 Library calls

              +

              curs_extend 3x 2025-11-11 ncurses 6.6 Library calls

               curs_extend(3x)                  Library calls                 curs_extend(3x)
 
 
-
-

              NAME

              -       curses_version, use_extended_names - miscellaneous curses extensions
+       curses_version, use_extended_names - miscellaneous ncurses extensions

              SYNOPSIS

                      #include <curses.h>
 
        const char * curses_version(void);
-       int use_extended_names(bool enable);
+       int use_extended_names(bool bf);

              DESCRIPTION

              -       These  functions  are extensions to the curses library which do not fit
-       easily into other categories.
+       These  ncurses  extensions to the curses library do not fit easily into
+       other functional categories.

              curses_version

              -       Use curses_version to get the version number, including patch level  of
-       the library, prefixed by "ncurses", e.g.,
-
-              ncurses 5.0.19991023
+       curses_version returns a pointer to a string containing  the  library's
+       name  and  version  number,  including  its  patch  level,  for example
+       "ncurses 6.5.20240720".

              use_extended_names

              -       The   use_extended_names   function   controls   whether   the  calling
-       application is able to use user-defined or nonstandard names which  may
-       be  compiled  into  the terminfo description, i.e., via the terminfo or
-       termcap interfaces.  Normally these names are available for use,  since
-       the essential decision is made by using the -x option of tic to compile
-       extended terminal definitions.  However you can disable this feature to
-       ensure compatibility with other implementations of curses.
+       use_extended_names configures  whether  the  library  recognizes  user-
+       defined  or  nonstandard terminfo capability names that may be compiled
+       into  terminal  type  descriptions   via   the   curs_terminfo(3x)   or
+       curs_termcap(3x)  interfaces.   Normally  these names are available for
+       use, since the essential decision is made through use  of  tic(1)'s  -x
+       option  to  include  such  extensions  in  terminal  type descriptions.
+       use_extended_names(FALSE)  prevents  ncurses  from  recognizing   these
+       capabilities  to  ensure  compatibility  with  other implementations of
+       curses.

              RETURN VALUE

              -       curses_version  returns a pointer to static memory; you should not free
-       this in your application.
+       curses_version returns a constant string.
 
-       use_extended_names returns the previous state,  allowing  you  to  save
-       this and restore it.
+       use_extended_names returns the previous state  of  extended  capability
+       name recognition, allowing you to save this property and restore it.
+
+
+

              NOTES

              +       The  pointer  returned  by  curses_version  corresponds  to  statically
+       allocated memory; do not attempt to free(3) it.

              EXTENSIONS

              -       These  functions  are ncurses(3x) extensions, and are not found in SVr4
-       curses, 4.4BSD curses, or any other previous curses implementation.
+       These functions are ncurses extensions,  and  are  not  found  in  SVr4
+       curses, 4.4BSD curses, or any other previous curses implementation.

              PORTABILITY

                      Applications employing ncurses extensions should condition their use on
        the visibility of the NCURSES_VERSION preprocessor macro.
 
+       NetBSD  9  added a curses_version function that intentionally returns a
+       string devoid of version information.
+

              AUTHORS

              -       Thomas Dickey.
+       Thomas Dickey

              SEE ALSO

              -       curs_getch(3x),    curs_mouse(3x),    curs_print(3x),    curs_util(3x),
-       default_colors(3x),    define_key(3x),     keybound(3x),     keyok(3x),
-       resizeterm(3x), wresize(3x)
+       ncurses offers several other extensions to the X/Open Curses API.
 
+       curs_getch(3x),   curs_inopts(3x),   curs_mouse(3x),    curs_print(3x),
+       curs_util(3x),    default_colors(3x),   define_key(3x),   keybound(3x),
+       keyok(3x), new_pair(3x), resizeterm(3x), wresize(3x)
 
-
-ncurses 6.5                       2024-03-16                   curs_extend(3x)
+ncurses 6.6                       2025-11-11                   curs_extend(3x)
                @@ -122,6 +128,7 @@ ncurses 6.5 2024-03-16 RETURN VALUE +
              • NOTES
              • EXTENSIONS
              • PORTABILITY
              • AUTHORS
                • diff --git a/doc/html/man/curs_get_wch.3x.html b/doc/html/man/curs_get_wch.3x.html index 291ef67..317e52e 100644 --- a/doc/html/man/curs_get_wch.3x.html +++ b/doc/html/man/curs_get_wch.3x.html @@ -1,6 +1,6 @@ -curs_get_wch 3x 2024-04-20 ncurses 6.5 Library calls +curs_get_wch 3x 2025-08-16 ncurses 6.6 Library calls -

                curs_get_wch 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_get_wch 3x 2025-08-16 ncurses 6.6 Library calls

                 curs_get_wch(3x)                 Library calls                curs_get_wch(3x)
 
 
-
-

                NAME

                        get_wch,  wget_wch,  mvget_wch,  mvwget_wch,  unget_wch  - get (or push
-       back) a wide character from curses terminal keyboard
+       back) a wide character from curses terminal keyboard buffer

                SYNOPSIS

                        #include <curses.h>
 
-       int get_wch(wint_t *wch);
-       int wget_wch(WINDOW *win, wint_t *wch);
-       int mvget_wch(int y, int x, wint_t *wch);
-       int mvwget_wch(WINDOW *win, int y, int x, wint_t *wch);
+       int get_wch(wint_t * wch);
+       int wget_wch(WINDOW * win, wint_t * wch);
+       int mvget_wch(int y, int x, wint_t * wch);
+       int mvwget_wch(WINDOW * win, int y, int x, wint_t * wch);
 
        int unget_wch(const wchar_t wc);
 
@@ -65,65 +63,80 @@

                DESCRIPTION

                Reading Characters

                -       wget_wch gathers a key stroke wch from the terminal keyboard associated
-       with  a  curses  window  win, returning OK if a wide character is read,
-       KEY_CODE_YES if a function key is read, and ERR  if  no  key  event  is
+       wget_wch gathers a key event from the terminal keyboard associated with
+       a curses window  win,  returning  OK  if  a  wide  character  is  read,
+       KEY_CODE_YES  if  a  function  key  is read, and ERR if no key event is
        available.  ncurses(3x) describes the variants of this function.
 
-       When  input  is pending, wget_wch stores an integer identifying the key
-       stroke in wch;  for  alphanumeric  and  punctuation  keys,  this  value
+       When input is pending, wget_wch stores an integer identifying  the  key
+       event  in  wch;  for  alphanumeric  and  punctuation  keys,  this value
        corresponds to the character encoding used by the terminal.  Use of the
-       control key as a modifier  often  results  in  a  distinct  code.   The
-       behavior  of  other  keys depends on whether win is in keypad mode; see
-       subsections "Keypad Mode" and "Predefined Key Codes" in getch(3x).
+       control key as a modifier,  by  holding  it  down  while  pressing  and
+       releasing  another key, often results in a distinct code.  The behavior
+       of other keys depends on whether win is in keypad mode; see subsections
+       "Keypad Mode" and "Key Codes" in getch(3x).
 
        If no input is pending, then if the no-delay flag is set in the  window
        (see  nodelay(3x)),  the  function returns ERR; otherwise, curses waits
-       until the terminal has input.  If  cbreak(3x)  has  been  called,  this
-       happens  after one character is read.  If nocbreak(3x) has been called,
-       it occurs when the next newline is read.   If  halfdelay(3x)  has  been
-       called,  curses waits until a character is typed or the specified delay
-       elapses.
+       until the terminal has  input.   If  cbreak(3x)  or  raw(3x)  has  been
+       called,  this  happens after one character is read.  If nocbreak(3x) or
+       noraw(3x) has been called, it occurs when the  next  newline  is  read.
+       (Because  the  terminal's  canonical or "cooked" mode is line-buffered,
+       multiple wget_wch calls may  then  be  necessary  to  empty  the  input
+       queue.)   If halfdelay(3x) has been called, curses waits until input is
+       available or the specified delay elapses.
 
        If echo(3x) has been called, and the window is not a pad, curses writes
-       wch to the window (at the cursor position) per the following rules.
+       the wide character from the input queue to the window  (at  the  cursor
+       position) per the following rules.
 
-       o   If  wch  matches  the  terminal's erase character, the cursor moves
-           leftward one  position  and  the  new  position  is  erased  as  if
-           wmove(3x)  and  then  wdelch(3x)  were  called.   When the window's
-           keypad mode is enabled (see below), KEY_LEFT and KEY_BACKSPACE  are
-           handled the same way.
+       o   If  the  wide character matches the terminal's erase character (see
+           erasewchar(3x)), the cursor moves leftward one position and the new
+           position is erased as if wmove(3x) and then wdelch(3x) were called.
+           When the window's keypad mode is enabled (see below), KEY_LEFT  and
+           KEY_BACKSPACE are handled the same way.
 
-       o   curses writes any other wch to the window, as with wecho_wchar(3x).
+       o   curses  writes  any  other  wide  character  to the window, as with
+           wecho_wchar(3x).
 
-       o   If  the  window  has  been moved or modified since the last call to
-           wrefresh(3x), curses calls wrefresh.
+       o   If the window win has been moved or modified since the last call to
+           wrefresh(3x), curses calls wrefresh on it.
 
-       If wch is a carriage return and nl(3x) has been called,  wgetch  stores
-       the the character code for newline (line feed) in wch instead.
+       If the wide character is a carriage return and nl(3x) has been  called,
+       wget_wch stores the wide character code for line feed in wch instead.

                Ungetting Characters

                -       unget_wch  places  wch  into the input queue to be returned by the next
-       call to wget_wch.  A single input queue serves all windows.
+       unget_wch  places  wc  into the input queue to be retrieved by the next
+       call to wget_wch.  A single input queue serves all  windows  associated
+       with the screen.

                RETURN VALUE

                -       wget_wch returns OK when it reads a  wide  character  and  KEY_CODE_YES
-       when it reads a function key code.  It returns ERR if
+       wget_wch  returns  OK when it reads a wide character, KEY_CODE_YES when
+       it reads a function key code, and ERR on failure.   wget_wch  fails  if
+       its  timeout  expires without any data arriving, which cannot happen if
+       nodelay(3x) is in effect on the window.
 
-       o   the WINDOW pointer is NULL, or
+       In ncurses, wget_wch also fails if
 
-       o   its timeout expires without any data arriving, or
+       o   the curses screen has not been initialized,
 
-       o   execution  was  interrupted by a signal, in which case errno is set
-           to EINTR.
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer, or
+
+       o   execution  was  interrupted by a signal, in which case errno is set
+           to EINTR.
 
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.
 
-       unget_wch returns OK on success and ERR if there is no more room in the
-       input queue.
+       unget_wch  returns  OK  on  success  and  ERR  on failure.  In ncurses,
+       unget_wch fails if
+
+       o   the curses screen has not been initialized, or
+
+       o   there is no more room in the input queue.

                NOTES

                @@ -132,15 +145,13 @@
        All of these functions except wget_wch and unget_wch may be implemented
        as macros.
 
-       Unlike  wgetch(3x),  wget_wch  and  its variants store the value of the
-       input character in an additional wch parameter instead  of  the  return
-       value.
+       Unlike wgetch(3x), wget_wch stores the value of the input character  in
+       an additional wch parameter instead of the return value.
 
-       Unlike   ungetch,  unget_wch  cannot  distinguish  function  key  codes
-       wget_wch  from  conventional  character  codes.   An  application   can
-       overcome this limitation by pushing function key codes with ungetch and
-       subsequently checking the return value of wget_wch  for  a  match  with
-       KEY_CODE_YES.
+       Unlike  ungetch,  unget_wch  cannot distinguish function key codes from
+       conventional  character  codes.   An  application  can  overcome   this
+       limitation  by pushing function key codes with ungetch and subsequently
+       checking the return value of wget_wch for a match with KEY_CODE_YES.

                EXTENSIONS

                @@ -151,23 +162,32 @@
        Applications employing ncurses extensions should condition their use on
        the visibility of the NCURSES_VERSION preprocessor macro.
 
-       X/Open Curses, Issue 4 describes  these  functions.   It  specifies  no
-       error conditions for them.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       See  the  "PORTABILITY" section of wgetch(3x) regarding the interaction
-       of wget_wch with signal handlers.
+       See the "PORTABILITY" section of wgetch(3x) regarding  the  interaction
+       of wget_wch with signal handlers.
+
+
+

                HISTORY

                +       X/Open  Curses Issue 4 (1995) initially specified these functions.  The
+       System V Interface Definition Version 4  of  the  same  year  specified
+       functions named wgetwch (with its variants) ungetwch.  These were later
+       additions  to  SVr4.x,  not  appearing  in the first SVr4 (1989).  They
+       differ from X/Open's later wget_wch and unget_wch in that wgetwch takes
+       no wch argument, but returns the (wide) key code as  an  int  (with  no
+       provision  for  distinguishing  a  character  code  from a function key
+       code); and ungetwch takes a non-const int argument.

                SEE ALSO

                        curs_getch(3x) describes comparable functions of the ncurses library in
        its non-wide-character configuration.
 
-       curses(3x),     curs_add_wch(3x),    curs_inopts(3x),    curs_move(3x),
+       curses(3x),    curs_add_wch(3x),    curs_inopts(3x),     curs_move(3x),
        curs_refresh(3x)
 
-
-
-ncurses 6.5                       2024-04-20                  curs_get_wch(3x)
+ncurses 6.6                       2025-08-16                  curs_get_wch(3x)
                diff --git a/doc/html/man/curs_get_wstr.3x.html b/doc/html/man/curs_get_wstr.3x.html index 9e18e64..e828cf3 100644 --- a/doc/html/man/curs_get_wstr.3x.html +++ b/doc/html/man/curs_get_wstr.3x.html @@ -1,6 +1,6 @@ -curs_get_wstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_get_wstr 3x 2025-10-20 ncurses 6.6 Library calls -

                curs_get_wstr 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_get_wstr 3x 2025-10-20 ncurses 6.6 Library calls

                 curs_get_wstr(3x)                Library calls               curs_get_wstr(3x)
 
 
-
-

                NAME

                        get_wstr,  getn_wstr,  wget_wstr,  wgetn_wstr, mvget_wstr, mvgetn_wstr,
-       mvwget_wstr, mvwgetn_wstr - get a wide-character string from  a  curses
+       mvwget_wstr, mvwgetn_wstr - read a wide-character string from a  curses
        terminal keyboard

                SYNOPSIS

                        #include <curses.h>
 
-       int get_wstr(wint_t *wstr);
-       int getn_wstr(wint_t *wstr, int n);
-       int wget_wstr(WINDOW *win, wint_t *wstr);
-       int wgetn_wstr(WINDOW *win, wint_t *wstr, int n);
+       int get_wstr(wint_t * wstr);
+       int wget_wstr(WINDOW * win, wint_t * wstr);
+       int mvget_wstr(int y, int x, wint_t * wstr);
+       int mvwget_wstr(WINDOW * win, int y, int x, wint_t * wstr);
 
-       int mvget_wstr(int y, int x, wint_t *wstr);
-       int mvgetn_wstr(int y, int x, wint_t *wstr, int n);
-       int mvwget_wstr(WINDOW *win, int y, int x, wint_t *wstr);
-       int mvwgetn_wstr(WINDOW *win, int y, int x, wint_t *wstr, int n);
+       int getn_wstr(wint_t * wstr, int n);
+       int wgetn_wstr(WINDOW * win, wint_t * wstr, int n);
+       int mvgetn_wstr(int y, int x, wint_t * wstr, int n);
+       int mvwgetn_wstr(WINDOW * win, int y, int x, wint_t * wstr, int n);

                DESCRIPTION

                -       The  function  wgetn_wstr  is  equivalent  to  a  series  of  calls  to
-       wget_wch(3x) until a newline or carriage return terminates the series:
+       wget_wstr  populates  a user-supplied wide-character string buffer wstr
+       by repeatedly calling wget_wch(3x) with the win argument until  a  line
+       feed or carriage return character is input.  The function
 
-       o   The terminating character is not included in the returned string.
+       o   does not copy the terminating character to wstr;
 
-       o   An end-of-file condition is represented  by  WEOF,  as  defined  in
-           <wchar.h>.
+       o   populates  wstr with WEOF (as defined in wchar.h) if an end-of-file
+           condition occurs on the input;
 
-       o   In  all  instances,  the  end of the string is terminated by a null
-           wchar_t.
+       o   always terminates the string with a null wide character (after  any
+           WEOF);
 
-       o   The function stores the result in the area pointed to by  the  wstr
-           parameter.
+       o   interprets  the  screen's  wide erase and wide kill characters (see
+           erasewchar(3x) and killwchar(3x));
 
-       o   The function reads at most n characters, thus preventing a possible
-           overflow of the input buffer.
+       o   recognizes function keys only if  the  screen's  keypad  option  is
+           enabled (see keypad(3x));
 
-           Any attempt to enter more characters (other  than  the  terminating
-           newline or carriage return) causes a beep.
+       o   treats the function keys KEY_LEFT and KEY_BACKSPACE the same as the
+           wide erase character; and
 
-           Function keys also cause a beep and are ignored.
+       o   discards  function  key inputs other than those treated as the wide
+           erase or wide kill characters, calling beep(3x).
 
-       The user's erase and kill characters are interpreted:
+       The wide erase character replaces the  character  at  the  end  of  the
+       buffer  with  a null wide character, while the wide kill character does
+       the same for the entire buffer.
 
-       o   The  erase  character (e.g., ^H) erases the character at the end of
-           the buffer, moving the cursor to the left.
+       If the screen's  echo  option  is  enabled  (see  echo(3x)),  wget_wstr
+       updates win with wadd_wch(3x).  Further,
 
-           If keypad mode is on for the window, KEY_LEFT and KEY_BACKSPACE are
-           both considered equivalent to the user's erase character.
+       o   the  wide  erase  character  and its function key synonyms move the
+           cursor to the left, and
 
-       o   The kill character (e.g., ^U) erases the entire buffer, leaving the
-           cursor at the beginning of the buffer.
+       o   the wide kill character returns the cursor to where it was  located
+           when wget_wstr was called.
 
-       Characters input are echoed only if echo  is  currently  on.   In  that
-       case,  backspace  is  echoed  as  deletion  of  the  previous character
-       (typically a left motion).
+       wgetn_wstr  is similar, but reads at most n wide characters, aiding the
+       application to avoid overrunning  the  buffer  to  which  wstr  points.
+       curses  ignores  an attempt to input more than n wide characters (other
+       than the terminating line feed or carriage return),  calling  beep(3x).
+       If  n is negative, wgetn_wstr reads up to LINE_MAX wide characters (see
+       sysconf(3)).
 
-       The getn_wstr, mvgetn_wstr, mvwgetn_wstr, and wgetn_wstr functions  are
-       identical  to  the  get_wstr,  mvget_wstr,  mvwget_wstr,  and wget_wstr
-       functions, respectively, except that the *n_* versions read at  most  n
-       characters,  letting  the  application  prevent  overflow  of the input
-       buffer.
+       ncurses(3x) describes the variants of these functions.

                RETURN VALUE

                -       All  of  these  functions  return  the  integer  OK   upon   successful
-       completion.  If unsuccessful, they return ERR.
+       These functions return OK on success and ERR on failure.
 
-       X/Open defines no error conditions.
+       In ncurses, these functions fail if
 
-       In this implementation, these functions return an error
+       o   the curses screen has not been initialized,
 
-       o   if the window pointer is null,
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer,
 
-       o   if its timeout expires without having any data, or
+       o   wstr is a null pointer, or
 
-       o   if the associated call to wget_wch failed.
+       o   an internal wget_wch(3x) call fails.
 
        Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.

                NOTES

                -       Any of these functions other than wgetn_wstr may be macros.
+       All of these functions except wgetn_wstr may be implemented as macros.
 
-       Using get_wstr, mvget_wstr, mvwget_wstr, or wget_wstr to  read  a  line
-       that  overflows  the array pointed to by wstr causes undefined results.
-       The  use  of  getn_wstr,  mvgetn_wstr,  mvwgetn_wstr,  or   wgetn_wstr,
-       respectively, is recommended.
+       Reading input that overruns  the  buffer  pointed  to  by  wstr  causes
+       undefined   results.    Use   the  n-infixed  functions,  and  allocate
+       sufficient storage for wstr -- at least n+1 times sizeof(wchar_t).
 
-       These  functions  cannot  return KEY_ values because there is no way to
-       distinguish a KEY_ value from a valid wchar_t value.
+       These functions cannot store a KEY_ value in wstr because there  is  no
+       way to distinguish it from a valid wchar_t value.
+
+       While  these  functions  conceptually  implement  a  series of calls to
+       wget_wch, they also temporarily change properties of the curses  screen
+       to  permit simple editing of the input buffer.  Each function saves the
+       screen's state, calls nl(3x), and,  if  the  screen  was  in  canonical
+       ("cooked")  mode,  cbreak(3x).  Before returning, it restores the saved
+       screen state.  Other implementations differ in detail, affecting  which
+       control   characters  they  can  accept  in  the  buffer;  see  section
+       "PORTABILITY" below.
+
+       Unlike getstr(3x) and related  functions  of  ncurses's  non-wide  API,
+       these functions do not return KEY_RESIZE if a SIGWINCH event interrupts
+       the function.
+
+
+

                EXTENSIONS

                +       getn_wstr,  wgetn_wstr,  mvgetn_wstr,  and  mvwgetn_wstr's  handing  of
+       negative n values is an ncurses extension.

                PORTABILITY

                -       These functions are described in The Single Unix Specification, Version
-       2.  No error conditions are defined.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
-       This  implementation  returns  ERR if the window pointer is null, or if
-       the lower-level wget_wch call returns an ERR.  In the latter  case,  an
-       ERR  return  without other data is treated as an end-of-file condition,
-       and the returned array contains a WEOF followed by a null wchar_t.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       X/Open curses documented these functions to pass an array of wchar_t in
-       1997, but that was an error because of this part of the description:
+       Issue 4 documented these functions as passing an array of wchar_t,  but
+       that  was  an  error,  conflicting  with  the following language in the
+       standard.
 
-              The effect of get_wstr is as though a series of calls to get_wch
-              were made, until a newline character, end-of-line character,  or
-              end-of-file character is processed.
+              The effect of get_wstr() is as  though  a  series  of  calls  to
+              get_wch()  were  made,  until  a  newline character, end-of-line
+              character, or end-of-file character is processed.
 
-       The  latter function get_wch can return a negative value, while wchar_t
-       is a unsigned type.  All of the vendors implement  this  using  wint_t,
-       following the standard.
+       get_wch can return a negative value (WEOF), but wchar_t is  a  unsigned
+       type.   All  of  the  vendors  implement  these functions using wint_t,
+       following the Issue 7 standard.
 
-       X/Open  Curses,  Issue  7  (2009)  is  unclear  regarding  whether  the
-       terminating null wchar_t value is counted in the  length  parameter  n.
-       X/Open  Curses,  Issue  7  revised  the  corresponding  description  of
-       wgetnstr  to  address  this  issue.   The  unrevised   description   of
-       wget_nwstr  can  be interpreted either way.  This implementation counts
-       the terminator in the length.
+       X/Open Curses Issue 7 is unclear  whether  the  terminating  null  wide
+       character  counts  toward  the  length  parameter  n.   A similar issue
+       affected  wgetnstr  in  Issue 4,  Version 2;   Issue 7   revised   that
+       function's   description   to  address  the  issue,  but  not  that  of
+       wget_nwstr, leaving it ambiguous.  ncurses counts the terminator in the
+       length.
 
        X/Open Curses does  not  specify  what  happens  if  the  length  n  is
        negative.
 
-       o   For  analogy  with  wgetnstr,  ncurses  6.2  uses a limit (based on
-           LINE_MAX).
+       o   For  consistency  with  wgetnstr, ncurses 6.2 uses a limit based on
+           LINE_MAX.
 
-       o   Some other implementations (such as Solaris xcurses) do  the  same,
-           while others (PDCurses) do not allow this.
+       o   Some other implementations (such as Solaris xcurses) do  the  same,
+           while others (PDCurses) do not permit a negative n.
 
-       o   NetBSD  7 curses imitates ncurses 6.1 in this regard, treating a -1
-           as an indefinite number of characters.
+       o   NetBSD 7  curses  imitates  ncurses  6.1  and  earlier,  treating a
+           negative n as an unbounded count of wide characters.
+
+       Implementations vary in their handling of input control characters.
+
+       o   While they may enable the screen's echo option, some do not take it
+           out of raw mode,  and  may  take  cbreak  mode  into  account  when
+           deciding  whether to handle echoing within wgetn_wstr or to rely on
+           it as a side effect of calling wget_wch.
+
+           Since 1995, ncurses has provided handlers for SIGINTR  and  SIGQUIT
+           events,  which  are typically generated at the keyboard with ^C and
+           ^\ respectively.  In cbreak mode, those handlers catch a signal and
+           stop  the  program,  whereas  other  implementations  write   those
+           characters into the buffer.
+
+       o   Starting  with ncurses 6.3 (2021), wgetn_wstr preserves raw mode if
+           the screen was already in that state, allowing  one  to  enter  the
+           characters  the  terminal  interprets  as interrupt and quit events
+           into the buffer, for consistency with SVr4 curses's wgetnstr.
+
+
+

                HISTORY

                +       X/Open Curses Issue 4 (1995) initially specified these functions.   The
+       System V  Interface  Definition  Version 4  of  the same year specified
+       functions named wgetwstr and wgetnwstr (and the usual variants).  These
+       were later additions to SVr4.x, not appearing in the first SVr4 (1989).
+       Except in name, their declarations did not differ from  X/Open's  later
+       wget_wstr  and wgetn_wstr until X/Open Curses Issue 7 (2009) eventually
+       changed the type of the buffer argument to a pointer to wint_t.

                SEE ALSO

                @@ -187,9 +232,7 @@
 
        curses(3x), curs_get_wch(3x)
 
-
-
-ncurses 6.5                       2024-04-20                 curs_get_wstr(3x)
+ncurses 6.6                       2025-10-20                 curs_get_wstr(3x)
                diff --git a/doc/html/man/curs_getcchar.3x.html b/doc/html/man/curs_getcchar.3x.html index c1edf28..26a5dff 100644 --- a/doc/html/man/curs_getcchar.3x.html +++ b/doc/html/man/curs_getcchar.3x.html @@ -1,6 +1,6 @@ -curs_getcchar 3x 2024-04-20 ncurses 6.5 Library calls +curs_getcchar 3x 2025-02-23 ncurses 6.6 Library calls -

                curs_getcchar 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_getcchar 3x 2025-02-23 ncurses 6.6 Library calls

                 curs_getcchar(3x)                Library calls               curs_getcchar(3x)
 
 
-
-

                NAME

                        getcchar,  setcchar  -  convert  between  a wide-character string and a
        curses complex character
@@ -54,149 +52,157 @@

                SYNOPSIS

                        #include <curses.h>
 
-       int getcchar(
-               const cchar_t *wch,
-               wchar_t *wc,
-               attr_t *attrs,
-               short *color_pair,
-               void *opts );
-
-       int setcchar(
-               cchar_t *wch,
-               const wchar_t *wc,
-               const attr_t attrs,
-               short color_pair,
-               const void *opts );
+       int getcchar(const cchar_t * wch, wchar_t * wc,
+             attr_t * attrs, short * pair, void * opts);
+       int setcchar(cchar_t * wch, const wchar_t * wc,
+             const attr_t attrs, short pair, const void * opts);

                DESCRIPTION

                +       The curses complex character data type  cchar_t  is  a  structure  type
+       comprising  a  wide-character  string, a set of attributes, and a color
+       pair identifier.  The cchar_t structure is opaque; do  not  attempt  to
+       access  its  members  directly.   The  library  provides  functions  to
+       manipulate this type.
+

                getcchar

                -       The getcchar function gets a wide-character string and rendition from a
-       cchar_t argument.  When wc is not a null pointer, the getcchar function
-       does the following:
+       getcchar destructures a cchar_t into its components.
 
-       o   Extracts information from a cchar_t value wch
+       If wc is not a null pointer, getcchar:
 
-       o   Stores the character attributes in the location pointed to by attrs
+       o   stores the wide-character string in the  curses  complex  character
+           wch into wc;
 
-       o   Stores the color pair in the location pointed to by color_pair
+       o   stores the attributes in attrs; and
 
-       o   Stores the wide-character string,  characters  referenced  by  wch,
-           into the array pointed to by wc.
+       o   stores the color pair identifier in pair.
 
-       When wc is a null pointer, the getcchar function does the following:
-
-       o   Obtains the number of wide characters pointed to by wch
-
-       o   Does not change the data referenced by attrs or color_pair
+       If wc is a null pointer, getcchar counts the wchar_t wide characters in
+       wch, returns that value, and leaves attrs and pair unchanged.

                setcchar

                -       The  setcchar  function  initializes  the location pointed to by wch by
-       using:
+       setcchar  constructs a curses complex character wch from the components
+       wc, attrs, and pair.  The wide-character string wch must be  terminated
+       with  a  null wide character L'\0' and must contain at most one spacing
+       character, which, if present, must be the first wide character  in  the
+       string.
 
-       o   The character attributes in attrs
+       Up   to   CCHARW_MAX - 1   non-spacing   characters   may  follow  (see
+       curs_variables(3x)).   ncurses  ignores  any   additional   non-spacing
+       characters.
 
-       o   The color pair in color_pair
-
-       o   The wide-character string pointed to by wc.   The  string  must  be
-           L'\0' terminated, contain at most one spacing character, which must
-           be the first.
-
-           Up to CCHARW_MAX-1 non-spacing characters may  follow.   Additional
-           non-spacing characters are ignored.
-
-           The string may contain a single control character instead.  In that
-           case, no non-spacing characters are allowed.
+       The  string  may  contain  a single control character instead.  In that
+       case, no non-spacing characters are allowed.

                RETURN VALUE

                -       When wc is  a  null  pointer,  getcchar  returns  the  number  of  wide
-       characters referenced by wch, including one for a trailing null.
+       If getcchar is passed a null pointer as its wc argument, it returns the
+       number of wide characters for a given wch that it would  store  in  wc,
+       counting  a  trailing null wide character.  If getcchar is not passed a
+       null pointer as its wc argument, it returns OK on success  and  ERR  on
+       failure.
 
-       When  wc  is  not  a  null pointer, getcchar returns OK upon successful
-       completion, and ERR otherwise.
+       In  ncurses,  getcchar  returns  ERR  if either attrs or pair is a null
+       pointer and wc is not.
 
-       Upon successful completion, setcchar returns OK.  Otherwise, it returns
-       ERR.
+       setcchar returns OK on success and ERR on failure.
+
+       In ncurses, setcchar returns ERR if
+
+       o   wch is a null pointer,
+
+       o   wc starts with a (wide) control character and  contains  any  other
+           wide characters, or
+
+       o   pair has a negative value.

                NOTES

                -       The wch argument may be a value generated by a call to setcchar or by a
-       function that has a cchar_t output argument.  If wch is constructed  by
-       any other means, the effect is unspecified.
+       wch may be a value stored by setcchar or another curses function with a
+       writable  cchar_t  argument.  If wch is constructed by any other means,
+       the library's behavior is unspecified.

                EXTENSIONS

                -       X/Open  Curses  documents the opts argument as reserved for future use,
-       saying that it must be null.  This implementation uses  that  parameter
-       in ABI 6 for the functions which have a color pair parameter to support
-       extended color pairs:
+       X/Open Curses documents the opts argument as reserved for  future  use,
+       saying  that it must be a null pointer.  The ncurses 6 ABI uses it with
+       functions that have a color pair parameter to  support  extended  color
+       pairs.
 
-       o   For  functions  which modify the color, e.g., setcchar, if opts  is
-           set it is treated as a pointer to int, and used to  set  the  color
-           pair instead of the short pair parameter.
+       o   In functions that assign colors, such as setcchar, if opts is not a
+           null pointer, ncurses treats it as a pointer to int, and interprets
+           it instead of the short pair parameter as a color pair identifier.
 
-       o   For functions which retrieve the color, e.g., getcchar, if opts  is
-           set it is treated as a pointer to int, and  used  to  retrieve  the
-           color pair as an int value,  in  addition  retrieving  it  via  the
-           standard pointer to short parameter.
+       o   In functions that retrieve colors, such as getcchar, if opts is not
+           a  null  pointer, ncurses treats it as a pointer to int, and stores
+           the retrieved color pair identifier there as well as in  the  short
+           pair   parameter   (which   may   therefore   undergo  a  narrowing
+           conversion).

                PORTABILITY

                -       The  CCHARW_MAX  symbol is specific to ncurses.  X/Open Curses does not
-       provide details for the layout of the cchar_t structure.  It tells what
-       data are stored in it:
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
-       o   a spacing character (wchar_t, i.e., 32-bits).
+       These functions are described in X/Open Curses Issue 4.   It  specifies
+       no error conditions for them.
 
-       o   non-spacing characters (again, wchar_t's).
+       X/Open  Curses  does  not  detail  the layout of the cchar_t structure,
+       describing only its minimal required contents:
 
-       o   attributes  (at  least  16 bits, inferred from the various ACS- and
-           WACS-flags).
+       o   a spacing wide character (wchar_t),
 
-       o   color pair (at least 16 bits,  inferred  from  the  unsigned  short
-           type).
+       o   at least five non-spacing wide characters (wchar_t; see below),
 
-       The non-spacing characters are optional, in the sense that zero or more
-       may be stored in a cchar_t.  XOpen/Curses specifies a limit:
+       o   attributes (at least 15 bits' worth, inferred  from  the  count  of
+           specified WA_ constants),
+
+       o   a  color pair identifier (at least 16 bits, inferred from the short
+           type used to encode it).
+
+       Non-spacing characters are optional, in the sense that zero or more may
+       be stored in a cchar_t.  XOpen/Curses specifies a limit:
 
            Implementations may limit the number of non-spacing characters that
-           can  be  associated with a spacing character, provided any limit is
+           can be associated with a spacing character, provided any  limit  is
            at least 5.
 
-       The Unix implementations at the time follow that limit:
+       Then-contemporary Unix implementations adhered to that limit.
 
-       o   AIX 4 and OSF1 4 use the same declaration with an array of  5  non-
-           spacing characters z and a single spacing character c.
+       o   AIX 4  and  OSF/1 4 used the same declaration with a single spacing
+           wide character c and an array of 5 non-spacing wide characters z.
 
-       o   HP-UX 10  uses  an  opaque  structure with 28 bytes, which is large
-           enough for the 6 wchar_t values.
+       o   HP-UX 10 used an opaque structure of 28 bytes, large enough  for  6
+           wchar_t values.
 
-       o   Solaris xpg4 curses uses a single array of 6 wchar_t values.
+       o   Solaris xcurses uses a single array of 6 wchar_t values.
 
-       This implementation's cchar_t was defined in 1995 using 5 for the total
-       of  spacing and non-spacing characters (CCHARW_MAX).  That was probably
-       due to a misreading of the  AIX 4  header  files,  because  the  X/Open
-       Curses  document  was  not generally available at that time.  Later (in
-       2002), this detail was  overlooked  when  beginning  to  implement  the
-       functions using the structure.
+       ncurses defined its cchar_t in 1995 using 5 as the total of spacing and
+       non-spacing  characters  (CCHARW_MAX).   That  was  probably  due  to a
+       misreading of  the  AIX 4  header  files,  because  the  X/Open  Curses
+       document  was  not  generally available at that time.  Later (in 2002),
+       this detail was overlooked when work began to implement  the  functions
+       using the structure.
 
-       In  practice, even four non-spacing characters may seem enough.  X/Open
-       Curses documents possible uses for  non-spacing  characters,  including
-       using  them  for ligatures between characters (a feature apparently not
-       supported by any curses implementation).  Unicode does  not  limit  the
-       (analogous) number of combining characters, so some applications may be
-       affected.
+       In  practice,  a  mere  four  non-spacing characters may seem adequate.
+       X/Open  Curses   documents   possible   applications   of   non-spacing
+       characters,  including their use as ligatures (a feature apparently not
+       supported by any curses implementation).  Unicode does  not  limit  the
+       (analogous)  number of combining characters in a grapheme cluster; some
+       applications may be affected.  ncurses can be compiled with a different
+       CCHARW_MAX value; doing so alters the library's ABI.
+
+
+

                HISTORY

                +       X/Open Curses Issue 4 (1995) initially specified these functions.

                SEE ALSO

                        curses(3x), curs_attr(3x), curs_color(3x), wcwidth(3)
 
-
-
-ncurses 6.5                       2024-04-20                 curs_getcchar(3x)
+ncurses 6.6                       2025-02-23                 curs_getcchar(3x)
                diff --git a/doc/html/man/curs_getch.3x.html b/doc/html/man/curs_getch.3x.html index fd8a890..f095fdb 100644 --- a/doc/html/man/curs_getch.3x.html +++ b/doc/html/man/curs_getch.3x.html @@ -1,7 +1,7 @@ -curs_getch 3x 2024-04-20 ncurses 6.5 Library calls +curs_getch 3x 2025-11-11 ncurses 6.6 Library calls -

                curs_getch 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_getch 3x 2025-11-11 ncurses 6.6 Library calls

                 curs_getch(3x)                   Library calls                  curs_getch(3x)
 
 
-
-

                NAME

                        getch, wgetch, mvgetch, mvwgetch, ungetch, has_key - get (or push back)
-       characters from curses terminal keyboard
+       characters from curses terminal keyboard buffer

                SYNOPSIS

                        #include <curses.h>
 
        int getch(void);
-       int wgetch(WINDOW *win);
+       int wgetch(WINDOW * win);
        int mvgetch(int y, int x);
-       int mvwgetch(WINDOW *win, int y, int x);
+       int mvwgetch(WINDOW * win, int y, int x);
 
        int ungetch(int c);
 
@@ -69,92 +67,114 @@

                DESCRIPTION

                Reading Characters

                -       wgetch gathers a key stroke from the terminal keyboard associated  with
-       a  curses  window  win.   ncurses(3x)  describes  the  variants of this
+       wgetch gathers a key event from the terminal keyboard associated with a
+       curses   window  win.   ncurses(3x)  describes  the  variants  of  this
        function.
 
        When input is pending, wgetch returns an integer  identifying  the  key
-       stroke;  for  alphanumeric and punctuation keys, this value corresponds
-       to the character encoding used by the terminal.  Use of the control key
-       as  a modifier often results in a distinct code.  The behavior of other
-       keys depends on whether win is in keypad mode; see  subsection  "Keypad
-       Mode" below.
+       event;  for  alphanumeric  and  punctuation  keys,  the  space bar, and
+       (usually) the Backspace, Tab,  Return,  and  Escape  keys,  this  value
+       corresponds to the character encoding used by the terminal.  Use of the
+       control  key  as  a  modifier,  by  holding  it down while pressing and
+       releasing another key, often results in a distinct code.  The  behavior
+       of  other keys depends on whether win is in keypad mode; see subsection
+       "Keypad Mode" below.
 
-       If  no input is pending, then if the no-delay flag is set in the window
-       (see nodelay(3x)), the function returns ERR;  otherwise,  curses  waits
-       until  the  terminal  has  input.   If cbreak(3x) has been called, this
-       happens after one character is read.  If nocbreak(3x) has been  called,
-       it  occurs  when  the  next newline is read.  If halfdelay(3x) has been
-       called, curses waits until a character is typed or the specified  delay
-       elapses.
+       If no input is pending, then if the no-delay flag is set in the  window
+       (see  nodelay(3x)),  the  function returns ERR; otherwise, curses waits
+       until the terminal has  input.   If  cbreak(3x)  or  raw(3x)  has  been
+       called, this happens after curses reads one key event.  If nocbreak(3x)
+       or  noraw(3x)  has  been called, it occurs when curses reads a newline.
+       (Because the terminal's canonical or "cooked"  mode  is  line-buffered,
+       multiple  wgetch calls may then be necessary to empty the input queue.)
+       If halfdelay(3x) has been called, curses waits until input is available
+       or the specified delay elapses.
 
        If echo(3x) has been called, and the window is not a pad, curses writes
        the returned character c to the window (at the cursor position) per the
        following rules.
 
-       o   If  c  matches  the  terminal's  erase  character, the cursor moves
-           leftward one  position  and  the  new  position  is  erased  as  if
+       o   If c matches the terminal's erase  character  (see  erasechar(3x)),
+           and  the  cursor is not at the window's leftmost column, the cursor
+           moves leftward one position and the new position is  erased  as  if
            wmove(3x)  and  then  wdelch(3x)  were  called.   When the window's
            keypad mode is enabled (see below), KEY_LEFT and KEY_BACKSPACE  are
            handled the same way.
 
        o   curses writes any other c to the window, as with wechochar(3x).
 
-       o   If  the  window  has  been moved or modified since the last call to
-           wrefresh(3x), curses calls wrefresh.
+       o   If the window win has been moved or modified since the last call to
+           wrefresh(3x), curses calls wrefresh on it.
 
-       If c is a carriage return and nl(3x) has been  called,  wgetch  returns
+       If  c  is  a carriage return and nl(3x) has been called, wgetch returns
        the character code for line feed instead.

                Keypad Mode

                -       To  curses, key strokes not from the alphabetic section of the keyboard
-       (those    corresponding    to    the    ECMA-6    character    set--see
-       ascii(7)--optionally  modified by either the control or shift keys) are
-       treated as function keys.  (In curses, the term "function key" includes
-       but  is  not  limited to keycaps engraved with "F1", "PF1", and so on.)
-       If the  window  is  in  keypad  mode,  these  produce  a  numeric  code
-       corresponding  to the KEY_ symbols listed in subsection "Predefined Key
-       Codes" below; otherwise, they transmit a sequence  of  codes  typically
-       starting  with  the  escape character, and which must be collected with
-       multiple wgetch calls.
+       Call keypad(3x) on a window to configure keypad mode when reading input
+       from it.  In keypad mode,  curses  treats  key  strokes  not  from  the
+       alphabetic  section  of the keyboard (those corresponding to the ECMA-6
+       character set -- see ascii(7) --  optionally  modified  by  either  the
+       control  or  shift  keys)  as  function  keys.   (In  curses,  the term
+       "function key" includes but is not limited  to  keycaps  engraved  with
+       "F1",  "PF1",  and  so  on.)   If  a  window  is in keypad mode, wgetch
+       translates these key strokes to a numeric  code  corresponding  to  the
+       KEY_  symbols listed in subsection "Key Codes" below.  If the window is
+       not in keypad mode, the input queue populates with  the  characters  of
+       the  function key's escape sequence, which the application must collect
+       individually with multiple wgetch calls.
 
-       o   The curses.h header file declares  many  predefined  function  keys
-           whose  names  begin with KEY_; these object-like macros have values
+       o   The curses.h header file declares many function  keys  whose  names
+           begin  with  KEY_;  these  object-like  macros  have integer values
            outside the range of eight-bit character codes.
 
        o   In  ncurses,  user-defined  function  keys  are   configured   with
            define_key(3x);  they  have no names, but are also expected to have
-           values outside the range of eight-bit codes.
+           integer values outside the range of eight-bit character codes.
 
        A variable intended to hold a function key code must thus  be  of  type
        short or larger.
 
        Most  terminals  one  encounters follow the ECMA-48 standard insofar as
        their function keys  produce  character  sequences  prefixed  with  the
-       escape  character  ESC.   This  fact  implies  that  curses cannot know
-       whether the terminal has sent an ESC key stroke or the beginning  of  a
-       function  key's  character  sequence without waiting to see if, and how
-       soon, further input arrives.   When  curses  reads  such  an  ambiguous
-       character,  it sets a timer.  If the remainder of the sequence does not
-       arrive within the designated time, wgetch returns the prefix character;
-       otherwise, it returns the function key code corresponding to the unique
-       sequence defined by the terminal.  Consequently, a  user  of  a  curses
-       application  may  experience  a  delay  after pressing ESC while curses
-       disambiguates the input; see section "EXTENSIONS" below.  If the window
-       is  in "no time-out" mode, the timer does not expire; it is an infinite
-       (or very  large)  value.   See  notimeout(3x).   Because  function  key
-       sequences  usually  begin  with  an  escape character, the terminal may
-       appear to hang in no time-out mode after  the  user  has  pressed  ESC.
-       Generally, further typing "awakens" curses.
+       escape character ESC.  This fact implies that curses cannot distinguish
+       a  user's  press  of  the  escape  key (assuming it sends ESC) from the
+       beginning of a function key's character sequence without waiting to see
+       if, and how soon, further input arrives.
+
+       o   If the escape sequence  matches  a  string  capability  defining  a
+           function  key  for  the  terminal type (such as key_home (khome) or
+           key_up (kuu1)), wgetch returns the function key code  corresponding
+           to the unique sequence defined by the terminal.
+
+       o   If  the  escape  sequence  matches no function keys defined for the
+           terminal type, call wgetch repeatedly to obtain the  codes  of  the
+           individual  characters  of the sequence, in the order they occurred
+           in the input.
+
+       o   If wgetch cannot decide the validity of the input as a function key
+           because it has not read enough characters to disambiguate  it,  the
+           function  waits  until  it has this information or the escape delay
+           elapses.  Configure the  escape  delay  with  the  global  variable
+           ESCDELAY,  an  extension  (see  section "EXTENSIONS" below), or the
+           environment variable of the same name (see section "ENVIRONMENT" of
+           ncurses(3x)), also an extension.
+
+       Consequently, a user of a curses application that employs  keypad  mode
+       may  experience  a  pause or "hang" after pressing the escape key while
+       curses collects sufficient characters to disambiguate  the  input.   If
+       the  window  is  in "no time-out" mode, the escape delay is effectively
+       infinite; see notimeout(3x).  In the event of  such  a  pause,  further
+       typing "awakens" curses.

                Ungetting Characters

                        ungetch  places  c into the input queue to be returned by the next call
-       to wgetch.  A single input queue serves all windows.
+       to wgetch.  A single input queue serves all windows associated with the
+       screen.
 
 
-

                Predefined Key Codes

                +

                Key Codes

                        The header file curses.h defines the following function key codes.
 
        o   Except for the special case of KEY_RESIZE, a window's  keypad  mode
@@ -180,7 +200,6 @@
               KEY_BACKSPACE   Backspace
               KEY_F0          Function keys; space for 64 keys is reserved
               KEY_F(n)        Function key n where 0 <= n <= 63
-
               KEY_DL          Delete line
               KEY_IL          Insert line
               KEY_DC          Delete character
@@ -246,7 +265,6 @@
               KEY_SDL         Shifted delete line key
               KEY_SEND        Shifted end key
               KEY_SEOL        Shifted clear line key
-
               KEY_SEXIT       Shifted exit key
               KEY_SFIND       Shifted find key
               KEY_SHELP       Shifted help key
@@ -269,70 +287,82 @@
 
        Many keyboards feature a nine-key directional pad.
 
-                                   +-----+------+-------+
-                                   | A1  |  up  |  A3   |
-                                   +-----+------+-------+
-                                   |left |  B2  | right |
-                                   +-----+------+-------+
-                                   | C1  | down |  C3   |
-                                   +-----+------+-------+
+                                  +------+------+-------+
+                                  |  A1  |  up  |  A3   |
+                                  +------+------+-------+
+                                  | left |  B2  | right |
+                                  +------+------+-------+
+                                  |  C1  | down |  C3   |
+                                  +------+------+-------+
+
        Two of the symbols in the list above do not correspond  to  a  physical
        key.
 
        o   wgetch  returns  KEY_RESIZE,  even  if  the window's keypad mode is
-           disabled, when ncurses handles a SIGWINCH signal;  see  initscr(3x)
-           and resizeterm(3x).
+           disabled, if ncurses has handled a SIGWINCH signal since wgetch was
+           called; see initscr(3x) and resizeterm(3x).
 
-       o   wgetch  returns KEY_MOUSE to indicate that a mouse event is pending
-           collection; see curs_mouse(3x).  Receipt of this  code  requires  a
-           window's  keypad  mode  to  be  enabled, because to interpret mouse
-           input (as with with xterm(1)'s mouse prototocol), ncurses must read
-           an escape sequence, as with a function key.
+       o   wgetch returns KEY_MOUSE to indicate that a mouse event is  pending
+           collection;  see  curs_mouse(3x).   Receipt of this code requires a
+           window's keypad mode to be  enabled,  because  to  interpret  mouse
+           input  (as  with  xterm(1)'s  mouse protocol), ncurses must read an
+           escape sequence, as with a function key.

                Testing Key Codes

                -       In  ncurses,  has_key  returns  a  Boolean value indicating whether the
-       terminal type recognizes its parameter as a key code value.   See  also
+       In ncurses, has_key returns a  Boolean  value  indicating  whether  the
+       terminal  type  recognizes its parameter as a key code value.  See also
        define_key(3x) and key_defined(3x).

                RETURN VALUE

                -       Except  for  has_key,  these  functions return OK on success and ERR on
-       failure.
+       wgetch returns a key code identifying the key event as described above,
+       which may include KEY_RESIZE or KEY_MOUSE indicating non-key events, or
+       ERR on failure.  wgetch fails if its timeout expires without  any  data
+       arriving,  which  cannot  happen  if  nodelay(3x)  is  in effect on the
+       window.
 
-       Functions taking a WINDOW pointer argument fail if the pointer is NULL.
+       In ncurses, wgetch also fails if
+
+       o   the curses screen has not been initialized,
+
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer, or
+
+       o   execution  was  interrupted  by a signal, in which case the library
+           sets errno to EINTR.
 
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.
 
-       wgetch also fails if
+       ungetch  returns OK on success and ERR on failure.  In ncurses, ungetch
+       fails if
 
-       o   its timeout expires without any data arriving, or
+       o   the curses screen has not been initialized, or
 
-       o   execution  was  interrupted by a signal, in which case errno is set
-           to EINTR.
-
-       ungetch fails if there is no more room in the input queue.
+       o   there is no more room in the input queue.
 
        has_key returns TRUE or FALSE.

                NOTES

                +       getch, mvgetch, and mvwgetch may be implemented as macros.
+
        curses discourages assignment of the ESC key to a discrete function  by
        the programmer because the library requires a delay while it awaits the
        potential remainder of a terminal escape sequence.
 
-       Some key strokes are indistinguishable  from  control  characters;  for
-       example,  KEY_ENTER may be the same as ^M, and KEY_BACKSPACE may be the
-       same as ^H or ^?.  Consult the terminal's terminfo entry  to  determine
-       whether this is the case; see infocmp(1).  Some curses implementations,
-       including ncurses, honor the terminfo  key  definitions;  others  treat
-       such control characters specially.
+       Some  key  strokes  are  indistinguishable from control characters; for
+       example, KEY_ENTER may be the same as ^M, and KEY_BACKSPACE may be  the
+       same  as ^H or ^?.  Consult the terminfo entry for the terminal type to
+       determine whether this  is  the  case;  see  infocmp(1).   Some  curses
+       implementations, including ncurses, honor the terminfo key definitions;
+       others treat such control characters specially.
 
        curses  distinguishes  the  Enter  keys  in  the alphabetic and numeric
        keypad sections of a keyboard because (most) terminals  do.   KEY_ENTER
        refers  to the key on the numeric keypad and, like other function keys,
-       and is reliably recognized only if the window's keypad mode is enabled.
+       is reliably recognized only if the window's keypad mode is enabled.
 
        o   The terminfo key_enter (kent) capability  describes  the  character
            (sequence)  sent  by  the  Enter  key  of  a terminal's numeric (or
@@ -346,69 +376,84 @@
        o   It usually produces a control code for carriage return (^M) or line
            feed (^J).
 
-       o   Depending on the terminal mode  (raw,  cbreak,  or  "cooked"),  and
-           whether  nl(3x)  or  nonl(3x)  has  been  called, wgetch may return
-           either a carriage return or line feed upon an Enter or  Return  key
+       o   Depending  on  the  terminal  mode (raw, cbreak, or canonical), and
+           whether nl(3x) or nonl(3x)  has  been  called,  wgetch  may  return
+           either  a  carriage return or line feed upon an Enter or Return key
            stroke.
 
-       Use  of  wgetch with echo(3x) and neither cbreak(3x) nor raw(3x) is not
+       Use of wgetch with echo(3x) and neither cbreak(3x) nor raw(3x)  is  not
        well-defined.
 
-       Historically, the list of key code macros above was influenced  by  the
-       function-key-rich  keyboard  of  the AT&T 7300 (also known variously as
-       the "3B1", "Safari  4",  and  "UNIX  PC"),  a  1985  machine.   Today's
-       computer  keyboards  are  based  that of the IBM PC/AT and tend to have
+       Historically,  the  list of key code macros above was influenced by the
+       keyboard of the AT&T 7300 (also known variously as the  "3B1",  "Safari
+       4",  and  "UNIX  PC"),  a  1985 machine rich in function keys.  Today's
+       computer keyboards are based on that of the IBM PC/AT and tend to  have
        fewer.  A curses application can expect such a keyboard to transmit key
        codes   KEY_UP,   KEY_DOWN,  KEY_LEFT,  KEY_RIGHT,  KEY_HOME,  KEY_END,
        KEY_PPAGE (Page Up), KEY_NPAGE (Page  Down),  KEY_IC  (Insert),  KEY_DC
-       (Delete), and KEY_F(n) for 1 <= n <= 12.
-
-       getch, mvgetch, and mvwgetch may be implemented as macros.
+       (Delete), KEY_A1, KEY_A3, KEY_B2, KEY_C1, KEY_C3, and KEY_F(n) for 1 <=
+       n <= 12.

                EXTENSIONS

                        In ncurses, when a window's "no time-out" mode is not set, the ESCDELAY
-       variable configures the duration of the timer used  to  disambiguate  a
-       function  key character sequence from a series of key strokes beginning
+       variable  configures  the  duration of the timer used to disambiguate a
+       function key character sequence from a series of key strokes  beginning
        with ESC typed by the user; see curs_variables(3x).
 
-       has_key was designed for ncurses(3x), and is not found in SVr4  curses,
-       4.4BSD curses, or any other previous curses implementation.
+       has_key  is  an  ncurses  extension,  and  is not found in SVr4 curses,
+       4.4BSD curses, or any other previous curses implementation.

                PORTABILITY

                        Applications employing ncurses extensions should condition their use on
        the visibility of the NCURSES_VERSION preprocessor macro.
 
-       X/Open Curses, Issue 4 describes getch, wgetch, mvgetch, mvwgetch,  and
-       ungetch.  It specifies no error conditions for them.
+       Except as noted in section "EXTENSIONS" above,  X/Open  Curses  Issue 4
+       describes these functions.  It specifies no error conditions for them.
 
-       wgetch reads only single-byte characters.
+       SVr4  describes  a  successful  return  value only as "an integer value
+       other than ERR".
 
-       The  echo  behavior  of  these  functions on input of KEY_ or backspace
-       characters  was  not  specified  in  the  SVr4   documentation.    This
-       description is adapted from X/Open Curses.
+       wgetch reads only single-byte characters.
 
-       The   behavior  of  wgetch  in  the  presence  of  signal  handlers  is
-       unspecified in the SVr4 documentation and X/Open Curses.  In historical
-       curses  implementations,  it  varied depending on whether the operating
-       system's dispatch of a signal to a handler interrupting a read(2)  call
-       in  progress,  and  also  (in  some  implementations)  whether an input
-       timeout or non-blocking mode has been set.  Programmers concerned about
-       portability  should  be  prepared  for  either of two cases: (a) signal
-       receipt does not interrupt wgetch; or  (b)  signal  receipt  interrupts
-       wgetch and causes it to return ERR with errno set to EINTR.
+       The echo behavior of these functions on  input  of  KEY_  or  backspace
+       characters is not documented in SVr4 curses.
 
-       KEY_MOUSE is mentioned in X/Open Curses, along with a few related term-
+       The  behavior  of  wgetch  in  the  presence  of signal handlers is not
+       documented in SVr4 curses and is  unspecified  by  X/Open  Curses.   In
+       historical  curses  implementations, it varied depending on whether the
+       operating system's dispatch of a signal  to  a  handler  interrupted  a
+       read(2) call in progress, and also (in some implementations) whether an
+       input  timeout  or  non-blocking  mode had been set.  A portable curses
+       application prepares  for  two  cases:  (a)  signal  receipt  does  not
+       interrupt  wgetch;  and (b) signal receipt interrupts wgetch and causes
+       it to return ERR with errno set to EINTR.
+
+       KEY_MOUSE is mentioned in X/Open Curses, along with a few related term-
        info capabilities, but no higher-level functions use the feature.   The
        implementation in ncurses is an extension.
 
-       KEY_RESIZE  and  has_key  are extensions first implemented for ncurses.
+       KEY_RESIZE  and  has_key  are extensions first implemented for ncurses.
        By  2022,  PDCurses  and  NetBSD  curses  had  added  them  along  with
-       KEY_MOUSE.
+       KEY_MOUSE.
+
+
+

                HISTORY

                +       4BSD (1980) introduced wgetch and its variants.
+
+       SVr3 (1987) added ungetch.
+
+       ncurses 1.9.9g (1996) furnished the has_key extension.

                SEE ALSO

                +       ECMA-6  "7-bit  coded  Character  Set" <https://ecma-international.org/
+       publications-and-standards/standards/ecma-6/>
+
+       ECMA-48  "Control  Functions  for  Coded  Character   Sets"   <https://
+       ecma-international.org/publications-and-standards/standards/ecma-48/>
+
        curs_get_wch(3x)  describes comparable functions of the ncurses library
        in its wide-character configuration (ncursesw).
 
@@ -416,15 +461,7 @@
        curs_move(3x),  curs_outopts(3x), curs_refresh(3x), curs_variables(3x),
        resizeterm(3x), ascii(7)
 
-       ECMA-6 "7-bit  coded  Character  Set"  <https://ecma-international.org/
-       publications-and-standards/standards/ecma-6/>
-
-       ECMA-48   "Control   Functions  for  Coded  Character  Sets"  <https://
-       ecma-international.org/publications-and-standards/standards/ecma-48/>
-
-
-
-ncurses 6.5                       2024-04-20                    curs_getch(3x)
+ncurses 6.6                       2025-11-11                    curs_getch(3x)
                @@ -443,6 +480,7 @@ ncurses 6.5 2024-04-20 NOTES
              • EXTENSIONS
              • PORTABILITY
                • +
              • HISTORY
              • SEE ALSO
              diff --git a/doc/html/man/curs_getstr.3x.html b/doc/html/man/curs_getstr.3x.html index 0142df9..97565fc 100644 --- a/doc/html/man/curs_getstr.3x.html +++ b/doc/html/man/curs_getstr.3x.html @@ -1,6 +1,6 @@ -curs_getstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_getstr 3x 2025-10-20 ncurses 6.6 Library calls -

              curs_getstr 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_getstr 3x 2025-10-20 ncurses 6.6 Library calls

               curs_getstr(3x)                  Library calls                 curs_getstr(3x)
 
 
-
-

              NAME

                      getstr,  getnstr,  wgetstr,  wgetnstr,  mvgetstr, mvgetnstr, mvwgetstr,
-       mvwgetnstr - accept character strings from curses terminal keyboard
+       mvwgetnstr - read a character string from curses terminal keyboard

              SYNOPSIS

                      #include <curses.h>
 
-       int getstr(char *str);
-       int getnstr(char *str, int n);
-       int wgetstr(WINDOW *win, char *str);
-       int wgetnstr(WINDOW *win, char *str, int n);
+       int getstr(char * str);
+       int wgetstr(WINDOW * win, char * str);
+       int mvgetstr(int y, int x, char * str);
+       int mvwgetstr(WINDOW * win, int y, int x, char * str);
 
-       int mvgetstr(int y, int x, char *str);
-       int mvwgetstr(WINDOW *win, int y, int x, char *str);
-       int mvgetnstr(int y, int x, char *str, int n);
-       int mvwgetnstr(WINDOW *win, int y, int x, char *str, int n);
+       int getnstr(char * str, int n);
+       int wgetnstr(WINDOW * win, char * str, int n);
+       int mvgetnstr(int y, int x, char * str, int n);
+       int mvwgetnstr(WINDOW * win, int y, int x, char * str, int n);

              DESCRIPTION

              -       The function wgetnstr is equivalent to a series of calls to wgetch(3x),
-       until a newline or carriage return terminates the series:
+       wgetstr populates a  user-supplied  string  buffer  str  by  repeatedly
+       calling  wgetch(3x) with the win argument until a line feed or carriage
+       return character is input.  The function
 
-       o   The terminating character is not included in the returned string.
+       o   does not copy the terminating character to str;
 
-       o   In all instances, the end of the string is terminated by a NUL.
+       o   always terminates str with a null character;
 
-       o   The  function  stores  the result in the area pointed to by the str
-           parameter.
+       o   interprets  the   screen's   erase   and   kill   characters   (see
+           erasechar(3x) and killchar(3x));
 
-       o   The function reads at most n characters, thus preventing a possible
-           overflow of the input buffer.
+       o   recognizes  function  keys  only  if  the screen's keypad option is
+           enabled (see keypad(3x));
 
-           Any  attempt  to  enter more characters (other than the terminating
-           newline or carriage return) causes a beep.
+       o   treats the function keys KEY_LEFT and KEY_BACKSPACE the same as the
+           erase character; and
 
-           Function keys also cause a beep and are ignored.
+       o   discards function key inputs other than those treated as the  erase
+           or kill characters, calling beep(3x).
 
-       The user's erase and kill characters are interpreted:
+       If  any  characters  have  been  written to the input buffer, the erase
+       character replaces the character at the current position in the  buffer
+       with  a  null  character, then decrements the position by one; the kill
+       character does the same repeatedly, backtracking to  the  beginning  of
+       the buffer.
 
-       o   The erase character (e.g., ^H) erases the character at the  end  of
-           the buffer, moving the cursor to the left.
+       If  the screen's echo option is enabled (see echo(3x)), wgetstr updates
+       win with waddch(3x).  Further,
 
-           If keypad mode is on for the window, KEY_LEFT and KEY_BACKSPACE are
-           both considered equivalent to the user's erase character.
+       o   the erase character and its function key synonyms move  the  cursor
+           to  the  left (if not already where it was located when wgetstr was
+           called) and
 
-       o   The kill character (e.g., ^U) erases the entire buffer, leaving the
-           cursor at the beginning of the buffer.
+       o   the kill character returns the cursor to where it was located  when
+           wgetstr was called.
 
-       Characters  input  are  echoed  only  if echo is currently on.  In that
-       case, backspace  is  echoed  as  deletion  of  the  previous  character
-       (typically a left motion).
+       wgetnstr  is  similar,  but  reads  at  most  n  characters, aiding the
+       application to avoid  overrunning  the  buffer  to  which  str  points.
+       curses  ignores  an attempt to input more than n characters (other than
+       the terminating line feed or carriage return), calling beep(3x).  If  n
+       is   negative,   wgetn_wstr   reads  up  to  LINE_MAX  characters  (see
+       sysconf(3)).
 
-       The   getnstr,   mvgetnstr,  mvwgetnstr,  and  wgetnstr  functions  are
-       identical to the getstr, mvgetstr, mvwgetstr,  and  wgetstr  functions,
-       respectively,  except  that the *n* versions read at most n characters,
-       letting the application prevent overflow of the input buffer.
+       ncurses(3x) describes the variants of these functions.

              RETURN VALUE

              -       All  of  these  functions  return  the  integer  OK   upon   successful
-       completion.  (SVr4 specifies only "an integer value other than ERR") If
-       unsuccessful, they return ERR.
+       These functions return OK on success and ERR on failure.
 
-       X/Open defines no error conditions.
+       In ncurses, these functions fail if
 
-       In this implementation, these functions return an error
+       o   the curses screen has not been initialized,
 
-       o   if the window pointer is null,
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer,
 
-       o   if its timeout expires without having any data, or
+       o   str is a null pointer, or
 
-       o   if the associated call to wgetch failed.
+       o   an internal wgetch(3x) call fails.
 
-       This implementation provides an  extension  as  well.   If  a  SIGWINCH
-       interrupts  the  function,  it will return KEY_RESIZE rather than OK or
-       ERR.
+       Further,  in  ncurses,  these functions return KEY_RESIZE if a SIGWINCH
+       event interrupts the function.
 
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

              NOTES

              -       Any of these functions other than wgetnstr may be macros.
+       All of these functions except wgetnstr may be implemented as macros.
 
-       Using  getstr,  mvgetstr,  mvwgetstr,  or  wgetstr  to read a line that
-       overflows the array pointed to by str causes  undefined  results.   The
-       use  of  getnstr,  mvgetnstr, mvwgetnstr, or wgetnstr, respectively, is
-       recommended.
+       Reading  input  that  overruns  the  buffer  pointed  to  by str causes
+       undefined  results.   Use  the  n-infixed   functions,   and   allocate
+       sufficient storage for str -- at least n+1 times sizeof(char).
+
+       While  these  functions  conceptually  implement  a  series of calls to
+       wgetch, they also temporarily change properties of the curses screen to
+       permit simple editing of the input buffer.   Each  function  saves  the
+       screen's  state,  calls  nl(3x),  and,  if  the screen was in canonical
+       ("cooked") mode, cbreak(3x).  Before returning, it restores  the  saved
+       screen  state.  Other implementations differ in detail, affecting which
+       control  characters  they  can  accept  in  the  buffer;  see   section
+       "PORTABILITY" below.
+
+
+

              EXTENSIONS

              +       getnstr,  wgetnstr,  mvgetnstr,  and mvwgetnstr's handing of negative n
+       values is an ncurses extension.
+
+       The return value KEY_RESIZE is an ncurses extension.

              PORTABILITY

              -       These functions are described in The Single Unix Specification, Version
-       2.  No error conditions are defined.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
-       This  implementation  returns  ERR if the window pointer is null, or if
-       the lower-level wgetch(3x) call returns an ERR.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them, but indicates that wgetnstr and its variants  read
+       "the entire multi-byte sequence associated with a character" and "fail"
+       if n and str together do not describe a buffer "large enough to contain
+       any  complete  characters".   In  ncurses,  however,  wgetch reads only
+       single-byte characters, so this scenario does not arise.
 
-       SVr3 and early SVr4 curses  implementations  did  not  reject  function
-       keys;  the  SVr4.0  documentation  claimed that "special keys" (such as
-       function keys,  "home"  key,  "clear"  key,  etc.)  are  "interpreted",
-       without  giving  details.   It  lied.   In  fact, the "character" value
-       appended to the string by those implementations was predictable but not
-       useful  (being,  in  fact,  the  low-order eight bits of the key's KEY_
-       value).
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
 
-       The functions getnstr, mvgetnstr, and mvwgetnstr were present  but  not
-       documented in SVr4.
+       SVr3  and  early  SVr4  curses  implementations did not reject function
+       keys; the SVr4 documentation asserted that, like the screen's erase and
+       kill characters, they were
 
-       X/Open Curses, Issue 5 (2007) stated that these functions "read at most
-       n bytes" but did not state whether the terminating NUL  is  counted  in
-       that  limit.   X/Open  Curses,  Issue 7 (2009) changed that to say they
-       "read at most n-1 bytes" to allow for the terminating NUL.  As of 2018,
-       some implementations count it, some do not:
+              interpreted, as well as any special keys (such as function keys,
+              "home" key, "clear" key, etc.)
 
-       o   ncurses  6.1  and PDCurses do not count the NUL in the given limit,
-           while
+       without further detail.  It lied.  The "character"  value  appended  to
+       the  string  by those implementations was predictable but not useful --
+       being, in fact, the  low-order  eight  bits  of  the  key  code's  KEY_
+       constant  value.   (The  same  language,  unchanged except for styling,
+       survived into X/Open Curses Issue 4,  Version 2  but  disappeared  from
+       Issue 7.)
 
-       o   Solaris SVr4 and NetBSD curses count the NUL as part of the limit.
+       A draft of X/Open Curses Issue 5 (which never saw final release) stated
+       that  these  functions "read at most n bytes" but did not state whether
+       the terminating null  character  counted  toward  that  limit.   X/Open
+       Curses  Issue 7  changed  that  to say they "read at most n-1 bytes" to
+       allow  for  the  terminating  null  character.   As   of   2018,   some
+       implementations count it, some do not.
 
-       o   Solaris  xcurses  provides  both:  its   wide-character   wget_nstr
-           reserves   a   NUL,  but  its  wgetnstr  does  not  count  the  NUL
-           consistently.
+       o   ncurses 6.1 and PDCurses do not count the null character toward the
+           limit, while Solaris and NetBSD curses do.
 
-       In SVr4 curses, a negative value of n tells wgetnstr to assume that the
-       caller's  buffer  is large enough to hold the result, i.e., to act like
-       wgetstr.  X/Open Curses does not mention this (or anything  related  to
-       negative  or  zero  values  of n), however most implementations use the
-       feature, with different limits:
+       o   Solaris   xcurses   offers   both   behaviors:  its  wide-character
+           wgetn_wstr reserves room for a wide null character,  but  its  non-
+           wide  wgetnstr  does not consistently count a null character toward
+           the limit.
 
-       o   Solaris SVr4 curses and PDCurses limit the  result  to  255  bytes.
-           Other Unix systems than Solaris are likely to use the same limit.
+       X/Open Curses does  not  specify  what  happens  if  the  length  n  is
+       negative.
 
-       o   Solaris xcurses limits the result to LINE_MAX bytes.
+       o   ncurses  6.2  uses  LINE_MAX  or  a larger (system-dependent) value
+           provided  by  sysconf(3).   If  neither  LINE_MAX  nor  sysconf  is
+           available,  ncurses  uses  the  POSIX  minimum  value  for LINE_MAX
+           (2048).  In either case, it reserves a  byte  for  the  terminating
+           null character.
 
-       o   NetBSD  7  assumes no particular limit for the result from wgetstr.
-           However, it limits the wgetnstr parameter n to ensure  that  it  is
-           greater than zero.
+       o   In  SVr4  curses,  a  negative  n tells wgetnstr to assume that the
+           caller's buffer is large enough to hold the result;  that  is,  the
+           function  then  acts  like wgetstr.  X/Open Curses does not mention
+           this behavior  (or  anything  related  to  nonpositive  n  values),
+           however  most  curses libraries implement it.  Most implementations
+           nevertheless enforce an upper limit on  the  count  of  bytes  they
+           write to the destination buffer str.
 
-           A  comment in NetBSD's source code states that this is specified in
-           SUSv2.
+       o   BSD   curses   lacked  wgetnstr,  and  its  wgetstr  wrote  to  str
+           unboundedly, as did that in SVr2.
 
-       o   ncurses (before 6.2) assumes no particular  limit  for  the  result
-           from  wgetstr,  and  treats  the  n parameter of wgetnstr like SVr4
-           curses.
+       o   PDCurses, and  SVr3  and  later,  and  Solaris  curses  limit  both
+           functions  to  writing  256  bytes.  Other System V-based platforms
+           likely use the same limit.
 
-       o   ncurses 6.2 uses LINE_MAX, or  a  larger  (system-dependent)  value
-           which  the  sysconf  function  may provide.  If neither LINE_MAX or
-           sysconf is available, ncurses uses the POSIX value for LINE_MAX  (a
-           2048  byte  limit).   In  either  case,  it reserves a byte for the
-           terminating NUL.
+       o   Solaris  xcurses  limits  the  write   to   LINE_MAX   bytes   (see
+           sysconf(3)).
 
-       Although getnstr is equivalent to a series of calls to getch,  it  also
-       makes  changes to the curses modes to allow simple editing of the input
-       buffer:
+       o   NetBSD  7  curses  imposes no particular limit on the length of the
+           write, but does validate n to ensure that it is greater than  zero.
+           A  comment  in  NetBSD's  source  code asserts that SUSv2 specifies
+           this.
 
-       o   getnstr saves the current value of the nl,  echo,  raw  and  cbreak
-           modes, and sets nl, noecho, noraw, and cbreak.
+       Implementations vary in their handling of input control characters.
 
-           getnstr  handles  the echoing of characters, rather than relying on
-           the caller to set an appropriate mode.
+       o   While they may enable the screen's echo option, some do not take it
+           out of raw mode,  and  may  take  cbreak  mode  into  account  when
+           deciding whether to handle echoing within wgetnstr or to rely on it
+           as a side effect of calling wgetch.
 
-       o   It also obtains the erase and kill characters  from  erasechar  and
-           killchar, respectively.
+       o   Originally,  ncurses, like its progenitor pcurses, had its wgetnstr
+           call noraw and cbreak before accepting input.  That may  have  been
+           done  to  make  function keys work; it is not necessary with modern
+           ncurses.
 
-       o   On return, getnstr restores the modes to their previous values.
+           Since 1995, ncurses has provided handlers for SIGINTR  and  SIGQUIT
+           events,  which  are typically generated at the keyboard with ^C and
+           ^\ respectively.  In cbreak mode, those handlers catch a signal and
+           stop  the  program,  whereas  other  implementations  write   those
+           characters into the buffer.
 
-       Other implementations differ in their treatment of special characters:
+       o   Starting  with  ncurses  6.3 (2021), wgetnstr preserves raw mode if
+           the screen was already in that state, allowing  one  to  enter  the
+           characters  the  terminal  interprets  as interrupt and quit events
+           into the buffer, for better compatibility with SVr4 curses.
 
-       o   While  they  may  set  the  echo mode, other implementations do not
-           modify the raw mode, They may take  the  cbreak  mode  set  by  the
-           caller  into account when deciding whether to handle echoing within
-           getnstr or as a side-effect of the getch calls.
 
-       o   The original ncurses (as pcurses in 1986) set noraw and cbreak when
-           accepting  input  for  getnstr.   That  may  have been done to make
-           function- and cursor-keys work; it is not necessary with ncurses.
+

              HISTORY

              +       4BSD (1980) introduced wgetstr along with its variants.
 
-           Since 1995, ncurses has provided signal handlers for INTR and  QUIT
-           (e.g.,  ^C  or  ^\).  With the noraw and cbreak settings, those may
-           catch a signal and stop the program,  where  other  implementations
-           allow one to enter those characters in the buffer.
+       SVr3.1 (1987) added wgetnstr, but none of its variants.
 
-       o   Starting in 2021 (ncurses 6.3), getnstr sets raw, rather than noraw
-           and  cbreak  for  better  compatibility  with  SVr4-curses,   e.g.,
-           allowing one to enter a ^C into the buffer.
+       X/Open  Curses  Issue 4  (1995)  specified  getnstr,   mvgetnstr,   and
+       mvwgetnstr.

              SEE ALSO

                      curs_get_wstr(3x) describes comparable functions of the ncurses library
        in its wide-character configuration (ncursesw).
 
-       curses(3x), curs_getch(3x), curs_termattrs(3x), curs_variables(3x)
+       curses(3x),     curs_addch(3x),     curs_getch(3x),    curs_inopts(3x),
+       curs_termattrs(3x),
 
-
-
-ncurses 6.5                       2024-04-20                   curs_getstr(3x)
+ncurses 6.6                       2025-10-20                   curs_getstr(3x)
              diff --git a/doc/html/man/curs_getyx.3x.html b/doc/html/man/curs_getyx.3x.html index 1857170..41a26bd 100644 --- a/doc/html/man/curs_getyx.3x.html +++ b/doc/html/man/curs_getyx.3x.html @@ -1,6 +1,6 @@ -curs_getyx 3x 2024-04-20 ncurses 6.5 Library calls +curs_getyx 3x 2025-02-01 ncurses 6.6 Library calls -

              curs_getyx 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_getyx 3x 2025-02-01 ncurses 6.6 Library calls

               curs_getyx(3x)                   Library calls                  curs_getyx(3x)
 
 
-
-

              NAME

                      getyx,  getparyx,  getbegyx,  getmaxyx  -  get curses cursor and window
        coordinates
@@ -55,61 +53,66 @@
        #include <curses.h>
 
        void getyx(WINDOW *win, int y, int x);
-       void getparyx(WINDOW *win, int y, int x);
        void getbegyx(WINDOW *win, int y, int x);
        void getmaxyx(WINDOW *win, int y, int x);
 
+       void getparyx(WINDOW *win, int y, int x);
+

              DESCRIPTION

              -       The getyx macro places the current cursor position of the given  window
-       in the two integer variables y and x.
+       These macros obtain the cursor position and  bounds  information  of  a
+       curses window win.  getyx stores win's cursor position in the variables
+       y  and  x.  getmaxyx stores win's maximum valid line and column numbers
+       in y and x, respectively.  getbegyx similarly stores  the  position  of
+       win's  origin  relative  to  that  of  the  screen  (for  stdscr, these
+       coordinates are always 0).
 
-       If  win  is  a  subwindow,  the  getparyx  macro  places  the beginning
-       coordinates of the subwindow relative to the  parent  window  into  two
-       integer variables y and x.  Otherwise, -1 is placed into y and x.
-
-       Like  getyx,  the  getbegyx  and  getmaxyx  macros  store  the  current
-       beginning coordinates and size of the specified window.
+       If win is a subwindow (see subwin(3x)), the getparyx macro  places  the
+       coordinates  of  its origin relative to its parent window into y and x,
+       and -1 into both if it is not.

              RETURN VALUE

              -       The return values of these macros are undefined (i.e., they should  not
-       be used as the right-hand side of assignment statements).
+       No return values are defined for macros.  Do not use them as the right-
+       hand side of assignment statements.

              NOTES

              -       All  of these interfaces are macros.  A "&" is not necessary before the
-       variables y and x.
+       All of these interfaces are implemented as macros.  An "&" operator  is
+       not necessary before the variables y and x.

              PORTABILITY

              -       The getyx, getparyx, getbegyx and  getmaxyx  macros  are  described  in
-       X/Open Curses, Issue 4.
+       These macros are described in X/Open Curses Issue 4.
 
-       This  implementation also provides functions getbegx, getbegy, getcurx,
-       getcury, getmaxx, getmaxy, getparx and getpary for  compatibility  with
-       older versions of curses; see curs_legacy(3x).
+       ncurses  also  provides  functions  getbegy, getbegx, getcury, getcurx,
+       getmaxy, getmaxx, getpary, and getparx for compatibility with  System V
+       curses that were not standardized; see curs_legacy(3x).
 
-       Although  X/Open  Curses  does  not  address this, many implementations
-       provide members of the WINDOW structure containing values corresponding
-       to  these  macros.  For best portability, do not rely on using the data
-       in WINDOW, since some implementations make WINDOW opaque (do not  allow
-       direct use of its members).
+       Although X/Open Curses does not address the issue, many implementations
+       expose  members of the WINDOW structure containing values corresponding
+       to  these  macros.   Do  not   rely   on   their   availability;   some
+       implementations  make  WINDOW opaque (that is, they do not allow direct
+       access to its members).
 
        Besides the problem of opaque structures, the data stored in like-named
-       members may not have like-values  in  different  implementations.   For
-       example,  the  WINDOW._maxx and WINDOW._maxy values in ncurses have (at
-       least  since  release  1.8.1)  differed  by   one   from   some   other
-       implementations.   The  difference  is  hidden  by  means  of the macro
-       getmaxyx.
+       members may not have  values  of  the  same  meaning  across  different
+       implementations.    For   example,   the  values  of  WINDOW._maxx  and
+       WINDOW._maxy in ncurses have long  differed  by  one  from  some  other
+       implementations.  The getmaxyx macro hides this difference.
+
+
+

              HISTORY

              +       4BSD (1980) introduced getyx.
+
+       SVr3  (1987)  added  getbegyx  and  getmaxyx.   SVr3.1  later that year
+       supplied getparyx.

              SEE ALSO

                      curses(3x), curs_legacy(3x), curs_opaque(3x)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_getyx(3x)
+ncurses 6.6                       2025-02-01                    curs_getyx(3x)
              diff --git a/doc/html/man/curs_in_wch.3x.html b/doc/html/man/curs_in_wch.3x.html index 1ea5b63..6e8d956 100644 --- a/doc/html/man/curs_in_wch.3x.html +++ b/doc/html/man/curs_in_wch.3x.html @@ -1,6 +1,6 @@ -curs_in_wch 3x 2024-04-20 ncurses 6.5 Library calls +curs_in_wch 3x 2025-02-01 ncurses 6.6 Library calls -

              curs_in_wch 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_in_wch 3x 2025-02-01 ncurses 6.6 Library calls

               curs_in_wch(3x)                  Library calls                 curs_in_wch(3x)
 
 
-
-

              NAME

              -       in_wch,  mvin_wch,  mvwin_wch, win_wch - get a curses complex character
+       in_wch,  win_wch,  mvin_wch, mvwin_wch - get a curses complex character
        from a window

              SYNOPSIS

                      #include <curses.h>
 
-       int in_wch(cchar_t *wch);
-       int win_wch(WINDOW *win, cchar_t *wch);
-
-       int mvin_wch(int y, int x, cchar_t *wch);
-       int mvwin_wch(WINDOW *win, int y, int x, cchar_t *wch);
+       int in_wch(cchar_t * wch);
+       int win_wch(WINDOW * win, cchar_t * wch);
+       int mvin_wch(int y, int x, cchar_t * wch);
+       int mvwin_wch(WINDOW * win, int y, int x, cchar_t * wch);

              DESCRIPTION

              -       These functions extract the complex character and  rendition  from  the
-       current position in the named window into the cchar_t object referenced
-       by wch.
+       win_wch copies the curses complex character at the cursor  position  in
+       win  into  wch.   Use  getcchar(3x)  to  extract  its  character  code,
+       attributes, and  color  pair  identifier.   ncurses(3x)  describes  the
+       variants of this function.

              RETURN VALUE

              -       No errors are defined in X/Open Curses.  This implementation checks for
-       null  pointers,  returns ERR in that case.  Also, the mv routines check
-       for error moving the cursor, returning ERR  in  that  case.   Otherwise
-       they return OK.
+       These functions return OK on success and ERR on failure.
+
+       In ncurses, they return ERR if win is NULL.
 
        Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.

              NOTES

              -       Note that all of these routines may be macros.
+       in_wch, mvin_wch, and mvwin_wch may be implemented as macros.
+
+       Unlike winch(3x), win_wch and its  variants  store  the  value  of  the
+       retrieved  character  in  an  additional  wch  parameter instead of the
+       return value.

              PORTABILITY

              -       These functions are described in X/Open Curses, Issue 4.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+
+

              HISTORY

              +       X/Open Curses Issue 4 (1995) initially specified these functions.   The
+       System V  Interface  Definition  Version 4 of the same year specified a
+       function named winwch (and the  usual  variants).   This  was  a  later
+       addition  to  SVr4.x,  not  appearing  in  the  first  SVr4 (1989).  It
+       differed from X/Open's later win_wch in that it  returned  a  value  of
+       type chtype instead of cchar_t.

              SEE ALSO

              -       curs_inch(3x) describes comparable functions of the ncurses library  in
+       curs_inch(3x)  describes comparable functions of the ncurses library in
        its non-wide-character configuration.
 
        curses(3x), curs_inwstr(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_in_wch(3x)
+ncurses 6.6                       2025-02-01                   curs_in_wch(3x)
              diff --git a/doc/html/man/curs_in_wchstr.3x.html b/doc/html/man/curs_in_wchstr.3x.html index d7af18d..52919fc 100644 --- a/doc/html/man/curs_in_wchstr.3x.html +++ b/doc/html/man/curs_in_wchstr.3x.html @@ -1,6 +1,6 @@ -curs_in_wchstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_in_wchstr 3x 2025-10-20 ncurses 6.6 Library calls -

              curs_in_wchstr 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_in_wchstr 3x 2025-10-20 ncurses 6.6 Library calls

               curs_in_wchstr(3x)               Library calls              curs_in_wchstr(3x)
 
 
-
-

              NAME

                      in_wchstr,    in_wchnstr,    win_wchstr,    win_wchnstr,   mvin_wchstr,
        mvin_wchnstr,  mvwin_wchstr,  mvwin_wchnstr  -  get  a  curses  complex
@@ -55,70 +53,73 @@

              SYNOPSIS

                      #include <curses.h>
 
-       int in_wchstr(cchar_t *wchstr);
-       int win_wchstr(WINDOW *win, cchar_t *wchstr);
-       int mvin_wchstr(int y, int x, cchar_t *wchstr);
-       int mvwin_wchstr(WINDOW *win, int y, int x, cchar_t *wchstr);
+       int in_wchstr(cchar_t * wchstr);
+       int win_wchstr(WINDOW * win, cchar_t * wchstr);
+       int mvin_wchstr(int y, int x, cchar_t * wchstr);
+       int mvwin_wchstr(WINDOW * win, int y, int x, cchar_t * wchstr);
 
-       int in_wchnstr(cchar_t *wchstr, int n);
-       int win_wchnstr(WINDOW *win, cchar_t *wchstr, int n);
-       int mvin_wchnstr(int y, int x, cchar_t *wchstr, int n);
-       int mvwin_wchnstr(WINDOW *win, int y, int x, cchar_t *wchstr, int n);
+       int in_wchnstr(cchar_t * wchstr, int n);
+       int win_wchnstr(WINDOW * win, cchar_t * wchstr, int n);
+       int mvin_wchnstr(int y, int x, cchar_t * wchstr, int n);
+       int mvwin_wchnstr(WINDOW * win, int y, int x, cchar_t * wchstr, int n)

              DESCRIPTION

              -       These  functions  return  an  array  of  complex  characters in wchstr,
-       starting  at  the  current  cursor  position  in  the   named   window.
-       Attributes (rendition) are stored with the characters.
-
-       The  four  functions  with  n  as  the  last  argument return a leading
-       substring at most n characters long (exclusive of the  trailing  zeroed
-       cchar_t.   Transfer  stops  at  the  end of the current line, or when n
-       characters have been stored at the location referenced by wchstr.
-
-       Constants defined in <curses.h> can be used with the  &  (logical  AND)
-       operator  to  extract  the  character  or  the attribute alone from any
-       position in the wchstr [see getcchar(3x)].
+       win_wchstr  extracts  a  curses  complex character string from a curses
+       window win, starting at the cursor and stopping at the end of the line,
+       and stores it in  wchstr,  terminating  it  with  a  wide  null  curses
+       character.   win_wchnstr  does  the  same,  but copies at most n curses
+       complex  characters  from  win.   A  negative  n  implies   no   limit;
+       win_wchnstr  then  works  like  win_wchstr.   ncurses(3x) describes the
+       variants of these functions.

              RETURN VALUE

              -       Upon successful completion, these functions return OK.  Otherwise, they
-       return ERR.
+       These functions return OK on success and ERR on failure.
 
-       X/Open Curses defines no error conditions.  This implementation returns
-       an error
+       In ncurses, these functions fail if
 
-       o   if the win parameter is null or
+       o   the curses screen has not been initialized,
 
-       o   if the wchstr parameter is null.
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer, or
 
-       Functions prefixed with "mv" first perform cursor movement and fail  if
+       o   wchstr is a null pointer.
+
+       Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.

              NOTES

              -       All routines except win_wchnstr may be macros.
+       All of these functions except win_wchnstr may be implemented as macros.
 
-       Reading  a  line  that  overflows  the  array pointed to by wchstr with
-       in_wchstr, mvin_wchstr, mvwin_wchstr  or  win_wchstr  causes  undefined
-       results.     Therefore,    the   use   of   in_wchnstr,   mvin_wchnstr,
-       mvwin_wchnstr, or win_wchnstr is recommended.
+       Reading a line that overflows the array pointed to by  wchstr  and  its
+       variants   causes   undefined  results.   Instead,  use  the  n-infixed
+       functions with a positive n argument no larger than  the  size  of  the
+       buffer backing wchstr.

              PORTABILITY

              -       X/Open Curses defines no error conditions.  This implementation  checks
-       for null pointers, returning ERR in that case.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+
+

              HISTORY

              +       X/Open  Curses Issue 4 (1995) initially specified these functions.  The
+       System V Interface Definition Version 4 of the same  year  specified  a
+       function  named  winwchstr  (and the usual variants).  This was a later
+       addition to SVr4.x,  not  appearing  in  the  first  SVr4  (1989).   It
+       differed  from X/Open's later win_wchstr in that it took an argument of
+       type pointer-to-chtype instead of pointer-to-cchar_t.

              SEE ALSO

              -       curs_inchstr(3x)  describes comparable functions of the ncurses library
+       curs_inchstr(3x) describes comparable functions of the ncurses  library
        in its non-wide-character configuration.
 
        curses(3x), curs_inwstr(3x), curs_in_wch(3x)
 
-
-
-ncurses 6.5                       2024-04-20                curs_in_wchstr(3x)
+ncurses 6.6                       2025-10-20                curs_in_wchstr(3x)
              diff --git a/doc/html/man/curs_inch.3x.html b/doc/html/man/curs_inch.3x.html index 15bd134..512fe8a 100644 --- a/doc/html/man/curs_inch.3x.html +++ b/doc/html/man/curs_inch.3x.html @@ -1,7 +1,7 @@ -curs_inch 3x 2024-04-20 ncurses 6.5 Library calls +curs_inch 3x 2025-02-15 ncurses 6.6 Library calls -

              curs_inch 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_inch 3x 2025-02-15 ncurses 6.6 Library calls

               curs_inch(3x)                    Library calls                   curs_inch(3x)
 
 
-
-

              NAME

                      inch, winch, mvinch, mvwinch - get a curses character from a window
 
@@ -55,92 +53,78 @@
        #include <curses.h>
 
        chtype inch(void);
-       chtype winch(WINDOW *win);
-
+       chtype winch(WINDOW * win);
        chtype mvinch(int y, int x);
-       chtype mvwinch(WINDOW *win, int y, int x);
+       chtype mvwinch(WINDOW * win, int y, int x);

              DESCRIPTION

              -       These  routines  return  the  character, of type chtype, at the current
-       position in the named window.  If  any  attributes  are  set  for  that
-       position,  their  values  are OR'ed into the value returned.  Constants
-       defined in <curses.h> can be used with the & (logical AND) operator  to
-       extract the character or attributes alone.
-
-
-

              Attributes

              -       The  following  bit  masks  may  be  AND-ed with characters returned by
-       winch.
-
-       Name           Description
-       ------------------------------------------------------------------------
-       A_CHARTEXT     Extract character
-       A_ATTRIBUTES   Extract attributes
-       A_COLOR        Extract color pair information
+       winch  returns the curses character, including its attributes and color
+       pair identifier, at the cursor position in the window win.   Subsection
+       "Video  Attributes"  of  attron(3x)  explains how to extract these data
+       from a chtype.  ncurses(3x) describes the variants of this function.

              RETURN VALUE

              +       These functions return OK on success and ERR on failure.
+
+       In ncurses, they return ERR if win is NULL.
+
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.
 
-       The  winch  function  does  not  return an error if the window contains
-       characters larger than 8-bits (255).  Only the low-order 8 bits of  the
-       character are used by winch.
-

              NOTES

              -       Note that all of these routines may be macros.
+       inch, mvinch, and mvwinch may be implemented as macros.
+
+       These  functions  do  not  fail  if the window contains cells of curses
+       complex characters; that is, if  they  contain  characters  with  codes
+       wider  than  eight  bits  (or  greater  than 255 as an unsigned decimal
+       integer).  They instead extract only the low-order eight  bits  of  the
+       character code from the cell.

              PORTABILITY

              -       These functions are described in X/Open Curses, Issue 4.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       Very  old systems (before standardization) provide a different function
-       with the same name:
 
-       o   The winch function was part of the  original  BSD  curses  library,
-           which   stored   a  7-bit  character  combined  with  the  standout
-           attribute.
+

              HISTORY

              +       The  original  curses in 4BSD (1980) defined winch as a macro accessing
+       the WINDOW structure member representing character cell data,  at  that
+       time  a  char,  containing  only  a  7-bit  ASCII  character code and a
+       "standout" attribute bit, the only one the library supported.
 
-           In BSD curses, winch returned only the character  (as  an  integer)
-           with the standout attribute removed.
-
-       o   System  V  curses  added support for several video attributes which
-           could be combined with characters in the window.
-
-           Reflecting this improvement, the function was altered to return the
-           character combined with all video attributes in a chtype value.
-
-       X/Open Curses does not specify the size and layout of attributes, color
-       and character values in chtype; it is  implementation-dependent.   This
-       implementation  uses 8 bits for character values.  An application using
-       more bits,  e.g.,  a  Unicode  value,  should  use  the  wide-character
-       equivalents to these functions.
+       SVr2 curses (1984) extended this approach, widening the character  code
+       to  eight bits and permitting several attributes to be combined with it
+       by storing them together in a  chtype,  an  alias  of  unsigned  short.
+       Because  a macro was used, its value was not type-checked as a function
+       return value could have been.  Goodheart documented SVr3  (1987)  winch
+       as  returning  an  int.   SVr3.1's  (1987)  chtype  became  an alias of
+       unsigned long, using 16 bits for the character code  and  widening  the
+       type in practical terms to 32 bits, as 64-bit Unix systems were not yet
+       in wide use, and fixed-width integral types would not be standard until
+       ISO  C99.   SVr3.2 (1988) added a 6-bit color pair identifier alongside
+       the attributes.

              SEE ALSO

              -       curs_in_wch(3x)  describes  comparable functions of the ncurses library
+       curs_in_wch(3x) describes comparable functions of the  ncurses  library
        in its wide-character configuration (ncursesw).
 
        curses(3x), curs_instr(3x)
 
-
-
-ncurses 6.5                       2024-04-20                     curs_inch(3x)
+ncurses 6.6                       2025-02-15                     curs_inch(3x)
              diff --git a/doc/html/man/curs_inchstr.3x.html b/doc/html/man/curs_inchstr.3x.html index 1eeb1b3..362f541 100644 --- a/doc/html/man/curs_inchstr.3x.html +++ b/doc/html/man/curs_inchstr.3x.html @@ -1,6 +1,6 @@ -curs_inchstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_inchstr 3x 2025-10-20 ncurses 6.6 Library calls -

              curs_inchstr 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_inchstr 3x 2025-10-20 ncurses 6.6 Library calls

               curs_inchstr(3x)                 Library calls                curs_inchstr(3x)
 
 
-
-

              NAME

                      inchstr,   inchnstr,   winchstr,   winchnstr,   mvinchstr,  mvinchnstr,
        mvwinchstr, mvwinchnstr - get a curses character string from a window
@@ -54,73 +52,85 @@

              SYNOPSIS

                      #include <curses.h>
 
-       int inchstr(chtype *chstr);
-       int inchnstr(chtype *chstr, int n);
-       int winchstr(WINDOW *win, chtype *chstr);
-       int winchnstr(WINDOW *win, chtype *chstr, int n);
+       int inchstr(chtype * chstr);
+       int inchnstr(chtype * chstr, int n);
+       int winchstr(WINDOW * win, chtype * chstr);
+       int winchnstr(WINDOW * win, chtype * chstr, int n);
 
-       int mvinchstr(int y, int x, chtype *chstr);
-       int mvinchnstr(int y, int x, chtype *chstr, int n);
-       int mvwinchstr(WINDOW *win, int y, int x, chtype *chstr);
-       int mvwinchnstr(WINDOW *win, int y, int x, chtype *chstr, int n);
+       int mvinchstr(int y, int x, chtype * chstr);
+       int mvinchnstr(int y, int x, chtype * chstr, int n);
+       int mvwinchstr(WINDOW * win, int y, int x, chtype * chstr);
+       int mvwinchnstr(WINDOW * win, int y, int x, chtype * chstr, int n);

              DESCRIPTION

              -       These routines return a NULL-terminated  array  of  chtype  quantities,
-       starting  at the current cursor position in the named window and ending
-       at the right margin of the window.
-
-       The four functions with n  as  the  last  argument,  return  a  leading
-       substring  at  most  n  characters  long  (exclusive  of  the  trailing
-       (chtype)0).  Transfer stops at the end of the current line, or  when  n
-       characters have been stored at the location referenced by chstr.
-
-       Constants  defined  in  <curses.h> can be used with the & (logical AND)
-       operator to extract the character  or  the  attribute  alone  from  any
-       position in the chstr [see curs_inch(3x)].
+       winchstr extracts a curses character string from a curses  window  win,
+       starting  at the cursor and stopping at the end of the line, and stores
+       it in chstr, terminating it with a null  curses  character.   winchnstr
+       does  the  same,  but  copies  at most n curses characters from win.  A
+       negative n implies  no  limit;  winchnstr  then  works  like  winchstr.
+       ncurses(3x) describes the variants of these functions.

              RETURN VALUE

              -       All  routines  return the integer ERR upon failure and an integer value
-       other than ERR upon successful completion  (the  number  of  characters
-       retrieved, exclusive of the trailing 0).
+       These functions return OK on success and ERR on failure.
 
-       X/Open Curses defines no error conditions.  This implementation returns
-       an error
+       In ncurses, these functions fail if
 
-       o   if the win parameter is null or
+       o   the curses screen has not been initialized,
 
-       o   if the chstr parameter is null.
+       o   (for  functions  taking  a  WINDOW  pointer argument) win is a null
+           pointer, or
+
+       o   chstr is a null pointer.
 
        Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

              NOTES

              -       All routines except winchnstr may be macros.
+       All of these functions except winchnstr may be implemented as macros.
 
-       SVr4 does not document whether the result string is zero-terminated; it
-       does not document whether a length limit argument includes any trailing
-       0; and it does not document the meaning of the return value.
+       Reading  a  line  that  overflows the array pointed to by chstr and its
+       variants  causes  undefined  results.   Instead,  use   the   n-infixed
+       functions  with  a  positive  n argument no larger than the size of the
+       buffer backing chstr.
 
-       Reading  a  line  that  overflows  the  array  pointed to by chstr with
-       inchstr, mvinchstr, mvwinchstr or winchstr  causes  undefined  results.
-       Therefore,  the  use of inchnstr, mvinchnstr, mvwinchnstr, or winchnstr
-       is recommended.
+
+

              EXTENSIONS

              +       inchnstr,  winchnstr,  mvinchnstr,  and  mvwinchnstr's  acceptance   of
+       negative n values is an ncurses extension.

              PORTABILITY

              -       These functions are described in X/Open Curses, Issue 4.  It is no more
-       specific  than  the  SVr4  documentation  on  the  trailing 0.  It does
-       specify that the successful return of the functions is OK.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
+
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions  for  them.   It  characterizes  the strings stored by these
+       functions as containing "at most n elements" from a  window,  but  does
+       not  specify  whether  the  string  stored  by these functions is null-
+       terminated.
+
+       SVr4 does not document whether it null-terminates the curses  character
+       string  it  stores  in  chstr, and does not document whether a trailing
+       null curses character counts toward the length limit n.
+
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+
+
+

              HISTORY

              +       SVr3.1 (1987) introduced these functions.

              SEE ALSO

              -       curses(3x), curs_inch(3x), curs_inwstr(3x), curs_in_wchstr(3x)
+       curs_in_wchstr(3x)   describes  comparable  functions  of  the  ncurses
+       library in its wide-character configuration (ncursesw).
 
+       curses(3x), curs_inch(3x), curs_inwstr(3x)
 
-
-ncurses 6.5                       2024-04-20                  curs_inchstr(3x)
+ncurses 6.6                       2025-10-20                  curs_inchstr(3x)
              diff --git a/doc/html/man/curs_initscr.3x.html b/doc/html/man/curs_initscr.3x.html index 778fc00..9ef40ac 100644 --- a/doc/html/man/curs_initscr.3x.html +++ b/doc/html/man/curs_initscr.3x.html @@ -1,6 +1,6 @@ -curs_initscr 3x 2024-04-20 ncurses 6.5 Library calls +curs_initscr 3x 2025-08-23 ncurses 6.6 Library calls -

              curs_initscr 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_initscr 3x 2025-08-23 ncurses 6.6 Library calls

               curs_initscr(3x)                 Library calls                curs_initscr(3x)
 
 
-
-

              NAME

                      initscr,  newterm,  endwin, isendwin, set_term, delscreen - initialize,
        manipulate, or tear down curses terminal interface
@@ -54,252 +52,297 @@

              SYNOPSIS

                      #include <curses.h>
 
-       WINDOW *initscr(void);
+       WINDOW * initscr(void);
        int endwin(void);
 
        bool isendwin(void);
 
-       SCREEN *newterm(const char *type, FILE *outf, FILE *inf);
-       SCREEN *set_term(SCREEN *new);
-       void delscreen(SCREEN* sp);
+       SCREEN * newterm(const char * type, FILE * outf, FILE * inf);
+       SCREEN * set_term(SCREEN * new);
+       void delscreen(SCREEN * sp);

              DESCRIPTION

              initscr

              -       initscr is normally the first curses routine to call when  initializing
-       a  program.   A few special routines sometimes need to be called before
-       it; these are slk_init(3x), filter, ripoffline, use_env.  For multiple-
-       terminal applications, newterm may be called before initscr.
+       initscr determines the terminal  type  and  initializes  the  library's
+       SCREEN,  WINDOW,  and  other data structures.  It is normally the first
+       curses function call a program performs.  However, an application  with
+       unusual needs might employ a few other curses functions beforehand:
 
-       The  initscr  code  determines  the  terminal  type and initializes all
-       curses  data  structures.   initscr  also  causes  the  first  call  to
-       refresh(3x)  to  clear  the screen.  If errors occur, initscr writes an
-       appropriate error message to standard error  and  exits;  otherwise,  a
-       pointer is returned to stdscr.
+       o   slk_init(3x) to set up soft-label keys;
+
+       o   filter(3x)  if  the  program  is  designed  to operate in a process
+           pipeline;
+
+       o   ripoffline(3x) to reserve up to five lines at the top and/or bottom
+           of the screen  from  management  by  stdscr,  the  standard  curses
+           window; and
+
+       o   use_env(3x)  and/or  use_tioctl(3x) to configure use of the process
+           environment and operating system's terminal  driver,  respectively,
+           when determining the dimensions of the terminal display.
+
+       Further,  a  curses  program  might call newterm prior to or instead of
+       initscr in two specialized cases described in its subsection below.
+
+       initscr causes the first refresh(3x) call  to  clear  the  screen.   If
+       errors  occur,  initscr writes an appropriate diagnostic message to the
+       standard error stream and exits; otherwise, it  returns  a  pointer  to
+       stdscr.

              newterm

              -       A program that outputs to more than one terminal should use the newterm
-       routine for each terminal instead of initscr.  A program that needs  to
-       inspect capabilities, so it can continue to run in a line-oriented mode
-       if the terminal cannot support a screen-oriented  program,  would  also
-       use newterm.
+       An application that manages multiple terminals should call newterm once
+       for each such device instead of initscr.  newterm's arguments are
 
-       The  routine  newterm  should  be  called  once  for each terminal.  It
-       returns a variable of  type  SCREEN  *  which  should  be  saved  as  a
-       reference to that terminal.  newterm's arguments are
+       o   the  type  of the associated terminal, or a null pointer to use the
+           TERM environment variable;
 
-       o   the type of the terminal to be used in place of $TERM,
+       o   an output stream outf connected to the terminal; and
 
-       o   an output stream connected to the terminal, and
+       o   an input stream inf connected to the terminal.
 
-       o   an input stream connected to the terminal
+       newterm returns a variable of pointer-to-SCREEN type, which  should  be
+       saved for later use with set_term and delscreen.
 
-       If the type parameter is NULL, $TERM will be used.
+       newterm passes the file descriptor of the output stream to the terminfo
+       function setupterm(3x), which returns a pointer to a TERMINAL structure
+       that newterm stores in the SCREEN it returns to the application.
 
-       The  file  descriptor  of the output stream is passed to setupterm(3x),
-       which returns a pointer to  a  TERMINAL  structure.   newterm's  return
-       value holds a pointer to the TERMINAL structure.
+       An application that needs to inspect a terminal type's capabilities, so
+       that  it  can  continue  to run in a line-oriented mode if the terminal
+       type does not support capabilities the application demands, would  also
+       use  newterm.   If  at  most  one  terminal  connection  is needed, the
+       programmer could perform such a capability test,  decide  the  mode  in
+       which  to  operate,  then  call  delscreen  on  the pointer returned by
+       newterm, and proceed with either initscr or a non-curses interface.

              endwin

              -       The  program  must also call endwin for each terminal being used before
-       exiting from curses.  If newterm is called more than once for the  same
+       The program must also call endwin for each terminal being  used  before
+       exiting  from curses.  If newterm is called more than once for the same
        terminal, the first terminal referred to must be the last one for which
        endwin is called.
 
-       A program should always call endwin before  exiting  or  escaping  from
-       curses mode temporarily.  This routine
+       A program should always call endwin before exiting the  application  or
+       temporarily suspending curses's management of the terminal.  endwin:
 
-       o   resets colors to correspond with the default color pair 0,
+       o   (if   start_color(3x)   has  been  called)  resets  the  terminal's
+           foreground and background colors to correspond with those of  color
+           pair 0 (the default pair),
 
        o   moves the cursor to the lower left-hand corner of the screen,
 
-       o   clears  the  remainder  of  the  line  so  that it uses the default
-           colors,
+       o   (if  start_color(3x)  has  been  called) restores the default color
+           pair,
+
+       o   clears the line,
 
        o   sets the cursor to normal visibility (see curs_set(3x)),
 
-       o   stops  cursor-addressing  mode  using  the  exit_ca_mode   terminal
-           capability,
+       o   if applicable, stops cursor-addressing mode using the  exit_ca_mode
+           (rmcup) terminal capability, and
 
-       o   restores tty modes (see reset_shell_mode(3x)).
+       o   restores terminal modes (see reset_shell_mode(3x)).
 
-       Calling refresh(3x) or doupdate(3x) after a temporary escape causes the
-       program to resume visual mode.
+       Calling refresh(3x) or doupdate(3x) after a temporary suspension causes
+       curses to resume managing the terminal.

              isendwin

              -       The isendwin routine returns TRUE if endwin has been called without any
-       subsequent calls to wrefresh, and FALSE otherwise.
+       isendwin  returns  TRUE  if  wrefresh(3x) has not been called since the
+       most recent endwin call, and FALSE otherwise.

              set_term

              -       The  set_term  routine  is  used to switch between different terminals.
-       The screen  reference  new  becomes  the  new  current  terminal.   The
-       previous terminal is returned by the routine.  This is the only routine
-       which manipulates SCREEN pointers; all other routines affect  only  the
-       current terminal.
+       set_term re-orients the curses library's operations to another terminal
+       when the application has arranged to manage more than one with newterm.
+       set_term expects a SCREEN pointer previously returned by newterm as  an
+       argument,  and returns the previous one.  set_term is the only standard
+       curses API function that manipulates SCREEN pointers; all others affect
+       only the current terminal (but see curs_sp_funcs(3x)).

              delscreen

              -       The  delscreen  routine  frees  storage associated with the SCREEN data
-       structure.  The endwin routine does not do this, so delscreen should be
-       called after endwin if a particular SCREEN is no longer needed.
+       delscreen  frees  the  storage  backing  the  supplied  SCREEN  pointer
+       argument.   endwin does not, so that an application can resume managing
+       a terminal with curses after  a  (possibly  conditional  or  temporary)
+       suspension;  see  curs_kernel(3x).  Use delscreen after endwin when the
+       application has no more need of a terminal device  but  will  not  soon
+       exit.

              RETURN VALUE

              -       endwin  returns  the  integer  ERR  upon failure and OK upon successful
-       completion.
+       delscreen  returns  no  value.  endwin returns OK on success and ERR on
+       failure.  isendwin returns TRUE or FALSE as described above.
 
-       Routines that return pointers always return NULL on error.
+       In ncurses,
 
-       X/Open defines no error conditions.  In this implementation
+       o   endwin returns ERR if
 
-       o   endwin returns an error if
+           o   the terminal was not initialized,
 
-           o   the terminal was not initialized, or
+           o   it is called more than once without updating the screen, or
 
-           o   endwin is called more than once without updating the screen, or
+           o   its call of reset_shell_mode(3x) returns ERR; and
 
-           o   reset_shell_mode(3x) returns an error.
+       o   newterm returns ERR if it cannot allocate storage  for  the  SCREEN
+           structure  or  the  WINDOW structures automatically associated with
+           it: curscr, newscr, and stdscr.
 
-       o   newterm returns an error if it cannot allocate the data  structures
-           for  the  screen,  or  for the top-level windows within the screen,
-           i.e., curscr, newscr, or stdscr.
+       Functions that return pointers  return  null  pointers  on  error.   In
+       ncurses,  set_term  does not fail, and initscr exits the application if
+       it does not operate successfully.
 
-       o   set_term returns no error.
+
+

              NOTES

              +       ncurses establishes signal handlers when a function that initializes  a
+       SCREEN,  either initscr or newterm, is first called.  Applications that
+       wish to handle the following signals themselves  should  set  up  their
+       corresponding handlers after initializing the screen.
+
+       SIGINT ncurses's  handler  attempts  to  clean  up  the screen on exit.
+              Although it usually works as expected, there are limitations.
+
+              o   Walking the SCREEN list is unsafe, since all list management
+                  is done without any signal blocking.
+
+              o   When an application has been built with the _REENTRANT macro
+                  defined (and corresponding system  support),  set_term  uses
+                  functions that could deadlock or misbehave in other ways.
+
+              o   endwin  calls other functions, many of which use stdio(3) or
+                  other library functions that are clearly unsafe.
+
+       SIGTERM
+              ncurses uses the same handler  as  for  SIGINT,  with  the  same
+              limitations.   It is not mentioned in X/Open Curses, but is more
+              suitable for  this  purpose  than  SIGQUIT  (which  is  used  in
+              debugging).
+
+       SIGTSTP
+              ncurses's  handler  manages  the terminal-generated stop signal,
+              used  in  job  control.   When  resuming  the  process,  ncurses
+              discards  pending  input  with  flushinp(3x)  and  repaints  the
+              screen, assuming that it has been completely altered.   It  also
+              updates the saved terminal modes with def_shell_mode(3x).
+
+       SIGWINCH
+              ncurses  handles  changes  to  the  terminal's  window  size,  a
+              phenomenon  ignored  in  standardization  efforts.   It  sets  a
+              (signal-safe)  variable  that  is later tested by wgetch(3x) and
+              wget_wch(3x).
+
+              o   wgetch returns the key code KEY_RESIZE.
+
+              o   wget_wch returns KEY_CODE_YES and sets its wch parameter  to
+                  KEY_RESIZE.
+
+              At  the  same  time,  ncurses calls resizeterm(3x) to adjust the
+              standard screen stdscr and update global variables such as LINES
+              and COLS.

              PORTABILITY

              -       These functions were described in X/Open Curses, Issue 4.  As of  2015,
-       the current document is X/Open Curses, Issue 7.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.

              Differences

              -       X/Open  Curses  specifies  that  portable  applications  must  not call
-       initscr more than once:
+       X/Open Curses  specifies  that  portable  applications  must  not  call
+       initscr more than once.
 
-       o   The portable way to use initscr is once only, using refresh(3x)  to
-           restore the screen after endwin.
+       o   The  portable  way  to  use  initscr is once only, using refresh to
+           restore the screen after endwin.
 
-       o   This implementation allows using initscr after endwin.
+       o   ncurses permits use of initscr after endwin.
 
-       Old versions of curses, e.g., BSD 4.4, would return a null pointer from
-       initscr when an error is detected, rather than exiting.  It is safe but
-       redundant to check the return value of initscr in X/Open Curses.
+       initscr in BSD, from its inception (1980)  through  the  Net/2  release
+       (1991)  returned  ERR cast to a WINDOW pointer when detecting an error.
+       4.4BSD (1995) instead returned a  null  pointer.   Neither  exited  the
+       application.   It  is  safe  but redundant to check the return value of
+       initscr in X/Open Curses.
 
-       Calling  endwin  does not dispose of the memory allocated in initscr or
-       newterm.  Deleting a SCREEN provides a way to do this:
+       Calling endwin does not dispose of the memory allocated by  initscr  or
+       newterm.  Deleting a SCREEN provides a way to do this.
 
-       o   X/Open Curses does not say what happens to WINDOWs  when  delscreen
-           "frees  storage  associated  with  the  SCREEN"  nor  does the SVr4
-           documentation help, adding that it should be called after endwin if
+       o   X/Open  Curses  does not say what happens to WINDOWs when delscreen
+           "frees storage associated  with  the  SCREEN"  nor  does  the  SVr4
+           documentation help, adding that it should be called after endwin if
            a SCREEN is no longer needed.
 
-       o   However,  WINDOWs are implicitly associated with a SCREEN.  so that
-           it is reasonable to expect delscreen to deal with these.
+       o   However, every WINDOW is implicitly associated with a SCREEN, so it
+           is reasonable to expect delscreen to dispose of them.
 
-       o   SVr4 curses deletes  the  standard  WINDOW  structures  stdscr  and
-           curscr  as  well  as a work area newscr.  SVr4 curses ignores other
-           windows.
+       o   SVr4  deletes  the  standard WINDOW structures stdscr and curscr as
+           well as a work area newscr.  It ignores other windows.
 
        o   Since version 4.0 (1996), ncurses has  maintained  a  list  of  all
            windows  for  each  screen,  using that information to delete those
-           windows when delscreen is called.
+           windows when delscreen is called.
 
-       o   NetBSD copied this feature of ncurses in  2001.   PDCurses  follows
-           the SVr4 model, deleting only the standard WINDOW structures.
+       o   NetBSD copied this feature of ncurses in  2001.   PDCurses  follows
+           the  SVr4  model,  deleting only the standard WINDOW structures and
+           newscr.
 
 
-

              High-level versus Low-level

              -       Different  implementations  may  disagree  regarding  the level of some
-       functions.  For example, SCREEN  (returned  by  newterm)  and  TERMINAL
-       (returned  by  setupterm(3x))  hold  file  descriptors  for  the output
-       stream.  If an application switches screens using set_term, or switches
-       terminals using set_curterm(3x), applications which use the output file
-       descriptor can have different behavior  depending  on  which  structure
-       holds the corresponding descriptor.
+

              High-level versus Low-level Functions

              +       Implementations disagree regarding the level of abstraction  applicable
+       to  a  function or property.  For example, SCREEN (returned by newterm)
+       and TERMINAL (returned by setupterm(3x)) hold file descriptors for  the
+       output  stream.   If an application switches screens using set_term, or
+       switches terminals using set_curterm(3x), applications using the output
+       file descriptor can  behave  differently  depending  on  the  structure
+       holding the corresponding descriptor.
 
-       For example
-
-       o   NetBSD's  baudrate(3x)  function  uses  the descriptor in TERMINAL.
+       o   NetBSD's   baudrate  function  uses  the  descriptor  in  TERMINAL.
            ncurses and SVr4 use the descriptor in SCREEN.
 
        o   NetBSD and ncurses use the descriptor in TERMINAL for terminal  I/O
-           modes,  e.g.,  def_shell_mode(3x),  def_prog_mode(3x).  SVr4 curses
-           uses the descriptor in SCREEN.
+           modes,  e.g., def_shell_mode(3x), def_prog_mode(3x).  SVr4 uses the
+           descriptor in SCREEN.
 
-   Unset TERM Variable
-       If the TERM variable is  missing  or  empty,  initscr  uses  the  value
-       "unknown",  which  normally  corresponds  to  a terminal entry with the
-       generic (gn) capability.  Generic entries are detected by setupterm(3x)
-       and  cannot  be  used for full-screen operation.  Other implementations
-       may handle a missing/empty TERM variable differently.
+
+

              Unset TERM Environment Variable

              +       If the TERM variable is not set in the  environment  or  has  an  empty
+       value,  initscr uses the value "unknown", which normally corresponds to
+       a terminal entry with the generic (gn) capability.  Generic entries are
+       detected by setupterm(3x) and cannot be used for full-screen operation.
+       Other implementations may handle  a  missing  or  empty  TERM  variable
+       differently.

              Signal Handlers

              -       Quoting from X/Open Curses Issue 7, section 3.1.1:
+       Quoting X/Open Curses Issue 7, section 3.1.1:
 
-            Curses implementations may provide for  special  handling  of  the
-            SIGINT,  SIGQUIT,  and  SIGTSTP  signals  if  their disposition is
-            SIG_DFL at the time initscr is called...
+            Curses  implementations  may  provide  for special handling of the
+            SIGINT, SIGQUIT, and  SIGTSTP  signals  if  their  disposition  is
+            SIG_DFL at the time initscr() is called...
 
-            Any special handling for these signals may remain  in  effect  for
+            Any  special  handling  for these signals may remain in effect for
             the  life  of  the  process  or  until  the  process  changes  the
             disposition of the signal.
 
-            None of the Curses functions are required to be safe with  respect
+            None  of the Curses functions are required to be safe with respect
             to signals...
 
-       This  implementation establishes signal handlers during initialization,
-       e.g., initscr or newterm.  Applications which must handle these signals
-       should  set  up  the  corresponding  handlers  after  initializing  the
-       library:
+       Section "NOTES" above discusses ncurses's signal handlers.
 
-       SIGINT
-            The handler attempts to clean up the screen on exit.  Although  it
-            usually works as expected, there are limitations:
 
-            o   Walking  the  SCREEN list is unsafe, since all list management
-                is done without any signal blocking.
+

              HISTORY

              +       4BSD (1980) introduced initscr and endwin.
 
-            o   On systems which  have  REENTRANT  turned  on,  set_term  uses
-                functions which could deadlock or misbehave in other ways.
+       SVr2 (1984) added newterm and set_term.
 
-            o   endwin  calls  other  functions, many of which use stdio(3) or
-                other library functions which are clearly unsafe.
-
-       SIGTERM
-            This uses the same handler as SIGINT, with the  same  limitations.
-            It  is  not  mentioned  in X/Open Curses, but is more suitable for
-            this purpose than SIGQUIT (which is used in debugging).
-
-       SIGTSTP
-            This handles the stop signal, used in job control.  When  resuming
-            the  process,  this  implementation  discards  pending  input with
-            flushinp(3x), and repaints the screen assuming that  it  has  been
-            completely altered.  It also updates the saved terminal modes with
-            def_shell_mode(3x).
-
-       SIGWINCH
-            This handles the window-size changes which  were  ignored  in  the
-            standardization   efforts.    The  handler  sets  a  (signal-safe)
-            variable which is later tested in wgetch(3x).  If keypad has  been
-            enabled  for  the  corresponding  window,  wgetch  returns the key
-            symbol KEY_RESIZE.  At the same time, wgetch calls  resizeterm  to
-            adjust  the  standard screen stdscr, and update other data such as
-            LINES and COLS.
+       SVr3.1 (1987) supplied delscreen and isendwin.

              SEE ALSO

                      curses(3x),    curs_kernel(3x),     curs_refresh(3x),     curs_slk(3x),
        curs_terminfo(3x), curs_util(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                  curs_initscr(3x)
+ncurses 6.6                       2025-08-23                  curs_initscr(3x)
              diff --git a/doc/html/man/curs_inopts.3x.html b/doc/html/man/curs_inopts.3x.html index 149b2b8..8b3c155 100644 --- a/doc/html/man/curs_inopts.3x.html +++ b/doc/html/man/curs_inopts.3x.html @@ -1,7 +1,7 @@ -curs_inopts 3x 2024-04-13 ncurses 6.5 Library calls +curs_inopts 3x 2025-10-04 ncurses 6.6 Library calls -

              curs_inopts 3x 2024-04-13 ncurses 6.5 Library calls

              +

              curs_inopts 3x 2025-10-04 ncurses 6.6 Library calls

               curs_inopts(3x)                  Library calls                 curs_inopts(3x)
 
 
-
-

              NAME

                      cbreak,  echo, halfdelay, intrflush, is_cbreak, is_echo, is_nl, is_raw,
        keypad, meta, nl, nocbreak, nodelay, noecho,  nonl,  noqiflush,  noraw,
@@ -63,24 +61,24 @@
        int echo(void);
        int noecho(void);
 
-       int intrflush(WINDOW *win, bool bf);
-       int keypad(WINDOW *win, bool bf);
-       int meta(WINDOW *win, bool bf);
-       int nodelay(WINDOW *win, bool bf);
-       int notimeout(WINDOW *win, bool bf);
+       int intrflush(WINDOW * win /* ignored */, bool bf);
+       int keypad(WINDOW * win, bool bf);
+       int meta(WINDOW * win /* ignored */, bool bf);
+       int nodelay(WINDOW * win, bool bf);
+       int notimeout(WINDOW * win, bool bf);
 
        int nl(void);
        int nonl(void);
 
-       int raw(void);
-       int noraw(void);
-
        void qiflush(void);
        void noqiflush(void);
 
+       int raw(void);
+       int noraw(void);
+
        int halfdelay(int tenths);
        void timeout(int delay);
-       void wtimeout(WINDOW *win, int delay);
+       void wtimeout(WINDOW * win, int delay);
 
        int typeahead(int fd);
 
@@ -92,174 +90,225 @@

              DESCRIPTION

              -       ncurses provides several functions that let an application  change  the
-       way  input  from the terminal is handled.  Some are global, applying to
-       all windows.  Others apply only to a specific window.   Window-specific
-       settings  are  not automatically applied to new or derived windows.  An
-       application must apply these to each window if  the  same  behavior  is
-       desired.
+       curses offers configurable  parameters  permitting  an  application  to
+       control  the  handling of input from the terminal.  Some, such as those
+       affecting the terminal's mode or line discipline, are global,  applying
+       to  all  windows;  others apply only to a specific window.  The library
+       does not automatically apply such parameters to new or derived windows;
+       an application must configure each window for the desired behavior.
+
+       Some descriptions below make reference to an  input  character  reading
+       function:  this  is wgetch(3x) in the non-wide character curses API and
+       wget_wch(3x) in the wide character API.  In  addition  to  the  variant
+       forms   of   these  described  in  ncurses(3x),  the  curses  functions
+       wgetstr(3x)  and  wget_wstr(3x)  and  their  own  variants   call   the
+       appropriate input character reading function.

              cbreak, nocbreak

              -       Normally,  the terminal driver buffers typed characters until a newline
-       or  carriage  return  is  typed.   The  cbreak  routine  disables  line
-       buffering  and  erase/kill  character-processing  (interrupt  and  flow
-       control characters are unaffected), making characters typed by the user
-       immediately available to the program.  The nocbreak routine returns the
-       terminal to normal (cooked) mode.
+       Normally,  the terminal driver buffers typed characters, not delivering
+       them to an application until a line feed or carriage return  is  typed.
+       This  canonical  ("cooked") line discipline also supports software flow
+       control, simple line editing functions (character and word  erase,  and
+       whole-line  erasure or "kill"), and job control.  cbreak configures the
+       terminal in cbreak mode, which disables line buffering  and  erase  and
+       kill  character  processing  --  the interrupt, quit, suspend, and flow
+       control characters are unaffected -- and makes characters typed by  the
+       user immediately available to the program.  nocbreak restores canonical
+       ("cooked") mode.
 
-       Initially the terminal may or may not be in cbreak mode, as the mode is
-       inherited;   therefore,  a  program  should  call  cbreak  or  nocbreak
-       explicitly.  Most interactive programs  using  curses  set  the  cbreak
-       mode.   Note  that  cbreak  overrides  raw.   [See curs_getch(3x) for a
-       discussion of how these routines interact with echo and noecho.]
+       The  state  of  the terminal is unknown to a curses application when it
+       starts; therefore, a program should call cbreak or nocbreak explicitly.
+       Most interactive programs using curses set cbreak mode.  Calling cbreak
+       overrides raw.  The man page for the input character  reading  function
+       discusses how cbreak and nocbreak interact with echo and noecho.

              echo, noecho

              -       The echo and noecho routines control whether characters  typed  by  the
-       user  are  echoed  by  getch(3x)  as  they  are  typed.  Echoing by the
-       terminal driver is always disabled, but  initially  getch  is  in  echo
-       mode,  so  characters  typed  are  echoed.  Authors of most interactive
-       programs prefer to do their own echoing in a  controlled  area  of  the
-       screen,  or  not  to  echo  at  all, so they disable echoing by calling
-       noecho.  [See curs_getch(3x) for a discussion  of  how  these  routines
-       interact with cbreak and nocbreak.]
+       echo  and  noecho  determine  whether  characters typed by the user are
+       written to the curses window by the input character reading function as
+       they are typed.  curses  always  disables  the  terminal  driver's  own
+       echoing.  By default, a curses screen's echo option is set.  Authors of
+       most  interactive  programs  prefer  to  do  their  own  echoing  in  a
+       controlled area of the screen, or not to echo  at  all,  so  they  call
+       noecho.   The  man  page  for  the  input  character  reading  function
+       discusses how echo and noecho interact with cbreak and nocbreak.

              halfdelay

              -       The  halfdelay routine is used for half-delay mode, which is similar to
-       cbreak mode in that  characters  typed  by  the  user  are  immediately
-       available to the program.  However, after blocking for tenths tenths of
-       seconds, ERR is returned if nothing  has  been  typed.   The  value  of
-       tenths must be a number between 1 and 255.  Use nocbreak to leave half-
+       halfdelay configures half-delay mode, which is similar to  cbreak  mode
+       in  that  characters typed by the user are immediately available to the
+       program.  However, after blocking for tenths  tenth-seconds,  an  input
+       character  reading  function  returns  ERR if no input is pending.  The
+       value of tenths must be between 1 and 255.  Use nocbreak to leave half-
        delay mode.

              intrflush

              -       If the intrflush option is enabled (bf is TRUE), and an  interrupt  key
-       is  pressed on the keyboard (interrupt, break, quit), all output in the
-       terminal driver queue is flushed, giving the effect of faster  response
-       to  the interrupt, but causing curses to have the wrong idea of what is
-       on the screen.  Disabling the option (bf is FALSE), prevents the flush.
-       The  default  for  the  option  is  inherited  from the terminal driver
-       settings.  The win argument is ignored.
+       intrflush calls qiflush (see below) if bf is TRUE, and noqiflush if  bf
+       is FALSE.  It ignores its win argument.

              keypad

              -       The keypad option enables  the  keypad  of  the  user's  terminal.   If
-       enabled  (bf  is  TRUE),  the user can press a function key (such as an
-       arrow key) and wgetch(3x)  returns  a  single  value  representing  the
-       function  key,  as in KEY_LEFT.  If disabled (bf is FALSE), curses does
-       not treat function keys specially and the program has to interpret  the
-       escape  sequences  itself.  If the keypad in the terminal can be turned
-       on (made to transmit) and off (made to work locally), turning  on  this
-       option  causes  the  terminal keypad to be turned on when wgetch(3x) is
-       called.  The default value for keypad is FALSE.
+       keypad  enables  recognition of a terminal's function keys.  If enabled
+       (bf is TRUE) then when an input character reading function  reads  ESC,
+       it  waits for further input corresponding to an escape sequence defined
+       by the terminal type description.  If a valid  sequence  populates  the
+       input  stream,  the  input  character  reading function returns a value
+       representing the function key, such as KEY_LEFT.   (Wide-character  API
+       users:  wget_wch(3x)  returns KEY_CODE_YES to indicate the availability
+       of a function key code in its  wch  parameter.)   If  the  sequence  is
+       invalid,  the  input  character  reading function returns only its last
+       character.  If disabled (bf is FALSE), curses does not  treat  function
+       keys  specially  and  the  program  has  to  interpret escape sequences
+       itself.  If the terminal  type  description  defines  the  keypad_local
+       (rmkx)  and keypad_xmit (smkx) capabilities, enabling a window's keypad
+       mode sets the terminal's keypad to transmit, and disabling keypad  mode
+       sets  the  terminal's  keypad  to work locally.  By default, a window's
+       keypad mode is off.

              meta

              -       Initially, whether the terminal returns 7  or  8  significant  bits  on
-       input  depends  on  the  control  mode  of  the  terminal  driver  [see
-       termios(3)].  To force 8 bits to be returned, invoke  meta(win,  TRUE);
-       this  is  equivalent,  under  POSIX,  to  setting  the  CS8 flag on the
-       terminal.  To force 7 bits to be  returned,  invoke  meta(win,  FALSE);
-       this  is  equivalent,  under  POSIX,  to  setting  the  CS7 flag on the
-       terminal.  The  window  argument,  win,  is  always  ignored.   If  the
-       terminfo  capabilities smm (meta_on) and rmm (meta_off) are defined for
-       the terminal, smm is sent to  the  terminal  when  meta(win,  TRUE)  is
-       called and rmm is sent when meta(win, FALSE) is called.
+       Initially, whether the terminal returns 7- or 8-bit character codes  on
+       input  depends  on  the  configuration of the terminal driver; on POSIX
+       systems, see  termios(3).   To  force  8  bits  to  be  returned,  call
+       meta(...,  TRUE);  this is equivalent, on POSIX systems, to setting the
+       CS8 flag on the terminal.   To  force  7  bits  to  be  returned,  call
+       meta(...,  FALSE); this is equivalent, on POSIX systems, to setting the
+       CS7 flag on the terminal.  curses ignores the window argument win.   If
+       the  terminfo  string capabilities meta_on (smm) and meta_off (rmm) are
+       defined for the terminal type, enabling meta mode sends smm's value  to
+       the terminal and disabling it sends that of rmm to the terminal.

              nl, nonl

              -       The  nl and nonl routines control whether the underlying display device
-       translates the return key into newline on input.
+       Initially,  whether  the  terminal  reports a carriage return using the
+       character code for a line feed in cbreak or raw modes  depends  on  the
+       configuration  of  the  terminal driver; see termios(3).  nl configures
+       the terminal to perform this translation.  nonl disables it.  Under its
+       canonical  ("cooked")  line  discipline,  the  terminal  driver  always
+       translates carriage returns to line feeds.

              nodelay

              -       The nodelay option causes getch to be a non-blocking call.  If no input
-       is  ready,  getch  returns ERR.  If disabled (bf is FALSE), getch waits
-       until a key is pressed.
+       nodelay  configures  the  input  character  reading function to be non-
+       blocking for window win.  If no input is ready,  the  reading  function
+       returns  ERR.  If disabled (bf is FALSE), the reading function does not
+       return until it has input.

              notimeout

              -       When interpreting an escape sequence, wgetch(3x)  sets  a  timer  while
-       waiting  for  the  next  character.  If notimeout(win, TRUE) is called,
-       then wgetch does not set a timer.  The purpose of  the  timeout  is  to
-       distinguish  sequences produced by a function key from those typed by a
-       user.
+       When keypad has been called on a window and the input character reading
+       function reads an ESC character from it,  curses  sets  a  timer  while
+       waiting   for  the  next  character.   If  the  timer  elapses,  curses
+       interprets the ESC as an explicit press of the  terminal's  Escape  key
+       (or  equivalent).   notimeout(win,  TRUE)  disables  this  timer.   The
+       purpose of the timeout  is  to  distinguish  sequences  produced  by  a
+       function  key  from  those typed by a user.  If this timer is disabled,
+       curses waits forever for subsequent keystrokes until it determines  the
+       escape sequence to be valid or invalid.
+
+
+

              qiflush, noqiflush

              +       qiflush  and noqiflush configure the terminal driver's treatment of its
+       input and output queues when it handles the interrupt, suspend, or quit
+       characters under the canonical ("cooked") or cbreak line disciplines on
+       POSIX systems; see termios(3).  The default behavior is inherited  from
+       the  terminal driver settings.  Calling qiflush configures the terminal
+       to flush the queues (discarding  their  contents)  when  any  of  these
+       events  occurs, giving the impression of faster response to user input,
+       but making the  library's  model  of  the  screen  contents  incorrect.
+       Calling noqiflush prevents such flushing, but might frustrate impatient
+       users  on  slow  connections  if  a  curses  update of the screen is in
+       progress when the event occurs; see typeahead below for a mitigation of
+       this problem.  You may want to call noqiflush in a signal  handler  if,
+       after  the  handler  exits,  you  want output to continue as though the
+       signal had not occurred.

              raw, noraw

              -       The raw and noraw routines place the terminal into or out of raw  mode.
-       Raw  mode  is  similar  to  cbreak  mode,  in that characters typed are
-       immediately passed through to the user program.   The  differences  are
-       that  in  raw  mode,  the  interrupt,  quit,  suspend, and flow control
-       characters are all passed through uninterpreted, instead of  generating
-       a  signal.   The behavior of the BREAK key depends on other bits in the
-       terminal driver that are not set by curses.
-
-
-

              qiflush, nqiflush

              -       When the noqiflush routine is used, normal flush of  input  and  output
-       queues  associated  with the INTR, QUIT and SUSP characters will not be
-       done [see termios(3)].  When qiflush is  called,  the  queues  will  be
-       flushed  when  these control characters are read.  You may want to call
-       noqiflush in a signal handler if you want output to continue as  though
-       the interrupt had not occurred, after the handler exits.
+       raw configures the terminal to read input in raw mode, which is similar
+       to cbreak mode (see cbreak above) except  that  it  furthermore  passes
+       through  the  terminal's  configured interrupt, quit, suspend, and flow
+       control  characters  uninterpreted  to  the  application,  instead   of
+       generating  a  signal  or  acting  on  I/O  flow.   The behavior of the
+       terminal's  "Break"  key  (if   any)   depends   on   terminal   driver
+       configuration  parameters  that curses does not handle.  noraw restores
+       the terminal's canonical ("cooked") line discipline.

              timeout, wtimeout

              -       The timeout and wtimeout routines set blocking or non-blocking read for
-       a given window.  If delay is negative, a blocking read is  used  (i.e.,
-       waits  indefinitely  for input).  If delay is zero, then a non-blocking
-       read is used (i.e., read returns ERR if no input is waiting).  If delay
-       is  positive,  then read blocks for delay milliseconds, and returns ERR
-       if there is still no input.  Hence, these  routines  provide  the  same
-       functionality  as nodelay, plus the additional capability of being able
-       to block for only delay milliseconds (where delay is positive).
+       wtimeout configures whether a curses input character  reading  function
+       called  on window win uses blocking or non-blocking reads.  If delay is
+       negative, curses uses a blocking read, waiting indefinitely for  input.
+       If  delay is zero, the read is non-blocking; an input character reading
+       function returns ERR if no input is pending.  If delay is positive,  an
+       input  character  reading  function  blocks for delay milliseconds, and
+       returns ERR if the delay elapses and there is still no  input  pending.
+       timeout calls wtimeout on stdscr.

              typeahead

              -       curses does  "line-breakout  optimization"  by  looking  for  typeahead
-       periodically  while  updating the screen.  If input is found, and it is
-       coming  from  a  terminal,  the  current  update  is  postponed   until
-       refresh(3x)  or  doupdate is called again.  This allows faster response
-       to commands typed in advance.  Normally, the input FILE pointer  passed
-       to newterm, or stdin in the case that initscr was used, will be used to
-       do this typeahead checking.  The typeahead routine specifies  that  the
-       file descriptor fd is to be used to check for typeahead instead.  If fd
-       is -1, then no typeahead checking is done.
+       Normally,  a curses library checks the terminal's input file descriptor
+       for activity with poll(2) or select(2) while updating the screen; if it
+       finds  any,  it  postpones  output  until  the  next  wrefresh(3x)   or
+       doupdate(3x)  call,  allowing faster response to user key strokes.  The
+       library tests the file descriptor  corresponding  to  the  FILE  stream
+       pointer passed to newterm(3x) (or stdin if initscr(3x) was called), for
+       pending  input.   typeahead instructs curses to test file descriptor fd
+       instead.  An fd of -1 disables the check.

              RETURN VALUE

              -       All routines that return an integer return  ERR  upon  failure  and  OK
-       (SVr4 specifies only "an integer value other than ERR") upon successful
-       completion,  unless  otherwise   noted   in   the   preceding   routine
-       descriptions.
+       timeout and wtimeout return no value.
 
-       X/Open   Curses  does  not  specify  any  error  conditions.   In  this
-       implementation, functions with a window parameter will return an  error
-       if  it is null.  Any function will also return an error if the terminal
-       was not initialized.  Also,
+       cbreak, nocbreak, echo, noecho,  halfdelay,  intrflush,  keypad,  meta,
+       nodelay,  notimeout,  nl,  nonl, raw, noraw, and typeahead return OK on
+       success and ERR on failure.
 
-          halfdelay
-               returns an error if its parameter is outside the range 1..255.
+       In ncurses, the functions in the previous paragraph return ERR if
+
+       o   the library's TERMINAL  structure  for  the  device  has  not  been
+           initialized with initscr(3x), newterm(3x), or setupterm(3x), or
+
+       o   win is a null pointer (except with intrflush and meta, which ignore
+           its value).
+
+       Further, halfdelay returns ERR if delay is outside the range 1..255.
+
+       See  section  "EXTENSIONS"  below  for  the return values of is_cbreak,
+       is_echo, is_nl, and is_raw.

              NOTES

                      echo, noecho, halfdelay, intrflush, meta, nl, nonl, nodelay, notimeout,
        noqiflush, qiflush, timeout, and wtimeout may be implemented as macros.
 
-       noraw  and  nocbreak follow historical practice in that they attempt to
-       restore normal ("cooked") mode from raw and cbreak modes  respectively.
-       Mixing  raw/noraw  and  cbreak/nocbreak  calls leads to terminal driver
-       control states that are hard to predict or understand; doing so is  not
-       recommended.
+       noraw and nocbreak follow historical practice in that they  attempt  to
+       restore  the  terminal's  canonical ("cooked") line discipline from raw
+       and cbreak, respectively.  Mixing raw/noraw calls with  cbreak/nocbreak
+       calls  leads to terminal driver control states that are hard to predict
+       or understand; doing so is not recommended.
+
+       curses documentation uses the terms "delay"  and  "timeout"  freely  to
+       describe  two  related  but  distinct aspects of input handling, at the
+       risk of confusing the user.  The functions halfdelay, nodelay, timeout,
+       and wtimeout configure whether the  input  character  reading  function
+       (wgetch(3x) or wget_wch(3x)) waits for keyboard input to begin, and for
+       how  long.   keypad  configures whether that function waits for further
+       input if the first character it reads is ESC.  Calling notimeout, which
+       has nothing to do  with  timeout  or  wtimeout,  makes  this  delay  in
+       expectation  of further characters effectively infinite.  X/Open Curses
+       affords no means of otherwise configuring the  length  of  this  second
+       delay, but an AIX and ncurses extension, ESCDELAY, is available both as
+       an  environment  variable  and  a global symbol permitting the user and
+       application,   respectively,   to   do   so;   see   ncurses(3x)    and
+       curs_variables(3x).

              EXTENSIONS

              -       ncurses provides four "is_" functions that may be used to detect if the
-       corresponding flags were set or reset.
+       ncurses  provides  four  "is_" functions corresponding to cbreak, echo,
+       nl, and raw, permitting their states to be queried by the application.
 
                             Query       Set      Reset
                             ------------------------------
@@ -270,86 +319,100 @@
 
        In each case, the function returns
 
-       1   if the flag is set,
+       1    if the option is set,
 
-       0   if the flag is reset, or
+       0    if the option is unset, or
 
-       -1  if the library is not initialized.
-
-       They were designed for ncurses(3x), and are not found in  SVr4  curses,
-       4.4BSD curses, or any other previous curses implementation.
+       -1   if the library's TERMINAL structure for the device  has  not  been
+            initialized.

              PORTABILITY

                      Applications employing ncurses extensions should condition their use on
        the visibility of the NCURSES_VERSION preprocessor macro.
 
-       Except as noted in section "EXTENSIONS" above, X/Open Curses, Issue  4,
-       Version 2 describes these functions.
+       Except  as  noted  in section "EXTENSIONS" above, X/Open Curses Issue 4
+       describes these functions.  It specifies no error conditions for them.
 
-       ncurses  follows  X/Open  Curses  and  the  historical practice of AT&T
-       curses implementations, in that the echo bit  is  cleared  when  curses
-       initializes   the  terminal  state.   BSD  curses  differed  from  this
-       slightly; it left the echo bit on at initialization, but  the  BSD  raw
-       call turned it off as a side effect.  For best portability, set echo or
-       noecho explicitly just  after  initialization,  even  if  your  program
-       remains in cooked mode.
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
 
-       X/Open  Curses  is  ambiguous  regarding whether raw should disable the
-       CR/LF translations controlled by nl and nonl.  BSD curses did turn  off
-       these  translations;  AT&T  curses  (at least as late as SVr1) did not.
-       ncurses does so, on the assumption that  a  programmer  requesting  raw
-       input  wants  a  clean  (ideally,  8-bit  clean)  connection  that  the
+       ncurses  follows  X/Open Curses and the historical practice of System V
+       curses, clearing the terminal driver's "echo"  flag  when  initializing
+       the  screen.  BSD curses did not, but its raw function turned it off as
+       a side effect.  For best portability, call echo  or  noecho  explicitly
+       just  after initialization, even if your program retains the terminal's
+       canonical ("cooked") line discipline.
+
+       X/Open Curses is ambiguous regarding whether  raw  should  disable  the
+       carriage  return and line feed translation feature controlled by nl and
+       nonl.  BSD curses turned off these translations;  System V  curses  did
+       not.   ncurses  does so, on the assumption that a programmer requesting
+       raw input wants a clean (ideally,  8-bit  clean)  connection  that  the
        operating system will not alter.
 
-       When keypad is first enabled, ncurses loads the key definitions for the
-       current  terminal  description.   If  the terminal description includes
-       extended string capabilities, e.g., from using the -x  option  of  tic,
-       then  ncurses  also defines keys for the capabilities whose names begin
-       with "k".  The corresponding keycodes are generated and  (depending  on
-       previous  loads of terminal descriptions) may differ from one execution
-       of a program to the next.  The generated keycodes are recognized by the
-       keyname(3x)  function (which will then return a name beginning with "k"
-       denoting the terminfo capability name rather than "K", used for  curses
-       key  names).   On the other hand, an application can use define_key(3x)
-       to establish a specific keycode for a  given  string.   This  makes  it
-       possible  for  an  application  to  check  for an extended capability's
-       presence with tigetstr, and reassign  the  keycode  to  match  its  own
-       needs.
+       When  keypad  is first enabled for a window, ncurses loads the standard
+       function key string capabilities for the terminal type  description  of
+       its  screen;  see the entries beginning with "key_" in terminfo(5).  If
+       that description includes extended string capabilities, produced by the
+       -x option of tic(1), for example, then ncurses also  defines  keys  for
+       the  capabilities  whose  codes  begin  with  "k".  ncurses generates a
+       numeric key code  for  each  such  extended  capability;  depending  on
+       previous loads of terminal type descriptions, these may differ from one
+       execution  of  a  program  to  the  next.   keyname(3x)  recognizes the
+       generated key codes and returns a name beginning with "k" denoting  the
+       terminfo capability name rather than "KEY_", used for curses key names.
+       On  the  other  hand,  an  application can use define_key(3x) to bind a
+       selected key to a string of  the  programmer's  choice.   This  feature
+       enables an application to check for its presence with tigetstr(3x), and
+       reassign the numeric key code to match its own needs.
 
-       Low-level applications can use tigetstr to obtain the definition of any
-       particular string capability.  Higher-level applications which use  the
-       curses  wgetch  and  similar functions to return keycodes rely upon the
-       order in which the strings are loaded.  If more than one key definition
-       has  the  same  string  value, then wgetch can return only one keycode.
-       Most curses implementations (including ncurses) load key definitions in
-       the  order  defined  by the array of string capability names.  The last
-       key to be loaded determines the keycode which  will  be  returned.   In
-       ncurses,  you  may  also  have extended capabilities interpreted as key
-       definitions.  These are loaded after the  predefined  keys,  and  if  a
-       capability's  value  is the same as a previously-loaded key definition,
-       the later definition is the one used.
+       Low-level applications can use tigetstr(3x) to obtain the definition of
+       any  string  capability.   curses  applications use the input character
+       reading function to obtain key codes from input and rely upon the order
+       in which the string capabilities are loaded.  Multiple  key  capability
+       strings  can  have  the  same  value,  but  the input character reading
+       function can report only one key  code.   Most  curses  implementations
+       (including  ncurses)  load  key definitions in the order they appear in
+       the strfnames array of string capability names; see term_variables(3x).
+       The last capability read using a particular definition  determines  the
+       key  code  to  be  reported.   In ncurses, extended capabilities can be
+       interpreted as key definitions.  The  library  loads  these  after  its
+       built-in definitions, and if an extended capability's value is the same
+       as one previously loaded, the library uses the later definition.

              HISTORY

              -       Formerly, ncurses used  nl  and  nonl  to  control  the  conversion  of
+       4BSD (1980) introduced echo, noecho, nl, nonl, raw, and noraw.
+
+       SVr2 (1984) featured a new terminal driver, extending the curses API to
+       support it with cbreak, nocbreak, intrflush, keypad, meta, nodelay, and
+       typeahead.
+
+       SVr3  (1987)  added  halfdelay,  notimeout,  and wtimeout.  qiflush and
+       noqiflush appeared in SVr3.1 (1987), at which point intrflush became  a
+       wrapper  for  either  of these functions, depending on the value of its
+       Boolean argument.  SVr3.1 also added timeout.
+
+       ncurses 6.5 (2024) introduced is_cbreak, is_echo, is_nl, and is_raw.
+
+       Formerly, ncurses used  nl  and  nonl  to  control  the  conversion  of
        newlines  to  carriage  return/line  feed  on  output as well as input.
        X/Open Curses documents the use of  these  functions  only  for  input.
        This  difference arose from converting the pcurses source (1986), which
        used ioctl(2) calls and the sgttyb structure,  to  termios  (the  POSIX
-       terminal  API).   In  the former, both input and output were controlled
-       via a single option CRMOD, while the latter separates  these  features.
-       Because  that  conversion  interferes with output optimization, ncurses
-       6.2 (2020) amended nl and nonl to eliminate their effect on output.
+       terminal  API).   In the former, both input and output conversions were
+       controlled via a single option  "CRMOD",  while  the  latter  separates
+       these   features.   Because  that  conversion  interferes  with  output
+       optimization, ncurses 6.2 (2020) amended nl and nonl to eliminate their
+       effect on output.

              SEE ALSO

                      curses(3x),    curs_getch(3x),     curs_initscr(3x),     curs_util(3x),
-       define_key(3x), termios(3)
+       define_key(3x), termios(3), term_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-13                   curs_inopts(3x)
+ncurses 6.6                       2025-10-04                   curs_inopts(3x)
              diff --git a/doc/html/man/curs_ins_wch.3x.html b/doc/html/man/curs_ins_wch.3x.html index 7c25b2e..9f087ce 100644 --- a/doc/html/man/curs_ins_wch.3x.html +++ b/doc/html/man/curs_ins_wch.3x.html @@ -1,6 +1,6 @@ -curs_ins_wch 3x 2024-04-20 ncurses 6.5 Library calls +curs_ins_wch 3x 2025-10-20 ncurses 6.6 Library calls -

              curs_ins_wch 3x 2024-04-20 ncurses 6.5 Library calls

              +

              curs_ins_wch 3x 2025-10-20 ncurses 6.6 Library calls

               curs_ins_wch(3x)                 Library calls                curs_ins_wch(3x)
 
 
-
-

              NAME

              -       ins_wch,  mvins_wch,  mvwins_wch,  wins_wch  -  insert a curses complex
+       ins_wch,  wins_wch,  mvins_wch,  mvwins_wch  -  insert a curses complex
        character in a window

              SYNOPSIS

                      #include <curses.h>
 
-       int ins_wch(const cchar_t *wch);
-       int wins_wch(WINDOW *win, const cchar_t *wch);
-       int mvins_wch(int y, int x, const cchar_t *wch);
-       int mvwins_wch(WINDOW *win, int y, int x, const cchar_t *wch);
+       int ins_wch(const cchar_t * wch);
+       int wins_wch(WINDOW * win, const cchar_t * wch);
+       int mvins_wch(int y, int x, const cchar_t * wch);
+       int mvwins_wch(WINDOW * win, int y, int x, const cchar_t * wch);

              DESCRIPTION

              -       These functions insert the curses complex character wch at  the  cursor
-       in  the  specified window win (or stdscr).  The character previously at
-       the cursor and any to its  right  move  one  cell  to  the  right;  the
-       rightmost  character  on  the  line  is discarded.  The cursor does not
-       advance.
+       wins_wch inserts  the  curses  complex  character  wch  at  the  cursor
+       position in the window win.  The character previously at the cursor and
+       any  to  its  right  move one cell to the right; the formerly rightmost
+       character on the line is discarded.  Unlike add_wch(3x), wins_wch  does
+       not  advance  the  cursor.   ncurses(3x) describes the variants of this
+       function.

              RETURN VALUE

                      These functions return OK on success and ERR on failure.
 
-       Functions taking a WINDOW pointer argument fail if the pointer is NULL.
+       In ncurses, they return ERR if
 
-       Functions prefixed with "mv" first perform cursor movement and fail  if
+       o   the curses screen has not been initialized, or
+
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer.
+
+       Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.

              NOTES

              -       A  terminal's  insert_character  (ich1)  capability  is not necessarily
-       employed.
-
        ins_wch, mvins_wch, and mvwins_wch may be implemented as macros.
 
+       curses does not  necessarily  employ  the  terminal's  insert_character
+       (ich1) capability to achieve insertion.
+

              PORTABILITY

              -       X/Open Curses, Issue 4 describes these functions.
-
-       SVr4 describes successful return values only as "an integer value other
-       than ERR".
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.

              HISTORY

              -       SVr4  (1989)  implemented  these  functions  under  the  names  inswch,
-       winswch, mvinswch, and mvwinswch.
+       X/Open  Curses Issue 4 (1995) initially specified these functions.  The
+       System V Interface Definition Version 4 of the same  year  specified  a
+       function  named  winswch  (and  the  usual variants).  This was a later
+       addition to SVr4.x,  not  appearing  in  the  first  SVr4  (1989).   It
+       differed  from  X/Open's  later wins_wch in that it took an argument of
+       type chtype instead of cchar_t.

              SEE ALSO

              @@ -102,9 +108,7 @@
 
        curses(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-04-20                  curs_ins_wch(3x)
+ncurses 6.6                       2025-10-20                  curs_ins_wch(3x)
                diff --git a/doc/html/man/curs_ins_wstr.3x.html b/doc/html/man/curs_ins_wstr.3x.html index f2982ea..c6f9e46 100644 --- a/doc/html/man/curs_ins_wstr.3x.html +++ b/doc/html/man/curs_ins_wstr.3x.html @@ -1,6 +1,6 @@ -curs_ins_wstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_ins_wstr 3x 2025-03-01 ncurses 6.6 Library calls -

                curs_ins_wstr 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_ins_wstr 3x 2025-03-01 ncurses 6.6 Library calls

                 curs_ins_wstr(3x)                Library calls               curs_ins_wstr(3x)
 
 
-
-

                NAME

                -       ins_wstr,  ins_nwstr,  wins_wstr,  wins_nwstr, mvins_wstr, mvins_nwstr,
-       mvwins_wstr, mvwins_nwstr - insert a wide-character string in a  curses
+       ins_wstr,  wins_wstr,  mvins_wstr,  mvwins_wstr, ins_nwstr, wins_nwstr,
+       mvins_nwstr, mvwins_nwstr - insert a wide-character string in a  curses
        window

                SYNOPSIS

                        #include <curses.h>
 
-       int ins_wstr(const wchar_t *wstr);
-       int ins_nwstr(const wchar_t *wstr, int n);
-       int wins_wstr(WINDOW *win, const wchar_t *wstr);
-       int wins_nwstr(WINDOW *win, const wchar_t *wstr, int n);
+       int ins_wstr(const wchar_t * wstr);
+       int wins_wstr(WINDOW * win, const wchar_t * wstr);
+       int mvins_wstr(int y, int x, const wchar_t * wstr);
+       int mvwins_wstr(WINDOW * win, int y, int x,
+             const wchar_t * wstr);
 
-       int mvins_wstr(int y, int x, const wchar_t *wstr);
-       int mvins_nwstr(int y, int x, const wchar_t *wstr, int n);
-       int mvwins_wstr(WINDOW *win, int y, int x, const wchar_t *wstr);
-       int mvwins_nwstr(WINDOW *win, int y, int x, const wchar_t *wstr, int n);
+       int ins_nwstr(const wchar_t * wstr, int n);
+       int wins_nwstr(WINDOW * win, const wchar_t * wstr, int n);
+       int mvins_nwstr(int y, int x, const wchar_t * wstr, int n);
+       int mvwins_nwstr(WINDOW * win, int y, int x,
+             const wchar_t * wstr, int n);

                DESCRIPTION

                -       These routines insert a wchar_t character string (as many characters as
-       will fit on the line) before the character  under  the  cursor,  as  if
-       calling  wins_wch(3x).   All  characters to the right of the cursor are
-       shifted right, with the possibility of the rightmost characters on  the
-       line being lost.  No wrapping is performed.
-
-       The  cursor  position  does  not  change  (after  moving  to  y,  x, if
-       specified).
-
-       The functions with n as the last argument insert a leading substring of
-       at  most  n  wchar_t  characters.   If  n is less than zero, the entire
-       string is inserted (stopping on a L'\0' character).
-
-       Special characters are handled as in wadd_wch(3x).
+       wins_wstr  inserts a wide-character string wstr before the character at
+       the cursor in window win as if by calling wins_wch(3x) for each wchar_t
+       in wstr.  No line wrapping is performed.  Characters to  the  right  of
+       the cursor are shifted right; those at the right edge of the window may
+       be  lost.   wins_wstr  stops  inserting if it would have to wrap to the
+       next line to write the next wchar_t in wstr.  The cursor position  does
+       not change (after moving to (y, x), if specified).  wins_nwstr does the
+       same, but inserts at most n wide characters, or as many as possible (up
+       to  the  end  of the line) if n is negative.  ncurses(3x) describes the
+       variants of these functions.

                RETURN VALUE

                -       All functions return the integer ERR upon failure and OK on success.
+       These functions return OK on success and ERR on failure.
 
-       X/Open  Curses  does  not   specify   any   error   conditions.    This
-       implementation returns an error
+       In ncurses, they return ERR if
 
-       o   if the win parameter is null or
+       o   win is NULL,
 
-       o   if the wstr parameter is null or
+       o   wstr is NULL,
 
-       o   if the wins_wch function returns an error.
+       o   the first wide character in wstr is a non-spacing character, or
 
-       Functions  prefixed with "mv" first perform cursor movement and fail if
+       o   an internal wins_wch(3x) call returns ERR.
+
+       Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

                NOTES

                -       All but wins_nwstr may be macros.
+       All of these functions except wins_nwstr may be implemented as macros.
 
-       If the first character in the string is a non-spacing character,  these
-       functions will fail.  X/Open Curses does not define what will happen if
-       a non-spacing character follows a control character.
+
+

                EXTENSIONS

                +       ins_nwstr,  wins_nwstr,  mvins_nwstr,  and mvwins_nwstr's acceptance of
+       negative n values is an ncurses extension.

                PORTABILITY

                -       These functions are described in X/Open Curses,  Issue  4,  which  adds
-       const qualifiers to the arguments.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
-       X/Open  states  that the entire string is inserted if n is less than 1.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       X/Open Curses does not specify what happens if a non-spacing  character
+       follows a control character.
+
+       Issue 4  states that the entire string is inserted if n is less than 1.
        This is probably an  error,  because  it  is  inconsistent  with  other
-       functions, and differs from the X/Open implementation on Solaris.
+       functions  such  as  waddwstr,  and  differs  from  the SVr4 curses and
+       Solaris xcurses implementations.   Nevertheless,  Issue 7  retains  the
+       language.
+
+
+

                HISTORY

                +       X/Open  Curses Issue 4 (1995) initially specified these functions.  The
+       System V Interface Definition  Version 4  (1995),  specified  functions
+       named  winswstr  and  winsnwstr  (and  the usual variants).  These were
+       later additions to SVr4.x, not appearing  in  the  first  SVr4  (1989).
+       They  differ from X/Open's later wins_wstr and wins_nwstr in that their
+       wstr parameters are not const-qualified.

                SEE ALSO

                -       curs_insstr(3x)  describes  comparable functions of the ncurses library
+       curs_insstr(3x) describes comparable functions of the  ncurses  library
        in its non-wide-character configuration.
 
        curses(3x), curs_ins_wch(3x), curs_in_wch(3x)
 
-
-
-ncurses 6.5                       2024-04-20                 curs_ins_wstr(3x)
+ncurses 6.6                       2025-03-01                 curs_ins_wstr(3x)
                diff --git a/doc/html/man/curs_insch.3x.html b/doc/html/man/curs_insch.3x.html index 5f60c67..6c732a5 100644 --- a/doc/html/man/curs_insch.3x.html +++ b/doc/html/man/curs_insch.3x.html @@ -1,6 +1,6 @@ -curs_insch 3x 2024-04-20 ncurses 6.5 Library calls +curs_insch 3x 2025-03-08 ncurses 6.6 Library calls -

                curs_insch 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_insch 3x 2025-03-08 ncurses 6.6 Library calls

                 curs_insch(3x)                   Library calls                  curs_insch(3x)
 
 
-
-

                NAME

                        insch,  winsch,  mvinsch,  mvwinsch  -  insert  a curses character in a
        window
@@ -55,22 +53,28 @@
        #include <curses.h>
 
        int insch(chtype ch);
-       int winsch(WINDOW *win, chtype ch);
+       int winsch(WINDOW * win, chtype ch);
        int mvinsch(int y, int x, chtype ch);
-       int mvwinsch(WINDOW *win, int y, int x, chtype ch);
+       int mvwinsch(WINDOW * win, int y, int x, chtype ch);

                DESCRIPTION

                -       These functions insert the curses character ch at  the  cursor  in  the
-       specified  window  win  (or  stdscr).   The character previously at the
-       cursor and any to its right move one cell to the right;  the  rightmost
-       character on the line is discarded.  The cursor does not advance.
+       winsch inserts the curses character ch at the cursor  position  in  the
+       window  win.   The  character  previously  at the cursor and any to its
+       right move one cell to the right; the formerly rightmost  character  on
+       the  line  is discarded.  Unlike addch(3x), winsch does not advance the
+       cursor.  ncurses(3x) describes the variants of this function.

                RETURN VALUE

                        These functions return OK on success and ERR on failure.
 
-       Functions taking a WINDOW pointer argument fail if the pointer is NULL.
+       In ncurses, they return ERR if
+
+       o   the curses screen has not been initialized, or
+
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer.
 
        Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.
@@ -79,15 +83,20 @@

                NOTES

                        insch, mvinsch, and mvwinsch may be implemented as macros.
 
-       A terminal's insert_character  (ich1)  capability  is  not  necessarily
-       employed.
+       curses does not  necessarily  employ  the  terminal's  insert_character
+       (ich1) capability to achieve insertion.

                PORTABILITY

                -       X/Open Curses, Issue 4 describes these functions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       SVr4  curses  describes  a  successful return value only as "an integer
-       value other than ERR".
+       SVr4  describes  a  successful  return  value only as "an integer value
+       other than ERR".
+
+
+

                HISTORY

                +       SVr2 (1984) introduced these functions.

                SEE ALSO

                @@ -96,9 +105,7 @@
 
        curses(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_insch(3x)
+ncurses 6.6                       2025-03-08                    curs_insch(3x)
                diff --git a/doc/html/man/curs_insstr.3x.html b/doc/html/man/curs_insstr.3x.html index 04e0239..8f3eb19 100644 --- a/doc/html/man/curs_insstr.3x.html +++ b/doc/html/man/curs_insstr.3x.html @@ -1,6 +1,6 @@ -curs_insstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_insstr 3x 2025-10-20 ncurses 6.6 Library calls -

                curs_insstr 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_insstr 3x 2025-10-20 ncurses 6.6 Library calls

                 curs_insstr(3x)                  Library calls                 curs_insstr(3x)
 
 
-
-

                NAME

                -       insstr,  insnstr,  winsstr,  winsnstr,  mvinsstr, mvinsnstr, mvwinsstr,
+       insstr,  winsstr,  mvinsstr,  mvinsnstr,  insnstr, winsnstr, mvwinsstr,
        mvwinsnstr - insert a string in a curses window

                SYNOPSIS

                        #include <curses.h>
-       int insstr(const char *str);
-       int insnstr(const char *str, int n);
-       int winsstr(WINDOW *win, const char *str);
-       int winsnstr(WINDOW *win, const char *str, int n);
 
-       int mvinsstr(int y, int x, const char *str);
-       int mvinsnstr(int y, int x, const char *str, int n);
-       int mvwinsstr(WINDOW *win, int y, int x, const char *str);
-       int mvwinsnstr(WINDOW *win, int y, int x, const char *str, int n);
+       int insstr(const char * str);
+       int winsstr(WINDOW * win, const char * str);
+       int mvinsstr(int y, int x, const char * str);
+       int mvwinsstr(WINDOW * win, int y, int x, const char * str);
+
+       int insnstr(const char * str, int n);
+       int winsnstr(WINDOW * win, const char * str, int n);
+       int mvinsnstr(int y, int x, const char * str, int n);
+       int mvwinsnstr(WINDOW * win, int y, int x, const char * str, int n);

                DESCRIPTION

                -       These routines insert a character string (as many  characters  as  will
-       fit  on  the line) before the character under the cursor, as if calling
-       winsch(3x).  All characters to the right  of  the  cursor  are  shifted
-       right,  with  the  possibility  of the rightmost characters on the line
-       being lost.  No wrapping is performed.
-
-       The cursor  position  does  not  change  (after  moving  to  y,  x,  if
-       specified).
-
-       The functions with n as the last argument insert a leading substring of
-       at most n characters.  If n is less than zero,  the  entire  string  is
-       inserted (stopping on a NUL character).
-
-       Special characters are handled as in waddch(3x).
+       winsstr inserts a string str before the  character  at  the  cursor  in
+       window  win  as if by calling winsch(3x) for each char in str.  No line
+       wrapping is performed.  Characters to  the  right  of  the  cursor  are
+       shifted  right;  those  at  the  right  edge of the window may be lost.
+       winsstr stops inserting if it would have to wrap to the  next  line  to
+       write the next char in str.  The cursor position does not change (after
+       moving to (y, x), if specified).  insnstr does the same, but inserts at
+       most  n  characters, or as many as possible (up to the end of the line)
+       if  n  is  negative.   ncurses(3x)  describes  the  variants  of  these
+       functions.

                RETURN VALUE

                -       All functions return the integer ERR upon failure and OK on success.
+       These functions return OK on success and ERR on failure.
 
-       X/Open   Curses   does   not   specify   any  error  conditions.   This
-       implementation returns an error
+       In ncurses, they return ERR if
 
-       o   if the win parameter is null or
+       o   win is NULL,
 
-       o   if the str parameter is null or
+       o   str is NULL, or
 
-       o   the winsch(3x) function returns an error.
+       o   an internal winsch(3x) call returns ERR.
 
-       Functions prefixed with "mv" first perform cursor movement and fail  if
+       Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.

                NOTES

                -       All but winsnstr may be macros.
+       All of these functions except winsnstr may be implemented as macros.
+
+
+

                EXTENSIONS

                +       insnstr, winsnstr, mvinsnstr, and mvwinsnstr's acceptance of negative n
+       values is an ncurses extension.

                PORTABILITY

                -       These  functions  are  described  in X/Open Curses, Issue 4, which adds
-       const qualifiers to the arguments.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
-       The Single Unix  Specification,  Version  2  states  that  insnstr  and
-       winsnstr  perform  wrapping.  This is probably an error, since it makes
-       this group of  functions  inconsistent.   Also,  no  implementation  of
-       curses documents this inconsistency.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       X/Open  states  that the entire string is inserted if n is less than 1.
-       This is probably an  error,  because  it  is  inconsistent  with  other
-       functions,  and  differs  from  the  SVr4 and X/Open implementations on
-       Solaris.
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+
+       Issue 4  distinguished  insnstr  and  winsnstr from the other functions
+       documented above by stating they "do not perform wrapping".   This  was
+       probably an error, since it makes this group of functions inconsistent.
+       No  implementation  of curses manifests this inconsistency, and Issue 7
+       removed the claim.
+
+       Issue 4 states that the entire string is inserted if n is less than  1.
+       This  is  probably  an  error,  because  it  is inconsistent with other
+       functions such as waddstr, and differs from the SVr4 curses and Solaris
+       xcurses implementations.  Nevertheless, Issue 7 retains the language.
+
+
+

                HISTORY

                +       SVr3.1 (1987) introduced winsstr and winsnstr and their variants.

                SEE ALSO

                +       curs_ins_wstr(3x) describes comparable functions of the ncurses library
+       in its wide-character configuration (ncursesw).
+
        curses(3x), curs_inch(3x), curs_ins_wstr(3x), curs_util(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_insstr(3x)
+ncurses 6.6                       2025-10-20                   curs_insstr(3x)
                diff --git a/doc/html/man/curs_instr.3x.html b/doc/html/man/curs_instr.3x.html index 50d0f20..75e03f5 100644 --- a/doc/html/man/curs_instr.3x.html +++ b/doc/html/man/curs_instr.3x.html @@ -1,6 +1,6 @@ -curs_instr 3x 2024-04-20 ncurses 6.5 Library calls +curs_instr 3x 2025-10-20 ncurses 6.6 Library calls -

                curs_instr 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_instr 3x 2025-10-20 ncurses 6.6 Library calls

                 curs_instr(3x)                   Library calls                  curs_instr(3x)
 
 
-
-

                NAME

                -       instr,  innstr, winstr, winnstr, mvinstr, mvinnstr, mvwinstr, mvwinnstr
+       instr,  winstr, mvinstr, mvwinstr, innstr, winnstr, mvinnstr, mvwinnstr
        - get a string from a curses window

                SYNOPSIS

                        #include <curses.h>
 
-       int instr(char *str);
-       int innstr(char *str, int n);
-       int winstr(WINDOW *win, char *str);
-       int winnstr(WINDOW *win, char *str, int n);
+       int instr(char * str);
+       int winstr(WINDOW * win, char * str);
+       int mvinstr(int y, int x, char * str);
+       int mvwinstr(WINDOW * win, int y, int x, char * str);
 
-       int mvinstr(int y, int x, char *str);
-       int mvinnstr(int y, int x, char *str, int n);
-       int mvwinstr(WINDOW *win, int y, int x, char *str);
-       int mvwinnstr(WINDOW *win, int y, int x, char *str, int n);
+       int innstr(char * str, int n);
+       int winnstr(WINDOW * win, char * str, int n);
+       int mvinnstr(int y, int x, char * str, int n);
+       int mvwinnstr(WINDOW * win, int y, int x, char * str, int n);

                DESCRIPTION

                -       These routines return a string of characters in str,  starting  at  the
-       current  cursor  position in the named window.  Attributes are stripped
-       from the characters.
-
-       The four functions with  n  as  the  last  argument  return  a  leading
-       substring  at  most  n characters long (exclusive of the trailing NUL).
-       Transfer stops at the end of the current line,  or  when  n  characters
-       have been stored at the location referenced by str.
+       winstr extracts a string from a curses  window  win,  starting  at  the
+       cursor  and  stopping  at  the  end  of the line, and stores it in str,
+       terminating it with a null character and omitting  any  attributes  and
+       color  pair  identifier  that  curses  associates  with each character.
+       winnstr does the same, but copies at most n  characters  from  win.   A
+       negative   n   implies  no  limit;  winnstr  then  works  like  winstr.
+       ncurses(3x) describes the variants of these functions.

                RETURN VALUE

                -       All  of  the  functions  return  ERR  upon  failure,  or  the number of
-       characters actually read into the string.
+       These functions return the count of characters copied from win  to  str
+       (not including the null terminator), or ERR upon failure.
 
-       X/Open Curses defines no error conditions.  This implementation returns
-       an error
+       In ncurses, these functions fail if
 
-       o   if the win parameter is null or
+       o   the curses screen has not been initialized,
 
-       o   if the chstr parameter is null.
+       o   (for  functions  taking  a  WINDOW  pointer argument) win is a null
+           pointer, or
 
-       Functions  prefixed with "mv" first perform cursor movement and fail if
+       o   str is a null pointer.
+
+       Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

                NOTES

                -       All routines except winnstr may be macros.
+       All of these functions except winnstr may be implemented as macros.
 
-       Reading a line that overflows the array pointed to by str  with  instr,
-       mvinstr,  mvwinstr  or winstr causes undefined results.  Therefore, the
-       use of innstr, mvinnstr, mvwinnstr, or winnstr is recommended.
+       Reading  a line that overflows the array pointed to by str with and its
+       variants  causes  undefined  results.   Instead,  use   the   n-infixed
+       functions  with  a  positive  n argument no larger than the size of the
+       buffer backing str.
+
+
+

                EXTENSIONS

                +       innstr, winnstr, mvinnstr, and mvwinnstr's  acceptance  of  negative  n
+       values is an ncurses extension.

                PORTABILITY

                -       SVr4 does not document whether a length limit includes or excludes  the
-       trailing NUL.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
-       The ncurses library extends the X/Open Curses description by allowing a
-       negative value for n.  In this case, the functions  return  the  string
-       ending at the right margin.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       X/Open  Curses  Issues  4 and 7 both state that instr, winstr, mvinstr,
+       and mvwinstr return OK rather than a character count.  This  is  likely
+       an erratum.
+
+       o   SVr3.1  and  SVr4  implemented  winstr as a wrapper around winnstr,
+           returning the latter's return value.  X/Open Curses's specification
+           thus may have been an editorial  solecism  copied  from  System V's
+           documentation  (see  below)  by  X/Open, rather than an intentional
+           change.
+
+       o   ncurses retains compatibility with System V curses behavior.
+
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+
+       SVr4  does not document whether n counts the null terminator that these
+       functions write to str.
+
+
+

                HISTORY

                +       SVr3.1 (1987) introduced these functions.

                SEE ALSO

                -       curs_ins_wstr(3x) describes comparable functions of the ncurses library
+       curs_inwstr(3x) describes comparable functions of the  ncurses  library
        in its wide-character configuration (ncursesw).
 
        curses(3x), curs_inch(3x), curs_inchstr(3x)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_instr(3x)
+ncurses 6.6                       2025-10-20                    curs_instr(3x)
                diff --git a/doc/html/man/curs_inwstr.3x.html b/doc/html/man/curs_inwstr.3x.html index 6c79b59..7ea4b80 100644 --- a/doc/html/man/curs_inwstr.3x.html +++ b/doc/html/man/curs_inwstr.3x.html @@ -1,6 +1,6 @@ -curs_inwstr 3x 2024-04-20 ncurses 6.5 Library calls +curs_inwstr 3x 2025-10-20 ncurses 6.6 Library calls -

                curs_inwstr 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_inwstr 3x 2025-10-20 ncurses 6.6 Library calls

                 curs_inwstr(3x)                  Library calls                 curs_inwstr(3x)
 
 
-
-

                NAME

                -       inwstr,  innwstr,  winwstr,  winnwstr,  mvinwstr, mvinnwstr, mvwinwstr,
+       inwstr,  winwstr,  mvinwstr,  mvwinwstr,  innwstr, winnwstr, mvinnwstr,
        mvwinnwstr - get a wide-character string from a curses window

                SYNOPSIS

                        #include <curses.h>
 
-       int inwstr(wchar_t *wstr);
-       int innwstr(wchar_t *wstr, int n);
-       int winwstr(WINDOW *win, wchar_t *wstr);
-       int winnwstr(WINDOW *win, wchar_t *wstr, int n);
+       int inwstr(wchar_t * wstr);
+       int winwstr(WINDOW * win, wchar_t * wstr);
+       int mvinwstr(int y, int x, wchar_t * wstr);
+       int mvwinwstr(WINDOW * win, int y, int x, wchar_t * wstr);
 
-       int mvinwstr(int y, int x, wchar_t *wstr);
-       int mvinnwstr(int y, int x, wchar_t *wstr, int n);
-       int mvwinwstr(WINDOW *win, int y, int x, wchar_t *wstr);
-       int mvwinnwstr(WINDOW *win, int y, int x, wchar_t *wstr, int n);
+       int innwstr(wchar_t * wstr, int n);
+       int winnwstr(WINDOW * win, wchar_t * wstr, int n);
+       int mvinnwstr(int y, int x, wchar_t * wstr, int n);
+       int mvwinnwstr(WINDOW * win, int y, int x, wchar_t * wstr, int n);

                DESCRIPTION

                -       These routines return a string of  wchar_t  wide  characters  in  wstr,
-       starting at the current cursor position in the named window.
-
-       The  four  functions  with  n  as  the  last  argument return a leading
-       substring at most n characters long (exclusive of  the  trailing  NUL).
-       Transfer  stops  at  the  end of the current line, or when n characters
-       have been stored at the location referenced by wstr.
-
-       If the size  n  is  not  large  enough  to  store  a  complete  complex
-       character, an error is generated.
+       winwstr extracts a wide-character string  from  a  curses  window  win,
+       starting  at the cursor and stopping at the end of the line, and stores
+       it in wstr, terminating it with a wide null character and omitting  any
+       attributes  and  color pair identifier that curses associates with each
+       character.   winnwstr  does  the  same,  but  copies  at  most  n  wide
+       characters  from  win.   A  negative  n implies no limit; winnwstr then
+       works like  winwstr.   ncurses(3x)  describes  the  variants  of  these
+       functions.

                RETURN VALUE

                -       All  routines return ERR upon failure.  Upon successful completion, the
-       *inwstr routines return OK, and the *innwstr routines return the number
-       of characters read into the string.
+       On  successful  operation,  these  functions  return  the count of wide
+       characters copied from  win  to  wstr  (not  including  the  wide  null
+       terminator),  or  ERR  upon failure.  innwstr, winnwstr, mvinnwstr, and
+       mvwinnwstr return ERR if n is insufficiently large to store a  complete
+       wide  character  string.   (Recall  that a curses complex character can
+       contain multiple wide characters, some of which may be non-spacing.)
 
-       X/Open  defines  no  error  conditions.  This implementation returns an
-       error
+       In ncurses, these functions return ERR if
 
-       o   if the win parameter is null or
+       o   the curses screen has not been initialized,
 
-       o   if the wstr parameter is null, or
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer, or
 
-       o   if no characters could be read.
+       o   wstr is a null pointer.
 
-       Functions prefixed with "mv" first perform cursor movement and fail  if
+       Functions  prefixed with "mv" first perform cursor movement and fail if
        the position (y, x) is outside the window boundaries.

                NOTES

                -       All routines except winnwstr may be macros.
+       All of these functions except winnwstr may be implemented as macros.
 
-       Each  cell in the window holds a complex character (a spacing character
-       and zero or more non-spacing characters) together with  attributes  and
-       color.   These  functions  store  only  the  wide  characters, ignoring
-       attributes and color.  Use in_wchstr to return the  complex  characters
-       from a window.
+       Reading a line that overflows the array pointed  to  by  wstr  and  its
+       variants   causes   undefined  results.   Instead,  use  the  n-infixed
+       functions with a positive n argument no larger than  the  size  of  the
+       buffer backing wstr.
 
-       Reading a line that overflows the array pointed to by wstr with inwstr,
-       mvinwstr, mvwinwstr or winwstr causes  undefined  results.   Therefore,
-       the use of innwstr, mvinnwstr, mvwinnwstr, or winnwstr is recommended.
+
+

                EXTENSIONS

                +       innwstr, winnwstr, mvinnwstr, and mvwinnwstr's acceptance of negative n
+       values is an ncurses extension.

                PORTABILITY

                -       These functions are described in X/Open Curses, Issue 4.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
+
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       Notwithstanding  the foregoing, X/Open Curses Issues 4 and 7 both state
+       that innwstr, winnwstr, mvinnwstr, and mvwinnwstr "fail  ...  [i]f  the
+       array  is  not  large  enough  to  contain  any  complete  characters".
+       Strictly interpreted, this means  that  a  caller  of  these  functions
+       cannot use their return values to detect truncation of a wide-character
+       string  copied  from  more  than  one  character  cell in win.  ncurses
+       reports any truncation with ERR.
+
+       X/Open Curses specifies inwstr, winwstr,  mvinwstr,  and  mvwinwstr  as
+       returning  OK  rather  than a (wide) character count, unlike their non-
+       wide  counterparts  instr,  winstr,  mvinstr,  and  mvwinstr.   ncurses
+       regards this inconsistency as an error in the standard.
+
+
+

                HISTORY

                +       The  System V Interface Definition, Version 4 (1995), specified winwstr
+       and winnwstr (and the usual variants).  These were later  additions  to
+       SVr4.x,  not  appearing  in  the  first  SVr4  (1989).   Their synopses
+       described each function as taking an argument of  type  pointer-to-char
+       instead  of  pointer-to-wchar_t,  despite describing them as "returning
+       the string of wchar_t in str".  Presumably this was  an  error  in  the
+       System V Interface Definition.

                SEE ALSO

                -       curses(3x),     curs_inch(3x),     curs_inchstr(3x),    curs_instr(3x),
-       curs_in_wchstr(3x)
+       curs_instr(3x) describes comparable functions of the ncurses library in
+       its non-wide-character configuration.
 
+       curses(3x), curs_in_wch(3x), curs_in_wchstr(3x)
 
-
-ncurses 6.5                       2024-04-20                   curs_inwstr(3x)
+ncurses 6.6                       2025-10-20                   curs_inwstr(3x)
                diff --git a/doc/html/man/curs_kernel.3x.html b/doc/html/man/curs_kernel.3x.html index 90042ca..c296f96 100644 --- a/doc/html/man/curs_kernel.3x.html +++ b/doc/html/man/curs_kernel.3x.html @@ -1,6 +1,6 @@ -curs_kernel 3x 2024-04-20 ncurses 6.5 Library calls +curs_kernel 3x 2025-08-16 ncurses 6.6 Library calls -

                curs_kernel 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_kernel 3x 2025-08-16 ncurses 6.6 Library calls

                 curs_kernel(3x)                  Library calls                 curs_kernel(3x)
 
 
-
-

                NAME

                        def_prog_mode,   def_shell_mode,   reset_prog_mode,   reset_shell_mode,
-       resetty, savetty, getsyx, setsyx, ripoffline, curs_set,  napms  -  low-
-       level curses routines
+       resetty, savetty, getsyx, setsyx, curs_set, mvcur, napms, ripoffline  -
+       low-level curses routines

                SYNOPSIS

                @@ -67,9 +65,10 @@
        void getsyx(int y, int x);
        void setsyx(int y, int x);
 
-       int ripoffline(int line, int (*init)(WINDOW *, int));
        int curs_set(int visibility);
+       int mvcur(int oldrow, int oldcol, int newrow, int newcol);
        int napms(int ms);
+       int ripoffline(int line, int (*init)(WINDOW *, int));

                DESCRIPTION

                @@ -82,133 +81,201 @@
        The def_prog_mode and def_shell_mode routines save the current terminal
        modes as the "program" (in curses) or "shell" (not in curses) state for
        use by the reset_prog_mode and reset_shell_mode routines.  This is done
-       automatically by initscr.  There is one such save area for each  screen
+       automatically  by initscr.  There is one such save area for each screen
        context allocated by newterm.

                reset_prog_mode, reset_shell_mode

                -       The  reset_prog_mode and reset_shell_mode routines restore the terminal
-       to "program" (in curses) or "shell" (out of curses) state.   These  are
-       done  automatically by endwin(3x) and, after an endwin, by doupdate, so
+       The reset_prog_mode and reset_shell_mode routines restore the  terminal
+       to  "program"  (in curses) or "shell" (out of curses) state.  These are
+       done automatically by endwin(3x) and, after an endwin, by doupdate,  so
        they normally are not called.

                resetty, savetty

                -       The resetty and savetty routines save and  restore  the  state  of  the
-       terminal  modes.   savetty  saves  the  current  state  in a buffer and
+       The  resetty  and  savetty  routines  save and restore the state of the
+       terminal modes.  savetty saves  the  current  state  in  a  buffer  and
        resetty restores the state to what it was at the last call to savetty.

                getsyx

                -       The getsyx routine returns  the  current  coordinates  of  the  virtual
-       screen  cursor in y and x.  If leaveok is currently TRUE, then -1,-1 is
-       returned.  If lines have been removed from the top of the screen, using
-       ripoffline,  y  and x include these lines; therefore, y and x should be
-       used only as arguments for setsyx.
+       getsyx  stores  the  coordinates of virtual screen (newscr) cursor in y
+       and x.  If newscr's leaveok(3x) output option is TRUE, getsyx stores -1
+       in both y and x.  If lines have been removed from the top of the screen
+       using ripoffline, y includes these lines; therefore, y and x  populated
+       by getsyx should be used only as arguments for setsyx.
 
-       Few applications will use this feature, most use getyx instead.
+       Few applications use this feature; most call getyx(3x) instead.

                setsyx

                -       The setsyx routine sets the virtual screen cursor to y, x.  If y and  x
-       are  both  -1, then leaveok is set.  The two routines getsyx and setsyx
-       are designed to be used by a library routine, which manipulates  curses
-       windows  but  does  not  want  to  change  the  current position of the
-       program's cursor.   The  library  routine  would  call  getsyx  at  the
-       beginning, do its manipulation of its own windows, do a wnoutrefresh on
-       its windows, call setsyx, and then call doupdate.
+       setsyx  sets  the  virtual  screen  (newscr) cursor location to (y, x).
+       setsyx(-1, -1) is equivalent to leaveok(newscr, TRUE).
 
-       Few applications will use this feature, most use wmove instead.
+       getsyx  and  setsyx  are  designed  to  be  used  by  a  function  that
+       manipulates  curses  windows  but  seeks  to  avoid changing the cursor
+       position.  Such a function would first call getsyx, modify its windows'
+       content,  call  wnoutrefresh(3x)  on  them,  call  setsyx,  then   call
+       doupdate(3x).
 
-
-

                ripoffline

                -       ripoffline provides access to the same facility that slk_init(3x)  uses
-       to  reduce  the  size  of the screen.  ripoffline must be called before
-       initscr or newterm is called, to prepare these initial actions:
-
-       o   If line is positive, a line is removed from the top of stdscr.
-
-       o   if line is negative, a line is removed from the bottom.
-
-       When the resulting initialization is done inside initscr,  the  routine
-       init (supplied by the user) is called with two arguments:
-
-       o   a window pointer to the one-line window that has been allocated and
-
-       o   an integer with the number of columns in the window.
-
-       Inside  this  initialization  routine,  the integer variables LINES and
-       COLS (defined in <curses.h>) are not  guaranteed  to  be  accurate  and
-       wrefresh  or  doupdate  must  not  be  called.  It is allowable to call
-       wnoutrefresh during the initialization routine.
-
-       ripoffline can be called up to five times  before  calling  initscr  or
-       newterm.
+       Few applications use this feature; most call wmove(3x) instead.

                curs_set

                -       The  curs_set  routine  sets  the cursor state to invisible, normal, or
-       very visible for visibility equal to 0, 1, or 2 respectively.   If  the
-       terminal  supports  the visibility requested, the previous cursor state
-       is returned; otherwise, ERR is returned.
+       curs_set adjusts the cursor visibility to "invisible", "visible", "very
+       visible",  as its argument is 0, 1, or 2, respectively.  It returns the
+       previous  visibility  if  the  requested  one  is  supported,  and  ERR
+       otherwise.
+
+
+

                mvcur

                +       mvcur  provides  low-level cursor motion.  It takes effect immediately,
+       rather than at the next refresh.  Unlike  the  other  low-level  output
+       functions,  which  either  write  to  the standard output stream or are
+       passed a  function  pointer  to  perform  output,  mvcur  uses  a  file
+       descriptor derived from the output stream parameter of newterm(3x).
+
+       One  application  of  mvcur  accompanies  the  temporary use of another
+       program to write to the  terminal  screen.   For  example,  first  call
+       refresh(3x) to ensure that the screen and the library's model of it are
+       up  to  date;  then call reset_shell_mode; write to the screen with the
+       external application; call reset_prog_mode; and finally call mvcur(...,
+       ..., -1, -1) to move the terminal cursor to where curses thinks it  is,
+       since  the  library  has  no  knowledge of how the external application
+       moved it.

                napms

                        napms sleeps  for  ms  milliseconds.   If  ms  exceeds  30,000  (thirty
-       seconds), it is capped at that value.
+       seconds), ncurses caps it at that value.
+
+
+

                ripoffline

                +       ripoffline  provides access to the same facility that slk_init(3x) uses
+       to reduce the size of the screen.  The application must call ripoffline
+       before initscr(3x) or newterm(3x) so that the latter functions  prepare
+       a stdscr of the correct size.
+
+       o   If line is positive, ripoffline removes a line from the top of what
+           will become stdscr.
+
+       o   If  line  is negative, ripoffline removes a line from the bottom of
+           what will become stdscr.
+
+       When initscr initializes curses, it calls the init function supplied to
+       ripoffline by the application with two arguments:
+
+       o   a pointer to the one-line WINDOW that it allocates, and
+
+       o   an integer with the number of columns in the window.
+
+       Inside this init function, the values of the  integer  variables  LINES
+       and COLS (see curs_variables(3x)) are not guaranteed to be reliable; it
+       must not call wrefresh(3x) or doupdate(3x).  A wnoutrefresh(3x) call is
+       permissible.
+
+       ripoffline can be called up to five times before initscr or newterm.

                RETURN VALUE

                -       Except for curs_set, these routines always return OK.
+       Except  for  curs_set,  these functions return OK on success and ERR on
+       failure.
 
-       curs_set  returns  the  previous  cursor state, or ERR if the requested
-       visibility is not supported.
+       curs_set returns the previous cursor visibility, and returns ERR if the
+       terminal type does not support the requested visibility.
 
-       X/Open defines no error conditions.  In this implementation
+       napms always succeeds.
 
-       def_prog_mode, def_shell_mode, reset_prog_mode, reset_shell_mode
-            return an error if the terminal was not initialized, or if the I/O
-            call to obtain the terminal settings fails.
+       mvcur fails if the position (newrow,  newcol)  is  outside  the  screen
+       boundaries.
 
-       ripoffline
-            returns an error if the maximum number of ripped-off lines exceeds
-            the maximum (5).
+       In ncurses,
+
+       o   def_prog_mode,       def_shell_mode,      reset_prog_mode,      and
+           reset_shell_mode return ERR if the terminal was not initialized, or
+           if the operating system's function for obtaining terminal  settings
+           fails.
+
+       o   ripoffline  returns  ERR  if the accumulated quantity of ripped-off
+           lines would exceed the maximum (5).

                NOTES

                -       Note that getsyx is a macro, so & is not necessary before the variables
-       y and x.
+       getsyx is a macro; use of  the  &  operator  before  its  arguments  is
+       unnecessary.
 
-       Older  SVr4  man  pages  warn  that  the  return  value of curs_set "is
-       currently incorrect".  This implementation gets it right, but it may be
-       unwise to count on the correctness of the return value anywhere else.
+       The  endwin  function of both ncurses and SVr4 curses calls curs_set if
+       the latter has previously been called to set the cursor visibility to a
+       value other than normal; that is, either  invisible  or  very  visible.
+       There  is no way for ncurses to determine the initial cursor visibility
+       to restore it.
 
-       Both ncurses and SVr4 will call curs_set in endwin if curs_set has been
-       called to make the cursor other than normal, i.e., either invisible  or
-       very  visible.   There  is  no way for ncurses to determine the initial
-       cursor state to restore that.
+       ncurses imposes a limit of 30 seconds on a delay requested of napms.
+
+       While the init function called by ripoffline is specified to return  an
+       int, ncurses pays no attention to its return value.
+
+       If  ripoffline cannot allocate memory for the required WINDOW structure
+       backing the ripped-off line, it stores a null  pointer  to  the  WINDOW
+       pointer   argument  supplied  by  the  init  function  the  application
+       specifies.  The application must check this argument for validity after
+       calling initscr and prior  to  performing  curses  operations  on  that
+       window.
+
+
+

                EXTENSIONS

                +       In  ncurses, mvcur accepts -1 for either or both old coordinates.  This
+       value tells ncurses that the old location is unknown, and that it  must
+       use  only absolute motion, as with the cursor_address (cup) capability,
+       rather than the least  costly  combination  of  absolute  and  relative
+       motion.

                PORTABILITY

                -       The virtual screen functions setsyx and getsyx  are  not  described  in
-       X/Open Curses, Issue 4.  All other functions are as described in X/Open
-       Curses.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
 
-       The SVr4 documentation describes setsyx and  getsyx  as  having  return
-       type  int.   This  is misleading, as they are macros with no documented
-       semantics for the return value.
+       The  virtual  screen  functions  setsyx and getsyx are not described in
+       X/Open Curses Issue 4.  SVr4 documents each of  them  as  returning  an
+       int.   This  is  misleading,  as  they  are  macros  with no documented
+       semantics for returning values.
 
-       If interrupted, ncurses restarts napms.  That, and the limitation to 30
-       seconds, are different from other implementations.
+       All other functions are as described in X/Open Curses.  It specifies no
+       error conditions for them, except as described for curs_set in  section
+       "RETURN VALUE" above.
+
+       The  System V  Interface Definition, Version 4 (1995), specified all of
+       these functions except curs_set as returning OK.
+
+       Older SVr4 man pages  warn  that  the  return  value  of  curs_set  "is
+       currently  incorrect".  This implementation gets it right, but counting
+       on its correctness anywhere else may be unwise.
+
+       X/Open Curses specifies ripoffline as returning OK with no  possibility
+       of  failure  ("[c]alls to ripoffline above this limit [five lines] have
+       no effect but report success").
+
+       X/Open Curses notes:
+
+              After use of mvcur(), the model Curses maintains of the state of
+              the terminal might not match the actual state of  the  terminal.
+              An  application  should  touch  and  refresh  the  window before
+              resuming conventional use of Curses.
+
+       Both ncurses and SVr4 curses implement mvcur using  the  SCREEN  object
+       allocated  in  either initscr(3x) or newterm(3x).  X/Open Curses states
+       that the old location must be given for mvcur to accommodate  terminals
+       that lack absolute cursor positioning.
+
+       If  interrupted  by  a  signal,  ncurses restarts napms.  That, and the
+       limitation to 30 seconds, differ from other implementations.

                SEE ALSO

                        curses(3x),   curs_initscr(3x),   curs_outopts(3x),   curs_refresh(3x),
        curs_scr_dump(3x), curs_slk(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_kernel(3x)
+ncurses 6.6                       2025-08-16                   curs_kernel(3x)
              • RETURN VALUE
              • NOTES
                • +
              • EXTENSIONS
              • PORTABILITY
              • SEE ALSO
              diff --git a/doc/html/man/curs_legacy.3x.html b/doc/html/man/curs_legacy.3x.html index 22f78dd..ec4e429 100644 --- a/doc/html/man/curs_legacy.3x.html +++ b/doc/html/man/curs_legacy.3x.html @@ -1,6 +1,6 @@ -curs_legacy 3x 2024-03-16 ncurses 6.5 Library calls +curs_legacy 3x 2025-02-15 ncurses 6.6 Library calls -

              curs_legacy 3x 2024-03-16 ncurses 6.5 Library calls

              +

              curs_legacy 3x 2025-02-15 ncurses 6.6 Library calls

               curs_legacy(3x)                  Library calls                 curs_legacy(3x)
 
 
-
-

              NAME

                      getattrs,   getbegx,   getbegy,  getcurx,  getcury,  getmaxx,  getmaxy,
        getparx,  getpary  -  get  curses  cursor  and  window  coordinates  or
@@ -82,9 +80,9 @@
            fit into a chtype, so wattr_get is the only way to obtain the color
            information.
 
-           Because getattrs returns the attributes in a single  parameter,  it
-           would  not  be possible for an application to distinguish that from
-           ERR (a -1).  If the window  parameter  is  null,  getattrs  returns
+           Because  getattrs  returns the attributes in a single parameter, it
+           would not be possible for an application to distinguish  that  from
+           ERR  (a  -1).   If  the  window parameter is null, getattrs returns
            A_NORMAL (zero).
 
        o   The getbegy and getbegx functions return the same data as getbegyx.
@@ -97,21 +95,10 @@

              RETURN VALUE

              -       Except  as  noted,  these  functions  return  an integer, or ERR if the
+       Except as noted, these functions return  an  integer,  or  ERR  if  the
        window parameter is null.
 
 
-

              NOTES

              -       All of these interfaces are implemented as macros and  functions.   The
-       macros  are suppressed (and only the functions provided) in an "opaque"
-       ncurses build, which defines the  preprocessor  symbol  NCURSES_OPAQUE.
-       See section "ALTERNATE CONFIGURATIONS" in ncurses(3x).
-
-       The standard forms such as getyx must be implemented as macros, and (in
-       this implementation) are defined in terms of  the  functions  described
-       here, to avoid reliance on internal details of the WINDOW structure.
-
-

              PORTABILITY

                      These   functions  were  supported  on  Version  7,  BSD  or  System  V
        implementations.  None of  those  implementations  checked  the  window
@@ -125,9 +112,7 @@

              SEE ALSO

                      curses(3x), curs_getyx(3x), curs_opaque(3x)
 
-
-
-ncurses 6.5                       2024-03-16                   curs_legacy(3x)
+ncurses 6.6                       2025-02-15                   curs_legacy(3x)
              diff --git a/doc/html/man/curs_memleaks.3x.html b/doc/html/man/curs_memleaks.3x.html index 085e3ab..975ab0d 100644 --- a/doc/html/man/curs_memleaks.3x.html +++ b/doc/html/man/curs_memleaks.3x.html @@ -34,18 +34,16 @@ -curs_memleaks 3x 2024-03-16 ncurses 6.5 Library calls +curs_memleaks 3x 2024-03-16 ncurses 6.6 Library calls -

              curs_memleaks 3x 2024-03-16 ncurses 6.5 Library calls

              +

              curs_memleaks 3x 2024-03-16 ncurses 6.6 Library calls

               curs_memleaks(3x)                Library calls               curs_memleaks(3x)
 
 
-
-

              NAME

                      exit_curses, exit_terminfo - check for memory leaks in curses
 
@@ -76,7 +74,7 @@
        functions which free those chunks of memory, simplifying the process of
        memory-leak checking.
 
-       Some  of  the functions are named with a "_nc_" prefix because they are
+       Some of the functions are named with a "_nc_" prefix because  they  are
        not intended for use in the non-debugging library:
 
        _nc_freeall
@@ -85,11 +83,11 @@
        _nc_free_and_exit
             This frees the memory allocated by ncurses (like _nc_freeall), and
             exits the program.  It is preferred over _nc_freeall since some of
-            that memory may be  required  to  keep  the  application  running.
+            that  memory  may  be  required  to  keep the application running.
             Simply exiting (with the given exit-code) is safer.
 
        _nc_free_tinfo
-            Use  this  function  if only the low-level terminfo functions (and
+            Use this function if only the low-level  terminfo  functions  (and
             corresponding library) are used.  Like _nc_free_and_exit, it exits
             the program after freeing memory.
 
@@ -115,10 +113,10 @@
        In any implementation of X/Open Curses, an application can free part of
        the memory allocated by curses:
 
-       o   The  portable  part  of  exit_curses  can be freed using delscreen,
+       o   The portable part of exit_curses  can  be  freed  using  delscreen,
            passing the SCREEN pointer returned by newterm.
 
-           In some implementations, there is a global variable sp which  could
+           In  some implementations, there is a global variable sp which could
            be used, e.g., if the screen were only initialized using initscr.
 
        o   The portable part of exit_terminfo can be freed using del_curterm.
@@ -130,9 +128,7 @@

              SEE ALSO

                      curses(3x), curs_initscr(3x), curs_terminfo(3x)
 
-
-
-ncurses 6.5                       2024-03-16                 curs_memleaks(3x)
+ncurses 6.6                       2024-03-16                 curs_memleaks(3x)
                diff --git a/doc/html/man/curs_mouse.3x.html b/doc/html/man/curs_mouse.3x.html index cdb42f2..399dbbd 100644 --- a/doc/html/man/curs_mouse.3x.html +++ b/doc/html/man/curs_mouse.3x.html @@ -1,7 +1,7 @@ -curs_mouse 3x 2024-04-20 ncurses 6.5 Library calls +curs_mouse 3x 2025-11-11 ncurses 6.6 Library calls -

                curs_mouse 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_mouse 3x 2025-11-11 ncurses 6.6 Library calls

                 curs_mouse(3x)                   Library calls                  curs_mouse(3x)
 
 
-
-

                NAME

                        has_mouse,  getmouse,  ungetmouse,  mousemask,  wenclose,  mouse_trafo,
-       wmouse_trafo, mouseinterval - get mouse events in curses
+       wmouse_trafo, mouseinterval, mmask_t, MEVENT  -  get  mouse  events  in
+       ncurses

                SYNOPSIS

                        #include <curses.h>
 
+       /* data types */
        typedef unsigned long mmask_t;
 
        typedef struct {
-           short id;         /* ID to distinguish multiple devices */
-           int x, y, z;      /* event coordinates */
-           mmask_t bstate;   /* button state bits */
+           short id;       /* ID to distinguish multiple devices */
+           int x, y, z;    /* event coordinates */
+           mmask_t bstate; /* button state bits */
        } MEVENT;
 
+       /* functions */
        bool has_mouse(void);
 
-       mmask_t mousemask(mmask_t newmask, mmask_t *oldmask);
+       mmask_t mousemask(mmask_t new-mask, mmask_t * old-mask);
 
-       int getmouse(MEVENT *event);
-       int ungetmouse(MEVENT *event);
+       int getmouse(MEVENT * event);
+       int ungetmouse(MEVENT * event);
 
-       bool wenclose(const WINDOW *win, int y, int x);
+       bool wenclose(const WINDOW * win, int y, int x);
 
-       bool mouse_trafo(int* pY, int* pX, bool to_screen);
-       bool wmouse_trafo(const WINDOW* win,
-                         int* pY, int* pX, bool to_screen);
+       bool mouse_trafo(int * pY, int * pX, bool to-screen);
+       bool wmouse_trafo(const WINDOW * win,
+             int * pY, int * pX, bool to-screen);
 
        int mouseinterval(int erval);

                DESCRIPTION

                -       These functions provide an interface to mouse events from  ncurses(3x).
-       Mouse  events  are  represented  by  KEY_MOUSE pseudo-key values in the
-       wgetch(3x) input stream.
+       ncurses  provides  an  interface to the mouse or other pointing device.
+       An application can register its interest in such  events;  the  library
+       then  exposes  the availability of a mouse event via an input character
+       reading function: this is wgetch(3x) in the non-wide  character  curses
+       API  and wget_wch(3x) in the wide character API.  A queue distinct from
+       that used for keyboard events accumulates the details of mouse  events.
+       The  input  character  reading  function reports the KEY_MOUSE key code
+       when a mouse event is available for collection.  A single  mouse  event
+       queue serves all windows associated with the screen.
+
+       The  MEVENT structure describes a mouse event.  Its y and x coordinates
+       are screen-, not window-, relative.  The bstate member has exactly  one
+       bit set indicating the event type.
+
+       ncurses  ignores  mouse  events  when  input is in canonical ("cooked")
+       mode, and produces an error beep when  they  occur  while  the  library
+       simulates  canonical  mode  in  a  window,  as  with  getstr(3x) (wide-
+       character API users:  get_wstr(3x)),  which  expects  a  line  feed  to
+       terminate its input loop.

                has_mouse

                -       The has_mouse function returns  TRUE  if  the  mouse  driver  has  been
-       successfully initialized, and FALSE otherwise.
-
-       Mouse  events  are  ignored  when input is in cooked mode, and cause an
-       error beep when cooked mode  is  being  simulated  in  a  window  by  a
-       function  such  as  getstr  that  expects  a  linefeed  for  input-loop
-       termination.
+       The  terminal  type  or  operating  system  interface  must support the
+       encoding of mouse events.  has_mouse returns TRUE  if  ncurses's  mouse
+       driver initialized successfully, and FALSE otherwise.

                mousemask

                -       To make mouse events visible, use the mousemask  function.   This  sets
-       the  mouse  events  to  be  reported.   By default, no mouse events are
-       reported.
+       Use  mousemask  to select the varieties of mouse event your application
+       wishes to receive.  By default, ncurses reports no mouse events.
 
-       o   The function returns an updated copy of newmask to  indicate  which
-           of the specified mouse events can be reported.
+       o   The function returns an updated copy of new-mask  indicating  which
+           event  types  of  interest  are  reportable by the terminal's mouse
+           protocol.
 
-           If the screen has not been initialized, or if the terminal does not
-           support mouse-events, this function returns 0.
+           If the screen is not initialized, or the  terminal  interface  does
+           not report mouse events, mousemask returns 0.
 
-       o   If oldmask is non-NULL, this function fills the indicated  location
-           with the previous value of the current screen's mouse event mask.
+       o   If  old-mask  is  not a null pointer, mousemask stores the previous
+           value of the screen's mouse event mask there.
 
-       As  a  side  effect,  setting  a zero mouse mask may turn off the mouse
-       pointer; setting a nonzero mask may turn it on.  Whether  this  happens
-       is device-dependent.
+       As a side effect, setting a zero mouse mask  may  turn  off  the  mouse
+       cursor; setting a nonzero mask may turn it on.  Whether this happens is
+       device-dependent.

                Mouse Events

                -       Here are the mouse event type masks which may be defined:
+       Several  mouse  event  types  may  be  selected;  construct  a  mask by
+       logically "or"-ing their values.
 
        Name                     Description
        ------------------------------------------------------------------------
@@ -149,93 +163,83 @@
        BUTTON5_DOUBLE_CLICKED   mouse button 5 double clicked
        BUTTON5_TRIPLE_CLICKED   mouse button 5 triple clicked
        ------------------------------------------------------------------------
-       BUTTON_SHIFT             shift was down during button state change
-       BUTTON_CTRL              control was down during button state change
-       BUTTON_ALT               alt was down during button state change
+       BUTTON_SHIFT             a shift  key  was  down  during  button  state
+                                change
+       BUTTON_CTRL              a  control  key  was  down during button state
+                                change
+       BUTTON_ALT               an alt key was down during button state change
        ALL_MOUSE_EVENTS         report all button state changes
        REPORT_MOUSE_POSITION    report mouse movement
        ------------------------------------------------------------------------

                getmouse

                -       Once a class of mouse events has been made visible in a window, calling
-       the wgetch function on that window may return KEY_MOUSE as an indicator
-       that a mouse event has been queued.  To read the event data and pop the
-       event off the queue, call getmouse.  This function will return OK if  a
-       mouse  event  is  actually  visible in the given window, ERR otherwise.
-       When getmouse returns OK, the data deposited as y and x  in  the  event
-       structure    coordinates   will   be   screen-relative   character-cell
-       coordinates.  The returned state mask will have exactly one bit set  to
-       indicate the event type.  The corresponding data in the queue is marked
-       invalid.  A subsequent call to getmouse will retrieve  the  next  older
-       item from the queue.
+       When a window is configured to report a non-empty set of  event  types,
+       calling  the input character reading function on that window may return
+       KEY_MOUSE to indicate availability of an enqueued mouse event.  To read
+       the event data and remove it  from  the  queue,  call  getmouse,  which
+       returns  OK  if  a  mouse  event is visible in the given window and ERR
+       otherwise.  When getmouse returns OK, it deposits data  describing  the
+       mouse  event  in  the  event pointer you supply.  A subsequent getmouse
+       call retrieves the next older event from the queue.

                ungetmouse

                -       The  ungetmouse  function  behaves analogously to ungetch.  It pushes a
-       KEY_MOUSE event onto the input queue, and associates  with  that  event
-       the given state data and screen-relative character-cell coordinates.
+       ungetmouse behaves analogously to ungetch(3x).  It pushes  a  KEY_MOUSE
+       event  onto  the  screen's  input queue, and event onto the mouse event
+       queue.

                wenclose

                -       The  wenclose  function  tests  whether a given pair of screen-relative
-       character-cell coordinates is enclosed by  a  given  window,  returning
-       TRUE  if  it is and FALSE otherwise.  It is useful for determining what
-       subset of the screen windows enclose the location of a mouse event.
+       wenclose returns TRUE if the pair of screen-relative coordinates (y, x)
+       is enclosed by the given window win, and FALSE otherwise.  If win is  a
+       pad, wenclose uses its most recent screen coordinates as specified in a
+       prefresh(3x) or pnoutrefresh(3x) call.
 
-       If the parameter is  a  pad,  wenclose  uses  the  most  recent  screen
-       coordinates used for this pad in prefresh(3x) or pnoutrefresh(3x).
+       wenclose  is useful for determining what subset of the screen's windows
+       encloses the location of a mouse event; it is otherwise independent  of
+       the ncurses mouse API.

                wmouse_trafo

                -       The  wmouse_trafo  function transforms a given pair of coordinates from
-       stdscr-relative coordinates to coordinates relative to the given window
-       or  vice  versa.   The  resulting  stdscr-relative  coordinates are not
-       always identical to screen coordinates due to the mechanism to  reserve
-       lines  on  top  or  bottom  of  the  screen for other purposes (see the
-       ripoffline(3x) and slk_init(3x) calls, for example).
+       wmouse_trafo  transforms the given pair of coordinate pointers (pY, pX)
+       from a win-relative basis to a screen-relative one or  vice  versa,  as
+       to-screen  is TRUE or FALSE, respectively.  stdscr-relative coordinates
+       are  not  always  identical  to  screen  coordinates:  curses  supports
+       reservation  of  screen  lines  at  the  top  and/or  bottom  for other
+       purposes; see ripoffline(3x) and slk_init(3x).
 
-       o   If the parameter to_screen  is  TRUE,  the  pointers  pY,  pX  must
-           reference  the  coordinates  of  a  location inside the window win.
-           They are converted  to  stdscr-relative  coordinates  and  returned
-           through  the  pointers.   If  the  conversion  was  successful, the
-           function returns TRUE.
+       If to-screen is TRUE and the pointers (pY,  pX)  reference  coordinates
+       inside win, ncurses updates their values to stdscr-relative coordinates
+       and returns TRUE.  If either pY or pX is a null pointer, or (pY, pX) is
+       not inside win, wmouse_trafo returns FALSE.
 
-           If one of the parameters was NULL or the location is not inside the
-           window, FALSE is returned.
-
-       o   If   to_screen  is  FALSE,  the  pointers  pY,  pX  must  reference
-           stdscr-relative coordinates.  They are converted to window-relative
-           coordinates  if  the  window win encloses this point.  In this case
-           the function returns TRUE.
-
-           If one of the parameters is NULL or the point  is  not  inside  the
-           window, FALSE is returned.
-
-       The   referenced   coordinates  are  only  replaced  by  the  converted
-       coordinates if the transformation was successful.
+       If  to-screen  is FALSE and the pointers (pY, pX) reference coordinates
+       inside stdscr, ncurses updates their values to win-relative coordinates
+       and returns TRUE.  If either pY or pX is a null pointer, or (pY, pX) is
+       not inside stdscr, wmouse_trafo returns FALSE.

                mouse_trafo

                -       The mouse_trafo function performs the same translation as wmouse_trafo,
-       using stdscr for win.
+       mouse_trafo applies the wmouse_trafo  translation  to  stdscr.   If  no
+       screen  lines  are  reserved by ripoffline(3x) or slk_init(3x), this is
+       the identity transformation.

                mouseinterval

                -       The  mouseinterval  function  sets  the maximum time (in thousands of a
-       second) that can elapse between press and release events for them to be
-       resolved  as  a click.  An application might interpret button press and
-       release events separated by more than the mouse  interval  as  a  "long
-       press", or, with motion, as a "drag".
+       mouseinterval sets the maximum time (in thousandths of a  second)  that
+       can  elapse between press and release events for them to be resolved as
+       a click.  An application  might  interpret  button  press  and  release
+       events separated by more than the mouse interval as a "long press", or,
+       with motion, as a "drag".
 
-       Calling  mouseinterval(0)  disables  click  resolution.   When  ncurses
-       detects a mouse event, it awaits further  input  activity  up  to  this
-       interval,  and  then  checks  for a subsequent mouse event which can be
-       combined with the first event.  If the timeout  expires  without  input
-       activity  (which  would  happen  with  a  zero interval), then no click
-       resolution will occur.
+       When ncurses detects a mouse event, it awaits further input activity up
+       to  this  interval,  and then checks for a subsequent mouse event which
+       can be combined with the first event.  If the timeout  expires  without
+       input   activity,   then   no   click   resolution   occurs.    Calling
+       mouseinterval(0) disables click resolution.
 
-       This   function   returns   the   previous   interval    value.     Use
+       mouseinterval   returns   the    previous    interval    value.     Use
        mouseinterval(-1) to obtain the interval without altering it.
 
        The  mouse  interval  is  set  to  one  sixth  of  a  second  when  the
@@ -255,24 +259,24 @@
 
        o   the mask of reportable events is zero,
 
-       o   a mouse event was detected that does not match the mask,
+       o   a mouse event was detected that does not match the mask, or
 
-       o   or if no more events remain in the queue.
+       o   no more events remain in the queue.
 
-       ungetmouse returns an error if the event queue is full.
+       ungetmouse returns ERR if the event queue is full.
 
        mousemask returns the mask of reportable events.
 
-       mouseinterval returns the previous interval value, unless the  terminal
-       was  not  initialized.   In  that case, it returns the maximum interval
+       mouseinterval  returns the previous interval value, unless the terminal
+       was not initialized.  In that case, it  returns  the  maximum  interval
        value (166).

                NOTES

                -       The  order  of  the  MEVENT  structure  members  is   not   guaranteed.
+       The   order   of  the  MEVENT  structure  members  is  not  guaranteed.
        Additional fields may be added to the structure in the future.
 
-       Under  ncurses, these calls are implemented using either xterm's built-
+       Under ncurses, these calls are implemented using either xterm's  built-
        in mouse-tracking API or platform-specific drivers including
 
           o   Alessandro Rubini's gpm server
@@ -281,35 +285,40 @@
 
           o   OS/2 EMX
 
-       If you are using an unsupported configuration, mouse events will not be
-       visible to ncurses (and the mousemask function will always return 0).
+       If  you  are  using  an unsupported configuration, mouse events are not
+       visible to ncurses (and the mousemask function always returns 0).
 
-       If  the  terminfo entry contains a XM string, this is used in the xterm
-       mouse driver to control the way the terminal is initialized  for  mouse
-       operation.   The  default,  if  XM is not found, corresponds to private
-       mode 1000 of xterm:
+       If the  terminal  type  possesses  the  (nonstandard)  terminfo  string
+       capability  XM,  ncurses's xterm mouse driver uses it when initializing
+       the terminal for mouse operation.  The default, if  XM  is  not  found,
+       corresponds to private mode 1000 of xterm.
 
           \E[?1000%?%p1%{1}%=%th%el%;
 
-       The mouse driver also recognizes a newer xterm private mode 1006, e.g.,
+       ncurses also recognizes xterm's newer private mode 1006.
 
           \E[?1006;1000%?%p1%{1}%=%th%el%;
 
-       The z member in the event structure  is  not  presently  used.   It  is
-       intended  for  use with touch screens (which may be pressure-sensitive)
+       The  id  member  of the mouse event structure is not presently used; no
+       terminal type or operating system interface supports  reporting  events
+       from  distinguishable  pointing  devices.  If you synthesize an MEVENT,
+       use an id of 0.
+
+       The z member of the mouse event structure is not presently used.  It is
+       intended for use with touch screens (which may  be  pressure-sensitive)
        or with 3D-mice/trackballs/power gloves.
 
-       The ALL_MOUSE_EVENTS  class  does  not  include  REPORT_MOUSE_POSITION.
-       They  are  distinct.   For example, in xterm, wheel/scrolling mice send
-       position reports as a sequence of presses of buttons  4  or  5  without
+       The  ALL_MOUSE_EVENTS  class  does  not  include REPORT_MOUSE_POSITION.
+       They are distinct.  For example, in xterm,  wheel/scrolling  mice  send
+       position  reports  as  a  sequence of presses of buttons 4 or 5 without
        matching button-releases.

                EXTENSIONS

                -       These  functions  were  designed  for ncurses(3x), and are not found in
-       SVr4  curses,   4.4BSD   curses,   or   any   other   previous   curses
-       implementation.   (SVr4 curses did have a getmouse function, which took
-       no argument and returned a different type.)
+       These functions are ncurses extensions,  and  are  not  found  in  SVr4
+       curses,  4.4BSD  curses,  or  any other previous curses implementation.
+       (SVr4 curses did have a getmouse function, which took no  argument  and
+       returned an unsigned long.)

                PORTABILITY

                @@ -320,15 +329,17 @@
        "ALTERNATE CONFIGURATIONS" of ncurses(3x).  The following values may be
        specified.
 
-          1  has definitions for reserved events.  The mask uses 28 bits.
+          1  has definitions for reserved events.  The mask uses 28 bits.
 
-          2  adds  definitions  for  button  5,  removes  the  definitions for
+          2  adds definitions  for  button  5,  removes  the  definitions  for
              reserved events.  The mask uses 29 bits.
 
-       SVr4 curses had support for the mouse in a variant of xterm(1).  It  is
+
+

                HISTORY

                +       SVr4  (1989)  added  mouse  support  to its variant of xterm(1).  It is
        mentioned in a few places, with little supporting documentation.
 
-       o   Its  "libcurses"  manual  page  lists  functions  for  this feature
+       o   Its "libcurses"  manual  page  lists  functions  for  this  feature
            prototyped in curses.h.
 
                extern int mouse_set(long int);
@@ -347,21 +358,21 @@
                mouse_info      minfo   Mi   Mouse status information
                req_mouse_pos   reqmp   RQ   Request mouse position report
 
-       o   The interface made assumptions (as does ncurses) about  the  escape
+       o   The  interface  made assumptions (as does ncurses) about the escape
            sequences sent to and received from the terminal.
 
-           For instance, the SVr4 curses library used the get_mouse capability
-           to tell the terminal which mouse  button  events  it  should  send,
-           passing  the mouse-button bit mask to the terminal.  Also, it could
-           ask the terminal  where  the  mouse  was  using  the  req_mouse_pos
-           capability.
+           For instance, the SVr4 curses library  used  the  get_mouse  (getm)
+           capability to tell the terminal which mouse button events it should
+           send,  passing the mouse-button bit mask to the terminal.  Also, it
+           could ask the terminal where the mouse was using the  req_mouse_pos
+           (reqmp) capability.
 
            Those  features  required a terminal program that had been modified
            to work with SVr4 curses.  They were not part of the X Consortium's
            xterm.
 
-       When  developing the xterm mouse support for ncurses in September 1995,
-       Eric Raymond was uninterested in using the same interface  due  to  its
+       When developing the xterm mouse support for ncurses in September  1995,
+       Eric  Raymond  was  uninterested in using the same interface due to its
        lack of documentation.  Later, in 1998, Mark Hesseling provided support
        in PDCurses 2.3 using the SVr4 interface.  PDCurses, however, does  not
        use  video  terminals,  making  it  unnecessary  to  be concerned about
@@ -369,32 +380,32 @@

                BUGS

                -       Mouse events from xterm are not ignored in cooked  mode  if  they  have
-       been  enabled  by  mousemask.  Instead, the xterm mouse report sequence
-       appears in the string read.
+       Mouse events from xterm are not ignored in canonical ("cooked") mode if
+       they have been enabled by mousemask.  Instead, the xterm  mouse  report
+       sequence appears in the string read.
 
-       Mouse event reports from xterm are not detected correctly in  a  window
-       with  keypad application mode disabled, since they are interpreted as a
-       variety of function key.  Set the terminal's terminfo capability  kmous
-       to  "\E[M" (the beginning of the response from xterm for mouse clicks).
-       Other values of kmous are permitted under the same assumption, that is,
-       the report begins with that sequence.
+       An  ncurses  window  must  enable keypad(3x) to correctly receive mouse
+       event reports from xterm since they are  encoded  like  function  keys.
+       Set the terminal's terminfo capability key_mouse (kmous) to "\E[M" (the
+       beginning  of  the response from xterm for mouse clicks).  Other values
+       of key_mouse are permitted under the same  assumption  --  that  is,  a
+       mouse  report  begins  with  the  value of the key_mouse (kmous) string
+       capability.
 
        Because there are no standard response sequences that serve to identify
        terminals supporting the xterm mouse protocol, ncurses assumes that  if
-       kmous is defined in the terminal description, or if the terminal type's
-       primary name or aliases contain the string "xterm", then  the  terminal
-       may send mouse events.  The kmous capability is checked first, allowing
-       use of newer xterm mouse protocols, such as its private mode 1006.
+       key_mouse  (kmous)  is  defined  in the terminal description, or if the
+       terminal type's primary name or aliases  contain  the  string  "xterm",
+       then the terminal may send mouse events.  ncurses checks the kmous cap-
+       code  first,  allowing  use of newer xterm mouse protocols, such as its
+       private mode 1006.

                SEE ALSO

                        curses(3x),     curs_inopts(3x),     curs_kernel(3x),     curs_pad(3x),
        curs_slk(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_mouse(3x)
+ncurses 6.6                       2025-11-11                    curs_mouse(3x)
                diff --git a/doc/html/man/curs_move.3x.html b/doc/html/man/curs_move.3x.html index bbab2b8..a530ab0 100644 --- a/doc/html/man/curs_move.3x.html +++ b/doc/html/man/curs_move.3x.html @@ -1,6 +1,6 @@ -curs_move 3x 2024-04-27 ncurses 6.5 Library calls +curs_move 3x 2025-04-05 ncurses 6.6 Library calls -

                curs_move 3x 2024-04-27 ncurses 6.5 Library calls

                +

                curs_move 3x 2025-04-05 ncurses 6.6 Library calls

                 curs_move(3x)                    Library calls                   curs_move(3x)
 
 
-
-

                NAME

                        move, wmove - move cursor in a curses window
 
@@ -54,23 +52,26 @@
        #include <curses.h>
 
        int move(int y, int x);
-       int wmove(WINDOW *win, int y, int x);
+       int wmove(WINDOW * win, int y, int x);

                DESCRIPTION

                        wmove  relocates  the  cursor  associated with the curses window win to
        line y and column  x.   The  terminal's  cursor  does  not  move  until
        refresh(3x)  is  called.   The position (y, x) is relative to the upper
-       left-hand  corner  of  the  window,  which  has   coordinates   (0, 0).
-       ncurses(3x) describes the move variant of this function.
+       left-hand corner of the window, which  has  coordinates  (0, 0).   move
+       similarly moves the cursor in the stdscr window.

                RETURN VALUE

                -       These functions return OK on success and ERR on failure.
+       These  functions  return OK on success and ERR on failure.  In ncurses,
+       these functions fail if
 
-       They fail if the position (y, x) is outside the window boundaries.
+       o   the curses screen has not been initialized,
 
-       wmove fails if its WINDOW pointer argument is NULL.
+       o   (for wmove) win is a null pointer, or
+
+       o   the position (y, x) is outside the window boundaries.

                NOTES

                @@ -78,15 +79,21 @@

                PORTABILITY

                -       X/Open Curses, Issue 4 describes these functions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+
+
+

                HISTORY

                +       4BSD (1980) introduced these functions.

                SEE ALSO

                        curses(3x), curs_refresh(3x)
 
-
-
-ncurses 6.5                       2024-04-27                     curs_move(3x)
+ncurses 6.6                       2025-04-05                     curs_move(3x)
                diff --git a/doc/html/man/curs_opaque.3x.html b/doc/html/man/curs_opaque.3x.html index 50bb9ee..8802844 100644 --- a/doc/html/man/curs_opaque.3x.html +++ b/doc/html/man/curs_opaque.3x.html @@ -1,6 +1,6 @@ -curs_opaque 3x 2024-03-16 ncurses 6.5 Library calls +curs_opaque 3x 2025-02-15 ncurses 6.6 Library calls -

                curs_opaque 3x 2024-03-16 ncurses 6.5 Library calls

                +

                curs_opaque 3x 2025-02-15 ncurses 6.6 Library calls

                 curs_opaque(3x)                  Library calls                 curs_opaque(3x)
 
 
-
-

                NAME

                        is_cleared,  is_idlok,  is_idcok,  is_immedok,  is_keypad,  is_leaveok,
        is_nodelay, is_notimeout, is_pad,  is_scrollok,  is_subwin,  is_syncok,
@@ -124,12 +122,12 @@
               returns the delay timeout set by wtimeout(3x).
 
        wgetparent
-              returns the parent WINDOW pointer for subwindows,  or  NULL  for
+              returns the parent WINDOW pointer for subwindows,  or  NULL  for
               windows having no parent.
 
        wgetscrreg
-              stores  the the top and bottom rows for the scrolling margin set
-              by wsetscrreg(3x) in the corresponding arguments, returning  ERR
+              stores  the  top and bottom rows for the scrolling margin set by
+              wsetscrreg(3x) in the  corresponding  arguments,  returning  ERR
               upon failure and OK upon successful completion.
 
 
@@ -142,20 +140,23 @@
        function documented in this page.
 
 
+

                EXTENSIONS

                +       These functions originated with ncurses.
+
+

                PORTABILITY

                -       These routines are specific to ncurses.  They  were  not  supported  on
-       Version 7, BSD or System V implementations.  It is recommended that any
-       code   depending   on   ncurses   extensions   be   conditioned   using
-       NCURSES_VERSION.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
+
+       NetBSD  curses  since  10.1  (2024)  supports  wgetscr_reg.   It   also
+       implements getscr_reg, operating on stdscr.

                SEE ALSO

                        curses(3x),    curs_inopts(3x),   curs_outopts(3x),   curs_threads(3x),
        curs_window(3x)
 
-
-
-ncurses 6.5                       2024-03-16                   curs_opaque(3x)
+ncurses 6.6                       2025-02-15                   curs_opaque(3x)
                diff --git a/doc/html/man/curs_outopts.3x.html b/doc/html/man/curs_outopts.3x.html index 7f04d92..22d6826 100644 --- a/doc/html/man/curs_outopts.3x.html +++ b/doc/html/man/curs_outopts.3x.html @@ -1,6 +1,6 @@ -curs_outopts 3x 2024-04-20 ncurses 6.5 Library calls +curs_outopts 3x 2025-11-11 ncurses 6.6 Library calls -

                curs_outopts 3x 2024-04-20 ncurses 6.5 Library calls

                +

                curs_outopts 3x 2025-11-11 ncurses 6.6 Library calls

                 curs_outopts(3x)                 Library calls                curs_outopts(3x)
 
 
-
-

                NAME

                -       clearok,   idlok,   idcok,  immedok,  leaveok,  setscrreg,  wsetscrreg,
-       scrollok - set curses output options
+       clearok,   idcok,   idlok,   immedok,   leaveok,  scrollok,  setscrreg,
+       wsetscrreg - set curses output options

                SYNOPSIS

                        #include <curses.h>
 
-       int clearok(WINDOW *win, bool bf);
-       int idlok(WINDOW *win, bool bf);
-       void idcok(WINDOW *win, bool bf);
-       void immedok(WINDOW *win, bool bf);
-       int leaveok(WINDOW *win, bool bf);
-       int scrollok(WINDOW *win, bool bf);
+       int clearok(WINDOW * win, bool bf);
+       void idcok(WINDOW * win, bool bf);
+       int idlok(WINDOW * win, bool bf);
+       void immedok(WINDOW * win, bool bf);
+       int leaveok(WINDOW * win, bool bf);
+       int scrollok(WINDOW * win, bool bf);
 
        int setscrreg(int top, int bot);
-       int wsetscrreg(WINDOW *win, int top, int bot);
+       int wsetscrreg(WINDOW * win, int top, int bot);

                DESCRIPTION

                -       These routines set options that  change  the  style  of  output  within
-       curses.   All options are initially FALSE, unless otherwise stated.  It
-       is not necessary to turn these options off before calling endwin(3x).
+       These functions configure properties  of  curses  windows  that  affect
+       their  manner of output.  Boolean-valued properties are initially FALSE
+       except where noted.  endwin(3x) resets any terminal modes corresponding
+       to these properties; an application  need  not  restore  their  initial
+       values.

                clearok

                -       If clearok is called with TRUE as argument, the next call  to  wrefresh
-       with this window will clear the screen completely and redraw the entire
-       screen from scratch.  This is useful when the contents  of  the  screen
-       are  uncertain, or in some cases for a more pleasing visual effect.  If
-       the win argument to clearok is the global  variable  curscr,  the  next
-       call  to  wrefresh  with any window causes the screen to be cleared and
-       repainted from scratch.
-
-
-

                idlok

                -       If idlok is called with TRUE as second argument, curses considers using
-       the  hardware  insert/delete  line  feature  of  terminals so equipped.
-       Calling idlok with FALSE  as  second  argument  disables  use  of  line
-       insertion  and  deletion.   This  option  should be enabled only if the
-       application needs insert/delete line, for example, for a screen editor.
-       It  is  disabled  by  default  because  insert/delete  line tends to be
-       visually annoying when used in applications  where  it  is  not  really
-       needed.   If  insert/delete  line  cannot  be  used, curses redraws the
-       changed portions of all lines.
+       Setting win's clearok property to TRUE causes the next wrefresh call on
+       it  to clear the terminal screen and redraw it entirely.  This property
+       is useful to restore  the  contents  of  the  screen  (perhaps  because
+       another  process  has  written  to  the  terminal), or in some cases to
+       achieve  a  more  pleasing  visual  effect.   If  win  is  curscr  (see
+       curs_variables(3x)),  the  next  wrefresh call on any window causes the
+       terminal screen to clear and redraw as  above.   wrefresh  resets  this
+       property to FALSE.

                idcok

                -       If idcok is called with FALSE as  second  argument,  curses  no  longer
-       considers   using  the  hardware  insert/delete  character  feature  of
-       terminals so equipped.  Use of character insert/delete  is  enabled  by
-       default.   Calling idcok with TRUE as second argument re-enables use of
-       character insertion and deletion.
+       (This  property  defaults TRUE.)  Setting win's idcok property to FALSE
+       prevents curses from using the insert/delete character capabilities  of
+       terminal types possessing them according to the terminfo database.
+
+
+

                idlok

                +       Setting  win's  idlok  property to TRUE causes curses to consider using
+       the insert/delete line capabilities of terminal types  possessing  them
+       according  to  the  terminfo  database.   Enable  this  option  if  the
+       application explicitly requires these operations, as a full-screen text
+       editor might; otherwise the results may be  visually  annoying  to  the
+       user.

                immedok

                -       If immedok is called with TRUE as second argument, any  change  in  the
-       window  image,  such  as  the  ones caused by waddch, wclrtobot, wscrl,
-       etc., automatically causes a call to wrefresh.  However, it may degrade
-       performance  considerably,  due to repeated calls to wrefresh.  Calling
-       immedok with FALSE as second argument restores  the  default  behavior,
-       i.e., deferring screen updates until a refresh is needed.
+       If  immedok  is  called  with  TRUE  as second argument, changes to the
+       window image, such as those caused  by  waddch,  wclrtobot,  or  wscrl,
+       automatically  cause  a  call  to wrefresh.  Setting a window's immedok
+       property may degrade performance considerably if writes  are  frequent.
+       Calling  immedok  with  FALSE  as  second argument restores the default
+       behavior, deferring  screen  updates  until  a  refresh  is  needed  or
+       explicitly directed by the application.

                leaveok

                -       Normally,  the  hardware  cursor  is left at the location of the window
-       cursor being refreshed.  The leaveok option allows  the  cursor  to  be
-       left  wherever  the  update  happens  to  leave  it.   It is useful for
-       applications where the cursor is not used, since it  reduces  the  need
-       for cursor motions.
+       Normally,  curses  leaves  the  hardware cursor at the library's cursor
+       location of the window being refreshed.  The leaveok option allows  the
+       cursor  to  be  left  wherever  the  update happens to leave it.  It is
+       useful for applications that do not employ a visible cursor,  since  it
+       reduces the need for cursor motions.

                scrollok

                -       The  scrollok  option controls what happens when the cursor of a window
-       is moved off the edge of the window or scrolling region,  either  as  a
-       result  of  a  newline  action  on  the bottom line, or typing the last
-       character of the last line.  If disabled, (bf is FALSE), the cursor  is
-       left  on  the  bottom  line.   If  enabled, (bf is TRUE), the window is
-       scrolled up one line (Note that to get the physical scrolling effect on
-       the terminal, it is also necessary to call idlok).
+       The  scrollok option controls what happens when a window's cursor moves
+       off the edge of the window or scrolling region, as a result  of  either
+       (1)  writing  a  newline  anywhere on its bottom line, or (2) writing a
+       character that advances the cursor to the last position on  its  bottom
+       line.   If  disabled  (bf  is  FALSE),  curses leaves the cursor on the
+       bottom line of the window.  If enabled (bf is TRUE), curses scrolls the
+       window up one line.  (To get  the  physical  scrolling  effect  on  the
+       terminal, the application must also enable idlok).

                setscrreg, wsetscrreg

                -       The  setscrreg and wsetscrreg routines allow the application programmer
-       to set a software scrolling region  in  a  window.   The  top  and  bot
-       parameters  are  the  line  numbers of the top and bottom margin of the
-       scrolling region.  (Line 0 is the top line of  the  window.)   If  this
-       option  and  scrollok  are  enabled,  an attempt to move off the bottom
-       margin line causes all lines in the scrolling region to scroll one line
-       in  the  direction  of  the first line.  Only the text of the window is
-       scrolled.  (Note that this has nothing to do with the use of a physical
-       scrolling  region  capability  in the terminal, like that in the VT100.
-       If idlok is enabled and the terminal has either a scrolling  region  or
-       insert/delete line capability, they will probably be used by the output
-       routines.)
+       The  wsetscrreg  and setscrreg functions allow the application to set a
+       software  scrolling  region  in  the  specified   window   or   stdscr,
+       respectively.   The  top and bot parameters are the line numbers of the
+       top and bottom margin of the scrolling  region.   If  this  option  and
+       scrollok  are  enabled,  an  attempt to move off the bottom margin line
+       causes all lines in the scrolling region to  scroll  one  line  in  the
+       direction  of the first line.  Only the text of the window is scrolled.
+       (This process has nothing to do with the scrolling region capability of
+       the terminal, as found in the DEC VT100.)  If idlok is enabled and  the
+       terminal   has   either   a  scrolling  region  or  insert/delete  line
+       capability, they will probably be used by the output routines.

                RETURN VALUE

                @@ -148,55 +145,72 @@
        upon  failure.  All other routines that return an integer always return
        OK.
 
-       X/Open Curses does not specify any error conditions.
+       In ncurses, these functions fail if
 
-       In this implementation,
+       o   the curses screen has not been initialized,
 
-       o   those functions that have a window pointer will return an error  if
-           the window pointer is null
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer, or
 
-       o   wsetscrreg  returns  an error if the scrolling region limits extend
-           outside the window boundaries.
+       o   (for  setscrreg  and  wsetscrreg)  the function is passed arguments
+           describing a scrolling region with limits that extend  outside  the
+           window boundaries.

                NOTES

                -       Note that clearok, leaveok,  scrollok,  idcok,  and  setscrreg  may  be
+       clearok,  leaveok, scrollok, idcok, and setscrreg may be implemented as
        macros.
 
-       The  immedok  routine  is  useful for windows that are used as terminal
-       emulators.
+       Unlike the other functions described by this page, setscrreg  does  not
+       accept  a  pointer-to-WINDOW  parameter,  but  operates on stdscr.  Use
+       wsetscrreg to configure the scrolling region of a selected window.
+
+       Historically, applications used idcok(FALSE) to accommodate the  "magic
+       cookie"  feature  of some terminal types; see subsection "Highlighting,
+       Underlining, and Visible Bells" of terminfo(5).  When updating a  line,
+       the  presence  of  character  cells with magic cookies in them made the
+       curses library's computations of characters to be rewritten inaccurate.
+       A  better  solution  is  to  indicate  the  magic_cookie_glitch   (xmc)
+       capability in the terminal's type description.
+
+       immedok is useful for windows that are used as terminal emulators.

                PORTABILITY

                -       These functions are described in X/Open Curses, Issue 4.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       Some historic curses implementations had, as an  undocumented  feature,
-       the  ability  to  do  the  equivalent  of  clearok(...,  1)  by  saying
-       touchwin(stdscr) or clear(stdscr).  This will not work under ncurses.
+       Some  historic  curses implementations, as an undocumented feature, did
+       the  equivalent  of  "clearok(...,   1)"   when   touchwin(stdstr)   or
+       clear(stdstr) were used.  This trick does not work with ncurses.
 
-       Earlier System V curses implementations specified  that  with  scrollok
-       enabled,  any  window  modification  triggering  a scroll also forced a
-       physical refresh.  X/Open Curses does not  require  this,  and  ncurses
-       avoids  doing  it  to  perform  better  vertical-motion optimization at
-       wrefresh time.
+       Early  System V  curses  implementations  specified  that with scrollok
+       enabled, any window modification triggering  a  scroll  also  forced  a
+       physical  refresh.   X/Open  Curses  does not require this, and ncurses
+       avoids doing so to better optimize vertical motions upon a wrefresh.
 
        X/Open Curses does not mention that the cursor should be made invisible
-       as  a side-effect of leaveok.  SVr4 curses documentation does this, but
-       the code does not.  Use curs_set to make the cursor invisible.
+       as a side effect of leaveok.   SVr4  curses  documentation  notes  this
+       behavior,  but  the code neglects to implement it.  Use curs_set(3x) to
+       make the cursor invisible.

                HISTORY

                -       ncurses formerly treated nl(3x) and nonl(3x) as both input  and  output
-       options, but no longer; see curs_inopts(3x).
+       4BSD (1980) introduced clearok, leaveok, and scrollok.
+
+       SVr2 (1984) supplied idlok, setscrreg, and wsetscrreg.
+
+       SVr3.1 (1987) implemented idcok and immedok.
+
+       ncurses formerly treated nl and nonl as both input and output  options,
+       but no longer; see curs_inopts(3x).

                SEE ALSO

                        curses(3x),     curs_addch(3x),    curs_clear(3x),    curs_initscr(3x),
        curs_refresh(3x), curs_scroll(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                  curs_outopts(3x)
+ncurses 6.6                       2025-11-11                  curs_outopts(3x)
                  @@ -205,8 +219,8 @@ ncurses 6.5 2024-04-20 DESCRIPTION
                  • clearok
                    • -
                  • idlok
                  • idcok
                    • +
                  • idlok
                  • immedok
                  • leaveok
                  • scrollok
                    • diff --git a/doc/html/man/curs_overlay.3x.html b/doc/html/man/curs_overlay.3x.html index 61c4c19..5b431a4 100644 --- a/doc/html/man/curs_overlay.3x.html +++ b/doc/html/man/curs_overlay.3x.html @@ -1,6 +1,6 @@ -curs_overlay 3x 2024-04-20 ncurses 6.5 Library calls +curs_overlay 3x 2025-01-18 ncurses 6.6 Library calls -

                    curs_overlay 3x 2024-04-20 ncurses 6.5 Library calls

                    +

                    curs_overlay 3x 2025-01-18 ncurses 6.6 Library calls

                     curs_overlay(3x)                 Library calls                curs_overlay(3x)
 
 
-
-

                    NAME

                            overlay,  overwrite,  copywin  -  overlay curses windows and manipulate
        them
@@ -66,47 +64,48 @@

                    overlay, overwrite

                            The overlay and overwrite routines overlay srcwin  on  top  of  dstwin.
        scrwin and dstwin are not required to be the same size; only text where
-       the two windows overlap is copied.  The difference is that  overlay  is
-       non-destructive   (blanks   are   not   copied)  whereas  overwrite  is
+       the  two  windows overlap is copied.  The difference is that overlay is
+       non-destructive  (blanks  are  not   copied)   whereas   overwrite   is
        destructive.

                    copywin

                    -       The copywin routine provides a finer granularity of  control  over  the
+       The  copywin  routine  provides a finer granularity of control over the
        overlay  and  overwrite  routines.   As  in  the  prefresh  routine,  a
-       rectangle is specified in the destination  window,  (dminrow,  dmincol)
-       and  (dmaxrow,  dmaxcol),  and the upper-left-corner coordinates of the
-       source window, (sminrow, smincol).  If the argument  overlay  is  true,
+       rectangle  is  specified  in the destination window, (dminrow, dmincol)
+       and (dmaxrow, dmaxcol), and the upper-left-corner  coordinates  of  the
+       source  window,  (sminrow,  smincol).  If the argument overlay is true,
        then copying is non-destructive, as in overlay.

                    RETURN VALUE

                    -       These  routines  return  the  integer  ERR upon failure and an OK (SVr4
-       specifies only "an integer  value  other  than  ERR")  upon  successful
-       completion.
+       These functions return OK on success and ERR on failure.
 
-       X/Open  defines  no error conditions.  In this implementation, copywin,
-       overlay and overwrite return an error if either of the window  pointers
-       are null, or if some part of the window would be placed off-screen.
+       In ncurses, they return ERR if
+
+       o   either of the window pointers are null, or
+
+       o   any part of the window would be placed off-screen.

                    NOTES

                    -       Note that overlay and overwrite may be macros.
+       overlay and overwrite may be implemented as macros.

                    PORTABILITY

                    -       These  functions  are  described  in X/Open Curses, Issue 4, which adds
-       const qualifiers to the arguments.  It further specifies their behavior
-       in  the  presence  of  characters  with  multibyte  renditions (not yet
-       supported in this implementation).
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.  It adds const qualifiers to  the  arguments.   It
+       further  specifies  their  behavior  in the presence of characters with
+       multibyte renditions (not yet supported in this implementation).
+
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".

                    SEE ALSO

                            curses(3x), curs_pad(3x), curs_refresh(3x)
 
-
-
-ncurses 6.5                       2024-04-20                  curs_overlay(3x)
+ncurses 6.6                       2025-01-18                  curs_overlay(3x)
                      diff --git a/doc/html/man/curs_pad.3x.html b/doc/html/man/curs_pad.3x.html index ae27590..b1ed179 100644 --- a/doc/html/man/curs_pad.3x.html +++ b/doc/html/man/curs_pad.3x.html @@ -1,6 +1,6 @@ -curs_pad 3x 2024-04-27 ncurses 6.5 Library calls +curs_pad 3x 2025-08-23 ncurses 6.6 Library calls -

                      curs_pad 3x 2024-04-27 ncurses 6.5 Library calls

                      +

                      curs_pad 3x 2025-08-23 ncurses 6.6 Library calls

                       curs_pad(3x)                     Library calls                    curs_pad(3x)
 
 
-
-

                      NAME

                              newpad, subpad, prefresh, pnoutrefresh, pechochar, pecho_wchar - create
        and display curses pads
@@ -68,25 +66,25 @@

                      DESCRIPTION

                      -       A curses pad is like a window, except that it is not restricted by  the
-       screen  size,  and is not necessarily associated with a particular part
-       of the screen.  Pads can be used when a large window  is  needed,  only
+       A  curses pad is like a window, except that it is not restricted by the
+       screen size, and is not necessarily associated with a  particular  part
+       of  the  screen.   Pads can be used when a large window is needed, only
        part  of  which  is  to  be  visible  on  the  screen.   Pads  are  not
        automatically refreshed by scrolling or input-echoing operations.
 
-       Pads  cannot  be  refreshed  with   wrefresh(3x);   use   prefresh   or
+       Pads   cannot   be   refreshed   with  wrefresh(3x);  use  prefresh  or
        pnoutrefresh instead.

                      newpad

                      -       newpad  creates  and returns a pointer to a new pad data structure with
+       newpad creates and returns a pointer to a new pad data  structure  with
        the given number of lines, nlines, and columns, ncols.

                      subpad

                      -       subpad creates and returns a pointer to a subwindow within a  pad  with
+       subpad  creates  and returns a pointer to a subwindow within a pad with
        the  given  number  of  lines,  nlines,  and  columns,  ncols.   Unlike
-       subwin(3x), which uses screen coordinates, the new  pad  is  placed  at
+       subwin(3x),  which  uses  screen  coordinates, the new pad is placed at
        position (begin_y, begin_x) relative to its parent.  Thus, changes made
        to one pad can affect both.  When operating on a subpad,  it  is  often
        necessary  to  call  touchwin(3x)  or  touchline(3x)  on  parent before
@@ -99,10 +97,10 @@
        They require additional parameters are needed to indicate what portions
        of the pad and screen are involved.
 
-       o   pminrow  and  pmincol  specify  the  upper  left-hand  corner  of a
+       o   pminrow and  pmincol  specify  the  upper  left-hand  corner  of  a
            rectangular view of the pad.
 
-       o   sminrow, smincol, smaxrow, and smaxcol specify the vertices of  the
+       o   sminrow,  smincol, smaxrow, and smaxcol specify the vertices of the
            rectangle to be displayed on the screen.
 
        The lower right-hand corner of the rectangle to be displayed in the pad
@@ -122,115 +120,123 @@

                      pecho_wchar

                              pecho_wchar is functionally equivalent to calling wadd_wch(3x) followed
-       by prefresh.  It suggests to the curses optimizer that  only  a  single
-       wide  character is being output; a considerable performance benefit may
-       be thus enjoyed.  The location of the character wch written to the  pad
+       by  prefresh.   It  suggests to the curses optimizer that only a single
+       wide character is being output; a considerable performance benefit  may
+       be  thus enjoyed.  The location of the character wch written to the pad
        is used to populate the arguments to prefresh.

                      RETURN VALUE

                      -       Functions  that  return an integer return ERR upon failure and OK (SVr4
-       specifies only "an integer  value  other  than  ERR")  upon  successful
-       completion.
+       Functions that return an integer return ERR upon failure  and  OK  upon
+       successful completion.
 
-       Functions  that  return pointers return NULL on error, and set errno to
-       ENOMEM.
+       Functions  that  return  pointers return a null pointer on failure, and
+       set errno to ENOMEM.
 
-       X/Open  Curses  does  not  specify  any  error  conditions.   In   this
-       implementation
+       In this implementation
 
           prefresh and pnoutrefresh
-               return an error if the window pointer is null, or if the window
-               is not really a pad or if the  area  to  refresh  extends  off-
-               screen  or  if  the  minimum  coordinates  are greater than the
-               maximum.
+               return ERR if the window pointer is null, or if the  window  is
+               not  really  a pad or if the area to refresh extends off-screen
+               or if the minimum coordinates are greater than the maximum.
 
           pechochar
-               returns an error if the window is not really  a  pad,  and  the
-               associated call to wechochar returns an error.
+               returns ERR if  the  window  is  not  really  a  pad,  and  the
+               associated call to wechochar returns ERR.
 
           pecho_wchar
-               returns  an  error  if  the window is not really a pad, and the
-               associated call to wecho_wchar returns an error.
+               returns  ERR  if  the  window  is  not  really  a  pad, and the
+               associated call to wecho_wchar returns ERR.

                      NOTES

                      -       pechochar may be a macro.
+       pechochar may be implemented as a macro.
 
+       curses documentation is traditionally averse  to  motivating  the  term
+       "pad".   The  Apollo  Aegis  workstation  operating system (circa 1981)
+       supported a graphical pad feature.
 
-

                      PORTABILITY

                      -       BSD curses has no pad feature.
-
-       SVr2  curses  (1986)  provided  the  newpad  and   related   functions,
-       documenting  them  in  a  single  line each.  SVr3 (1987) provided more
-       extensive documentation.
-
-       The documentation does not explain the term pad.  However,  the  Apollo
-       Aegis workstation operating system supported a graphical pad feature:
-
-       o   These  graphical  pads  could  be  much  larger than the computer's
+       o   These graphical pads could  be  much  larger  than  the  computer's
            display.
 
-       o   The read-only output from a  command  could  be  scrolled  back  to
-           inspect, and select text from the pad.
+       o   The  read-only  output  from  a  command  could be scrolled back to
+           inspect and select text from the pad.
 
        The two uses may be related.
 
-       X/Open  Curses,  Issue 4 describes these functions, without significant
-       change from the SVr3 documentation.  It describes no error  conditions.
-       The  behavior  of  subpad  if  the  parent  window  is  not  a  pad  is
-       undocumented, and is not checked by the vendor Unix implementations:
 
-       o   SVr4 curses sets a flag in the WINDOW  structure  in  newpad  which
-           tells if the window is a pad.
+

                      PORTABILITY

                      +       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-           However,  it  uses this information only in waddch (to decide if it
-           should call wrefresh) and wscrl (to avoid  scrolling  a  pad),  and
-           does  not  check  in  wrefresh  to ensure that the pad is refreshed
-           properly.
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
 
-       o   Solaris xcurses checks whether a window is a pad  in  wnoutrefresh,
-           returning ERR in that case.
+       The  behavior  of  subpad  if  the  parent  window  is  not  a  pad  is
+       undocumented, and is not checked by the vendor Unix implementations.
 
-           However,  it only sets the flag for subwindows if the parent window
-           is a pad.  Its newpad  function  does  not  set  this  information.
-           Consequently, the check will never fail.
+       o   SVr4 curses's newpad sets a flag in the WINDOW structure indicating
+           that the window is a pad.
 
-           It  makes no comparable check in pnoutrefresh, though interestingly
-           enough, a comment in the source code states  that  the  lack  of  a
-           check was an MKS extension.
+           However, it uses this information only in waddch (to decide  if  it
+           should  call  wrefresh)  and  wscrl (to avoid scrolling a pad); its
+           wrefresh does not check  it  to  ensure  that  a  pad  is  properly
+           updated.
 
-       o   NetBSD  7 curses sets a flag in the WINDOW structure for newpad and
-           subpad,  using  this  to  help   with   the   distinction   between
-           wnoutrefresh and pnoutrefresh.
+       o   Solaris   xcurses   checks  whether  a  window  is  a  pad  in  its
+           wnoutrefresh, returning ERR in that case.
+
+           However, it sets the flag on subwindows only if the  parent  window
+           is a pad.  Its newpad does not set this information.  Consequently,
+           the check never fails.
+
+           It   makes   no   comparable   check   in  pnoutrefresh  --  though
+           interestingly enough, a comment in the source code states that  the
+           lack of a check was an MKS extension.
+
+       o   NetBSD 7  curses sets a flag in the WINDOW structure for newpad and
+           subpad, aiding  itself  to  distinguish  between  wnoutrefresh  and
+           pnoutrefresh.
 
            It  does  not  check for the case where a subwindow is created in a
-           pad using subwin or derwin.
+           pad using subwin or derwin.
 
-           The dupwin function returns a regular  window  when  duplicating  a
-           pad.   Likewise,  getwin always returns a window, even if the saved
+           Its dupwin  returns  a  regular  window  when  duplicating  a  pad.
+           Likewise,  its  getwin  always  returns a window, even if the saved
            data was from a pad.
 
-       This implementation
+       ncurses:
 
-       o   sets a flag in the WINDOW structure for newpad and subpad,
+       o   sets a flag in the WINDOW structure for newpad and subpad,
 
-       o   allows a subwin or derwin call to succeed having a  pad  parent  by
+       o   allows a subwin or derwin call to succeed having a  pad  parent  by
            forcing the subwindow to be a pad,
 
-       o   checks  in  both  wnoutrefresh and pnoutrefresh to ensure that pads
+       o   checks  in  both  wnoutrefresh and pnoutrefresh to ensure that pads
            and windows are handled distinctly, and
 
-       o   ensures  that  dupwin  and  getwin  treat   pads   versus   windows
+       o   ensures  that  dupwin  and  getwin  treat   pads   versus   windows
            consistently.
 
 
+

                      HISTORY

                      +       SVr2  (1984) introduced newpad, prefresh, and pnoutrefresh, documenting
+       them in a single line each.
+
+       SVr3 (1987) added subpad and pechochar,  and  provided  more  extensive
+       documentation.
+
+       The  System V  Interface  Definition,  Version  4  (1995),  specified a
+       function named pechowchar.  This was a later addition  to  SVr4.x,  not
+       appearing  in  the  first  SVr4 (1989).  It differs from X/Open's later
+       pecho_wchar in that its wstr  parameter  was  a  chtype  instead  of  a
+       wchar_t, and was not const-qualified.
+
+

                      SEE ALSO

                              curses(3x), curs_addch(3x), curs_refresh(3x), curs_touch(3x)
 
-
-
-ncurses 6.5                       2024-04-27                      curs_pad(3x)
+ncurses 6.6                       2025-08-23                      curs_pad(3x)
                      diff --git a/doc/html/man/curs_print.3x.html b/doc/html/man/curs_print.3x.html index 92fb48d..74177ac 100644 --- a/doc/html/man/curs_print.3x.html +++ b/doc/html/man/curs_print.3x.html @@ -1,6 +1,6 @@ -curs_print 3x 2024-03-16 ncurses 6.5 Library calls +curs_print 3x 2025-02-15 ncurses 6.6 Library calls -

                      curs_print 3x 2024-03-16 ncurses 6.5 Library calls

                      +

                      curs_print 3x 2025-02-15 ncurses 6.6 Library calls

                       curs_print(3x)                   Library calls                  curs_print(3x)
 
 
-
-

                      NAME

                              mcprint - write binary data to printer using terminfo capabilities
 
@@ -53,57 +51,63 @@

                      SYNOPSIS

                              #include <curses.h>
 
-       int mcprint(char *data, int len);
+       int mcprint(char * data, int len);

                      DESCRIPTION

                      -       This  function  uses  the mc5p or mc4 and mc5 capabilities, if they are
-       present, to ship given data to a printer attached to the terminal.
+       mcprint,   an  ncurses  extension  to  the  curses  library,  uses  the
+       terminal's prtr_non (mc5p) or prtr_on (mc5) and  prtr_off  (mc4)  media
+       copy  capabilities,  if  defined, to send len bytes of the given string
+       data to a printer attached to the terminal.
 
-       Note that the mcprint code has no way  to  do  flow  control  with  the
-       printer  or  to  know  how  much buffering it has.  Your application is
-       responsible for keeping the rate of writes to  the  printer  below  its
-       continuous  throughput  rate  (typically  about half of its nominal cps
-       rating).   Dot-matrix  printers  and   6-page-per-minute   lasers   can
-       typically  handle  80cps,  so  a  good conservative rule of thumb is to
-       sleep for a second after shipping each 80-character line.
+       mcprint has no means of flow control to the printer nor of knowing  how
+       much buffering it has.  Your application is responsible for keeping the
+       rate  of  writes  to  the printer below its continuous throughput rate,
+       typically about half of its nominal characters-per-second (cps) rating.
+       Dot-matrix printers and 6-page-per-minute laser printers can  typically
+       handle  80  cps,  so  a  conservative rule of thumb is to sleep for one
+       second after sending an 80-character line.

                      RETURN VALUE

                      -       The mcprint function returns ERR if the  write  operation  aborted  for
-       some  reason.   In  this  case,  errno  will  contain  either  an error
-       associated with write(2) or one of the following:
+       On success, mcprint returns  the  number  of  characters  sent  to  the
+       printer.
+
+       mcprint  returns  ERR  if the write operation fails for any reason.  In
+       that event, errno contains either a value set by write(2),  or  one  of
+       the following.
 
        ENODEV
-            Capabilities for printer redirection do not exist.
+            The terminal lacks relevant media copy capabilities.
 
        ENOMEM
-            Couldn't allocate sufficient memory to buffer the printer write.
-
-       When mcprint succeeds, it returns the  number  of  characters  actually
-       sent to the printer.
+            ncurses  could  not allocate sufficient memory to buffer the write
+            operation.

                      EXTENSIONS

                      -       mcprint was designed for ncurses(3x), and was not found in SVr4 curses,
-       4.4BSD curses, or any other previous curses implementation.
+       mcprint is an ncurses(3x) extension, and is not found in  SVr4  curses,
+       4.4BSD curses, or any other previous curses implementation.

                      PORTABILITY

                      -       Applications employing this ncurses extension should condition its  use
+       Applications  employing this ncurses extension should condition its use
        on the visibility of the NCURSES_VERSION preprocessor macro.
 
 
+

                      HISTORY

                      +       ncurses introduced mcprint prior to version 1.9.9g (1996).
+
+

                      BUGS

                      -       Padding in the mc5p, mc4, and mc5 capabilities is not interpreted.
+       Padding in the prtr_non  (mc5p),  prtr_on  (mc5),  and  prtr_off  (mc4)
+       capabilities is not interpreted.

                      SEE ALSO

                              curses(3x)
 
-
-
-ncurses 6.5                       2024-03-16                    curs_print(3x)
+ncurses 6.6                       2025-02-15                    curs_print(3x)
                      diff --git a/doc/html/man/curs_printw.3x.html b/doc/html/man/curs_printw.3x.html index 259b561..c4a3743 100644 --- a/doc/html/man/curs_printw.3x.html +++ b/doc/html/man/curs_printw.3x.html @@ -1,6 +1,6 @@ -curs_printw 3x 2024-04-20 ncurses 6.5 Library calls +curs_printw 3x 2025-08-16 ncurses 6.6 Library calls -

                      curs_printw 3x 2024-04-20 ncurses 6.5 Library calls

                      +

                      curs_printw 3x 2025-08-16 ncurses 6.6 Library calls

                       curs_printw(3x)                  Library calls                 curs_printw(3x)
 
 
-
-

                      NAME

                              printw,  wprintw,  mvprintw,  mvwprintw,  vwprintw,  vw_printw  - write
        formatted output to a curses window
@@ -80,74 +78,75 @@
        These functions return ERR upon failure and OK upon success.
 
        In ncurses, failure occurs if the library cannot allocate enough memory
-       for the buffer into which the output is formatted,  or  if  the  window
+       for  the  buffer  into  which the output is formatted, or if the window
        pointer win is null.
 
-       Functions  prefixed with "mv" first perform cursor movement and fail if
+       Functions prefixed with "mv" first perform cursor movement and fail  if
        the position (y, x) is outside the window boundaries.

                      NOTES

                      -       No wide character counterpart  functions  are  defined  by  the  "wide"
+       No  wide  character  counterpart  functions  are  defined by the "wide"
        ncurses configuration nor by any standard.  To format and write a wide-
        character string to a curses window,  consider  using  swprintf(3)  and
        waddwstr(3x) or similar.

                      PORTABILITY

                      -       X/Open  Curses,  Issue  4  describes  these functions.  It specifies no
-       error conditions for them.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       ncurses defines vw_printw and vwprintw identically  to  support  legacy
+       ncurses  defines  vw_printw  and vwprintw identically to support legacy
        applications.  However, the latter is obsolete.
 
-       o   X/Open  Curses,  Issue  4  Version  2  (1996),  marked  vwprintw as
-           requiring varargs.h and "TO BE WITHDRAWN", and specified  vw_printw
+       o   X/Open  Curses  Issue 4  Version 2  (1996),  marked   vwprintw   as
+           requiring  varargs.h and "TO BE WITHDRAWN", and specified vw_printw
            using the stdarg.h interface.
 
-       o   X/Open  Curses,  Issue  5,  Draft 2 (December 2007) marked vwprintw
+       o   X/Open Curses Issue 5, Draft  2  (December  2007)  marked  vwprintw
            (along with vwscanw and the termcap interface) as withdrawn.  After
-           incorporating  review  comments, this became X/Open Curses, Issue 7
+           incorporating  review  comments,  this became X/Open Curses Issue 7
            (2009).
 
        o   ncurses provides vwprintw, but marks it as deprecated.

                      HISTORY

                      -       While printw was implemented in 4BSD (November  1980),  it  was  unused
-       until  4.2BSD  (August  1983), which employed it for games.  That early
-       version of curses preceded the ANSI C standard of 1989.  It did not use
-       varargs.h,  though  that  had been available since Seventh Edition Unix
-       (1979).  In 1991 (a couple of years after SVr4 was generally available,
-       and  after  the C standard was published), other developers updated the
-       library, using stdarg.h internally in 4.4BSD curses.   Even  with  this
-       improvement,  BSD  curses  did  not  use  function prototypes (nor even
-       declare functions) in curses.h until 1992.
+       4BSD (1980) introduced wprintw and its variants.  It implemented all as
+       functions, not macros; this initial distribution of curses preceded the
+       ANSI C standard of 1989, prior to which a variadic macro  facility  was
+       not  widely  available in the language.  printw went unused in Berkeley
+       distributions until 4.1cBSD (1983), which employed it in games.  4BSD's
+       wprintw did not use varargs.h, which had been available  since  Seventh
+       Edition  Unix  (1979).   In  1991  (a  couple  of  years after SVr4 was
+       generally available, and after the C  standard  was  published),  other
+       developers  updated  the  library,  using stdarg.h internally in 4.4BSD
+       curses.  Even with this improvement, BSD curses did  not  use  function
+       prototypes (nor even declare functions) in curses.h until 1992.
 
-       SVr2 (1984) documented printw and wprintw tersely as "printf on stdscr"
-       and "printf on win", respectively.
+       4BSD  documented  printw  and wprintw tersely as "printf on stdscr" and
+       "printf on win", respectively.
 
-       SVr3  (1987)  added  mvprintw  and mvwprintw, with a three-line summary
-       asserting that they were analogous to printf(3),  explaining  that  the
-       string  that  printf(3) would write to the standard output stream would
-       instead be output  using  waddstr  to  the  given  window.   SVr3  also
-       implemented  vwprintw,  describing  its  third  parameter as a va_list,
-       defined in varargs.h, and referred the reader to the manual  pages  for
+       SVr3 summarized the functions in three lines, asserting that they  were
+       analogous  to  printf(3)  and explaining that the string that printf(3)
+       would write to the standard output stream would instead be output using
+       waddstr to the given window.
+
+       SVr3 added vwprintw, describing  its  third  parameter  as  a  va_list,
+       defined  in  varargs.h, and referred the reader to the manual pages for
        varargs and vprintf for detailed descriptions.
 
-       SVr4  (1989)  introduced  no new variations of printw, but provided for
+       SVr4 (1989) introduced no new variations of printw,  but  provided  for
        using either varargs.h or stdarg.h to define the va_list type.
 
-       X/Open Curses, Issue 4 (1995), defined vw_printw to  replace  vwprintw,
+       X/Open  Curses  Issue 4  (1995), defined vw_printw to replace vwprintw,
        stating that its va_list type is defined in stdarg.h.

                      SEE ALSO

                              curses(3x), curs_addstr(3x), curs_scanw(3x), printf(3), vprintf(3)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_printw(3x)
+ncurses 6.6                       2025-08-16                   curs_printw(3x)
                        diff --git a/doc/html/man/curs_refresh.3x.html b/doc/html/man/curs_refresh.3x.html index 4beec32..87d3ab3 100644 --- a/doc/html/man/curs_refresh.3x.html +++ b/doc/html/man/curs_refresh.3x.html @@ -1,6 +1,6 @@ -curs_refresh 3x 2024-04-20 ncurses 6.5 Library calls +curs_refresh 3x 2025-01-18 ncurses 6.6 Library calls -

                        curs_refresh 3x 2024-04-20 ncurses 6.5 Library calls

                        +

                        curs_refresh 3x 2025-01-18 ncurses 6.6 Library calls

                         curs_refresh(3x)                 Library calls                curs_refresh(3x)
 
 
-
-

                        NAME

                                doupdate,  redrawwin,  refresh,  wnoutrefresh,  wredrawln,  wrefresh  -
        refresh curses windows or lines thereupon
@@ -96,19 +94,19 @@
            physical screen and does the actual update.
 
        If the programmer wishes to output several windows at once, a series of
-       calls to wrefresh results in  alternating  calls  to  wnoutrefresh  and
-       doupdate,  causing  several  bursts  of output to the screen.  By first
-       calling wnoutrefresh for each window,  it  is  then  possible  to  call
-       doupdate  once, resulting in only one burst of output, with fewer total
+       calls  to  wrefresh  results  in  alternating calls to wnoutrefresh and
+       doupdate, causing several bursts of output to  the  screen.   By  first
+       calling  wnoutrefresh  for  each  window,  it  is then possible to call
+       doupdate once, resulting in only one burst of output, with fewer  total
        characters transmitted and less CPU time used.
 
-       If the win argument to wrefresh  is  the  physical  screen  (i.e.,  the
-       global   variable  curscr),  the  screen  is  immediately  cleared  and
+       If  the  win  argument  to  wrefresh  is the physical screen (i.e., the
+       global  variable  curscr),  the  screen  is  immediately  cleared   and
        repainted from scratch.
 
-       The phrase "copies the named window to the  virtual  screen"  above  is
-       ambiguous.   What  actually happens is that all touched (changed) lines
-       in the window are copied to the virtual screen.  This affects  programs
+       The  phrase  "copies  the  named window to the virtual screen" above is
+       ambiguous.  What actually happens is that all touched  (changed)  lines
+       in  the window are copied to the virtual screen.  This affects programs
        that use overlapping windows; it means that if two windows overlap, you
        can refresh them in  either  order  and  the  overlap  region  will  be
        modified  only  when it is explicitly changed.  (But see the section on
@@ -123,44 +121,42 @@

                        RETURN VALUE

                        -       These  routines  return  the  integer  ERR  upon  failure  and OK (SVr4
-       specifies only "an integer  value  other  than  ERR")  upon  successful
-       completion.
+       These routines return the integer ERR upon failure and OK
 
-       X/Open   Curses  does  not  specify  any  error  conditions.   In  this
-       implementation
+       In this implementation
 
           wnoutrefresh
-               returns an error if the window  pointer  is  null,  or  if  the
-               window is really a pad.
+               returns  ERR if the window pointer is null, or if the window is
+               really a pad.
 
           wredrawln
-               returns  an  error if the associated call to touchln returns an
-               error.
+               return ERR if the associated call to touchln returns ERR.

                        NOTES

                        -       Note that refresh and redrawwin may be macros.
+       refresh and redrawwin may be implemented as macros.

                        PORTABILITY

                        -       X/Open Curses, Issue 4 describes these functions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       Whether wnoutrefresh copies to the virtual screen the  entire  contents
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+
+       Whether  wnoutrefresh  copies to the virtual screen the entire contents
        of a window or just its changed portions has never been well-documented
        in historic curses versions (including SVr4).  It might  be  unwise  to
        rely  on  either behavior in programs that might have to be linked with
        other curses implementations.  Instead, you can do an explicit touchwin
-       before  the  wnoutrefresh  call  to  guarantee  an entire-contents copy
+       before the wnoutrefresh  call  to  guarantee  an  entire-contents  copy
        anywhere.

                        SEE ALSO

                        -       curses(3x), curs_outopts(3x) curs_variables(3x)
+       curses(3x), curs_outopts(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                  curs_refresh(3x)
+ncurses 6.6                       2025-01-18                  curs_refresh(3x)
                          diff --git a/doc/html/man/curs_scanw.3x.html b/doc/html/man/curs_scanw.3x.html index d0b9b79..6e7f697 100644 --- a/doc/html/man/curs_scanw.3x.html +++ b/doc/html/man/curs_scanw.3x.html @@ -1,6 +1,6 @@ -curs_scanw 3x 2024-04-20 ncurses 6.5 Library calls +curs_scanw 3x 2025-07-05 ncurses 6.6 Library calls -

                          curs_scanw 3x 2024-04-20 ncurses 6.5 Library calls

                          +

                          curs_scanw 3x 2025-07-05 ncurses 6.6 Library calls

                           curs_scanw(3x)                   Library calls                  curs_scanw(3x)
 
 
-
-

                          NAME

                                  scanw,  wscanw,  mvscanw,  mvwscanw, vwscanw, vw_scanw - read formatted
        input from a curses window
@@ -100,19 +98,19 @@

                          PORTABILITY

                          -       X/Open Curses, Issue 4 describes  these  functions.   It  specifies  no
-       error conditions for them.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       ncurses  defines  vw_scanw  and  vwscanw  identically to support legacy
+       ncurses defines vw_scanw and  vwscanw  identically  to  support  legacy
        applications.  However, the latter is obsolete.
 
-       o   X/Open  Curses,  Issue  4  Version  2  (1996),  marked  vwscanw  as
-           requiring  varargs.h  and "TO BE WITHDRAWN", and specified vw_scanw
-           using the stdarg.h interface.
+       o   X/Open Curses Issue 4 Version 2 (1996), marked vwscanw as requiring
+           varargs.h  and  "TO BE WITHDRAWN", and specified vw_scanw using the
+           stdarg.h interface.
 
-       o   X/Open Curses, Issue 5, Draft  2  (December  2007)  marked  vwscanw
+       o   X/Open Curses Issue 5,  Draft  2  (December  2007)  marked  vwscanw
            (along with vwscanw and the termcap interface) as withdrawn.  After
-           incorporating review comments, this became X/Open Curses,  Issue  7
+           incorporating  review  comments,  this became X/Open Curses Issue 7
            (2009).
 
        o   ncurses provides vwscanw, but marks it as deprecated.
@@ -141,45 +139,42 @@

                          HISTORY

                          -       scanw  was  implemented  in 4BSD (November 1980); that early version of
-       curses preceded the ANSI C standard of 1989.  The function  was  unused
-       in  Berkeley  distributions  for  over  ten  years, until 4.4BSD, which
-       employed it in a game.  The 4BSD scanw did not  use  varargs.h,  though
-       that  had been available since Seventh Edition Unix (1979).  In 1991 (a
-       couple of years after SVr4 was generally available,  and  after  the  C
-       standard  was  published),  other developers updated the library, using
-       stdarg.h internally in 4.4BSD curses.  Even with this improvement,  BSD
-       curses  did not use function prototypes (nor even declare functions) in
-       curses.h until 1992.
+       4BSD  (1980) introduced wscanw and its variants.  It implemented all as
+       functions, not macros; this initial distribution of curses preceded the
+       ANSI C standard of 1989, prior to which a variadic macro  facility  was
+       not  widely  available.   scanw  went  unused in Berkeley distributions
+       until 4.3BSD-Reno (1990), which employed it in a game.   4BSD's  wscanw
+       did  not  use varargs.h, which had been available since Seventh Edition
+       Unix (1979).  In 1991 (a couple  of  years  after  SVr4  was  generally
+       available,  and  after  the C standard was published), other developers
+       updated the library, using stdarg.h internally in 4.4BSD curses.   Even
+       with  this improvement, BSD curses did not use function prototypes (nor
+       even declare functions) in curses.h until 1992.
 
-       SVr2 (1984) documented scanw  and  wscanw  tersely  as  "scanf  through
-       stdscr" and "scanf through win", respectively.
+       4BSD documented scanw and wscanw tersely as "scanf through stdscr"  and
+       "scanf through win", respectively.  SVr3 (1987) stated
 
-       SVr3 (1987) added mvscanw, and mvwscanw, stating
+              [t]hese  routines correspond to scanf(3S), as do their arguments
+              and return values.  wgetstr() is called on the window,  and  the
+              resulting line is used as input for the scan.
 
-              "[t]hese routines correspond to scanf(3S), as do their arguments
-              and return values.  wgetstr() is called on the window,  and  the
-              resulting line is used as input for the scan."
-
-       SVr3  also  implemented  vwscanw,  describing  its third parameter as a
-       va_list, defined in varargs.h, and referred the reader  to  the  manual
-       pages  for varargs and vprintf for detailed descriptions.  (Because the
-       SVr3 documentation does not mention vscanf, the  reference  to  vprintf
-       might not be an error).
+       SVr3  added  vwscanw,  describing  its  third  parameter  as a va_list,
+       defined in varargs.h, and referred the reader to the manual  pages  for
+       varargs   and   vprintf   for  detailed  descriptions.   (Because  SVr3
+       documentation does not mention vscanf, the reference to  vprintf  might
+       not be an error).
 
        SVr4  (1989)  introduced  no  new variations of scanw, but provided for
        using either varargs.h or stdarg.h to define the va_list type.
 
-       X/Open Curses, Issue 4 (1995), defined  vw_scanw  to  replace  vwscanw,
+       X/Open Curses Issue 4  (1995)  defined  vw_scanw  to  replace  vwscanw,
        stating that its va_list type is defined in stdarg.h.

                          SEE ALSO

                                  curses(3x), curs_getstr(3x), curs_printw(3x), scanf(3), vscanf(3)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_scanw(3x)
+ncurses 6.6                       2025-07-05                    curs_scanw(3x)
                            diff --git a/doc/html/man/curs_scr_dump.3x.html b/doc/html/man/curs_scr_dump.3x.html index f1759cb..ec58e75 100644 --- a/doc/html/man/curs_scr_dump.3x.html +++ b/doc/html/man/curs_scr_dump.3x.html @@ -1,6 +1,6 @@ -curs_scr_dump 3x 2024-04-20 ncurses 6.5 Library calls +curs_scr_dump 3x 2025-01-18 ncurses 6.6 Library calls -

                            curs_scr_dump 3x 2024-04-20 ncurses 6.5 Library calls

                            +

                            curs_scr_dump 3x 2025-01-18 ncurses 6.6 Library calls

                             curs_scr_dump(3x)                Library calls               curs_scr_dump(3x)
 
 
-
-

                            NAME

                                    scr_dump,  scr_restore,  scr_init, scr_set - read/write a curses screen
        from/to a file
@@ -54,10 +52,10 @@

                            SYNOPSIS

                                    #include <curses.h>
 
-       int scr_dump(const char *filename);
-       int scr_restore(const char *filename);
-       int scr_init(const char *filename);
-       int scr_set(const char *filename);
+       int scr_dump(const char * filename);
+       int scr_restore(const char * filename);
+       int scr_init(const char * filename);
+       int scr_set(const char * filename);

                            DESCRIPTION

                            @@ -73,65 +71,93 @@

                            scr_restore

                            -       scr_restore updates the virtual  screen  to  contain  the  contents  of
-       filename  (if  it  was  validly  written with scr_dump).  No refresh is
-       performed;  after  performing  any  further   desired   updates,   call
-       doupdate(3x) or similar.
+       scr_restore updates  the  virtual  screen  to  match  the  contents  of
+       filename (if validly written with scr_dump).  curses does not perform a
+       refresh;  after  making  any  desired  changes,  call  doupdate(3x)  or
+       similar.

                            scr_init

                            -       scr_init  reads filename, using it to initialize curses data structures
-       describing the state of the terminal screen.  If these data are  valid,
-       curses  bases  its next update of the screen on this information rather
-       than clearing it and starting from scratch.
+       scr_init reads filename, using it to initialize curses data  structures
+       describing  the  state  of  the  terminal  screen.   curses then, if it
+       decides the terminal state is valid,  bases  its  next  update  of  the
+       screen  on  this  information rather than clearing it and starting from
+       scratch.
 
-       The data fail the validity check
+       curses regards the terminal as in an invalid state for  computation  of
+       updates based on the contents of filename if
 
-       o   if the terminal employs terminfo capabilities exit_ca_mode  (rmcup)
-           or non_rev_rmcup (nrrmc) are defined, or
+       o   curses  knows  that  the  terminal  has  been  written to since the
+           preceding scr_dump call, or
 
-       o   if  curses  knows  that  the terminal has been written to since the
-           preceding scr_dump call.
+       o   the terminal type supports the terminfo  capabilities  exit_ca_mode
+           (rmcup) or non_rev_rmcup (nrrmc).
 
-       scr_init could be used after initscr(3x)  or  system(3)  to  share  the
-       screen with another process that has done a scr_dump after endwin(3x).
+       Either of the foregoing conditions means that curses cannot assume that
+       the  terminal's  contents  match their representation in filename.  The
+       former is due to  terminal  features  (such  as  xterm(1)'s  "alternate
+       screen")  that  couple  cursor-positioning  mode  with a local cache of
+       screen contents.  curses cannot know whether the terminal is displaying
+       from that local cache at the time the application calls scr_init, so it
+       makes a pessimistic assumption that a  full  redraw  is  required;  see
+       subsection "Cursor Motions" of terminfo(5).
+
+       scr_init  could  be  used  after  initscr(3x) or system(3) to share the
+       screen with another process that has done a scr_dump after  endwin(3x).
+       An   application  that  supports  suspending  its  state  on  exit  and
+       subsequent resumption upon  later  execution  might  use  scr_dump  and
+       scr_init thus.

                            scr_set

                            -       The  scr_set  routine is a combination of scr_restore and scr_init.  It
-       tells the program that the information in filename is what is currently
-       on the screen, and also what the program wants on the screen.  This can
-       be thought of as a screen inheritance function.
+       scr_set  combines  scr_restore and scr_init, synchronizing the contents
+       of filename with the virtual screen.  It can be regarded  as  a  screen
+       inheritance function; consider a real-time screen-sharing application.

                            RETURN VALUE

                                    These functions return OK on success and ERR on failure.
 
-       X/Open defines no failure conditions.   In  this  implementation,  each
-       function fails if it cannot open filename.
+       In  ncurses,  each  function  returns  ERR  if it cannot open filename.
+       scr_init, scr_restore, and  scr_set  return  ERR  if  the  contents  of
+       filename are invalid.

                            NOTES

                            -       scr_init, scr_set, and scr_restore may be macros.
+       scr_init, scr_restore, and scr_set may be implemented as macros.

                            PORTABILITY

                            -       X/Open Curses, Issue 4 describes these functions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
        SVr4 omitted the const qualifiers.
 
-       SVr4  documentation  describes scr_init such that the dump data is also
+       SVr4  documentation  describes scr_init such that the dump data is also
        considered invalid "if the time-stamp of the tty is old" but  does  not
        define "old".
 
+       As of 2024, PDCurses provides these functions.  NetBSD curses does not.
+
+       Other  implementations of curses store the window in binary form, which
+       makes the dump  dependent  upon  the  curses  library's  internal  data
+       structures.   ncurses  avoids  this  drawback  by  storing  the dump in
+       textual form, allowing more flexible use of the  data.   For  instance,
+       the scr_restore of SVr4 curses requires that the dumped window have the
+       same  dimensions  as the restored window.  ncurses uses its wresize(3x)
+       extension to adjust the restored window size.
+
+
+

                            HISTORY

                            +       SVr3 (1987) introduced scr_dump,  scr_init,  and  scr_restore.   SVr3.1
+       added scr_set.
+

                            SEE ALSO

                            -       curses(3x),    curs_initscr(3x),    curs_refresh(3x),    curs_util(3x),
-       system(3), scr_dump(5)
+       curses(3x), curs_initscr(3x), curs_refresh(3x), curs_util(3x),
+       system(3), scr_dump(5), terminfo(5), wresize(3x)
 
-
-
-ncurses 6.5                       2024-04-20                 curs_scr_dump(3x)
+ncurses 6.6                       2025-01-18                 curs_scr_dump(3x)
                            diff --git a/doc/html/man/curs_scroll.3x.html b/doc/html/man/curs_scroll.3x.html index 5b827fe..3e0e44a 100644 --- a/doc/html/man/curs_scroll.3x.html +++ b/doc/html/man/curs_scroll.3x.html @@ -1,6 +1,6 @@ -curs_scroll 3x 2024-04-20 ncurses 6.5 Library calls +curs_scroll 3x 2025-04-05 ncurses 6.6 Library calls -

                            curs_scroll 3x 2024-04-20 ncurses 6.5 Library calls

                            +

                            curs_scroll 3x 2025-04-05 ncurses 6.6 Library calls

                             curs_scroll(3x)                  Library calls                 curs_scroll(3x)
 
 
-
-

                            NAME

                                    scroll, scrl, wscrl - scroll a curses window
 
@@ -53,27 +51,28 @@

                            SYNOPSIS

                                    #include <curses.h>
 
-       int scroll(WINDOW *win);
+       int scroll(WINDOW * win);
 
        int scrl(int n);
-       int wscrl(WINDOW *win, int n);
+       int wscrl(WINDOW * win, int n);

                            DESCRIPTION

                                    scroll  scrolls  the  given window up one line.  That is, every visible
-       line we might number i becomes line i-1.  The text of the top  line  in
-       the  window  disappears  and  the  bottom  line is populated with blank
-       characters; see bkgd(3x) or bkgrnd(3x).  As  an  optimization,  if  the
-       scrolling  region  of  the  window  is  the entire screen, the physical
-       screen may be scrolled at the same time; see curscr(3x).
-
-       scrl and wscrl scroll  stdscr  or  the  specified  window  up  or  down
-       depending on the sign of n.
+       line we might number i becomes line i-1.  wscrl  and  scrl  scroll  the
+       specified window or stdscr, respectively, up or down per the sign of n.
 
        o   For positive n, line i+n becomes i (scrolling up);
 
        o   for negative n, line i-n becomes i (scrolling down).
 
+       A  line  that  scrolls  beyond the window boundaries disappears; curses
+       populates a  new  one  emerging  at  the  opposite  boundary  with  the
+       background   character;   see   bkgd(3x)   (wide-character  API  users:
+       bkgrnd(3x)).  As an optimization, if the scrolling region of the window
+       is the entire screen, the physical screen may be scrolled at  the  same
+       time; see curscr(3x).
+
        The  cursor does not move.  These functions perform no operation unless
        scrolling is enabled for the window via scrollok(3x).
 
@@ -81,41 +80,52 @@

                            RETURN VALUE

                                    These functions return ERR upon failure and OK upon success.
 
-       ncurses returns ERR if scrolling is not  enabled  in  the  window,  for
-       example with scrollok(3x), or if the WINDOW pointer is null.
+       In ncurses, they return ERR if
+
+       o   the curses screen has not been initialized,
+
+       o   (for functions taking a WINDOW pointer  argument)  win  is  a  null
+           pointer, or
+
+       o   scrolling is not enabled in the window (as by scrollok(3x)).

                            NOTES

                            +       scroll and scrl may be implemented as macros.
+
        Unusually,  there  is  no wscroll function; scroll behaves as one would
        expect wscroll to, accepting a WINDOW pointer argument.
 
-       scrl and scroll may be implemented as macros.
-

                            PORTABILITY

                            -       X/Open Curses, Issue 4 describes these functions.  It defines no  error
-       conditions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       SVr4  specifies  only "an integer value other than ERR" as a successful
-       return value.
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
 
-       SVr4  indicates  that  the   optimization   of   physically   scrolling
-       immediately  if  the scroll region is the entire screen "is" performed,
-       not "may be" performed.  ncurses deliberately does not  guarantee  that
-       this  will occur, to leave open the possibility of smarter optimization
-       of multiple scroll actions on the next update.
+       SVr4   indicates   that   the   optimization  of  physically  scrolling
+       immediately if the scroll region is the entire screen  "is"  performed,
+       not  "may  be" performed.  ncurses deliberately does not guarantee that
+       this occurs, to leave open the possibility of  better  optimization  of
+       multiple scroll actions on the next update.
 
-       Neither SVr4 curses nor  X/Open  Curses  specify  whether  the  current
-       attribute  or  current  color  pair  of  blanks generated by the scroll
-       function are zeroed.  ncurses does so.
+       Neither  SVr4  curses nor X/Open Curses specify whether these functions
+       zero  the  attributes  or  color  pair  identifier  of  the  background
+       character.  In ncurses, they do not.
+
+
+

                            HISTORY

                            +       4BSD (1980) introduced scroll, defining it as a function.
+
+       SVr3.1  (1987)  added  scrl  and  wscrl,  redefining  scroll as a macro
+       wrapping the latter.

                            SEE ALSO

                                    curses(3x), curs_outopts(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_scroll(3x)
+ncurses 6.6                       2025-04-05                   curs_scroll(3x)
                            diff --git a/doc/html/man/curs_slk.3x.html b/doc/html/man/curs_slk.3x.html index 52f8c29..2e050b9 100644 --- a/doc/html/man/curs_slk.3x.html +++ b/doc/html/man/curs_slk.3x.html @@ -1,6 +1,6 @@ -curs_slk 3x 2024-04-20 ncurses 6.5 Library calls +curs_slk 3x 2025-01-18 ncurses 6.6 Library calls -

                            curs_slk 3x 2024-04-20 ncurses 6.5 Library calls

                            +

                            curs_slk 3x 2025-01-18 ncurses 6.6 Library calls

                             curs_slk(3x)                     Library calls                    curs_slk(3x)
 
 
-
-

                            NAME

                                    slk_init,  slk_set,  slk_wset, slk_refresh, slk_noutrefresh, slk_label,
        slk_clear,    slk_restore,    slk_touch,    slk_attron,    slk_attrset,
@@ -108,14 +106,14 @@
 
        2  indicates the PC-like 4-4-4 mode.
 
-       3  is again the PC-like 4-4-4 mode, but in addition an  index  line  is
-          generated,  helping  the  user  to  associate  each  label  with its
-          numbered function key.  LINES and the vertical size  of  stdscr  are
+       3  is  again  the  PC-like 4-4-4 mode, but in addition an index line is
+          generated, helping  the  user  to  associate  each  label  with  its
+          numbered  function  key.   LINES and the vertical size of stdscr are
           further reduced.

                            Labels

                            -       Populate  the  labels  with  normal strings (slk_set) or wide-character
+       Populate the labels with normal  strings  (slk_set)  or  wide-character
        strings (slk_wset).  Each function takes three parameters.
 
        labnum  is the label number, from 1 to 8 (12 if fmt in slk_init is 2 or
@@ -125,83 +123,79 @@
                in slk_init is 2 or 3) characters in length.  A empty string or
                a null pointer sets up a blank label.
 
-       align   is  0,  1,  or 2, aligning label to the left, center, or right,
+       align   is 0, 1, or 2, aligning label to the left,  center,  or  right,
                respectively, within the 8 (5) character cells housing it.
 
-       slk_label obtains the string assigned to label number labnum, with  any
+       slk_label  obtains the string assigned to label number labnum, with any
        leading and trailing blanks stripped.

                            Screen Updates

                            -       slk_refresh  and  slk_noutrefresh  affect  the  soft key label lines as
+       slk_refresh and slk_noutrefresh affect the  soft  key  label  lines  as
        wrefresh and wnoutrefresh do the curses window.
 
        The slk_clear routine clears the soft labels from the screen.
 
-       The slk_restore routine restores the soft labels to the screen after  a
+       The  slk_restore routine restores the soft labels to the screen after a
        slk_clear has been performed.
 
-       The  slk_touch routine forces all the soft labels to be output the next
+       The slk_touch routine forces all the soft labels to be output the  next
        time a slk_noutrefresh is performed.

                            Video Attributes

                            -       The  slk_attron,  slk_attrset,  slk_attroff,  and   slk_attr   routines
-       correspond  to  attron,  attrset,  attroff, and attr_get, respectively.
-       They have an effect only if soft labels are  simulated  on  the  bottom
-       line  of  the  screen.   The  default  highlight for soft key labels is
+       The   slk_attron,   slk_attrset,  slk_attroff,  and  slk_attr  routines
+       correspond to attron, attrset,  attroff,  and  attr_get,  respectively.
+       They  have  an  effect  only if soft labels are simulated on the bottom
+       line of the screen.  The default  highlight  for  soft  key  labels  is
        A_STANDOUT (as in System V curses, which does not document this fact).

                            Colors

                            -       The slk_color routine corresponds to color_set.  It has an effect  only
+       The  slk_color routine corresponds to color_set.  It has an effect only
        if soft labels are simulated on the bottom line of the screen.
 
-       Because  slk_color  accepts  only short (signed 16-bit integer) values,
-       this implementation provides extended_slk_color, which accepts  an  int
+       Because slk_color accepts only short (signed  16-bit  integer)  values,
+       this  implementation  provides extended_slk_color, which accepts an int
        value of at least 32 bits.

                            RETURN VALUE

                            -       Routines  that  return  an integer return ERR upon failure and OK (SVr4
-       specifies only "an integer  value  other  than  ERR")  upon  successful
-       completion.
+       Functions that return integers return ERR  upon  failure  and  OK  upon
+       success.
 
-       X/Open Curses defines no error conditions.
-
-       In this implementation
+       In ncurses,
 
           slk_attr
                returns the attribute used for the soft keys.
 
-          slk_attroff,  slk_attron,  slk_clear,  slk_noutrefresh, slk_refresh,
+          slk_attroff, slk_attron, slk_clear, slk_noutrefresh, slk_refresh,
           slk_touch
-               return an error if  the  terminal  or  the  softkeys  were  not
+               return   ERR   if   the  terminal  or  the  softkeys  were  not
                initialized.
 
           slk_attrset
-               returns  an  error  if  the  terminal  or the softkeys were not
+               returns  ERR  if  the  terminal  or  the  softkeys   were   not
                initialized.
 
           slk_attr_set
-               returns an error if the  terminal  or  the  softkeys  were  not
-               initialized,   or   the   color   pair  is  outside  the  range
+               returns   ERR   if  the  terminal  or  the  softkeys  were  not
+               initialized,  or  the  color  pair   is   outside   the   range
                0..COLOR_PAIRS-1.
 
           slk_color
-               returns an error if the  terminal  or  the  softkeys  were  not
-               initialized,   or   the   color   pair  is  outside  the  range
+               returns   ERR   if  the  terminal  or  the  softkeys  were  not
+               initialized,  or  the  color  pair   is   outside   the   range
                0..COLOR_PAIRS-1.
 
           slk_init
-               returns an error if the format parameter is outside  the  range
-               0..3.
+               returns ERR if the format parameter is outside the range 0..3.
 
           slk_label
-               returns NULL on error.
+               returns NULL on error.
 
           slk_set
-               returns  an  error  if  the  terminal  or the softkeys were not
+               returns   ERR   if  the  terminal  or  the  softkeys  were  not
                initialized, or the labnum parameter is outside  the  range  of
                label  counts,  or if the format parameter is outside the range
                0..2, or if memory for the labels cannot be allocated.
@@ -214,9 +208,9 @@

                            EXTENSIONS

                                    X/Open  Curses  documents the opts argument as reserved for future use,
-       saying that it must be null.  This implementation uses  that  parameter
-       in ABI 6 for the functions which have a color pair parameter to support
-       extended color pairs.
+       saying that it must be a null pointer.  The ncurses 6 ABI uses  it  for
+       the  functions  that  accept a color pair parameter to support extended
+       color pairs.
 
        For functions which modify the color, e.g., slk_attr_set,  if  opts  is
        set  it  is treated as a pointer to int, and used to set the color pair
@@ -224,8 +218,11 @@

                            PORTABILITY

                            -       X/Open Curses, Issue 4 describes these functions, with some differences
-       from SVr4 curses:
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
 
        o   X/Open   added   functions  like  the  SVr4  attribute-manipulation
            functions slk_attron, slk_attroff, and slk_attrset, but  which  use
@@ -253,32 +250,32 @@
 
        o   Soft-key groups are an array of ng integers.
 
-       o   In  SVr4, slk_init calls slk_start passing a null for gp.  For this
-           case, slk_start uses the number of  groups  ng  (3  for  the  3-2-3
+       o   In SVr4, slk_init calls slk_start passing a null for gp.  For  this
+           case,  slk_start  uses  the  number  of  groups ng (3 for the 3-2-3
            layout, 2 for the 4-4 layout) which slk_init provided.
 
-           If  ng  is  neither  2  or  3,  slk_start  checks  the terminfo fln
-           (label_format) capability, interpreting that as  a  comma-separated
+           If ng is  neither  2  or  3,  slk_start  checks  the  terminfo  fln
+           (label_format)  capability,  interpreting that as a comma-separated
            list of numbers, e.g., "3,2,3" for the 3-2-3 layout.
 
            Finally, if there is no fln capability, slk_start returns ERR.
 
-       o   If  slk_start  is given a non-null gp, it copies the ng elements of
+       o   If slk_start is given a non-null gp, it copies the ng  elements  of
            the group of soft-keys, up to 16.
 
-           If there are more than 16 elements, slk_start returns an error.
+           If there are more than 16 elements, slk_start returns ERR.
 
-       o   The format codes 2 and 3 for slk_init  were  added  by  ncurses  in
-           1996.  PDCurses 2.4 added this feature in 2001.
+       o   The  format  codes  2  and  3 for slk_init were added by ncurses in
+           1996.  PDCurses 2.4 added this feature in 2001.
 
        The function slk_attr was added by ncurses in 1996.
 
-       X/Open  Curses  does  not  specify a limit for the number of colors and
+       X/Open Curses does not specify a limit for the  number  of  colors  and
        color pairs which a terminal can support.  However, in its use of short
        for  the  parameters,  it carries over SVr4's implementation detail for
        the compiled terminfo database, which uses signed 16-bit numbers.  This
-       implementation  provides extended versions of those functions which use
-       int parameters, allowing applications to use larger  color-  and  pair-
+       implementation provides extended versions of those functions which  use
+       int  parameters,  allowing  applications to use larger color- and pair-
        numbers.
 
 
@@ -311,9 +308,7 @@
        curses(3x),    curs_attr(3x),    curs_initscr(3x),    curs_refresh(3x),
        curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                      curs_slk(3x)
+ncurses 6.6                       2025-01-18                      curs_slk(3x)
                              diff --git a/doc/html/man/curs_sp_funcs.3x.html b/doc/html/man/curs_sp_funcs.3x.html index 7695f68..4f361e3 100644 --- a/doc/html/man/curs_sp_funcs.3x.html +++ b/doc/html/man/curs_sp_funcs.3x.html @@ -1,6 +1,6 @@ -curs_sp_funcs 3x 2024-04-20 ncurses 6.5 Library calls +curs_sp_funcs 3x 2025-02-01 ncurses 6.6 Library calls -

                              curs_sp_funcs 3x 2024-04-20 ncurses 6.5 Library calls

                              +

                              curs_sp_funcs 3x 2025-02-01 ncurses 6.6 Library calls

                               curs_sp_funcs(3x)                Library calls               curs_sp_funcs(3x)
 
 
-
-

                              NAME

                                      curs_sp_funcs - curses screen-pointer extension
 
@@ -53,169 +51,169 @@

                              SYNOPSIS

                                      #include <curses.h>
 
-       int alloc_pair_sp(SCREEN* sp, int fg, int bg);
-       int assume_default_colors_sp(SCREEN* sp, int fg, int bg);
-       int baudrate_sp(SCREEN* sp);
-       int beep_sp(SCREEN* sp);
-       bool can_change_color_sp(SCREEN* sp);
-       int cbreak_sp(SCREEN* sp);
-       int color_content_sp(SCREEN* sp, short color, short* r, short* g, short* b);
-       int curs_set_sp(SCREEN* sp, int visibility);
-       int def_prog_mode_sp(SCREEN* sp);
-       int def_shell_mode_sp(SCREEN* sp);
+       int alloc_pair_sp(SCREEN * sp, int fg, int bg);
+       int assume_default_colors_sp(SCREEN * sp, int fg, int bg);
+       int baudrate_sp(SCREEN * sp);
+       int beep_sp(SCREEN * sp);
+       bool can_change_color_sp(SCREEN * sp);
+       int cbreak_sp(SCREEN * sp);
+       int color_content_sp(SCREEN * sp, short color, short * r, short * g, short * b);
+       int curs_set_sp(SCREEN * sp, int visibility);
+       int def_prog_mode_sp(SCREEN * sp);
+       int def_shell_mode_sp(SCREEN * sp);
 
-       int define_key_sp(SCREEN* sp, const char * definition, int keycode);
-       int delay_output_sp(SCREEN* sp, int ms);
-       int doupdate_sp(SCREEN* sp);
-       int echo_sp(SCREEN* sp);
-       int endwin_sp(SCREEN* sp);
-       char erasechar_sp(SCREEN* sp);
-       int erasewchar_sp(SCREEN* sp, wchar_t *wc);
+       int define_key_sp(SCREEN * sp, const char * definition, int keycode);
+       int delay_output_sp(SCREEN * sp, int ms);
+       int doupdate_sp(SCREEN * sp);
+       int echo_sp(SCREEN * sp);
+       int endwin_sp(SCREEN * sp);
+       char erasechar_sp(SCREEN * sp);
+       int erasewchar_sp(SCREEN * sp, wchar_t *wc);
        int extended_color_content_sp(SCREEN * sp, int color, int * r, int * g, int * b);
-       int extended_pair_content_sp(SCREEN* sp, int pair, int * fg, int * bg);
-       int extended_slk_color_sp(SCREEN* sp, int pair);
+       int extended_pair_content_sp(SCREEN * sp, int pair, int * fg, int * bg);
+       int extended_slk_color_sp(SCREEN * sp, int pair);
 
-       void filter_sp(SCREEN* sp);
-       int find_pair_sp(SCREEN* sp, int fg, int bg);
-       int flash_sp(SCREEN* sp);
-       int flushinp_sp(SCREEN* sp);
-       int free_pair_sp(SCREEN* sp, int pair);
-       int get_escdelay_sp(SCREEN* sp);
-       int getmouse_sp(SCREEN* sp, MEVENT* event);
-       WINDOW* getwin_sp(SCREEN* sp, FILE* filep);
-       int halfdelay_sp(SCREEN* sp, int tenths);
-       bool has_colors_sp(SCREEN* sp);
+       void filter_sp(SCREEN * sp);
+       int find_pair_sp(SCREEN * sp, int fg, int bg);
+       int flash_sp(SCREEN * sp);
+       int flushinp_sp(SCREEN * sp);
+       int free_pair_sp(SCREEN * sp, int pair);
+       int get_escdelay_sp(SCREEN * sp);
+       int getmouse_sp(SCREEN * sp, MEVENT * event);
+       WINDOW * getwin_sp(SCREEN * sp, FILE * filep);
+       int halfdelay_sp(SCREEN * sp, int tenths);
+       bool has_colors_sp(SCREEN * sp);
 
-       bool has_ic_sp(SCREEN* sp);
-       bool has_il_sp(SCREEN* sp);
-       int has_key_sp(SCREEN* sp, int c);
-       bool has_mouse_sp(SCREEN* sp);
-       int init_color_sp(SCREEN* sp, short color, short r, short g, short b);
-       int init_extended_color_sp(SCREEN* sp, int color, int r, int g, int b);
-       int init_extended_pair_sp(SCREEN* sp, int pair, int fg, int bg);
-       int init_pair_sp(SCREEN* sp, short pair, short fg, short bg);
-       int intrflush_sp(SCREEN* sp, WINDOW* win, bool bf);
-       int is_cbreak_sp(SCREEN* sp);
+       bool has_ic_sp(SCREEN * sp);
+       bool has_il_sp(SCREEN * sp);
+       int has_key_sp(SCREEN * sp, int c);
+       bool has_mouse_sp(SCREEN * sp);
+       int init_color_sp(SCREEN * sp, short color, short r, short g, short b);
+       int init_extended_color_sp(SCREEN * sp, int color, int r, int g, int b);
+       int init_extended_pair_sp(SCREEN * sp, int pair, int fg, int bg);
+       int init_pair_sp(SCREEN * sp, short pair, short fg, short bg);
+       int intrflush_sp(SCREEN * sp, WINDOW * win, bool bf);
+       int is_cbreak_sp(SCREEN * sp);
 
-       int is_echo_sp(SCREEN* sp);
-       int is_nl_sp(SCREEN* sp);
-       int is_raw_sp(SCREEN* sp);
-       bool is_term_resized_sp(SCREEN* sp, int lines, int columns);
-       bool isendwin_sp(SCREEN* sp);
-       int key_defined_sp(SCREEN* sp, const char *definition);
-       char* keybound_sp(SCREEN* sp, int keycode, int count);
-       NCURSES_CONST char* keyname_sp(SCREEN* sp, int c);
-       int keyok_sp(SCREEN* sp, int keycode, bool enable);
-       char killchar_sp(SCREEN* sp);
+       int is_echo_sp(SCREEN * sp);
+       int is_nl_sp(SCREEN * sp);
+       int is_raw_sp(SCREEN * sp);
+       bool is_term_resized_sp(SCREEN * sp, int lines, int columns);
+       bool isendwin_sp(SCREEN * sp);
+       int key_defined_sp(SCREEN * sp, const char *definition);
+       char * keybound_sp(SCREEN * sp, int keycode, int count);
+       NCURSES_CONST char * keyname_sp(SCREEN * sp, int c);
+       int keyok_sp(SCREEN * sp, int keycode, bool enable);
+       char killchar_sp(SCREEN * sp);
 
-       int killwchar_sp(SCREEN* sp, wchar_t *wc);
-       char* longname_sp(SCREEN* sp);
-       int mcprint_sp(SCREEN* sp, char *data, int len);
-       int mouseinterval_sp(SCREEN* sp, int erval);
-       mmask_t mousemask_sp(SCREEN* sp, mmask_t newmask, mmask_t *oldmask);
-       int mvcur_sp(SCREEN* sp, int oldrow, int oldcol, int newrow, int newcol);
-       int napms_sp(SCREEN* sp, int ms);
-       WINDOW* newpad_sp(SCREEN* sp, int nrows, int ncols);
-       SCREEN* new_prescr(void);
-       SCREEN* newterm_sp(SCREEN* sp, const char *type, FILE *outfd, FILE *infd);
+       int killwchar_sp(SCREEN * sp, wchar_t *wc);
+       char * longname_sp(SCREEN * sp);
+       int mcprint_sp(SCREEN * sp, char *data, int len);
+       int mouseinterval_sp(SCREEN * sp, int erval);
+       mmask_t mousemask_sp(SCREEN * sp, mmask_t newmask, mmask_t *oldmask);
+       int mvcur_sp(SCREEN * sp, int oldrow, int oldcol, int newrow, int newcol);
+       int napms_sp(SCREEN * sp, int ms);
+       WINDOW * newpad_sp(SCREEN * sp, int nrows, int ncols);
+       SCREEN * new_prescr(void);
+       SCREEN * newterm_sp(SCREEN * sp, const char *type, FILE *outf, FILE *inf);
 
-       WINDOW* newwin_sp(SCREEN* sp, int nlines, int ncols, int begin_y, int begin_x);
-       int nl_sp(SCREEN* sp);
-       int nocbreak_sp(SCREEN* sp);
-       int noecho_sp(SCREEN* sp);
-       void nofilter_sp(SCREEN* sp);
-       int nonl_sp(SCREEN* sp);
-       void noqiflush_sp(SCREEN* sp);
-       int noraw_sp(SCREEN* sp);
-       int pair_content_sp(SCREEN* sp, short pair, short* fg, short* bg);
-       void qiflush_sp(SCREEN* sp);
+       WINDOW * newwin_sp(SCREEN * sp, int nlines, int ncols, int begin_y, int begin_x);
+       int nl_sp(SCREEN * sp);
+       int nocbreak_sp(SCREEN * sp);
+       int noecho_sp(SCREEN * sp);
+       void nofilter_sp(SCREEN * sp);
+       int nonl_sp(SCREEN * sp);
+       void noqiflush_sp(SCREEN * sp);
+       int noraw_sp(SCREEN * sp);
+       int pair_content_sp(SCREEN * sp, short pair, short * fg, short * bg);
+       void qiflush_sp(SCREEN * sp);
 
-       int raw_sp(SCREEN* sp);
-       void reset_color_pairs_sp(SCREEN* sp);
-       int reset_prog_mode_sp(SCREEN* sp);
-       int reset_shell_mode_sp(SCREEN* sp);
-       int resetty_sp(SCREEN* sp);
-       int resize_term_sp(SCREEN* sp, int lines, int columns);
-       int resizeterm_sp(SCREEN* sp, int lines, int columns);
-       int ripoffline_sp(SCREEN* sp, int line, int (*init)(WINDOW* win, int fmt));
-       int savetty_sp(SCREEN* sp);
-       int scr_init_sp(SCREEN* sp, const char *filename);
+       int raw_sp(SCREEN * sp);
+       void reset_color_pairs_sp(SCREEN * sp);
+       int reset_prog_mode_sp(SCREEN * sp);
+       int reset_shell_mode_sp(SCREEN * sp);
+       int resetty_sp(SCREEN * sp);
+       int resize_term_sp(SCREEN * sp, int lines, int columns);
+       int resizeterm_sp(SCREEN * sp, int lines, int columns);
+       int ripoffline_sp(SCREEN * sp, int line, int (*init)(WINDOW * win, int fmt));
+       int savetty_sp(SCREEN * sp);
+       int scr_init_sp(SCREEN * sp, const char *filename);
 
-       int scr_restore_sp(SCREEN* sp, const char *filename);
-       int scr_set_sp(SCREEN* sp, const char *filename);
-       int set_escdelay_sp(SCREEN* sp, int ms);
-       int set_tabsize_sp(SCREEN* sp, int cols);
-       int slk_attrset_sp(SCREEN* sp, const chtype a);
-       int slk_attr_set_sp(SCREEN* sp, const attr_t attrs, short pair, void*opts);
-       int slk_attroff_sp(SCREEN* sp, const chtype a);
-       int slk_attron_sp(SCREEN* sp, const chtype a);
-       attr_t slk_attr_sp(SCREEN* sp);
-       int slk_clear_sp(SCREEN* sp);
+       int scr_restore_sp(SCREEN * sp, const char *filename);
+       int scr_set_sp(SCREEN * sp, const char *filename);
+       int set_escdelay_sp(SCREEN * sp, int ms);
+       int set_tabsize_sp(SCREEN * sp, int cols);
+       int slk_attrset_sp(SCREEN * sp, const chtype a);
+       int slk_attr_set_sp(SCREEN * sp, const attr_t attrs, short pair, void *opts);
+       int slk_attroff_sp(SCREEN * sp, const chtype a);
+       int slk_attron_sp(SCREEN * sp, const chtype a);
+       attr_t slk_attr_sp(SCREEN * sp);
+       int slk_clear_sp(SCREEN * sp);
 
-       int slk_color_sp(SCREEN* sp, short pair);
-       int slk_init_sp(SCREEN* sp, int fmt);
-       char* slk_label_sp(SCREEN* sp, int labnum);
-       int slk_noutrefresh_sp(SCREEN* sp);
-       int slk_refresh_sp(SCREEN* sp);
-       int slk_restore_sp(SCREEN* sp);
-       int slk_set_sp(SCREEN* sp, int labnum, const char * label, int fmt);
-       int slk_touch_sp(SCREEN* sp);
-       int start_color_sp(SCREEN* sp);
-       attr_t term_attrs_sp(SCREEN* sp);
+       int slk_color_sp(SCREEN * sp, short pair);
+       int slk_init_sp(SCREEN * sp, int fmt);
+       char * slk_label_sp(SCREEN * sp, int labnum);
+       int slk_noutrefresh_sp(SCREEN * sp);
+       int slk_refresh_sp(SCREEN * sp);
+       int slk_restore_sp(SCREEN * sp);
+       int slk_set_sp(SCREEN * sp, int labnum, const char * label, int fmt);
+       int slk_touch_sp(SCREEN * sp);
+       int start_color_sp(SCREEN * sp);
+       attr_t term_attrs_sp(SCREEN * sp);
 
-       chtype termattrs_sp(SCREEN* sp);
-       char* termname_sp(SCREEN* sp);
-       int typeahead_sp(SCREEN* sp, int fd);
-       int unget_wch_sp(SCREEN* sp, const wchar_t wc);
-       int ungetch_sp(SCREEN* sp, int c);
-       int ungetmouse_sp(SCREEN* sp, MEVENT* event);
-       int use_default_colors_sp(SCREEN* sp);
-       void use_env_sp(SCREEN* sp, bool bf);
-       int use_legacy_coding_sp(SCREEN* sp, int level);
+       chtype termattrs_sp(SCREEN * sp);
+       char * termname_sp(SCREEN * sp);
+       int typeahead_sp(SCREEN * sp, int fd);
+       int unget_wch_sp(SCREEN * sp, const wchar_t wc);
+       int ungetch_sp(SCREEN * sp, int c);
+       int ungetmouse_sp(SCREEN * sp, MEVENT * event);
+       int use_default_colors_sp(SCREEN * sp);
+       void use_env_sp(SCREEN * sp, bool bf);
+       int use_legacy_coding_sp(SCREEN * sp, int level);
        void use_tioctl_sp(SCREEN *sp, bool bf);
 
-       int vid_attr_sp(SCREEN* sp, attr_t attrs, short pair, void * opts);
-       int vid_puts_sp(SCREEN* sp, attr_t attrs, short pair, void * opts, NCURSES_SP_OUTC putc);
-       int vidattr_sp(SCREEN* sp, chtype attrs);
-       int vidputs_sp(SCREEN* sp, chtype attrs, NCURSES_SP_OUTC putc);
-       wchar_t* wunctrl_sp(SCREEN* sp, cchar_t *wch);
+       int vid_attr_sp(SCREEN * sp, attr_t attrs, short pair, void * opts);
+       int vid_puts_sp(SCREEN * sp, attr_t attrs, short pair, void * opts, NCURSES_SP_OUTC putc);
+       int vidattr_sp(SCREEN * sp, chtype attrs);
+       int vidputs_sp(SCREEN * sp, chtype attrs, NCURSES_SP_OUTC putc);
+       wchar_t * wunctrl_sp(SCREEN * sp, cchar_t *wch);
 
        #include <form.h>
 
-       FORM* new_form_sp(SCREEN* sp, FIELD **fields);
+       FORM * new_form_sp(SCREEN * sp, FIELD **fields);
 
        #include <menu.h>
 
-       MENU* new_menu_sp(SCREEN* sp, ITEM **items);
+       MENU * new_menu_sp(SCREEN * sp, ITEM **items);
 
        #include <panel.h>
 
-       PANEL* ceiling_panel(SCREEN* sp);
-       PANEL* ground_panel(SCREEN* sp);
-       void update_panels_sp(SCREEN* sp);
+       PANEL * ceiling_panel(SCREEN * sp);
+       PANEL * ground_panel(SCREEN * sp);
+       void update_panels_sp(SCREEN * sp);
 
        #include <term.h>
 
-       int del_curterm_sp(SCREEN* sp, TERMINAL *oterm);
-       int putp_sp(SCREEN* sp, const char *str);
-       int restartterm_sp(SCREEN* sp, NCURSES_CONST char*term, int filedes, int *errret);
-       TERMINAL* set_curterm_sp(SCREEN* sp, TERMINAL*nterm);
-       int tgetent_sp(SCREEN* sp, char *bp, const char *name);
-       int tgetflag_sp(SCREEN* sp, const char *capname);
-       int tgetnum_sp(SCREEN* sp, const char *capname);
-       char* tgetstr_sp(SCREEN* sp, const char *capname, char **area);
-       char* tgoto_sp(SCREEN* sp, const char *capname, int col, int row);
-       int tigetflag_sp(SCREEN* sp, const char *capname);
+       int del_curterm_sp(SCREEN * sp, TERMINAL *oterm);
+       int putp_sp(SCREEN * sp, const char *str);
+       int restartterm_sp(SCREEN * sp, NCURSES_CONST char *term, int filedes, int *errret);
+       TERMINAL * set_curterm_sp(SCREEN * sp, TERMINAL *nterm);
+       int tgetent_sp(SCREEN * sp, char *bp, const char *name);
+       int tgetflag_sp(SCREEN * sp, const char *capname);
+       int tgetnum_sp(SCREEN * sp, const char *capname);
+       char * tgetstr_sp(SCREEN * sp, const char *capname, char **area);
+       char * tgoto_sp(SCREEN * sp, const char *capname, int col, int row);
+       int tigetflag_sp(SCREEN * sp, const char *capname);
 
-       int tigetnum_sp(SCREEN* sp, const char *capname);
-       char* tigetstr_sp(SCREEN* sp, const char *capname);
+       int tigetnum_sp(SCREEN * sp, const char *capname);
+       char * tigetstr_sp(SCREEN * sp, const char *capname);
        /* tparm_sp may use 9 long parameters rather than being variadic */
-       char* tparm_sp(SCREEN* sp, const char *str, ...);
-       int tputs_sp(SCREEN* sp, const char *str, int affcnt, NCURSES_SP_OUTC putc);
+       char * tparm_sp(SCREEN * sp, const char *str, ...);
+       int tputs_sp(SCREEN * sp, const char *str, int affcnt, NCURSES_SP_OUTC putc);
 
        #include <unctrl.h>
 
-       NCURSES_CONST char* unctrl_sp(SCREEN* sp, chtype ch);
+       NCURSES_CONST char * unctrl_sp(SCREEN * sp, chtype ch);

                              DESCRIPTION

                              @@ -265,10 +263,10 @@
 
        NCURSES_SP_NAME
             The new functions are named using the macro NCURSES_SP_NAME, which
-            hides the actual implementation.   Currently  this  adds  a  "_sp"
-            suffix  to  the name of the unextended function.  This manual page
-            indexes the extensions showing the full name.  However the  proper
-            usage  of  these  functions  uses  the  macro,  to provide for the
+            hides  the  actual  implementation.   Currently  this adds a "_sp"
+            suffix to the name of the unextended function.  This  manual  page
+            indexes  the extensions showing the full name.  However the proper
+            usage of these functions  uses  the  macro,  to  provide  for  the
             possibility of changing the naming convention for specific library
             configurations.
 
@@ -292,9 +290,7 @@

                              SEE ALSO

                                      curses(3x), curs_opaque(3x), curs_threads(3x)
 
-
-
-ncurses 6.5                       2024-04-20                 curs_sp_funcs(3x)
+ncurses 6.6                       2025-02-01                 curs_sp_funcs(3x)
                                diff --git a/doc/html/man/curs_termattrs.3x.html b/doc/html/man/curs_termattrs.3x.html index 386b4b4..10677bd 100644 --- a/doc/html/man/curs_termattrs.3x.html +++ b/doc/html/man/curs_termattrs.3x.html @@ -1,6 +1,6 @@ -curs_termattrs 3x 2024-04-20 ncurses 6.5 Library calls +curs_termattrs 3x 2025-08-23 ncurses 6.6 Library calls -

                                curs_termattrs 3x 2024-04-20 ncurses 6.5 Library calls

                                +

                                curs_termattrs 3x 2025-08-23 ncurses 6.6 Library calls

                                 curs_termattrs(3x)               Library calls              curs_termattrs(3x)
 
 
-
-

                                NAME

                                        baudrate,  erasechar,  erasewchar, has_ic, has_il, killchar, killwchar,
-       longname, term_attrs, termattrs, termname -  curses  environment  query
-       routines
+       longname, term_attrs,  termattrs,  termname  -  get  and  set  terminal
+       attributes with curses

                                SYNOPSIS

                                @@ -57,99 +55,114 @@
 
        int baudrate(void);
        char erasechar(void);
-       int erasewchar(wchar_t *wc);
+       int erasewchar(wchar_t * wc);
        bool has_ic(void);
        bool has_il(void);
        char killchar(void);
-       int killwchar(wchar_t *wc);
-       char *longname(void);
+       int killwchar(wchar_t * wc);
+       char * longname(void);
        attr_t term_attrs(void);
        chtype termattrs(void);
-       char *termname(void);
+       char * termname(void);

                                DESCRIPTION

                                baudrate

                                -       The  baudrate  routine  returns  the output speed of the terminal.  The
-       number returned is in bits per second, for  example  9600,  and  is  an
-       integer.
+       baudrate  returns  the  line  speed  of  the terminal, an integer value
+       measured in bits per second, for example 9600.

                                erasechar, erasewchar

                                -       The erasechar routine returns the user's current erase character.
+       erasechar returns the terminal's erase character.
 
-       The  erasewchar  routine  stores  the  current  erase  character in the
-       location referenced by wc.  If no erase character has been defined, the
-       routine fails and the location referenced by wc is not changed.
+       erasewchar stores the erase character in the location referenced by wc.
+       If no erase character has been  defined,  it  fails  and  the  location
+       referenced by wc is not changed.

                                has_ic, has_il

                                -       The  has_ic  routine  is  true  if the terminal has insert- and delete-
-       character capabilities.
+       has_ic  returns  TRUE  if the terminal has insert- and delete-character
+       capabilities.
 
-       The has_il routine is true if the terminal has insert- and  delete-line
-       capabilities, or can simulate them using scrolling regions.  This might
-       be used to determine if it would be appropriate  to  turn  on  physical
-       scrolling using scrollok(3x).
+       has_il returns  TRUE  if  the  terminal  has  insert-  and  delete-line
+       capabilities,  or  can simulate them using scrolling regions.  It might
+       be  used  to  determine  whether  it  would  be  appropriate   to   use
+       scrollok(3x) to turn on scrolling.

                                killchar, killwchar

                                -       The killchar routine returns the user's current line kill character.
+       killchar returns the terminal's line kill character.
 
-       The  killwchar  routine  stores  the current line-kill character in the
-       location referenced by wc.  If no line-kill character has been defined,
-       the routine fails and the location referenced by wc is not changed.
+       killwchar  stores the line-kill character in the location referenced by
+       wc.  If no line-kill character has  been  defined,  it  fails  and  the
+       location referenced by wc is not changed.

                                longname

                                -       The  longname  routine  returns a pointer to a static area containing a
-       verbose description of the current terminal.  The maximum length  of  a
-       verbose  description  is  128 characters.  It is defined only after the
-       call to initscr or newterm.  The area is overwritten by  each  call  to
-       newterm  and  is not restored by set_term, so the value should be saved
-       between calls to newterm if longname is going to be used with  multiple
-       terminals.
+       longname  returns  a  pointer  to  static  storage containing a verbose
+       description of the terminal  being  managed  by  curses.   The  maximum
+       length  of  a  verbose  description  is 128 characters.  The storage is
+       populated only  after  initscr(3x)  or  newterm(3x)  is  called.   This
+       storage  is  overwritten  by  each  call to newterm and not restored by
+       set_term(3x), so its contents should be saved between calls to  initscr
+       or newterm if longname is to be used with multiple terminals.

                                termattrs, term_attrs

                                        If  a  given  terminal  does  not  support  a  video  attribute that an
-       application program is trying to use, curses may substitute a different
-       video  attribute for it.  The termattrs and term_attrs functions return
-       a logical OR of all video attributes supported by the terminal using A_
-       and  WA_  constants  respectively.   This  information is useful when a
-       curses program needs  complete  control  over  the  appearance  of  the
-       screen.
+       application program is trying to use, curses may substitute a different
+       video attribute for it.  termattrs and term_attrs return a logical "or"
+       of all video attributes supported by the  terminal  using  A_  and  WA_
+       constants  respectively.   This  information  is  useful  when a curses
+       program needs complete control over the appearance of the screen.

                                termname

                                -       The termname routine returns the terminal name used by setupterm.
+       termname returns the terminal name used by setupterm(3x).

                                RETURN VALUE

                                -       longname and termname return NULL on error.
+       longname and termname return NULL on error.
 
-       Routines  that  return  an integer return ERR upon failure and OK (SVr4
-       only specifies "an integer  value  other  than  ERR")  upon  successful
-       completion.
+       Functions that return an integer return ERR upon failure  and  OK  upon
+       success.

                                NOTES

                                -       Note that termattrs may be a macro.
+       erasewchar,  killwchar,  and  term_attrs  are  part  of ncurses's wide-
+       character  API,  and  are  not  available  in  its   non-wide-character
+       configuration.
+
+       termattrs may be implemented as a macro.

                                PORTABILITY

                                -       X/Open  Curses,  Issue  4  describes  these  functions.  It changes the
-       return type of termattrs to the new  type  attr_t.   Most  versions  of
-       curses truncate the result returned by termname to 14 characters.
+       X/Open Curses Issue 4 describes these functions.
+
+       SVr4  describes  a  successful  return  value only as "an integer value
+       other than ERR".
+
+       Most versions of curses truncate the string returned by termname to  14
+       characters.
+
+
+

                                HISTORY

                                +       4BSD (1980) introduced longname.
+
+       SVr2 (1984) added baudrate, erasechar, killchar, has_ic, and has_il.
+
+       SVr3  (1987)  supplied  termname.   Later  that  year,  SVr3.1  brought
+       termattrs.
+
+       X/Open Curses  Issue 4  (1995)  specified  erasewchar,  killwchar,  and
+       term_attrs.

                                SEE ALSO

                                        curses(3x), curs_initscr(3x), curs_outopts(3x)
 
-
-
-ncurses 6.5                       2024-04-20                curs_termattrs(3x)
+ncurses 6.6                       2025-08-23                curs_termattrs(3x)
                                diff --git a/doc/html/man/curs_termcap.3x.html b/doc/html/man/curs_termcap.3x.html index c2763af..00e1e81 100644 --- a/doc/html/man/curs_termcap.3x.html +++ b/doc/html/man/curs_termcap.3x.html @@ -1,6 +1,6 @@ -curs_termcap 3x 2024-04-20 ncurses 6.5 Library calls +curs_termcap 3x 2025-08-16 ncurses 6.6 Library calls -

                                curs_termcap 3x 2024-04-20 ncurses 6.5 Library calls

                                +

                                curs_termcap 3x 2025-08-16 ncurses 6.6 Library calls

                                 curs_termcap(3x)                 Library calls                curs_termcap(3x)
 
 
-
-

                                NAME

                                        PC, UP, BC, ospeed, tgetent, tgetflag, tgetnum, tgetstr, tgoto, tputs -
        curses emulation of termcap
@@ -60,16 +58,16 @@
        char * BC;
        short ospeed;
 
-       int tgetent(char *bp, const char *name);
-       int tgetflag(const char *id);
-       int tgetnum(const char *id);
-       char *tgetstr(const char *id, char **area);
-       char *tgoto(const char *cap, int col, int row);
-       int tputs(const char *str, int affcnt, int (*putc)(int));
+       int tgetent(char * bp, const char * name);
+       int tgetflag(const char * id);
+       int tgetnum(const char * id);
+       char * tgetstr(const char * id, char ** sbuf);
+       char * tgoto(const char * cap, int col, int row);
+       int tputs(const char * str, int affcnt, int (* putc)(int));

                                DESCRIPTION

                                -       ncurses  provides  the  foregoing  variables   and   functions   as   a
+       ncurses   provides   the   foregoing   variables  and  functions  as  a
        compatibility layer for programs that use the termcap library.  The API
        is the same, but behavior is  emulated  using  the  terminfo  database.
        Thus,  it  can  be  used  only  to  query  the capabilities of terminal
@@ -80,53 +78,53 @@
        tgetent loads the terminal database entry for name; see term(7).   This
        must be done before calling any of the other functions.  It returns
 
-          1    on success,
+          1    on success,
 
-          0    if there is no such entry (or if the matching entry describes a
-               generic terminal, having  too  little  information  for  curses
+          0    if there is no such entry (or if the matching entry describes a
+               generic  terminal,  having  too  little  information for curses
                applications to run), and
 
-          -1   if the terminfo database could not be found.
+          -1   if the terminfo database could not be found.
 
        This implementation differs from those of historical termcap libraries.
 
-          o   ncurses  ignores  the  buffer  pointer  bp,  as do other termcap
-              implementations conforming to  portions  of  X/Open  Curses  now
-              withdrawn.   The  BSD  termcap library would store a copy of the
-              terminal  type  description  in  the  area  referenced  by  this
-              pointer.  terminfo stores terminal type descriptions in compiled
-              form, which is not the same thing.
+       o   ncurses  ignores  the  buffer  pointer  bp,  as  do  other  termcap
+           implementations   conforming  to  portions  of  X/Open  Curses  now
+           withdrawn.  The BSD termcap library  would  store  a  copy  of  the
+           terminal type description in the buffer referenced by this pointer.
+           terminfo  stores terminal type descriptions in compiled form, which
+           is not the same thing.
 
-          o   The meanings of the  return  values  differ.   The  BSD  termcap
-              library  does  not  check  whether the terminal type description
-              includes the generic (gn) capability, nor whether  the  terminal
-              type  description  supports  an  addressable  cursor, a property
-              essential for any curses implementation to operate.
+       o   The meanings of the return values differ.  The BSD termcap  library
+           does  not  check whether the terminal type description includes the
+           generic (gn) capability, nor whether the terminal type  description
+           supports an addressable cursor, a property essential for any curses
+           implementation to operate.

                                Retrieving Capability Values

                                -       tgetflag reports the Boolean entry  for  id,  or  zero  if  it  is  not
+       tgetflag  reports  the  Boolean  entry  for  id,  or  zero if it is not
        available.
 
        tgetnum obtains the numeric entry for id, or -1 if it is not available.
 
-       tgetstr  returns  the  string  entry  for  id,  or  NULL  if  it is not
-       available.   Use  tputs  to  output  the  string  returned.   The  area
+       tgetstr returns the  string  entry  for  id,  or  NULL  if  it  is  not
+       available.   Use  tputs  to  output  the  string  returned.   The  sbuf
        parameter is used as follows.
 
-          o   It is assumed to be the address of a pointer to a buffer managed
-              by the calling application.
+       o   It is assumed to be the address of a pointer to a buffer managed by
+           the calling application.
 
-          o   However, ncurses checks to ensure that area  is  not  NULL,  and
-              also  that  the resulting buffer pointer is not NULL.  If either
-              check fails, area is ignored.
+       o   However, ncurses checks to ensure that sbuf is not NULL,  and  that
+           the  pointer  obtained  by dereferencing sbuf is also not NULL.  If
+           either check fails, ncurses ignores sbuf.
 
-          o   If the checks succeed, ncurses also copies the return  value  to
-              the  buffer  pointed to by area, and the library updates area to
-              point past the null character terminating this value.
+       o   If the checks succeed, ncurses also copies the return value to  the
+           buffer  pointed  to  by sbuf, and the library updates sbuf to point
+           past the null character terminating this value.
 
-          o   The return value itself is  an  address  in  the  terminal  type
-              description loaded into memory.
+       o   The return  value  itself  is  an  address  in  the  terminal  type
+           description loaded into memory.

                                Applying String Capabilities

                                @@ -140,18 +138,18 @@
            thus be passed to tputs rather than some other output function such
            as printf(3).
 
-       o   While  tgoto  is  assumed  to  be used for the two-parameter cursor
+       o   While tgoto is assumed to be  used  for  the  two-parameter  cursor
            positioning  capability,  termcap  applications  also  use  it  for
            single-parameter capabilities.
 
-           Doing  so  reveals  a  quirk  in tgoto: most hardware terminals use
-           cursor addressing with row first, but the  original  developers  of
-           the  termcap  interface  chose  to  put  the col (column) parameter
-           first.  The tgoto function swaps the order of its  parameters.   It
-           does  this  even  for  calls requiring only a single parameter.  In
+           Doing so reveals a quirk in  tgoto:  most  hardware  terminals  use
+           cursor  addressing  with  row first, but the original developers of
+           the termcap interface chose  to  put  the  col  (column)  parameter
+           first.   The  tgoto function swaps the order of its parameters.  It
+           does this even for calls requiring only  a  single  parameter.   In
            that case, the first parameter is merely a placeholder.
 
-       o   Normally the ncurses  library  is  compiled  without  full  termcap
+       o   Normally  the  ncurses  library  is  compiled  without full termcap
            support.  In that case, tgoto uses an internal version of tparm(3x)
            (a more capable function).
 
@@ -167,38 +165,39 @@

                                Global Variables

                                -       The variables PC, UP and BC are set by tgetent to the terminfo  entry's
-       data for pad_char, cursor_up and backspace_if_not_bs, respectively.  UP
-       is not used by ncurses.  PC is used by delay_output(3x).  BC is used by
-       tgoto emulation.  The variable ospeed is set by ncurses using a system-
-       specific encoding to indicate the terminal's data rate.
+       tgetent sets the variables PC, UP, and BC to the terminfo entry's  data
+       for  pad_char  (pad), cursor_up (cuu1), and backspace_if_not_bs (OTbs),
+       respectively.    ncurses   does    not    employ    cuu1    internally.
+       delay_output(3x)  uses  pad,  while  tgoto  emulation uses the obsolete
+       termcap capability bs,  represented  in  ncurses  terminfo  as  "OTbs".
+       ncurses  assigns  the variable ospeed a system-specific value to encode
+       the terminal's data rate.

                                Releasing Memory

                                        The termcap functions provide  no  means  of  freeing  memory,  because
-       legacy  termcap  implementations used only the buffer areas provided by
-       the caller via tgetent and tgetstr.  Those buffers are unused in  term-
-       info.
+       legacy  termcap  implementations  used only the storage provided by the
+       caller via tgetent and tgetstr.  Those buffers are unused in terminfo.
 
-       By  contrast,  terminfo  allocates  memory.   It  uses setupterm(3x) to
-       obtain the data  used  by  tgetent  and  the  functions  that  retrieve
+       By contrast, terminfo  allocates  memory.   It  uses  setupterm(3x)  to
+       obtain  the  data  used  by  tgetent  and  the  functions that retrieve
        capability values.  One could use
               del_curterm(cur_term);
-       to  free  this  memory,  but  there  is an additional complication with
+       to free this memory, but  there  is  an  additional  complication  with
        ncurses.  It uses a fixed-size pool of storage locations, one per value
        of the terminal name parameter given to tgetent.  The screen(1) program
        relies upon this arrangement to improve its performance.
 
-       An application that uses only the termcap  functions,  not  the  higher
-       level  curses  API,  could  release  the  memory using del_curterm(3x),
+       An  application  that  uses only the termcap functions, not the higher-
+       level curses API,  could  release  the  memory  using  del_curterm(3x),
        because the pool is freed using other functions; see curs_memleaks(3x).

                                RETURN VALUE

                                -       The return values of  tgetent,  tgetflag,  tgetname,  and  tgetstr  are
+       The  return  values  of  tgetent,  tgetflag,  tgetname, and tgetstr are
        documented above.
 
-       tgoto returns NULL on error.  Error conditions include:
+       tgoto returns NULL on error.  Error conditions include:
 
        o   uninitialized state (tgetent was not called successfully),
 
@@ -206,7 +205,7 @@
 
        o   cap referring to a canceled capability,
 
-       o   cap  being  a  capability  with  string-valued  parameters (a term-
+       o   cap being a  capability  with  string-valued  parameters  (a  term-
            info-only feature), and
 
        o   cap being a capability with more than two parameters.
@@ -215,79 +214,75 @@

                                NOTES

                                -       ncurses compares only the first two characters of the id  parameter  of
+       ncurses  compares  only the first two characters of the id parameter of
        tgetflag, tgetnum, and tgetstr to the capability names in the database.

                                PORTABILITY

                                -       These  functions  are  no  longer standardized (and the variables never
-       were); ncurses provides them  to  support  legacy  applications.   They
-       should not be used in new programs.
+       These functions are no longer standardized  (and  the  variables  never
+       were);  see  section "HISTORY" below.  ncurses provides them to support
+       legacy applications; they should not be used in new programs.
 
-
-

                                Standards

                                -       o   X/Open   Curses,   Issue  4,  Version  2  (1996),  describes  these
-           functions, marking them as "TO BE WITHDRAWN".
-
-       o   X/Open Curses, Issue 7 (2009) marks the  termcap  interface  (along
-           with vwprintw and vwscanw) as withdrawn.
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
 
        Neither  X/Open  Curses  nor  the  SVr4 man pages documented the return
-       values of tgetent correctly, though all three shown here were  in  fact
+       values of tgetent correctly, though all three shown here were  in  fact
        returned  ever  since  SVr1.   In particular, an omission in the X/Open
-       Curses specification has  been  misinterpreted  to  mean  that  tgetent
-       returns  OK  or  ERR.   Because  the  purpose  of these functions is to
+       Curses specification has  been  misinterpreted  to  mean  that  tgetent
+       returns  OK  or  ERR.   Because  the  purpose  of these functions is to
        provide compatibility with the termcap library, that  is  a  defect  in
-       X/Open Curses, Issue 4, Version 2 rather than in ncurses.
+       X/Open Curses Issue 4 Version 2 rather than in ncurses.
 
-   Compatibility with BSD termcap
-       Externally  visible  variables  are  provided  for  support  of certain
+
+

                                Compatibility with BSD termcap

                                +       ncurses  provides  externally  visible  variables  to  support  certain
        termcap  applications.   However,  their  correct   usage   is   poorly
        documented; for example, it is unclear when reading and writing them is
-       meaningful.  In particular, some applications are reported  to  declare
-       and/or modify ospeed.
+       meaningful.   In  particular, some applications are reported to declare
+       and/or modify ospeed.
 
-       The  constraint  that only the first two characters of the id parameter
-       are used escapes many application developers.  The BSD termcap  library
-       did  not require a trailing null character on the capability identifier
-       passed to tgetstr,  tgetnum,  and  tgetflag.   Some  applications  thus
-       assume  that  the  termcap interface does not require the trailing null
-       character for the capability identifier.
+       The constraint that only the first two characters of the  id  parameter
+       are  looked  up  in  the  terminal  database  escapes  many application
+       developers.  The BSD termcap library did not require  a  trailing  null
+       character  after  the capability identifier passed to tgetstr, tgetnum,
+       and tgetflag.  Some applications thus assume that the termcap interface
+       does not  require  the  trailing  null  character  for  the  capability
+       identifier.  ncurses disallows matches by the termcap interface against
+       extended  capability  names  that  are  longer than two characters; see
+       user_caps(5).
 
-       o   ncurses disallows matches by the termcap interface against extended
-           capability   names   that  are  longer  than  two  characters;  see
-           user_caps(5).
-
-       The BSD termcap function tgetent returns the text of a termcap entry in
-       the  buffer  passed  as an argument.  This library, like other terminfo
+       The BSD termcap function tgetent returns the text of a termcap entry in
+       the buffer  passed  as  an  argument.   ncurses,  like  other  terminfo
        implementations, does not store terminal type descriptions as text.  It
        sets the buffer contents to a null-terminated string.

                                Header File

                                -       This  library  includes a termcap.h header for compatibility with other
-       implementations, but the  header  is  rarely  used  because  the  other
-       implementations are not strictly compatible.
+       ncurses  includes  a termcap.h header file for compatibility with other
+       implementations,  but   it   is   rarely   used   because   the   other
+       implementations are not mutually compatible; see below.

                                HISTORY

                                        Bill  Joy  originated  a  forerunner  of termcap called "ttycap", dated
        September 1977, and released in 1BSD (March 1978).  It used many of the
-       same  function  names  as the later termcap, such as tgetent, tgetflag,
-       tgetnum, and tgetstr.
+       same function names as the later termcap, such  as  tgetent,  tgetflag,
+       tgetnum, and tgetstr.
 
-       A clear descendant, the termlib library, followed in 2BSD  (May  1979),
-       adding tgoto and tputs.  The former applied at that time only to cursor
+       A  clear  descendant, the termlib library, followed in 2BSD (May 1979),
+       adding tgoto and tputs.  The former applied at that time only to cursor
        positioning  capabilities,  thus  the  overly  specific  name.   Little
        changed  in 3BSD (late 1979) except the addition of test programs and a
        termlib man page, which documented the API shown in section  "SYNOPSIS"
        above.
 
        4BSD  (November 1980) renamed termlib to termcap and added another test
-       program.  The library remained much the same though 4.3BSD (June 1986).
-       4.4BSD-Lite (June 1994) refactored it, leaving the API unchanged.
+       program.  The library remained  much  the  same  through  4.3BSD  (June
+       1986).    4.4BSD-Lite  (June  1994)  refactored  it,  leaving  the  API
+       unchanged.
 
-       Function  prototypes were a feature of ANSI C (1989).  The library long
+       Function prototypes were a feature of ANSI C (1989).  The library  long
        antedated the standard and thus provided no header file declaring them.
        Nevertheless,  the  BSD sources included two different termcap.h header
        files over time.
@@ -295,81 +290,84 @@
        o   One was used internally by jove(1) from 4.3BSD onward.  It declared
            global symbols for the termcap variables that it used.
 
-       o   The  other appeared in 4.4BSD-Lite Release 2 (June 1995) as part of
-           libedit (also known as the editline library).  CSRG source  history
+       o   The other appeared in 4.4BSD-Lite Release 2 (June 1995) as part  of
+           libedit  (also known as the editline library).  CSRG source history
            shows that this was added in mid-1992.  The libedit header file was
            used  internally  as  a  convenience  for  compiling  the  editline
            library.  It declared function prototypes, but no global variables.
-           This header file was added to NetBSD's termcap library in mid-1994.
+           NetBSD's termcap library added this header file in mid-1994.
 
-       Meanwhile, GNU termcap began development in 1990.   Its  first  release
-       (1.0)  in  1991  included  a  termcap.h  header.   Its  second (1.1) in
-       September 1992 modified the  header  to  use  const  for  the  function
-       prototypes  in  the  header where one would expect the parameters to be
-       read-only.   BSD  termcap  did  not.   The  prototype  for  tputs  also
-       differed,  but  in that instance, it was libedit that differed from BSD
+       Meanwhile,  GNU  termcap  began development in 1990.  Its first release
+       (1.0) in 1991 included a  termcap.h  header  file.   Its  second  (1.1)
+       release  in  September  1992  modified  the  file  to use const for the
+       function prototypes in the header where one would expect parameters  to
+       be  read-only.   BSD  termcap  did  not.   The prototype for tputs also
+       differed, but in that instance, it was libedit that differed  from  BSD
        termcap.
 
-       GNU termcap 1.3 was bundled with bash(1) in  mid-1993  to  support  the
-       readline(3) library.
+       GNU  bash(1)  has bundled GNU termcap 1.3 since mid-1993 to support its
+       readline(3) library, and continues to use it if configured to do so.
 
-       ncurses  1.8.1 (November 1993) provided a termcap.h file.  It reflected
-       influence  from  GNU  termcap  and  emacs(1)  (rather  than   jove(1)),
+       ncurses 1.8.1 (November 1993) provided a termcap.h file.  It  reflected
+       influence   from  GNU  termcap  and  emacs(1)  (rather  than  jove(1)),
        providing the following interface:
 
        o   global symbols used by emacs,
 
        o   const-qualified function prototypes, and
 
-       o   a prototype for tparam, a GNU termcap feature.
+       o   a prototype for tparam, a GNU termcap feature.
 
-       Later  (in mid-1996) the tparam function was removed from ncurses.  Any
-       two of the four implementations thus differ, and programs  that  intend
+       Later (in mid-1996) the tparam function was removed from ncurses.   Any
+       two  of  the four implementations thus differ, and programs that intend
        to work with all termcap library interfaces must account for that fact.
 
+       X/Open Curses Issue 4, Version 2  (1996),  describes  these  functions,
+       marking them as "TO BE WITHDRAWN".
+
+       X/Open Curses Issue 7 (2009) withdrew the termcap interface (along with
+       the vwprintw and vwscanw functions).
+

                                BUGS

                                        If  you  call  tgetstr  to  fetch  column_address  (ch)  or  any  other
        parameterized string capability, be aware that it is returned in  term-
        info notation, not the older and not-quite-compatible termcap notation.
-       This does not cause problems if all you do with it  is  call  tgoto  or
-       tparm,   which   both   parametrically   expand  terminfo-style  string
-       capabilities as terminfo does.  (If ncurses is  configured  to  support
-       termcap,  tgoto  checks whether the string is terminfo-style by looking
-       for "%p" parameters or "<...>"  delays,  and  invokes  a  termcap-style
+       This  does  not  cause  problems if all you do with it is call tgoto or
+       tparm,  which  both   parametrically   expand   terminfo-style   string
+       capabilities  as  terminfo  does.  (If ncurses is configured to support
+       termcap, tgoto checks whether the string is terminfo-style  by  looking
+       for  "%p"  parameters  or  "<...>"  delays, and invokes a termcap-style
        parser if the string appears not to use terminfo syntax.)
 
-       Because  terminfo's  syntax  for padding in string capabilities differs
+       Because terminfo's syntax for padding in  string  capabilities  differs
        from termcap's, users can be surprised.
 
-       o   tputs("50") in a terminfo system transmits "50" rather  than  busy-
+       o   tputs("50")  in  a terminfo system transmits "50" rather than busy-
            waiting for 50 milliseconds.
 
-       o   However,  if  ncurses is configured to support termcap, it may also
-           have been configured to support BSD-style padding.
+           However, if ncurses is configured to support termcap, it  may  also
+           have  been  configured to support BSD-style padding.  In that case,
+           tputs inspects strings passed to it,  looking  for  digits  at  the
+           beginning of the string.
 
-           In that case, tputs inspects strings  passed  to  it,  looking  for
-           digits at the beginning of the string.
-
-           tputs("50")  in  a termcap system may busy-wait for 50 milliseconds
+       o   tputs("50")  in  a termcap system may busy-wait for 50 milliseconds
            rather than transmitting "50".
 
        termcap  has  nothing  analogous  to  terminfo's  set_attributes  (sgr)
        capability.   One  consequence is that termcap applications assume that
        "me" (equivalent to terminfo's exit_attribute_mode  (sgr0)  capability)
-       does  not  reset  the alternate character set.  ncurses checks for, and
-       modifies the data shared with, the termcap interface to accommodate the
-       latter's limitation in this respect.
+       does  not reset the alternate character set.  ncurses inspects the data
+       shared with the termcap interface  and  modifies  it  as  necessary  to
+       accommodate the latter's limitation in this respect.

                                SEE ALSO

                                +       TCTEST -- A Termcap Test Utility
+
        curses(3x), curs_terminfo(3x), putc(3), term_variables(3x), terminfo(5)
 
-       https://invisible-island.net/ncurses/tctest.html
-
-
-
-ncurses 6.5                       2024-04-20                  curs_termcap(3x)
+ncurses 6.6                       2025-08-16                  curs_termcap(3x)
                                  @@ -388,7 +386,7 @@ ncurses 6.5 2024-04-20 NOTES
                                • PORTABILITY
                                  • diff --git a/doc/html/man/curs_terminfo.3x.html b/doc/html/man/curs_terminfo.3x.html index 2bba9d9..8af1dee 100644 --- a/doc/html/man/curs_terminfo.3x.html +++ b/doc/html/man/curs_terminfo.3x.html @@ -1,7 +1,7 @@ -curs_terminfo 3x 2024-04-13 ncurses 6.5 Library calls +curs_terminfo 3x 2025-11-11 ncurses 6.6 Library calls -

                                  curs_terminfo 3x 2024-04-13 ncurses 6.5 Library calls

                                  +

                                  curs_terminfo 3x 2025-11-11 ncurses 6.6 Library calls

                                   curs_terminfo(3x)                Library calls               curs_terminfo(3x)
 
 
-
-

                                  NAME

                                  -       del_curterm,   mvcur,   putp,   restartterm,   set_curterm,  setupterm,
-       tigetflag,  tigetnum,  tigetstr,  tiparm,  tiparm_s,  tiscan_s,  tparm,
-       tputs,  vid_attr,  vid_puts,  vidattr,  vidputs  - curses interfaces to
-       terminfo database
+       del_curterm,  putp,  restartterm,  set_curterm,  setupterm,  tigetflag,
+       tigetnum, tigetstr, tiparm, tiparm_s, tiscan_s, tparm, tputs, vid_attr,
+       vid_puts, vidattr, vidputs - curses interfaces to terminfo database

                                  SYNOPSIS

                                          #include <curses.h>
        #include <term.h>
 
-       TERMINAL *cur_term;
+       TERMINAL * cur_term;
 
        const char * const boolnames[];
        const char * const boolcodes[];
@@ -70,95 +67,83 @@
        const char * const strcodes[];
        const char * const strfnames[];
 
-       int setupterm(const char *term, int filedes, int *errret);
-       TERMINAL *set_curterm(TERMINAL *nterm);
-       int del_curterm(TERMINAL *oterm);
-       int restartterm(const char *term, int filedes, int *errret);
+       int setupterm(const char * term, int filedes, int * errret);
+       TERMINAL * set_curterm(TERMINAL * nterm);
+       int del_curterm(TERMINAL * oterm);
+       int restartterm(const char * term, int filedes, int * errret);
 
-       char *tparm(const char *str, ...);
+       char * tparm(const char * str, ...);
             /* or */
-       char *tparm(const char *str, long p1 ... long p9);
+       char * tparm(const char * str, long p1 ... long p9);
 
-       int tputs(const char *str, int affcnt, int (*putc)(int));
-       int putp(const char *str);
+       int tputs(const char * str, int affcnt, int (* putc)(int));
+       int putp(const char * str);
 
-       int vidputs(chtype attrs, int (*putc)(int));
+       int vidputs(chtype attrs, int (* putc)(int));
        int vidattr(chtype attrs);
-       int vid_puts(attr_t attrs, short pair, void *opts, int (*putc)(int));
-       int vid_attr(attr_t attrs, short pair, void *opts);
+       int vid_puts(attr_t attrs, short pair, void * opts, int (* putc)(int));
+       int vid_attr(attr_t attrs, short pair, void * opts);
 
-       int mvcur(int oldrow, int oldcol, int newrow, int newcol);
+       int tigetflag(const char * cap-code);
+       int tigetnum(const char * cap-code);
+       char * tigetstr(const char * cap-code);
 
-       int tigetflag(const char *cap-code);
-       int tigetnum(const char *cap-code);
-       char *tigetstr(const char *cap-code);
-
-       char *tiparm(const char *str, ...);
+       char * tiparm(const char * str, ...);
 
        /* extensions */
-       char *tiparm_s(int expected, int mask, const char *str, ...);
-       int tiscan_s(int *expected, int *mask, const char *str);
+       char * tiparm_s(int expected, int mask, const char * str, ...);
+       int tiscan_s(int * expected, int * mask, const char * str);
 
        /* deprecated */
-       int setterm(const char *term);
+       int setterm(const char * term);

                                  DESCRIPTION

                                  -       These low-level functions must be called by programs that deal directly
-       with  the  terminfo  database  to handle certain terminal capabilities,
-       such as programming function keys.  For all other functionality, curses
-       functions are more suitable and their use is recommended.
+       These lower-level functions of the curses standard must  be  called  by
+       programs  that  deal  directly  with  the  terminfo  database to handle
+       certain terminal capabilities, such as programming function keys.   For
+       all  other  functionality, curses functions are more suitable and their
+       use is recommended.
 
-       None  of  these  functions  use  (or  are aware of) multibyte character
+       None of these functions use  (or  are  aware  of)  multibyte  character
        strings such as UTF-8.
 
        o   Capability names and codes use the POSIX portable character set.
 
-       o   Capability string values have  no  associated  encoding;  they  are
+       o   Capability  string  values  have  no  associated encoding; they are
            strings of 8-bit characters.

                                  Initialization

                                  -       Initially, setupterm should be called.  The high-level curses functions
-       initscr and newterm call setupterm to initialize the low-level  set  of
-       terminal-dependent variables listed in term_variables(3x).
+       Call setupterm from  your  application  to  have  terminfo  manage  the
+       terminal   device;   this  action  initializes  the  terminal-dependent
+       variables listed in term_variables(3x).  (A curses application  calling
+       initscr(3x) or newterm(3x) achieves the same result.)  Applications can
+       use  the  terminal  capabilities either directly, by object definitions
+       corresponding to capability names and codes (see term_variables(3x)) or
+       by calling the functions documented here.   setupterm  initializes  the
+       terminfo variables lines and columns as described in use_env(3x).
 
-       Applications  can  use  the  terminal capabilities either directly (via
-       header  definitions),  or  by  special  functions.   The  header  files
-       curses.h  and  term.h  should  be  included  (in that order) to get the
-       definitions for these strings, numbers, and flags.
+       Pass   parameterized   string   capability   values  through  tparm  to
+       instantiate them.  All terminfo strings (including the output of tparm)
+       should be sent to  the  terminal  device  with  tputs  or  putp.   Call
+       reset_shell_mode(3x)  to restore the terminal modes before exiting.  (A
+       curses application calling endwin(3x) achieves the same result.)
 
-       The terminfo variables lines and columns are initialized  by  setupterm
-       as follows.
+       Programs that use cursor addressing should emit certain capabilities at
+       specific times.  Specifically, output
 
-       o   If  use_env(FALSE)  has  been  called, values for lines and columns
-           specified in terminfo are used.
+       o   enter_ca_mode upon startup, and
 
-       o   Otherwise, if the environment variables LINES  and  COLUMNS  exist,
-           their values are used.  If these environment variables do not exist
-           and the program is running in a window, the current window size  is
-           used.   Otherwise,  if  the environment variables do not exist, the
-           values for lines and columns specified in the terminfo database are
-           used.
-
-       Parameterized  strings  should  be  passed through tparm to instantiate
-       them.  All terminfo strings (including the output of tparm)  should  be
-       sent  to the terminal device with tputs or putp.  Call reset_shell_mode
-       to restore the terminal modes before exiting; see curs_kernel(3x).
-
-       Programs that use cursor addressing should
-
-       o   output enter_ca_mode upon startup and
-
-       o   output exit_ca_mode before exiting.
+       o   exit_ca_mode before exiting.
 
        Programs that execute shell subprocesses should
 
-       o   call reset_shell_mode and output exit_ca_mode before the  shell  is
-           called and
+       o   call reset_shell_mode(3x) and output exit_ca_mode before the  shell
+           is called, and
 
-       o   output  enter_ca_mode and call reset_prog_mode after returning from
-           the shell.
+       o   output  enter_ca_mode  and call reset_prog_mode(3x) after returning
+           from the shell.
 
        setupterm reads in the terminfo  database,  initializing  the  terminfo
        structures,  but  does  not set up the output virtualization structures
@@ -168,29 +153,28 @@
                environment variable TERM is read.
 
           filedes
-               is  the  file  descriptor used for getting and setting terminal
+               is the file descriptor used for getting  and  setting  terminal
                I/O modes.
 
-               Higher-level applications use  newterm(3x)  to  initialize  the
-               terminal,  passing  an  output stream rather than a descriptor.
-               In  curses,  the  two  are  the  same  because  newterm   calls
-               setupterm,  passing the file descriptor derived from its output
+               Higher-level  applications  use  newterm(3x)  to initialize the
+               terminal, passing an output stream rather  than  a  descriptor.
+               In   curses,  the  two  are  the  same  because  newterm  calls
+               setupterm, passing the file descriptor derived from its  output
                stream parameter.
 
           errret
-               points to an optional location where an  error  status  can  be
-               returned  to the caller.  If errret is not null, then setupterm
-               returns OK or ERR and stores a  status  value  in  the  integer
-               pointed  to  by  errret.   A  return  value of OK combined with
+               points  to  an  optional  location where an error status can be
+               returned to the caller.  If errret is not null, then  setupterm
+               returns  OK  or  ERR  and  stores a status value in the integer
+               pointed to by errret.  A  return  value  of  OK  combined  with
                status of 1 in errret is normal.
 
-               If ERR is returned, examine errret:
+               If ERR is returned, examine errret.
 
-               1    means that the terminal is hardcopy, and  cannot  be  used
-                    for curses applications.
-
-                    setupterm  determines  if  the entry is a hardcopy type by
-                    checking the hardcopy (hc) capability.
+               1    means  that  the  terminal  is  a  hard-copy  type  (lacks
+                    destructive backspace), and  cannot  be  used  for  curses
+                    applications.    The   library  determines  this  fact  by
+                    checking the terminal type's hardcopy (hc) capability.
 
                0    means that the terminal could not be found, or that it  is
                     a  generic  type, having too little information for curses
@@ -204,47 +188,47 @@
                If  errret  is  null,  setupterm  reports an error message upon
                finding an error and exits.  Thus, the simplest call is:
 
-                      setupterm((char *)0, 1, (int *)0);
+                      setupterm((char *) NULL, 1, (int *) NULL);
 
-               which uses all the defaults and sends the output to stdout.
+               which uses all the defaults and sends the output to stdout.

                                  The Terminal State

                                          setupterm stores its information  about  the  terminal  in  a  TERMINAL
        structure pointed to by the global variable cur_term.  If it detects an
        error,  or  decides  that  the  terminal  is  unsuitable  (hardcopy  or
-       generic),  it  discards  this  information,  making it not available to
+       generic), it  discards  this  information,  making  it  unavailable  to
        applications.
 
-       If setupterm is called repeatedly for the same terminal type,  it  will
-       reuse  the  information.   It  maintains  only  one  copy  of  a  given
-       terminal's capabilities in memory.   If  it  is  called  for  different
-       terminal  types,  setupterm  allocates  new  storage  for  each  set of
-       terminal capabilities.
+       If setupterm is called repeatedly for the same terminal type, it reuses
+       the  information.   It  maintains  only  one  copy  of  a  given type's
+       capabilities in memory.   If  called  for  different  types,  setupterm
+       allocates new storage for each set of terminal capabilities.
 
-       set_curterm sets cur_term to nterm,  and  makes  all  of  the  terminfo
-       Boolean,  numeric,  and string variables use the values from nterm.  It
-       returns the old value of cur_term.
+       set_curterm sets cur_term to nterm, making all of the terminfo Boolean,
+       numeric, and string capabilities use the values from nterm.  It returns
+       the old value of cur_term.
 
-       del_curterm frees the space pointed to by oterm and makes it  available
-       for  further  use.  If oterm is the same as cur_term, references to any
-       of the terminfo Boolean, numeric, and string variables  thereafter  may
-       refer  to  invalid  memory  locations  until another setupterm has been
-       called.
+       del_curterm  releases  the memory pointed to by oterm.  If oterm is the
+       same as cur_term, references to any of the terminfo  Boolean,  numeric,
+       and   string  capabilities  thereafter  may  refer  to  invalid  memory
+       locations until setupterm is called again.
 
-       restartterm is similar to setupterm and  initscr,  except  that  it  is
-       called  after  restoring  memory to a previous state (for example, when
-       reloading a game saved as a core image dump).  restartterm assumes that
-       the  windows  and  the  input  and  output options are the same as when
-       memory was saved, but the terminal type and baud rate may be different.
-       Accordingly,  restartterm  saves  various  terminal  state  bits, calls
-       setupterm, and then restores the bits.
+       restartterm is similar to setupterm, but  is  intended  for  use  after
+       restoring  program  memory  to  a  previous  state  (for  example, when
+       reloading an application that has  been  suspended  from  one  terminal
+       session and restored in another).  restartterm assumes that the display
+       dimensions and the input and output options are the same as when memory
+       was   saved,   but  the  terminal  type  and  line  speed  may  differ.
+       Accordingly,  restartterm  saves   relevant   terminal   state,   calls
+       setupterm, then restores that state.

                                  Formatting Output

                                  -       tparm instantiates the string str with parameters  pi.   A  pointer  is
-       returned to the result of str with the parameters applied.  Application
-       developers should keep in mind these quirks of the interface:
+       tparm  instantiates  the  string  str with parameters pi.  It returns a
+       pointer to a character string  representing  str  with  the  parameters
+       applied  to "%" expressions within.  Application developers should keep
+       in mind some quirks of the interface.
 
        o   Although tparm's actual parameters may be integers or strings,  the
            prototype expects long (integer) values.
@@ -258,18 +242,18 @@
        o   The  capability  string  is  null-terminated.   Use "\200" where an
            ASCII NUL is needed in the output.
 
-       tiparm is a newer form of tparm  which  uses  stdarg.h  rather  than  a
-       fixed-parameter  list.   Its  numeric  parameters  are ints rather than
+       tiparm is a newer form of tparm that uses stdarg.h rather than a fixed-
+       length parameter list.  Its numeric parameters  are  ints  rather  than
        longs.
 
-       Both tparm and tiparm assume that  the  application  passes  parameters
-       consistent  with the terminal description.  Two extensions are provided
-       as alternatives to deal with untrusted data.
+       tparm   and  tiparm  assume  that  the  application  passes  parameters
+       consistent  with  the  terminal  description.   ncurses  provides   two
+       extensions as alternatives to deal with untrusted data.
 
-       o   tiparm_s is an extension which is a safer formatting function  than
-           tparm or tiparm, because it allows the developer to tell the curses
-           library how many parameters to expect in the  parameter  list,  and
-           which may be string parameters.
+       o   The tiparm_s extension is a safer formatting function than tparm or
+           tiparm,  because it allows the developer to tell the curses library
+           how many parameters to expect in the parameter list, and which  may
+           be string parameters.
 
            The  mask  parameter has one bit set for each of the parameters (up
            to 9) passed as char pointers rather than numbers.
@@ -279,31 +263,26 @@

                                  Output Functions

                                  -       String  capabilities  can  contain  padding  information,  a time delay
-       (accommodating performance limitations of hardware terminals) expressed
-       as $<n>, where n is a nonnegative integral count of milliseconds.  If n
-       exceeds 30,000 (thirty seconds), it is capped at that value.
+       String  capabilities  can  contain padding, a time delay (accommodating
+       performance limitations of hardware terminals) expressed as $<n>, where
+       n is a nonnegative integral count of milliseconds.  If n exceeds 30,000
+       (thirty seconds), ncurses caps it at that value.
 
-       tputs interprets time-delay information in the string str  and  outputs
-       it, executing the delays:
+       tputs interprets time delays in the string str and acts upon them.
 
-       o   The  str parameter must be a terminfo string variable or the return
-           value of tparm, tiparm, tgetstr, or tgoto.
-
-           The tgetstr and tgoto functions are part of the termcap  interface,
-           which happens to share these function names with the terminfo API.
+       o   The str parameter must be  a  terminfo  string  capability  or  the
+           return value of tparm or tiparm.
 
        o   affcnt is the number of lines affected, or 1 if not applicable.
 
        o   putc is a putchar-like function to which the characters are passed,
            one at a time.
 
-           If tputs processes  a  time-delay,  it  uses  the  delay_output(3x)
-           function,  routing  any  resulting  padding characters through this
-           function.
+       tputs  processes  each  time  delay with the delay_output(3x) function,
+       routing any resulting padding characters through this function.
 
        putp calls "tputs(str, 1, putchar)".  The output of putp always goes to
-       stdout, rather than the filedes specified in setupterm.
+       stdout, rather than the filedes specified in setupterm.
 
        vidputs displays the string on the terminal in the video attribute mode
        attrs, which is any combination of the attributes listed in curses(3x).
@@ -311,37 +290,31 @@
 
        vidattr is like vidputs, except that it outputs through putchar(3).
 
-       vid_attr  and vid_puts correspond to vidattr and vidputs, respectively.
-       They use multiple parameters to represent the character attributes  and
+       vid_attr and vid_puts correspond to vidattr and vidputs,  respectively.
+       They  use multiple parameters to represent the character attributes and
        color; namely,
 
        o   attrs, of type attr_t, for the attributes and
 
        o   pair, of type short, for the color pair number.
 
-       Use  the  attribute  constants  prefixed  with  "WA_" with vid_attr and
+       Use the attribute constants  prefixed  with  "WA_"  with  vid_attr  and
        vid_puts.
 
-       X/Open Curses reserves the opts argument for future  use,  saying  that
-       applications  must  provide  a  null pointer for that argument; but see
+       X/Open  Curses  reserves  the opts argument for future use, saying that
+       applications must provide a null pointer for  that  argument;  but  see
        section "EXTENSIONS" below.
 
-       mvcur provides low-level cursor motion.  It  takes  effect  immediately
-       (rather  than  at the next refresh).  Unlike the other low-level output
-       functions, which either write to the standard output or pass an  output
-       function  parameter,  mvcur uses an output file descriptor derived from
-       the output stream parameter of newterm(3x).
-
-       While putp and mvcur are low-level functions that do not use high-level
-       curses  state,  ncurses  declares them in curses.h because System V did
-       this (see section "HISTORY" below).
+       While  putp  is  a  lower-level function that does not use higher-level
+       curses state, ncurses declares it in curses.h because System V  did  so
+       (see section "HISTORY" below).

                                  Terminal Capability Functions

                                  -       tigetflag, tigetnum, and tigetstr return the value  of  the  capability
-       corresponding  to  the terminfo cap-code, such as xenl, passed to them.
-       The cap-code for each capability is given in the table column  entitled
-       cap-code code in the capabilities section of terminfo(5).
+       tigetflag,  tigetnum,  and  tigetstr return the value of the capability
+       corresponding to the terminfo cap-code, such as xenl, passed  to  them.
+       The  cap-code  for each capability is given in the table column of that
+       name in the "Capabilities" section of terminfo(5).
 
        These functions return special values to denote errors.
 
@@ -362,7 +335,7 @@
        (char *)-1
               if cap-code is not a string capability, or
 
-       0      if it is canceled or absent from the terminal description.
+       NULL   if it is canceled or absent from the terminal description.

                                  Terminal Capability Names

                                  @@ -374,7 +347,7 @@
 
        o   the long terminfo names ("fnames")
 
-       for each of the predefined terminfo variables:
+       for each standard terminfo capability name.
 
               const char *boolnames[], *boolcodes[], *boolfnames[]
               const char *numnames[], *numcodes[], *numfnames[]
@@ -385,9 +358,7 @@
        Each successful call to setupterm allocates memory to hold the terminal
        description.  As a side effect, it  sets  cur_term  to  point  to  this
        memory.  If an application calls
-
               del_curterm(cur_term);
-
        the memory will be freed.
 
        The  formatting functions tparm and tiparm extend the storage allocated
@@ -397,8 +368,8 @@
            6.3, those were shared by all screens.  With ncurses 6.3, those are
            allocated per screen.  See terminfo(5).
 
-       o   To improve performance, ncurses 6.3 caches the result of  analyzing
-           terminfo  strings  for  their parameter types.  That is stored as a
+       o   To  improve performance, ncurses 6.3 caches the result of analyzing
+           terminfo strings for their parameter types.  That is  stored  as  a
            binary tree referenced from the TERMINAL structure.
 
        The higher-level initscr and newterm functions use setupterm.  Normally
@@ -407,34 +378,37 @@

                                  RETURN VALUE

                                  -       X/Open Curses defines no failure conditions.  In ncurses,
+       Functions that return integers return ERR  upon  failure  and  OK  upon
+       success.
 
-       del_curtem
+       In ncurses,
+
+       del_curterm
             fails if its terminal parameter is null.
 
        putp calls tputs, returning the same error codes.
 
        restartterm
-            fails if the associated call to setupterm returns an error.
+            fails if the associated call to setupterm returns ERR.
 
        setupterm
-            fails if it cannot allocate enough memory, or create  the  initial
-            windows  (stdscr,  curscr,  and newscr) Other error conditions are
+            fails  if  it cannot allocate enough memory, or create the initial
+            windows (stdscr, curscr, and newscr).  Other error conditions  are
             documented above.
 
        tparm
-            returns a null pointer if the capability would require  unexpected
-            parameters;  that  is,  too  many,  too  few,  or  incorrect types
+            returns  a null pointer if the capability would require unexpected
+            parameters; that  is,  too  many,  too  few,  or  incorrect  types
             (strings where integers are expected, or vice versa).
 
        tputs
-            fails if the string parameter is null.  It  does  not  detect  I/O
-            errors:  X/Open  Curses states that tputs ignores the return value
+            fails  if  the  string  parameter is null.  It does not detect I/O
+            errors: X/Open Curses states that tputs ignores the  return  value
             of the output function putc.

                                  NOTES

                                  -       The vid_attr function in ncurses is a special case.  It was  originally
+       The  vid_attr function in ncurses is a special case.  It was originally
        implemented based on a draft of X/Open Curses, as a macro, before other
        parts of the ncurses wide-character API were developed, and unlike  the
        other  wide-character  functions,  is  also  provided  in the non-wide-
@@ -442,8 +416,8 @@

                                  EXTENSIONS

                                  -       The functions marked as extensions were designed for ncurses,  and  are
-       not  found  in SVr4 curses, 4.4BSD curses, or any other previous curses
+       The functions marked as extensions originated in ncurses, and  are  not
+       found  in  SVr4  curses,  4.4BSD  curses,  or any other previous curses
        implementation.
 
        ncurses allows opts to be a pointer to int, which  overrides  the  pair
@@ -451,115 +425,124 @@

                                  PORTABILITY

                                  -       setterm is not described by X/Open and must be considered non-portable.
-       All other functions are as described by X/Open.
+       Except  for  setterm,  X/Open Curses Issue 4 describes these functions.
+       It specifies no error conditions for them.
+
+       SVr4 describes a successful return value except where "otherwise noted"
+       as "an integer value other than ERR".
+
+
+

                                  Header Files

                                  +       On legacy curses systems, include curses.h and term.h in that order  to
+       make   visible  the  definitions  of  the  string  arrays  storing  the
+       capability names and codes.

                                  Compatibility Macros

                                  -       This implementation  provides  a  few  macros  for  compatibility  with
-       systems  before  SVr4  (see  section  "HISTORY"  below).   They include
-       Bcrmode, Bfixterm, Bgettmode,  Bnocrmode,  Bresetterm,  Bsaveterm,  and
-       Bsetterm.
+       ncurses implements a few macros for early System V curses compatibility
+       (see section "HISTORY" below).  They include crmode, fixterm, gettmode,
+       nocrmode, resetterm, saveterm, and setterm.
 
-       In  SVr4,  these  are  found  in  curses.h, but except for setterm, are
-       likewise macros.  The one function, setterm, is mentioned in the manual
-       page.  It further notes that setterm was replaced by setupterm, stating
+       In SVr4, these are found in  curses.h,  but  except  for  setterm,  are
+       likewise macros.  The one function, setterm, is mentioned in the manual
+       page.  It further notes that setterm was replaced by setupterm, stating
        that the call
               setupterm(term, 1, (int *)0)
-       provides the same  functionality  as  setterm(term),  discouraging  the
-       latter  for  new programs.  ncurses implements each of these symbols as
-       macros for BSD curses compatibility.
+       provides the same functionality as
+              setterm(term)
+       and discouraging the latter for new programs.

                                  Legacy Data

                                  -       setupterm copies the terminal name to the array ttytype.  This  is  not
-       part of X/Open Curses, but is assumed by some applications.
+       setupterm copies the terminal name to the array ttytype.  This behavior
+       is not specified by X/Open Curses, but is assumed by some applications.
 
-       Other  implementions  may not declare the capability name arrays.  Some
-       provide them without declaring them.  X/Open Curses  does  not  specify
+       Other implementations may not declare the capability name arrays.  Some
+       provide  them  without  declaring them.  X/Open Curses does not specify
        them.
 
-       Extended  terminal  capability  names,  as defined by "tic -x", are not
+       Extended terminal capability names, as defined by  "tic  -x",  are  not
        stored in the arrays described here.

                                  Output Buffering

                                  -       Older versions of ncurses assumed that the file  descriptor  passed  to
-       setupterm from initscr or newterm uses buffered I/O, and would write to
-       the corresponding stream.  In  addition  to  the  limitation  that  the
-       terminal  was  left  in  block-buffered  mode  on  exit  (like System V
-       curses), it was problematic because ncurses did not  allow  a  reliable
-       way to clean up on receiving SIGTSTP.
+       Older  versions  of  ncurses assumed that the file descriptor passed to
+       setupterm from initscr or newterm used buffered I/O, and wrote  to  the
+       corresponding  stdio  stream.   In  addition to the limitation that the
+       terminal was  left  in  block-buffered  mode  on  exit  (like  System V
+       curses),  it  was  problematic because ncurses did not allow a reliable
+       way to clean up on receiving SIGTSTP.
 
-       The  current version (ncurses6) uses output buffers managed directly by
-       ncurses.  Some of the low-level functions described in this manual page
-       write  to  the  standard  output.  They are not signal-safe.  The high-
-       level functions in ncurses employ alternate versions of these functions
-       using the more reliable buffering scheme.
+       ncurses 6.x uses output  buffers  managed  directly  by  ncurses.   The
+       lower-level  functions described here that write to the terminal device
+       do so via the standard output stream; they thus  are  not  signal-safe.
+       The  higher-level  functions  in  ncurses  employ alternate versions of
+       these functions using a more reliable buffering scheme.

                                  Function Prototypes

                                  -       The  X/Open  Curses  prototypes  are  based  on  the SVr4 curses header
-       declarations, which were defined at the same time the  C  language  was
+       The X/Open Curses prototypes  are  based  on  the  SVr4  curses  header
+       declarations,  which  were  defined at the same time the C language was
        first standardized in the late 1980s.
 
-       o   X/Open  Curses  uses  const  less  effectively  than a later design
-           might, sometimes applying it needlessly to values that are  already
-           constant,  and  in  most cases overlooking parameters that normally
-           would use const.  Passing const-qualified parameters  to  functions
-           that  do  not  declare  them  const  may  prevent  the program from
-           compiling.   On  the  other  hand,  "writable   strings"   are   an
-           obsolescent feature.
+       o   X/Open Curses uses const  less  effectively  than  a  later  design
+           might, sometimes applying it needlessly to function parameters that
+           are  passed  by  value  (and  therefore  copied), and in most cases
+           overlooking parameters that  normally  would  benefit  from  const.
+           Passing const-qualified parameters to functions that do not declare
+           them  const  may  prevent the program from compiling.  On the other
+           hand, "writable strings" are an obsolescent C language feature.
 
-           As  an  extension,  this implementation can be configured to change
-           the function prototypes to use the const keyword.  The ncurses  ABI
-           6 enables this feature by default.
+           As an extension, ncurses can be configured to change  the  function
+           prototypes  to  use  the  const keyword.  The ncurses ABI 6 enables
+           this feature by default.
 
-       o   X/Open  Curses  prototypes tparm with a fixed number of parameters,
+       o   X/Open Curses prototypes tparm with a fixed number  of  parameters,
            rather than a variable argument list.
 
-           This implementation uses a  variable  argument  list,  but  can  be
-           configured  to use the fixed-parameter list.  Portable applications
-           should provide nine parameters after the format;  zeroes  are  fine
-           for this purpose.
+           ncurses uses a variable argument list, but can be configured to use
+           the  fixed-parameter  list.   Portable  applications should provide
+           nine parameters after the format; zeroes are fine for this purpose.
 
-           In  response  to review comments by Thomas E. Dickey, X/Open Curses
-           Issue 7 proposed the tiparm function in mid-2009.
+           In response to review comments by Thomas E. Dickey,  X/Open  Curses
+           Issue 7 proposed the tiparm function in mid-2009.
 
-           While tiparm is always provided in ncurses, the older form is  only
-           available  as  a build-time configuration option.  If not specially
-           configured, tparm is the same as tiparm.
+           While  tiparm  is  always  provided  in  ncurses, the older form is
+           available only  as  a  build-time  configuration  option.   If  not
+           specially configured, tparm is the same as tiparm.
 
-       Both forms of tparm have drawbacks:
+       Both forms of tparm have drawbacks.
 
-       o   Most of the calls to tparm use only one or two parameters.  Passing
+       o   Most  calls  to  tparm require only one or two parameters.  Passing
            nine on each call is awkward.
 
-           Using  long  for the numeric parameter type is a workaround to make
-           the parameter use the same amount of  stack  as  a  pointer.   That
-           approach  dates  back  to the mid-1980s, before C was standardized.
-           Since then, there is a standard (and pointers are not  required  to
-           fit in a long).
+           Using long for the numeric parameter type is a workaround  to  make
+           the  parameter  use  the  same amount of stack memory as a pointer.
+           That approach dates to the mid-1980s, before  C  was  standardized.
+           Since  ANSI C (1989), C language standards do not require a pointer
+           to fit in a long).
 
-       o   Providing  the  right  number of parameters for a variadic function
-           such  as  tiparm  can  be  a  problem,  in  particular  for  string
-           parameters.   However,  only a few terminfo capabilities use string
-           parameters (for instance, the ones used for  programmable  function
+       o   Providing the right number of parameters for  a  variadic  function
+           such  as  tiparm  can  be  a  problem,  in  particular  for  string
+           parameters.  However, only a few terminfo capabilities  use  string
+           parameters  (for  instance, the ones used for programmable function
            keys).
 
            The ncurses library checks usage of these capabilities, and returns
-           an error if the capability mishandles string  parameters.   But  it
-           cannot  check  if  a  calling program provides strings in the right
-           places for the tparm calls.
+           ERR if the capability mishandles string parameters.  But it  cannot
+           check if a calling program provides strings in the right places for
+           the tparm calls.
 
-           The tput(1) program checks its use of  these  capabilities  with  a
-           table, so that it calls tparm correctly.
+           ncurses's  tput(1)  checks  its  use  of  these capabilities with a
+           table, so that it calls tparm correctly.
 
-   Special TERM treatment
-       If configured to use the terminal driver, as with the MinGW port,
 
-       o   setupterm  interprets  a missing/empty TERM variable as the special
-           value "unknown".
+

                                  Special TERM treatment

                                  +       If ncurses is configured to use a terminal driver that does not  employ
+       the POSIX termios API, as with the MinGW port,
+
+       o   setupterm  interprets  a  missing  or  empty  TERM  variable as the
+           special value "unknown".
 
            SVr4 curses uses the special value "dumb".
 
@@ -567,128 +550,113 @@
            generic_type  (gn)  terminfo capability, while the latter does not.
            A generic terminal is unsuitable for full-screen applications.
 
-       o   setupterm allows explicit use of the the windows console driver  by
-           checking  if $TERM is set to "#win32con" or an abbreviation of that
-           string.
+       o   setupterm allows explicit use  of  the  Microsoft  Windows  console
+           driver  by  checking  whether the TERM environment variable has the
+           value "#win32con" or an abbreviation of that string.

                                  Other Portability Issues

                                  -       In SVr4, set_curterm returns an int, OK or  ERR.   We  have  chosen  to
+       In SVr4, set_curterm returns an int, OK or  ERR.   We  have  chosen  to
        implement the X/Open Curses semantics.
 
-       In SVr4, the third argument of tputs has the type "int (*putc)(char)".
+       In SVr4, the third argument of tputs has the type "int (*)(char)".
 
-       At  least one implementation of X/Open Curses (Solaris) returns a value
-       other than OK or ERR from tputs.  It instead returns the length of  the
-       string, and does no error checking.
+       At  least one implementation of X/Open Curses (Solaris xcurses) returns
+       a value other than OK or ERR from tputs.  It instead returns the length
+       of the string, and does no error checking.
 
-       X/Open  Curses notes that after calling mvcur, the curses state may not
-       match the actual terminal state, and that an application  should  touch
-       and  refresh  the  window  before  resuming  normal curses calls.  Both
-       ncurses and SVr4 curses implement mvcur using the SCREEN data allocated
-       in either initscr or newterm.  So though it is documented as a terminfo
-       function, mvcur is really a curses function that is not well specified.
-
-       X/Open Curses states that the old location must be given for  mvcur  to
-       accommodate  terminals  that lack absolute cursor positioning.  ncurses
-       allows the caller to use -1 for either or both old coordinates.  The -1
-       tells  ncurses  that  the old location is unknown, and that it must use
-       only absolute motion, as  with  the  cursor_address  (cup)  capability,
-       rather  than  the  least  costly  combination  of absolute and relative
-       motion.
+       Very old versions of AIX curses required inclusion of  curses.h  before
+       term.h.

                                  HISTORY

                                  -       SVr2 (1984) introduced the terminfo feature.   Its  programming  manual
+       SVr2  (1984)  introduced  the terminfo feature.  Its programming manual
        mentioned the following low-level functions.
 
        Function    Description
        ------------------------------------------------------------------------
-       fixterm     restore terminal to "in curses" state
-       gettmode    establish current terminal modes
-       mvcur       low level cursor motion
-       putp        use tputs to send characters via putchar
-       resetterm   set terminal modes to "out of curses" state
+       fixterm     restore terminal to "in curses" state
+       gettmode    establish current terminal modes
+       mvcur       low level cursor motion
+       putp        use tputs to send characters via putchar
+       resetterm   set terminal modes to "out of curses" state
+       resetty     reset terminal flags to stored value
+       saveterm    save current modes as "in curses" state
+       savetty     store current terminal flags
+       setterm     establish terminal with given type
+       setupterm   establish terminal with given type
+       tparm       interpolate parameters into string capability
+       tputs       apply padding information to a string
+       vidattr     like vidputs, but output through putchar
+       vidputs     write string to terminal, applying specified attributes
 
-       resetty     reset terminal flags to stored value
-       saveterm    save current modes as "in curses" state
-       savetty     store current terminal flags
-       setterm     establish terminal with given type
-       setupterm   establish terminal with given type
-       tparm       interpolate parameters into string capability
-       tputs       apply padding information to a string
-       vidattr     like vidputs, but output through putchar
-       vidputs     write string to terminal, applying specified attributes
-
-       The  programming  manual  also mentioned functions provided for termcap
+       The programming manual also mentioned functions  provided  for  termcap
        compatibility (commenting that they "may go away at a later date").
 
        Function   Description
        ------------------------------------------------------------------------
-       tgetent    look up termcap entry for given name
-       tgetflag   get Boolean entry for given id
-       tgetnum    get numeric entry for given id
-       tgetstr    get string entry for given id
-       tgoto      apply parameters to given capability
-       tputs      write characters via a function parameter, applying padding
+       tgetent    look up termcap entry for given name
+       tgetflag   get Boolean entry for given id
+       tgetnum    get numeric entry for given id
+       tgetstr    get string entry for given id
+       tgoto      apply parameters to given capability
+       tputs      write characters via a function parameter, applying padding
 
-       Early terminfo programs obtained capability values  from  the  TERMINAL
-       structure initialized by setupterm.
+       Early  terminfo  programs  obtained capability values from the TERMINAL
+       structure initialized by setupterm.
 
-       SVr3   (1987)   extended  terminfo  by  adding  functions  to  retrieve
-       capability values (like the termcap interface), and reusing  tgoto  and
-       tputs.
+       SVr3  (1987)  extended  terminfo  by  adding  functions   to   retrieve
+       capability  values  (like the termcap interface), and reusing tgoto and
+       tputs.
 
        Function    Description
        ------------------------------------------------------------------------
-       tigetflag   get Boolean entry for given id
-       tigetnum    get numeric entry for given id
-       tigetstr    get string entry for given id
+       tigetflag   get Boolean entry for given id
+       tigetnum    get numeric entry for given id
+       tigetstr    get string entry for given id
 
-       SVr3  also  replaced several of the SVr2 terminfo functions that had no
+       SVr3 also replaced several of the SVr2 terminfo functions that  had  no
        counterpart in the termcap interface, documenting them as obsolete.
 
        Function    Replaced by
        ------------------------------------------------------------------------
-       crmode      cbreak
-       fixterm     reset_prog_mode
-       gettmode    n/a
-       nocrmode    nocbreak
-       resetterm   reset_shell_mode
-       saveterm    def_prog_mode
-       setterm     setupterm
+       crmode      cbreak
+       fixterm     reset_prog_mode
+       gettmode    n/a
+       nocrmode    nocbreak
+       resetterm   reset_shell_mode
+       saveterm    def_prog_mode
+       setterm     setupterm
 
-       SVr3 kept the mvcur, vidattr, and vidputs functions, along  with  putp,
-       tparm,  and  tputs.   The latter were needed to support padding, and to
-       handle capabilities accessed by functions such as vidattr  (which  used
-       more than the two parameters supported by tgoto).
+       SVr3  kept  the mvcur, vidattr, and vidputs functions, along with putp,
+       tparm, and tputs.  The latter were needed to support  padding,  and  to
+       handle  capabilities  accessed by functions such as vidattr (which used
+       more than the two parameters supported by tgoto).
 
-       SVr3   introduced   the   functions   for  switching  between  terminal
-       descriptions;  for  example,  set_curterm.   Some   changes   reflected
+       SVr3  introduced  the  functions   for   switching   between   terminal
+       descriptions;   for   example,  set_curterm.   Some  changes  reflected
        incremental improvements to the SVr2 library.
 
-       o   The  TERMINAL  type  definition  was introduced in SVr3.01, for the
+       o   The TERMINAL type definition was introduced  in  SVr3.01,  for  the
            term structure provided in SVr2.
 
-       o   Various global variables such as boolnames were  mentioned  in  the
-           programming  manual  at  this  point, though the variables had been
+       o   Various  global  variables  such as boolnames were mentioned in the
+           programming manual at this point, though  the  variables  had  been
            provided in SVr2.
 
-       SVr4 (1989) added the vid_attr and vid_puts functions.
+       SVr4 (1989) added the vid_attr and vid_puts functions.
 
-       Other low-level functions are declared in the curses  header  files  of
-       Unix  systems,  but  none are documented.  Those noted as "obsolete" by
+       Other  low-level  functions  are declared in the curses header files of
+       Unix systems, but none are documented.  Those noted  as  "obsolete"  by
        SVr3 remained in use by System V's vi(1) editor.

                                  SEE ALSO

                                          curses(3x),   curs_initscr(3x),   curs_kernel(3x),   curs_memleaks(3x),
-       curs_termcap(3x),   curs_variables(3x),   putc(3),  term_variables(3x),
+       curs_termcap(3x),  curs_variables(3x),   putc(3),   term_variables(3x),
        terminfo(5)
 
-
-
-ncurses 6.5                       2024-04-13                 curs_terminfo(3x)
+ncurses 6.6                       2025-11-11                 curs_terminfo(3x)
                                    @@ -710,10 +678,12 @@ ncurses 6.5 2024-04-13 EXTENSIONS
                                  • PORTABILITY
                                    • diff --git a/doc/html/man/curs_threads.3x.html b/doc/html/man/curs_threads.3x.html index 8681a8f..efebf01 100644 --- a/doc/html/man/curs_threads.3x.html +++ b/doc/html/man/curs_threads.3x.html @@ -1,7 +1,7 @@ -curs_threads 3x 2024-03-16 ncurses 6.5 Library calls +curs_threads 3x 2025-02-15 ncurses 6.6 Library calls -

                                    curs_threads 3x 2024-03-16 ncurses 6.5 Library calls

                                    +

                                    curs_threads 3x 2025-02-15 ncurses 6.6 Library calls

                                     curs_threads(3x)                 Library calls                curs_threads(3x)
 
 
-
-

                                    NAME

                                            NCURSES_WINDOW_CB,   NCURSES_SCREEN_CB,   get_escdelay,   set_escdelay,
        set_tabsize, use_screen, use_window - curses support for multi-threaded
@@ -70,7 +68,7 @@

                                    DESCRIPTION

                                            The  ncurses  library  can  be  configured  to  support  multi-threaded
-       applications in a  rudimentary  way.   Such  configuration  produces  a
+       applications  in  a  rudimentary  way.   Such  configuration produces a
        different set of libraries, named libncursest, for example, since doing
        so alters ncurses's application binary interface (ABI).
 
@@ -80,32 +78,32 @@
        mutexes (mutual exclusion locks) needed to prevent concurrent access to
        variables shared by multiple threads of execution.
 
-       ncurses threading support requires  the  use  of  functions  to  access
-       members  of  the  WINDOW  structure  (see curs_opaque(3x)).  It further
-       makes functions of the common  global  variables  COLORS,  COLOR_PAIRS,
-       COLS,   ESCDELAY,   LINES,   TABSIZE,   curscr,  newscr,  and  ttytype,
-       maintaining them as as read-only values in the SCREEN structure.
+       ncurses  threading  support  requires  the  use  of functions to access
+       members of the WINDOW  structure  (see  curs_opaque(3x)).   It  further
+       makes  functions  of  the  common global variables COLORS, COLOR_PAIRS,
+       COLS,  ESCDELAY,  LINES,  TABSIZE,   curscr,   newscr,   and   ttytype,
+       maintaining them as read-only values in the SCREEN structure.
 
-       Even this is not enough to make an  application  using  curses  thread-
-       safe.   We  would  expect  a multi-threaded application to have threads
-       updating separate windows (on the same device),  and  separate  screens
-       (on  different  devices).   Further,  applications  expect a few of the
-       global variables to be writable.  The functions described here  address
+       Even  this  is  not  enough to make an application using curses thread-
+       safe.  We would expect a multi-threaded  application  to  have  threads
+       updating  separate  windows  (on the same device), and separate screens
+       (on different devices).  Further, applications  expect  a  few  of  the
+       global  variables to be writable.  The functions described here address
        these special situations.
 
        The  ESCDELAY  and  TABSIZE  global  variables  are  modified  by  some
-       applications.   To  modify  them  in   any   configuration,   use   the
-       set_escdelay  or set_tabsize functions.  Other global variables are not
+       applications.    To   modify   them   in  any  configuration,  use  the
+       set_escdelay or set_tabsize functions.  Other global variables are  not
        modifiable.  get_escdelay retrieves ESCDELAY's value.
 
-       The use_window and use_screen functions provide coarse-grained  mutexes
-       for  their  respective  WINDOW and SCREEN parameters; they call a user-
-       supplied function, pass it a data parameter, and return the value  from
+       The  use_window and use_screen functions provide coarse-grained mutexes
+       for their respective WINDOW and SCREEN parameters; they  call  a  user-
+       supplied  function, pass it a data parameter, and return the value from
        the user-supplied function to the application.

                                    Usage

                                    -       All  ncurses  library  functions  assume that the locale is not altered
+       All ncurses library functions assume that the  locale  is  not  altered
        during operation.  In addition, they use data that is maintained within
        a hierarchy of scopes.
 
@@ -179,7 +177,6 @@
        box_set                window (stdscr)
        can_change_color       terminal
        cbreak                 screen
-
        chgat                  window (stdscr)
        clear                  window (stdscr)
        clearok                window
@@ -246,7 +243,6 @@
        immedok                window
        in_wch                 window (stdscr)
        in_wchnstr             window (stdscr)
-
        in_wchstr              window (stdscr)
        inch                   window (stdscr)
        inchnstr               window (stdscr)
@@ -313,7 +309,6 @@
        mvderwin               window (stdscr)
        mvget_wch              screen (input operation)
        mvget_wstr             screen (input operation)
-
        mvgetch                screen (input operation)
        mvgetn_wstr            screen (input operation)
        mvgetnstr              screen (input operation)
@@ -380,7 +375,6 @@
        mvwprintw              window
        mvwscanw               screen
        mvwvline               window
-
        mvwvline_set           window
        napms                  reentrant
        newpad                 global (locks window list)
@@ -447,7 +441,6 @@
        slk_clear              screen
        slk_color              screen
        slk_init               screen
-
        slk_label              screen
        slk_noutrefresh        screen
        slk_refresh            screen
@@ -514,7 +507,6 @@
        waddnstr               window
        waddnwstr              window
        waddstr                window
-
        waddwstr               window
        wattr_get              window
        wattr_off              window
@@ -581,7 +573,6 @@
        wscanw                 screen
        wscrl                  window
        wsetscrreg             window
-
        wstandend              window
        wstandout              window
        wsyncdown              screen (affects window plus parents)
@@ -615,9 +606,7 @@

                                    SEE ALSO

                                            curses(3x), curs_opaque(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-03-16                  curs_threads(3x)
+ncurses 6.6                       2025-02-15                  curs_threads(3x)
                                      diff --git a/doc/html/man/curs_touch.3x.html b/doc/html/man/curs_touch.3x.html index 5071766..b2e9adc 100644 --- a/doc/html/man/curs_touch.3x.html +++ b/doc/html/man/curs_touch.3x.html @@ -1,6 +1,6 @@ -curs_touch 3x 2024-04-20 ncurses 6.5 Library calls +curs_touch 3x 2025-01-18 ncurses 6.6 Library calls -

                                      curs_touch 3x 2024-04-20 ncurses 6.5 Library calls

                                      +

                                      curs_touch 3x 2025-01-18 ncurses 6.6 Library calls

                                       curs_touch(3x)                   Library calls                  curs_touch(3x)
 
 
-
-

                                      NAME

                                              touchwin,     touchline,    untouchwin,    wtouchln,    is_linetouched,
        is_wintouched - control terminal output refresh in a curses window
@@ -69,10 +67,10 @@
        The  touchwin  and  touchline  routines  throw  away  all  optimization
        information  about  which  parts  of  the  window have been touched, by
        pretending that the entire window has been drawn on.  This is sometimes
-       necessary  when using overlapping windows, since a change to one window
-       affects the other window, but the records  of  which  lines  have  been
-       changed  in  the  other  window do not reflect the change.  The routine
-       touchline only pretends that count lines have been  changed,  beginning
+       necessary when using overlapping windows, since a change to one  window
+       affects  the  other  window,  but  the records of which lines have been
+       changed in the other window do not reflect  the  change.   The  routine
+       touchline  only  pretends that count lines have been changed, beginning
        with line start.
 
        The untouchwin routine marks all lines in the window as unchanged since
@@ -89,19 +87,17 @@

                                      RETURN VALUE

                                      -       All  routines  return the integer ERR upon failure and an integer value
-       other than ERR upon successful completion, unless  otherwise  noted  in
-       the preceding routine descriptions.
+       Functions  returning  integers  return  ERR  upon  failure  and OK upon
+       success.
 
-       X/Open   Curses  does  not  specify  any  error  conditions.   In  this
-       implementation
+       In ncurses,
 
           is_linetouched
-               returns an error if the window pointer is null, or if the  line
+               returns ERR if the window pointer  is  null,  or  if  the  line
                number is outside the window boundaries.
 
                The constant ERR is distinct from TRUE and FALSE, which are the
-               normal return values of this function.   Because  the  function
+               normal  return  values  of this function.  Because the function
                returns a bool, returning ERR (which is neither TRUE nor FALSE)
                may not be supported by the compiler.
 
@@ -110,31 +106,35 @@
                The actual function returns FALSE when it detects an error.
 
           wtouchln
-               returns an error if the window pointer is null, or if the  line
+               returns  ERR  if  the  window  pointer  is null, or if the line
                number is outside the window boundaries.

                                      NOTES

                                      -       All of these routines except wtouchln may be macros.
+       All of these functions except wtouchln may be implemented as macros.

                                      PORTABILITY

                                      -       These  functions  were  introduced  by SVr4.  The Solaris curses header
-       file, for instance, defines both an actual function and macro for each.
-       The  macros  give the same result as the actual functions.  SVr4 curses
-       does not check the window parameter win to ensure that it is not  NULL;
-       otherwise this implementation behaves the same as SVr4.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
 
-       X/Open  Curses, Issue 4 describes these functions, but defines no error
-       conditions.
+       SVr4 describes a successful return value except where "otherwise noted"
+       as "an integer value other than ERR".
+
+       SVr4 does not check win to ensure that it is not a null pointer.
+
+
+

                                      HISTORY

                                      +       SVr2 (1984) introduced touchwin,
+
+       SVr3  (1987)  added  touchline.   SVr3.1  later  that   year   supplied
+       is_linetouched, is_wintouched, untouchwin, and wtouchln.

                                      SEE ALSO

                                              curses(3x), curs_refresh(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_touch(3x)
+ncurses 6.6                       2025-01-18                    curs_touch(3x)
                                      diff --git a/doc/html/man/curs_trace.3x.html b/doc/html/man/curs_trace.3x.html index c1ea937..244861d 100644 --- a/doc/html/man/curs_trace.3x.html +++ b/doc/html/man/curs_trace.3x.html @@ -1,6 +1,6 @@ -curs_trace 3x 2024-04-20 ncurses 6.5 Library calls +curs_trace 3x 2025-01-18 ncurses 6.6 Library calls -

                                      curs_trace 3x 2024-04-20 ncurses 6.5 Library calls

                                      +

                                      curs_trace 3x 2025-01-18 ncurses 6.6 Library calls

                                       curs_trace(3x)                   Library calls                  curs_trace(3x)
 
 
-
-

                                      NAME

                                              curses_trace,  trace,  _tracef, _traceattr, _traceattr2, _tracecchar_t,
        _tracecchar_t2, _tracechar, _tracechtype, _tracechtype2, _nc_tracebits,
@@ -83,10 +81,10 @@
        o   Aside from curses_trace, the other functions are normally available
            only with the debugging library e.g., libncurses_g.a.
 
-           All of the trace functions may be compiled into any model  (shared,
+           All  of the trace functions may be compiled into any model (shared,
            static, profile) by defining the symbol TRACE.
 
-       o   Additionally,  the  functions  which use cchar_t are only available
+       o   Additionally, the functions which use cchar_t  are  only  available
            with the wide-character configuration of the libraries.
 
 
@@ -100,8 +98,8 @@
 
            The  other  functions  either  return  a  pointer  to a string-area
            (allocated by the corresponding function), or return no value (such
-           as  _tracedump, which implements the screen dump for TRACE_UPDATE).
-           The caller should not free these strings, since the  allocation  is
+           as _tracedump, which implements the screen dump for  TRACE_UPDATE).
+           The  caller  should not free these strings, since the allocation is
            reused on successive calls.  To work around the problem of a single
            string-area per  function,  some  use  a  buffer-number  parameter,
            telling the library to allocate additional string-areas.
@@ -109,8 +107,8 @@
        The curses_trace function is always available, whether or not the other
        trace functions are available:
 
-       o   If tracing  is  available,  calling  curses_trace  with  a  nonzero
-           parameter  updates  the  trace mask, and returns the previous trace
+       o   If  tracing  is  available,  calling  curses_trace  with  a nonzero
+           parameter updates the trace mask, and returns  the  previous  trace
            mask.
 
            When the trace mask is nonzero, ncurses creates the file "trace" in
@@ -121,8 +119,8 @@

                                      Trace Parameter

                                      -       The trace parameter is  formed  by  OR'ing  values  from  the  list  of
-       TRACE_xxx definitions in <curses.h>.  These include:
+       The trace parameter is formed by logically  "or"-ing  values  from  the
+       list of TRACE_xxx definitions in <curses.h>.  These include:
 
        TRACE_DISABLE
             turn off tracing by passing a zero parameter.
@@ -198,19 +196,19 @@
 
        o   messages produced by the underlying library are written to trace.
 
-       If  ncurses  is built without tracing, none of the latter are produced,
+       If ncurses is built without tracing, none of the latter  are  produced,
        and fewer diagnostics are provided by the command-line utilities.

                                      RETURN VALUE

                                      -       Routines which return a value are designed to be used as parameters  to
+       Routines  which return a value are designed to be used as parameters to
        the _tracef routine.

                                      ENVIRONMENT

                                      NCURSES_TRACE

                                      -       A  positive integral value stored in this variable causes the following
+       A positive integral value stored in this variable causes the  following
        functions to enable the tracing feature as if curses_trace were called.
 
            filter, initscr, new_prescr, newterm, nofilter, restartterm,
@@ -219,49 +217,47 @@

                                      PORTABILITY

                                      -       These functions are not part of  the  X/Open  Curses  interface.   Some
-       other  curses  implementations  are known to have similar features, but
+       These  functions  are  not  part  of the X/Open Curses interface.  Some
+       other curses implementations are known to have  similar  features,  but
        they are not compatible with ncurses:
 
-       o   SVr4 provided traceon and traceoff, to  control  whether  debugging
-           information  was  written to the "trace" file.  While the functions
-           were always available, this feature was only enabled if  DEBUG  was
+       o   SVr4  provided  traceon  and traceoff, to control whether debugging
+           information was written to the "trace" file.  While  the  functions
+           were  always  available, this feature was only enabled if DEBUG was
            defined when building the library.
 
            The SVr4 tracing feature is undocumented.
 
-       o   PDCurses  provides  traceon  and  traceoff,  which  (like SVr4) are
-           always available, and enable tracing to the "trace" file only  when
+       o   PDCurses provides traceon  and  traceoff,  which  (like  SVr4)  are
+           always  available, and enable tracing to the "trace" file only when
            a debug-library is built.
 
-           PDCurses  has  a  short description of these functions, with a note
-           that they are not present in X/Open Curses, ncurses or NetBSD.   It
-           does  not  mention  SVr4,  but the functions' inclusion in a header
+           PDCurses has a short description of these functions,  with  a  note
+           that  they are not present in X/Open Curses, ncurses or NetBSD.  It
+           does not mention SVr4, but the functions'  inclusion  in  a  header
            file section labeled "Quasi-standard" hints at the origin.
 
-       o   NetBSD does not provide functions  for  enabling/disabling  traces.
-           It     uses    environment    variables    CURSES_TRACE_MASK    and
-           CURSES_TRACE_FILE to  determine  what  is  traced,  and  where  the
-           results  are  written.  This is available only when a debug-library
+       o   NetBSD  does  not  provide functions for enabling/disabling traces.
+           It    uses    environment    variables    CURSES_TRACE_MASK     and
+           CURSES_TRACE_FILE  to  determine  what  is  traced,  and  where the
+           results are written.  This is available only when  a  debug-library
            is built.
 
            The NetBSD tracing feature is undocumented.
 
-       A few ncurses functions are not  provided  when  symbol  versioning  is
+       A  few  ncurses  functions  are  not provided when symbol versioning is
        used:
 
            _nc_tracebits, _tracedump, _tracemouse
 
-       The  original  trace routine was deprecated because it often conflicted
+       The original trace routine was deprecated because it  often  conflicted
        with application names.

                                      SEE ALSO

                                              curses(3x)
 
-
-
-ncurses 6.5                       2024-04-20                    curs_trace(3x)
+ncurses 6.6                       2025-01-18                    curs_trace(3x)
                                        diff --git a/doc/html/man/curs_util.3x.html b/doc/html/man/curs_util.3x.html index 6160a2c..f6d4ae5 100644 --- a/doc/html/man/curs_util.3x.html +++ b/doc/html/man/curs_util.3x.html @@ -1,7 +1,7 @@ -curs_util 3x 2024-04-20 ncurses 6.5 Library calls +curs_util 3x 2025-11-11 ncurses 6.6 Library calls -

                                        curs_util 3x 2024-04-20 ncurses 6.5 Library calls

                                        +

                                        curs_util 3x 2025-11-11 ncurses 6.6 Library calls

                                         curs_util(3x)                    Library calls                   curs_util(3x)
 
 
-
-

                                        NAME

                                                delay_output,  filter,  flushinp,  getwin, key_name, keyname, nofilter,
        putwin, unctrl, use_env, use_tioctl,  wunctrl  -  miscellaneous  curses
@@ -56,72 +54,82 @@

                                        SYNOPSIS

                                                #include <curses.h>
 
-       const char *unctrl(chtype ch);
-       wchar_t *wunctrl(cchar_t *wch);
+       const char * unctrl(chtype ch);
+       wchar_t * wunctrl(cchar_t * wch);
 
-       const char *keyname(int c);
-       const char *key_name(wchar_t wc);
+       const char * keyname(int c);
+       const char * key_name(wchar_t wc);
 
        void filter(void);
+       /* extension */
+       void nofilter(void);
 
-       void use_env(bool f);
+       void use_env(bool bf);
+       /* extension */
+       void use_tioctl(bool bf);
 
-       int putwin(WINDOW *win, FILE *filep);
-       WINDOW *getwin(FILE *filep);
+       int putwin(WINDOW * win, FILE * filep);
+       WINDOW * getwin(FILE * filep);
 
        int delay_output(int ms);
-       int flushinp(void);
 
-       /* extensions */
-       void nofilter(void);
-       void use_tioctl(bool f);
+       int flushinp(void);

                                        DESCRIPTION

                                         
-

                                        unctrl

                                        -       The  unctrl  routine  returns  a  character string which is a printable
-       representation of the character ch:
+

                                        unctrl, wunctrl

                                        +       unctrl   returns   a   null-terminated   character   string   printably
+       representing the curses character ch,  often  one  that  originated  in
+       keyboard input; see getch(3x).
 
-       o   Printable characters are displayed  as  themselves,  e.g.,  a  one-
-           character string containing the key.
+       o   Printable   characters  represent  themselves  as  a  one-character
+           string.
 
-       o   Control characters are displayed in the ^X notation.
+       o   Control characters are expressed in ^X notation,  where  X  is  the
+           printable  symbol  of  the  control  code's  value  plus  32 in the
+           ISO 646/"ASCII" character set.
 
-       o   Printing characters are displayed as is.
+       o   DEL (character code 127) is represented as ^?.
 
-       o   DEL (character 127) is displayed as ^?.
+       o   A character code greater than 127 is  represented  in  one  of  two
+           ways.
 
-       o   Values  above 128 are either meta characters (if the screen has not
-           been initialized, or if  meta(3x)  has  been  called  with  a  TRUE
-           parameter),  shown  in  the  M-X  notation,  or  are  displayed  as
-           themselves.  In the latter case, the values may not  be  printable;
-           this follows the X/Open specification.
+           If  the  screen  has  not  been initialized or is in meta mode (see
+           meta(3x)), it  is  expressed  in  M-X  notation,  where  X  is  the
+           representation of the code's value minus 128, as described above.
 
-       The  corresponding  wunctrl  returns  a  printable  representation of a
-       complex character wch.
+           If the screen is not in meta mode, the character code is assumed to
+           represent  itself.   It  nevertheless may not be printable; this is
+           the case for character codes 128-159 in ISO 8859 encodings.
 
-       In both unctrl and wunctrl the attributes and color associated with the
-       character parameter are ignored.
+           ncurses's  use_legacy_coding(3x)   function   configures   unctrl's
+           handling of these character codes.
+
+       wunctrl  returns  a  null-terminated  wide-character  string  printably
+       representing the curses complex character wch.
+
+       Both functions ignore the attributes and color pair selection of  their
+       argument.

                                        keyname, key_name

                                                The keyname routine returns a character string corresponding to the key
        c.  Key codes are different from character codes.
 
-       o   Key codes below 256  are  characters.   They  are  displayed  using
+       o   Key  codes  below  256  are  characters.   They are displayed using
            unctrl.
 
-       o   Values  above 256 may be the codes for function keys.  The function
+       o   Values above 256 may be the codes for function keys.  The  function
            key name is displayed.
 
-       o   Otherwise (if there is no corresponding name and the key is  not  a
-           character)  the  function returns null, to denote an error.  X/Open
-           also  lists   an   "UNKNOWN   KEY"   return   value,   which   some
+       o   Otherwise  (if  there is no corresponding name and the key is not a
+           character) the function returns null, to denote an  error.   X/Open
+           also   lists   an   "UNKNOWN   KEY"   return   value,   which  some
            implementations return rather than null.
 
-       The   corresponding  key_name  returns  a  multibyte  character  string
-       corresponding  to  the  wide-character  value  w.   The  two  functions
+       The  corresponding  key_name  returns  a  multibyte  character   string
+       corresponding  to  the  wide-character  value  wc.   The  two functions
        (keyname and key_name) do not return the same set of strings:
 
        o   keyname returns null where key_name would display a meta character.
@@ -130,7 +138,7 @@

                                        filter, nofilter

                                        -       The  filter  routine, if used, must be called before initscr or newterm
+       The filter routine, if used, must be called before initscr  or  newterm
        are called.  Calling filter causes these changes in initialization:
 
        o   LINES is set to 1;
@@ -142,33 +150,33 @@
 
        o   and the home string is set to the value of cr.
 
-       The  nofilter  routine  cancels  the effect of a preceding filter call.
-       That allows the caller to initialize a screen on  a  different  device,
-       using  a  different  value of $TERM.  The limitation arises because the
+       The nofilter routine cancels the effect of  a  preceding  filter  call.
+       That  allows  the  caller to initialize a screen on a different device,
+       using a different value of $TERM.  The limitation  arises  because  the
        filter routine modifies the in-memory copy of the terminal information.

                                        use_env

                                        -       The use_env routine, if  used,  should  be  called  before  initscr  or
-       newterm  are  called  (because  those  compute  the  screen  size).  It
-       modifies the way ncurses treats environment variables when  determining
+       The  use_env  routine,  if  used,  should  be  called before initscr or
+       newterm are  called  (because  those  compute  the  screen  size).   It
+       modifies  the way ncurses treats environment variables when determining
        the screen size.
 
-       o   Normally  ncurses  looks  first  at  the  terminal database for the
+       o   Normally ncurses looks first  at  the  terminal  database  for  the
            screen size.
 
-           If use_env was called with  FALSE  for  parameter,  it  stops  here
+           If  use_env  was  called  with  FALSE  for parameter, it stops here
            unless use_tioctl was also called with TRUE for parameter.
 
-       o   Then  it  asks  for the screen size via operating system calls.  If
+       o   Then it asks for the screen size via operating  system  calls.   If
            successful, it overrides the values from the terminal database.
 
-       o   Finally (unless use_env was called with FALSE  parameter),  ncurses
-           examines  the LINES or COLUMNS environment variables, using a value
-           in those to override the  results  from  the  operating  system  or
+       o   Finally  (unless  use_env was called with FALSE parameter), ncurses
+           examines the LINES or COLUMNS environment variables, using a  value
+           in  those  to  override  the  results  from the operating system or
            terminal database.
 
-           curses also updates the screen size in response to SIGWINCH, unless
+           curses also updates the screen size in response to SIGWINCH, unless
            overridden by the LINES or COLUMNS environment variables,
 
 
@@ -178,94 +186,99 @@
        use_tioctl is called with TRUE as an  argument,  ncurses  modifies  the
        last step in its computation of screen size as follows:
 
-       o   checks  if the LINES and COLUMNS environment variables are set to a
-           number greater than zero.
+       o   checks  whether the LINES and COLUMNS environment variables are set
+           to a number greater than zero.
 
        o   for each, ncurses updates the  corresponding  environment  variable
            with  the  value  that it has obtained via operating system call or
            from the terminal database.
 
        o   ncurses re-fetches the value of the environment variables  so  that
-           it is still the environment variables which set the screen size.
+           it is still the environment variables that set the screen size.
 
        The use_env and use_tioctl routines combine as follows.
 
               use_env   use_tioctl   Summary
               -----------------------------------------------------------------
-              TRUE      FALSE        This  is  the  default behavior.  ncurses
-                                     uses  operating   system   calls   unless
-                                     overridden    by    LINES    or   COLUMNS
+              TRUE      FALSE        ncurses   uses   operating  system  calls
+                                     unless overridden  by  LINES  or  COLUMNS
                                      environment variables; default.
-              TRUE      TRUE         ncurses updates LINES and  COLUMNS  based
+              TRUE      TRUE         ncurses  updates  LINES and COLUMNS based
                                      on operating system calls.
-              FALSE     TRUE         ncurses  ignores LINES and COLUMNS, using
+              FALSE     TRUE         ncurses ignores LINES and COLUMNS,  using
                                      operating system calls to obtain size.

                                        putwin, getwin

                                        -       The putwin routine writes all data associated with window (or pad)  win
-       into  the  file  to  which filep points.  This information can be later
+       The  putwin routine writes all data associated with window (or pad) win
+       into the file to which filep points.  This  information  can  be  later
        retrieved using the getwin function.
 
-       The getwin routine reads window related data  stored  in  the  file  by
-       putwin.   The  routine  then creates and initializes a new window using
-       that data.  It returns a pointer to the new window.  There  are  a  few
+       The  getwin  routine  reads  window  related data stored in the file by
+       putwin.  The routine then creates and initializes a  new  window  using
+       that  data.   It  returns a pointer to the new window.  There are a few
        caveats:
 
-       o   the  data  written  is  a  copy  of  the  WINDOW structure, and its
-           associated character cells.  The format differs between  the  wide-
-           character  (ncursesw)  and  non-wide  (ncurses) libraries.  You can
+       o   the data written is  a  copy  of  the  WINDOW  structure,  and  its
+           associated  character  cells.  The format differs between the wide-
+           character (ncursesw) and non-wide  (ncurses)  libraries.   You  can
            transfer data between the two, however.
 
-       o   the retrieved window is always created as a  top-level  window  (or
+       o   the  retrieved  window  is always created as a top-level window (or
            pad), rather than a subwindow.
 
-       o   the  window's character cells contain the color pair value, but not
-           the actual color numbers.  If cells in  the  retrieved  window  use
-           color  pairs  which  have not been created in the application using
+       o   the window's character cells contain the color pair value, but  not
+           the  actual  color  numbers.   If cells in the retrieved window use
+           color pairs that have not been created  in  the  application  using
            init_pair, they will not be colored when the window is refreshed.

                                        delay_output

                                        -       The delay_output routine inserts an ms  millisecond  pause  in  output.
-       Employ  this  function  judiciously  when terminal output uses padding,
-       because ncurses  transmits  null  characters  (consuming  CPU  and  I/O
-       resources)  instead  of  sleeping  and  requesting  resumption from the
+       The  delay_output  routine  inserts  an ms millisecond pause in output.
+       Employ this function judiciously when  terminal  output  uses  padding,
+       because  ncurses  transmits  null  characters  (consuming  CPU  and I/O
+       resources) instead of  sleeping  and  requesting  resumption  from  the
        operating system.  Padding is used unless:
 
        o   the terminal description has npc (no_pad_char) capability, or
 
        o   the environment variable NCURSES_NO_PADDING is set.
 
-       If padding is not in use, ncurses uses napms to perform the delay.   If
-       the  value  of ms exceeds 30,000 (thirty seconds), it is capped at that
+       If  padding is not in use, ncurses uses napms to perform the delay.  If
+       the value of ms exceeds 30,000 (thirty seconds), it is capped  at  that
        value.

                                        flushinp

                                        -       The flushinp routine throws away any typeahead that has been  typed  by
+       The  flushinp  routine throws away any typeahead that has been typed by
        the user and has not yet been read by the program.

                                        RETURN VALUE

                                        -       Except  for  flushinp,  routines that return an integer return ERR upon
-       failure and OK (SVr4 specifies only "an integer value other than  ERR")
-       upon successful completion.
+       Except for flushinp, functions that return  integers  return  ERR  upon
+       failure and OK upon success.
 
-       Routines that return pointers return NULL on error.
+       Functions that return pointers return a null pointer on failure.
 
-       X/Open   Curses  does  not  specify  any  error  conditions.   In  this
-       implementation
+       In ncurses,
 
-          flushinp
-               returns an error if the terminal was not initialized.
+       o   flushinp returns ERR if the terminal was not initialized, and
 
-          putwin
-               returns an error if  the  associated  fwrite  calls  return  an
-               error.
+       o   putwin returns ERR if its associated write(2) calls return ERR.
+
+
+

                                        NOTES

                                        +       wunctrl  is  part of ncurses's wide-character API, and is not available
+       in its non-wide-character configuration.

                                        PORTABILITY

                                        +       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.
+
+       SVr4 describes a successful return value  only  as  "an  integer  value
+       other than ERR".
+

                                        filter

                                                The  SVr4  documentation  describes  the  action  of filter only in the
@@ -277,9 +290,9 @@
        The  limitation  to  30  seconds and the use of napms differ from other
        implementations.
 
-       o   SVr4 curses does not delay if no padding character is available.
+       o   SVr4 curses does not delay if no padding character is available.
 
-       o   NetBSD curses uses napms when no padding  character  is  available,
+       o   NetBSD curses uses napms when no padding  character  is  available,
            but  does  not  take  timing  into  account  when using the padding
            character.
 
@@ -288,57 +301,58 @@

                                        keyname

                                                The keyname function  may  return  the  names  of  user-defined  string
-       capabilities  which are defined in the terminfo entry via the -x option
-       of tic.  This implementation automatically assigns at run-time keycodes
-       to  user-defined  strings  which begin with "k".  The keycodes start at
-       KEY_MAX, but are not guaranteed to be the same value for different runs
-       because  user-defined  codes  are merged from all terminal descriptions
-       which have been loaded.  The use_extended_names(3x)  function  controls
-       whether  this  data  is loaded when the terminal description is read by
-       the library.
+       capabilities  that  are defined in the terminfo entry via the -x option
+       of tic.  This implementation  automatically  assigns  at  run-time  key
+       codes to user-defined strings that begin with "k".  The key codes start
+       at  KEY_MAX,  but are not guaranteed to be the same value for different
+       runs  because  user-defined  codes  are  merged   from   all   terminal
+       descriptions   that   have  been  loaded.   The  use_extended_names(3x)
+       function controls  whether  this  data  is  loaded  when  the  terminal
+       description is read by the library.

                                        nofilter, use_tioctl

                                        -       The nofilter and use_tioctl routines are  specific  to  ncurses.   They
-       were  not  supported on Version 7, BSD or System V implementations.  It
-       is recommended  that  any  code  depending  on  ncurses  extensions  be
+       The  nofilter  and  use_tioctl  routines are specific to ncurses.  They
+       were not supported on Version 7, BSD or System V  implementations.   It
+       is  recommended  that  any  code  depending  on  ncurses  extensions be
        conditioned using NCURSES_VERSION.

                                        putwin/getwin file-format

                                                The putwin and getwin functions have several issues with portability:
 
-       o   The   files   written   and   read   by   these  functions  use  an
-           implementation-specific format.  Although the format is an  obvious
+       o   The  files  written  and   read   by   these   functions   use   an
+           implementation-specific  format.  Although the format is an obvious
            target for standardization, it has been overlooked.
 
-           Interestingly  enough,  according to the copyright dates in Solaris
-           source, the functions (along with scr_init, etc.)  originated  with
+           Interestingly enough, according to the copyright dates  in  Solaris
+           source,  the  functions (along with scr_init, etc.) originated with
            the University of California, Berkeley (in 1982) and were later (in
            1988) incorporated into SVr4.  Oddly, there are no  such  functions
-           in the 4.3BSD curses sources.
+           in the 4.3BSD curses sources.
 
        o   Most implementations simply dump the binary WINDOW structure to the
-           file.  These include SVr4 curses, NetBSD and PDCurses, as  well  as
-           older ncurses versions.  This implementation (as well as the X/Open
-           variant of Solaris curses, dated 1995) uses textual dumps.
+           file.   These  include SVr4 curses, NetBSD curses, and PDCurses, as
+           well as older ncurses versions.  This implementation  (as  well  as
+           xcurses,  the  X/Open  variant  of Solaris curses, dated 1995) uses
+           textual dumps.
 
-           The implementations which  use  binary  dumps  use  block-I/O  (the
-           fwrite  and  fread  functions).   Those  that use textual dumps use
-           buffered-I/O.  A few applications may happen to write extra data in
-           the  file  using these functions.  Doing that can run into problems
-           mixing block- and buffered-I/O.  This  implementation  reduces  the
-           problem  on writes by flushing the output.  However, reading from a
-           file written using mixed schemes may not be successful.
+           The implementations that use binary dumps use block  I/O  (write(2)
+           and  read(2) functions).  Those that use textual dumps use buffered
+           I/O.  A few applications may happen to write extra data in the file
+           using these functions.  Doing that can  run  into  problems  mixing
+           block and buffered I/O.  This implementation reduces the problem on
+           writes  by  flushing  the  output.   However,  reading  from a file
+           written using mixed schemes may not be successful.

                                        unctrl, wunctrl

                                        -       X/Open Curses, Issue 4  describes  these  functions.   It  states  that
-       unctrl and wunctrl will return a null pointer if unsuccessful, but does
-       not define any error conditions.  This implementation checks for  three
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for them.  It states that unctrl and wunctrl will  return  a
+       null  pointer  if  unsuccessful.   This implementation checks for three
        cases:
 
-       o   the  parameter  is  a  7-bit  US-ASCII code.  This is the case that
+       o   the parameter is a 7-bit US-ASCII code.   This  is  the  case  that
            X/Open Curses documented.
 
        o   the parameter is in the range 128-159, i.e., a C1 control code.  If
@@ -348,7 +362,7 @@
            "~A", etc., analogous to "^@", "^A", C0 controls.
 
            X/Open Curses does not document whether unctrl can be called before
-           initializing curses.  This implementation permits that, and returns
+           initializing curses.  This implementation permits that, and returns
            the "~@", etc., values in that case.
 
        o   parameter values outside the 0 to 255 range.  unctrl returns a null
@@ -367,32 +381,46 @@
        Likewise,  the meta(3x) function allows the caller to change the output
        of keyname, i.e., it determines whether to  use  the  "M-"  prefix  for
        "meta"    keys    (codes    in   the   range   128   to   255).    Both
-       use_legacy_coding(3x)  and  meta(3x)  succeed  only  after  curses   is
+       use_legacy_coding(3x)  and  meta(3x)  succeed  only  after  curses   is
        initialized.   X/Open  Curses  does not document the treatment of codes
        128 to 159.  When treating them as "meta" keys (or if keyname is called
-       before   initializing  curses),  this  implementation  returns  strings
+       before  initializing  curses),  this  implementation  returns   strings
        "M-^@", "M-^A", etc.
 
-       X/Open Curses documents unctrl as declared in <unctrl.h>, which ncurses
-       does.   However,  ncurses' <curses.h> includes <unctrl.h>, matching the
-       behavior of SVr4 curses.  Other implementations may not do that.
+       X/Open  Curses  documents unctrl as declared in unctrl.h, which ncurses
+       does.  However, ncurses's  curses.h  includes  unctrl.h,  matching  the
+       behavior of SVr4 curses.  Other implementations may not do that.

                                        use_env, use_tioctl

                                        -       If ncurses is configured to provide  the  sp-functions  extension,  the
-       state  of  use_env  and  use_tioctl may be updated before creating each
-       screen rather than once  only  (curs_sp_funcs(3x)).   This  feature  of
-       use_env is not provided by other implementations of curses.
+       If  ncurses  is  configured  to provide the sp-functions extension, the
+       state of use_env and use_tioctl may be  updated  before  creating  each
+       screen  rather  than  once  only  (curs_sp_funcs(3x)).  This feature of
+       use_env is not provided by other implementations of curses.
+
+
+

                                        HISTORY

                                        +       4BSD (1980) introduced unctrl, defining it as a macro in unctrl.h.
+
+       SVr2 (1984) added delay_output, flushinp, and keyname.
+
+       SVr3 (1987) supplied filter.  Later that year,  SVr3.1  brought  getwin
+       and  putwin,  reading  and  writing  window  dumps  with  fread(3)  and
+       fwrite(3), respectively.
+
+       SVr4 (1989) furnished use_env.
+
+       X/Open Curses Issue 4 (1995) specified key_name and wunctrl.
+
+       ncurses 5.6 (2006) added nofilter, and 6.0 (2015) use_tioctl.

                                        SEE ALSO

                                        -       curses(3x),    curs_initscr(3x),    curs_inopts(3x),   curs_kernel(3x),
-       curs_scr_dump(3x),        curs_sp_funcs(3x),        curs_variables(3x),
+       curses(3x), curs_initscr(3x), curs_inopts(3x), curs_kernel(3x),
+       curs_scr_dump(3x), curs_sp_funcs(3x), curs_variables(3x),
        legacy_coding(3x)
 
-
-
-ncurses 6.5                       2024-04-20                     curs_util(3x)
+ncurses 6.6                       2025-11-11                     curs_util(3x)
                                        diff --git a/doc/html/man/curs_variables.3x.html b/doc/html/man/curs_variables.3x.html index 92ae985..f9b033e 100644 --- a/doc/html/man/curs_variables.3x.html +++ b/doc/html/man/curs_variables.3x.html @@ -1,6 +1,6 @@ -curs_variables 3x 2024-04-13 ncurses 6.5 Library calls +curs_variables 3x 2025-08-23 ncurses 6.6 Library calls -

                                        curs_variables 3x 2024-04-13 ncurses 6.5 Library calls

                                        +

                                        curs_variables 3x 2025-08-23 ncurses 6.6 Library calls

                                         curs_variables(3x)               Library calls              curs_variables(3x)
 
 
-
-

                                        NAME

                                                bool,  chtype,  cchar_t,  attr_t, SCREEN, WINDOW, TRUE, FALSE, ERR, OK,
-       curscr, newscr, stdscr, COLORS,  COLOR_PAIRS,  COLS,  LINES,  ESCDELAY,
-       TABSIZE - curses data types, constants, and global variables
+       CCHARW_MAX, curscr, newscr, stdscr, COLORS, COLOR_PAIRS,  COLS,  LINES,
+       ESCDELAY, TABSIZE - curses data types, constants, and global variables

                                        SYNOPSIS

                                        @@ -70,6 +68,9 @@
        const /* ... */ ERR;
        const /* ... */ OK;
 
+       /* extension */
+       const /* ... */ CCHARW_MAX;
+
        /* variables */
        int COLORS;
        int COLOR_PAIRS;
@@ -103,19 +104,25 @@

                                        ERR, OK

                                        -       curses  and terminfo routines frequently return these constant integral
+       curses and terminfo functions frequently return these constant integral
        values indicating failure and success, respectively.
 
 
-

                                        PREDEFINED TYPES

                                        +

                                        CCHARW_MAX

                                        +       This integral value, an ncurses extension, indicates the maximum number
+       of  wchar_t  wide  characters  that  can  be stored in a curses complex
+       character cchar_t.
+
+
+

                                        DATA TYPES

                                        bool

                                        -       X/Open Issue 4 curses  (1996)  preceded  the  ISO  C99  and  ISO  C++98
-       standards,  each of which also defined a Boolean data type.  The curses
-       library requires an integral type bool.
+       curses defines an integral type bool.   X/Open  Issue 4  curses  (1996)
+       preceded  the  ISO C99  and  ISO C++98  standards,  each  of which also
+       defined a Boolean data type of the same name.
 
-       ncurses' configure script attempts to discover the data  type  used  by
-       the system's C and C++ compilers, to reuse for the curses bool.
+       ncurses's configure script attempts to discover the data type  used  by
+       the system's C and C++ compilers, to reuse them as its own bool.

                                        chtype

                                        @@ -147,48 +154,52 @@

                                        VARIABLES

                                         
-

                                        curscr, stdscr, newscr

                                        -       The library records updates to the terminal screen in  a  window  named
-       curscr.   This  object  is  referred  to  as  the  "physical screen" in
+

                                        curscr, newscr, stdscr

                                        +       When a curses application calls initscr(3x) or newterm(3x), the library
+       creates a window named stdscr that is the same  size  as  the  terminal
+       screen,  (minus  any  lines reserved by ripoffline(3x) or slk_init(3x))
+       and is the implicit window used  by  functions  that  interact  with  a
+       window  but  do  not  take  a  parameter  identifying  one; many curses
+       functions use it.  An application need not use stdscr; it might  prefer
+       to tile the display into multiple windows instead.
+
+       The  library  records  updates to the terminal screen in a window named
+       curscr.  This object  is  referred  to  as  the  "physical  screen"  in
        curs_refresh(3x) and curs_outopts(3x).
 
-       ncurses collects pending updates to the terminal  screen  in  a  window
-       named  newscr.   This  object is referred to as the "virtual screen" in
-       the curs_kernel(3x), curs_refresh(3x), and curs_outopts(3x).  When  the
-       screen  is  refreshed, curses determines a minimal set of updates using
+       ncurses  collects  pending  updates  to the terminal screen in a window
+       named newscr.  This object is referred to as the  "virtual  screen"  in
+       the  curs_kernel(3x), curs_refresh(3x), and curs_outopts(3x).  When the
+       screen is refreshed, curses determines a minimal set of  updates  using
        the terminal's capabilities to make curscr look like newscr.
 
-       Once curses is initialized, it creates a window named  stdscr.   It  is
-       the  same size as the terminal screen and is the default window used by
-       routines that do not take a parameter  identifying  one.   Many  curses
-       functions use this window.
-

                                        COLORS

                                        -       Once  curses  is  initialized,  COLORS  contains  the  number of colors
-       supported by the terminal; see curs_color(3x).
+       Once  a  curses  screen  is  initialized, COLORS contains the number of
+       colors supported by the terminal; see curs_color(3x).

                                        COLOR_PAIRS

                                        -       Once curses is initialized, COLOR_PAIRS contains the  number  of  color
-       pairs supported by the terminal; see curs_color(3x).
+       Once a curses screen is initialized, COLOR_PAIRS contains the number of
+       color pairs supported by the terminal; see curs_color(3x).

                                        COLS, LINES

                                        -       Once  curses  is initialized, COLS and LINES contain the screen's width
-       and height in character cells, respectively; that  is,  the  number  of
+       Once a curses screen is initialized, COLS and LINES contain  its  width
+       and  height  in  character  cells, respectively; that is, the number of
        columns and lines.

                                        ESCDELAY

                                        -       For  curses  to  distinguish  the ESC character resulting from a user's
-       press of the "Escape" key on the input device  from  one  beginning  an
-       escape sequence (as commonly produced by function keys), it waits after
-       the escape character to see if further characters are available on  the
+       When  reading  key  strokes  from  a  window  in  keypad  mode,  curses
+       distinguishes  the  ESC  character resulting from a user's press of the
+       "Escape" key on the input device from one beginning an escape  sequence
+       (commonly  produced  by  function keys), by waiting after receiving the
+       escape character to see if further  characters  are  available  on  the
        input stream within a short interval.  ESCDELAY stores this interval in
        milliseconds.
 
-       If keypad(3x) is disabled for the  curses  window  receiving  input,  a
+       If  keypad(3x)  is  disabled  for  the curses window receiving input, a
        program must disambiguate escape sequences itself.
 
 
@@ -198,15 +209,24 @@

                                        NOTES

                                        -       Either initscr(3x) or newterm(3x) initializes curses.
+       Initialize a curses screen with either initscr(3x) or newterm(3x).
 
        If  ncurses  is  configured  to  provide  separate  curses  and   tinfo
-       libraries, most of these variables reside in the former.
+       libraries,  most  of  these symbols reside in the former.  Both use the
+       bool data type.
+
+
+

                                        EXTENSIONS

                                        +       The CCHARW_MAX constant, and ESCDELAY, TABSIZE, and  newscr  variables,
+       are extensions, the first of these originating in ncurses.

                                        PORTABILITY

                                        +       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
+
        The  X/Open  Curses  standard  documents all of the foregoing types and
-       symbols except for newscr, TABSIZE, and ESCDELAY.
+       symbols except for CCHARW_MAX, newscr, TABSIZE, and ESCDELAY.
 
        X/Open Curses describes curscr only as "an  internal  data  structure";
        SVr4   gave  more  details,  noting  its  use  "for  certain  low-level
@@ -214,59 +234,58 @@
        Neither specified its interaction with the rest of the interface beyond
        use as an argument to clearok(3x) and wrefresh(3x).
 
-       newscr is a feature of SVr4 curses.  When refreshing the screen, it  is
-       used  as  a  working area for combining the standard window stdscr with
-       any others the application may have created with newwin(3x).  When  the
+       newscr  is a feature of SVr4 curses.  When refreshing the screen, it is
+       used as a working area for combining the standard  window  stdscr  with
+       any  others the application may have created with newwin(3x).  When the
        update of newscr is complete, curses modifies curscr to match newscr.
 
        TABSIZE is a feature of SVr4 curses.
 
-       o   SVr4   initially  sets  TABSIZE  from  the  terminal  description's
-           init_tabs  capability.   After  that,  it   can   be   altered   by
+       o   SVr4  initially  sets  TABSIZE  from  the  terminal   description's
+           init_tabs  (it)  capability.   After  that,  it  can  be altered by
            applications using SVr4 curses.
 
-       o   SVr4  curses  uses  the value of TABSIZE to compute the position of
-           tab stops when updating both the virtual screen with addch(3x)  and
-           the physical screen with mvcur(3x).
+       o   SVr4 curses uses TABSIZE's value to compute  the  position  of  tab
+           stops  when updating both the virtual screen with addch(3x) and the
+           physical screen with mvcur(3x).
 
-       o   ncurses  uses  the  value  of  TABSIZE  only  to update the virtual
-           screen.   It  uses  the  terminal  description's  "it"  (init_tabs)
-           capability  for  computing hardware tabs (that is, tab stops on the
+       o   In ncurses, TABSIZE's value affects only the virtual  screen.   The
+           library   uses  the  terminal  type  description's  init_tabs  (it)
+           capability to compute hardware tabs (that  is,  tab  stops  on  the
            physical screen).
 
-       o   Other implementations differ.  For instance, NetBSD  curses  allows
-           TABSIZE  to  be  set through an environment variable.  ncurses does
+       o   Other  implementations  differ.  For instance, NetBSD curses allows
+           TABSIZE to be set through an environment  variable.   ncurses  does
            not.
 
            NetBSD curses does not support hardware tabs; it uses the init_tabs
-           capability  and  the TABSIZE variable only for updating the virtual
+           (it) capability and the TABSIZE variable only to update the virtual
            screen.
 
        ESCDELAY is a feature of AIX curses.
 
-       o   In AIX, the units for ESCDELAY are fifths of milliseconds.
+       o   AIX treats ESCDELAY's value as counting fifths of milliseconds.
 
-       o   The default value for AIX's ESCDELAY equals 0.1 seconds.
+       o   AIX's default ESCDELAY equals 0.1 seconds.
 
-       o   AIX also enforces a limit of 10,000 seconds for  ESCDELAY;  ncurses
-           does not enforce any upper limit.
+       o   AIX  also  enforces a limit of 10,000 seconds for ESCDELAY; ncurses
+           does not enforce an upper limit.
 
-       ncurses  has  long  used ESCDELAY with units of milliseconds, making it
-       impossible to be completely compatible with  AIX.   Consequently,  most
-       users  have  decided  either to override the value, or to rely upon its
-       default.
+       ncurses has long interpreted  ESCDELAY  as  a  count  of  milliseconds,
+       making   it   impossible   to   be   completely  compatible  with  AIX.
+       Consequently, most users have decided either to override the value,  or
+       to rely upon its default.

                                        SEE ALSO

                                        -       curses(3x),   curs_color(3x),    curs_opaque(3x),    curs_terminfo(3x),
+       [UAX #29] "Unicode Standard Annex #29: Unicode Text Segmentation"
+
+       getcchar(3x) further discusses the ncurses extension CCHARW_MAX.
+
+       curses(3x),    curs_color(3x),    curs_opaque(3x),   curs_terminfo(3x),
        curs_threads(3x), term_variables(3x), terminfo(5)
 
-       [UAX  #29]  "Unicode  Standard  Annex  #29: Unicode Text Segmentation";
-       <https://unicode.org/reports/tr29/>
-
-
-
-ncurses 6.5                       2024-04-13                curs_variables(3x)
+ncurses 6.6                       2025-08-23                curs_variables(3x)
                                        -
                                      • PREDEFINED TYPES +
                                      • DATA TYPES
                                        • bool
                                        • chtype
                                          • @@ -290,7 +310,7 @@ ncurses 6.5 2024-04-13 VARIABLES diff --git a/doc/html/man/curs_window.3x.html b/doc/html/man/curs_window.3x.html index ea99659..3f5274e 100644 --- a/doc/html/man/curs_window.3x.html +++ b/doc/html/man/curs_window.3x.html @@ -1,6 +1,6 @@ -curs_window 3x 2024-04-20 ncurses 6.5 Library calls +curs_window 3x 2025-08-23 ncurses 6.6 Library calls -

                                          curs_window 3x 2024-04-20 ncurses 6.5 Library calls

                                          +

                                          curs_window 3x 2025-08-23 ncurses 6.6 Library calls

                                           curs_window(3x)                  Library calls                 curs_window(3x)
 
 
-
-

                                          NAME

                                                  newwin,  delwin,  mvwin,  subwin,  derwin,  mvderwin,  dupwin, wsyncup,
        syncok, wcursyncup, wsyncdown - create and manipulate curses windows
@@ -54,23 +52,23 @@

                                          SYNOPSIS

                                                  #include <curses.h>
 
-       WINDOW *newwin(
-             int nlines, int ncols,
-             int begin_y, int begin_x);
-       int delwin(WINDOW *win);
-       int mvwin(WINDOW *win, int y, int x);
-       WINDOW *subwin(WINDOW *orig,
-             int nlines, int ncols,
-             int begin_y, int begin_x);
-       WINDOW *derwin(WINDOW *orig,
-             int nlines, int ncols,
-             int begin_y, int begin_x);
-       int mvderwin(WINDOW *win, int par_y, int par_x);
-       WINDOW *dupwin(WINDOW *win);
-       void wsyncup(WINDOW *win);
-       int syncok(WINDOW *win, bool bf);
-       void wcursyncup(WINDOW *win);
-       void wsyncdown(WINDOW *win);
+       WINDOW * newwin(
+            int nlines, int ncols,
+            int begin_y, int begin_x);
+       int delwin(WINDOW * win);
+       int mvwin(WINDOW * win, int y, int x);
+       WINDOW * subwin(WINDOW * orig,
+            int nlines, int ncols,
+            int begin_y, int begin_x);
+       WINDOW * derwin(WINDOW * orig,
+            int nlines, int ncols,
+            int begin_y, int begin_x);
+       int mvderwin(WINDOW * win, int par_y, int par_x);
+       WINDOW * dupwin(WINDOW * win);
+       void wsyncup(WINDOW * win);
+       int syncok(WINDOW * win, bool bf);
+       void wcursyncup(WINDOW * win);
+       void wsyncdown(WINDOW * win);

                                          DESCRIPTION

                                          @@ -90,16 +88,16 @@
 
        Regardless of the function  used  for  creating  a  new  window  (e.g.,
        newwin, subwin, derwin, newpad), rather than a duplicate (with dupwin),
-       all of the window modes are initialized to the default  values.   These
-       functions set window modes after a window is created:
+       all  of  the  window  modes are initialized to the default values.  The
+       following functions set a window's modes after it is created:
 
-              idcok  idlok  immedok  keypad leaveok nodelay scrollok setscrreg
-              syncok wbkgdset wbkgrndset and wtimeout.
+              idcok, idlok,  immedok,  keypad,  leaveok,  nodelay,  notimeout,
+              scrollok, setscrreg, syncok, wbkgdset, wbkgrndset, and wtimeout.

                                          delwin

                                          -       Calling delwin deletes the named window, freeing all memory  associated
-       with  it  (it  does  not  actually  erase  the  window's screen image).
+       Calling  delwin deletes the named window, freeing all memory associated
+       with it (it  does  not  actually  erase  the  window's  screen  image).
        Subwindows must be deleted before the main window can be deleted.
 
 
@@ -114,22 +112,22 @@
        Calling  subwin  creates and returns a pointer to a new window with the
        given number of lines, nlines, and columns, ncols.  The  window  is  at
        position (begin_y, begin_x) on the screen.  The subwindow shares memory
-       with the window orig, its ancestor, so that changes made to one  window
-       will  affect both windows.  When using this routine, it is necessary to
-       call touchwin or touchline on  orig  before  calling  wrefresh  on  the
+       with  the window orig, its ancestor, so that changes made to one window
+       will affect both windows.  When using this routine, it is necessary  to
+       call  touchwin  or  touchline  on  orig  before calling wrefresh on the
        subwindow.

                                          derwin

                                          -       Calling  derwin  is the same as calling subwin, except that begin_y and
-       begin_x are relative to the origin of the window orig rather  than  the
-       screen.   There is no difference between the subwindows and the derived
+       Calling derwin is the same as calling subwin, except that  begin_y  and
+       begin_x  are  relative to the origin of the window orig rather than the
+       screen.  There is no difference between the subwindows and the  derived
        windows.

                                          mvderwin

                                          -       Calling mvderwin moves a  derived  window  (or  subwindow)  inside  its
-       parent  window.   The  screen-relative parameters of the window are not
+       Calling  mvderwin  moves  a  derived  window  (or subwindow) inside its
+       parent window.  The screen-relative parameters of the  window  are  not
        changed.  This routine is used to display different parts of the parent
        window at the same physical position on the screen.
 
@@ -158,95 +156,81 @@

                                          RETURN VALUE

                                          -       Routines that return an integer return the integer ERR upon failure and
-       OK  (SVr4  only  specifies  "an  integer  value  other  than ERR") upon
-       successful completion.
+       Functions that return integers return ERR  upon  failure  and  OK  upon
+       success.
 
-       Routines that return pointers return NULL on error.
+       Functions that return pointers return a null pointer on failure.
 
-       X/Open defines no error conditions.  In this implementation
+       ncurses defines several error conditions.
 
-       delwin
-            returns an error if the window pointer is null, or if  the  window
-            is the parent of another window.
+       o   delwin returns ERR if win is a null pointer, or if it is the parent
+           of another window.
 
-       derwin
-            returns  an  error if the parent window pointer is null, or if any
-            of its ordinates or dimensions is negative, or  if  the  resulting
-            window does not fit inside the parent window.
+           ncurses  maintains  a  list of windows, and checks that the pointer
+           passed to delwin is one that it created, returning ERR  if  it  was
+           not.
 
-       dupwin
-            returns an error if the window pointer is null.
+       o   derwin  returns  ERR  if  orig  is a null pointer, or if any of the
+           ordinate or dimension arguments is negative, or  if  the  resulting
+           window does not fit inside the parent window.
 
-            This  implementation  also maintains a list of windows, and checks
-            that the  pointer  passed  to  delwin  is  one  that  it  created,
-            returning an error if it was not..
+       o   dupwin returns ERR if win is a null pointer.
 
-       mvderwin
-            returns an error if the window pointer is null, or if some part of
-            the window would be placed off-screen.
+       o   mvderwin  returns  ERR  if win is a null pointer, or if any part of
+           the window would be placed off-screen.
 
-       mvwin
-            returns an error if the window pointer is null, or if  the  window
-            is  really  a  pad,  or if some part of the window would be placed
-            off-screen.
+       o   mvwin returns ERR if win is a null pointer, if win is a pad, or  if
+           any part of the window would be placed off-screen.
 
-       newwin
-            will fail if either of its beginning ordinates is negative, or  if
-            either the number of lines or columns is negative.
+       o   newwin returns ERR if any of its arguments is negative.
 
-       syncok
-            returns an error if the window pointer is null.
+       o   subwin  returns  ERR  if  orig  is a null pointer, or if any of the
+           ordinate or dimension arguments is negative, or  if  the  resulting
+           window does not fit inside the parent window.
 
-       subwin
-            returns  an  error if the parent window pointer is null, or if any
-            of its ordinates or dimensions is negative, or  if  the  resulting
-            window does not fit inside the parent window.
+       o   syncok returns ERR if win is a null pointer.
 
-       The  functions  which return a window pointer may also fail if there is
-       insufficient memory for its data structures.  Any  of  these  functions
-       will fail if the screen has not been initialized, i.e., with initscr or
-       newterm.
+       Functions  that  return  a window pointer fail if memory allocation for
+       their data structures fails.
+
+       All of these functions fail if the screen has not been initialized; see
+       initscr(3x) or newterm(3x).

                                          NOTES

                                          -       If many small changes are made to the window, the wsyncup option  could
-       degrade performance.
+       syncok may be implemented as a macro.
 
-       Note that syncok may be a macro.
+       Calling syncup on a window and making many small changes  to  it  could
+       degrade performance.

                                          PORTABILITY

                                          -       X/Open Curses, Issue 4 describes these functions.
+       X/Open Curses Issue 4 describes these functions.  It specifies no error
+       conditions for delwin, derwin, dupwin, newwin, mvderwin, or syncok.
 
-       X/Open Curses states regarding delwin:
+       For  functions  returning  integers  (except  delwin), SVr4 describes a
+       successful return value only as "an integer value other than ERR".
 
-       o   It must delete subwindows before deleting their parent.
+       Regarding delwin, X/Open Curses states that
 
-       o   If  delwin  is asked to delete a parent window, it can only succeed
-           if the curses library keeps a list of the subwindows.  SVr4  curses
-           kept  a  count  of the number of subwindows rather than a list.  It
-           simply returned ERR when asked  to  delete  a  subwindow.   Solaris
-           X/Open  curses  does  not  even  make that check, and will delete a
-           parent window which still has subwindows.
+              [t]he application must delete  subwindows  before  deleting  the
+              main window.
 
-       o   Since release 4.0 (1996), ncurses maintains a list of  windows  for
-           each  screen,  to  ensure  that  a  window has no subwindows before
-           allowing deletion.
+       If  delwin  is  asked to delete a parent window, it can succeed only if
+       the curses library keeps a list of its subwindows.  SVr4 curses kept  a
+       count  of  the  number  of  subwindows  rather  than a list.  It simply
+       returned ERR when asked to delete a subwindow.  Solaris  X/Open  curses
+       (xcurses)  does  not  make  even  that  check, and will delete a parent
+       window that still has subwindows.  PDCurses also behaves this way.
 
-       o   NetBSD copied this feature of ncurses in 2003.
-           PDCurses follows the scheme used in Solaris X/Open curses.
+       ncurses 4.0 (1996) and later maintains  a  list  of  windows  for  each
+       screen  to  ensure  that a window has no subwindows before allowing its
+       deletion.  NetBSD curses has followed suit since 2003.
 
-
-

                                          BUGS

                                          -       The subwindow functions subwin, derwin, mvderwin,  wsyncup,  wsyncdown,
-       wcursyncup,  and  syncok  are  flaky, incompletely implemented, and not
-       well tested.
-
-       System V's curses documentation  is  unclear  about  what  wsyncup  and
-       wsyncdown  actually  do.   It  seems to imply that they are supposed to
-       touch only those lines that are  affected  by  changes  to  a  window's
-       ancestors.  The language here, and behavior of ncurses, is patterned on
+       SVr4 curses documentation is unclear about what wsyncup  and  wsyncdown
+       actually  do.   It  seems to imply that they are supposed to touch only
+       those lines that are affected by changes to a window's ancestors.   The
+       description  and behavior of these functions in ncurses is patterned on
        the X/Open Curses standard; this approach may result in slower updates.
 
 
@@ -254,9 +238,7 @@
        curses(3x),   curs_initscr(3x),    curs_refresh(3x),    curs_touch(3x),
        curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   curs_window(3x)
+ncurses 6.6                       2025-08-23                   curs_window(3x)
                                          diff --git a/doc/html/man/default_colors.3x.html b/doc/html/man/default_colors.3x.html index 14a0f8e..9cae26e 100644 --- a/doc/html/man/default_colors.3x.html +++ b/doc/html/man/default_colors.3x.html @@ -35,18 +35,16 @@ -default_colors 3x 2024-04-13 ncurses 6.5 Library calls +default_colors 3x 2024-04-13 ncurses 6.6 Library calls -

                                          default_colors 3x 2024-04-13 ncurses 6.5 Library calls

                                          +

                                          default_colors 3x 2024-04-13 ncurses 6.6 Library calls

                                           default_colors(3x)               Library calls              default_colors(3x)
 
 
-
-

                                          NAME

                                                  use_default_colors,  assume_default_colors  -  use  terminal's  default
        colors in curses
@@ -70,9 +68,9 @@
        not  take  advantage  of  SGR  39  and  SGR  49.  Some applications are
        designed to work with the default background,  using  colors  only  for
        text.  For example, there are several implementations of the ls program
-       which use colors to denote different file types or permissions.   These
-       "color  ls"  programs  do  not necessarily modify the background color,
-       typically  using  only  the  setaf  terminfo  capability  to  set   the
+       which  use colors to denote different file types or permissions.  These
+       "color ls" programs do not necessarily  modify  the  background  color,
+       typically   using  only  the  setaf  terminfo  capability  to  set  the
        foreground color.  Full-screen applications that use default colors can
        achieve similar visual effects.
 
@@ -103,7 +101,7 @@

                                          RETURN VALUE

                                          -       These  functions return the integer ERR upon failure and OK on success.
+       These functions return the integer ERR upon failure and OK on  success.
        They will fail if either the terminal does not support the orig_pair or
        orig_colors  capability.   If  the  initialize_pair  capability  is not
        found, this causes an error as well.
@@ -113,8 +111,8 @@
        Associated with this extension, the init_pair function accepts negative
        arguments to specify default foreground or background colors.
 
-       The  use_default_colors  function  was added to support ded.  This is a
-       full-screen application which uses curses to manage only  part  of  the
+       The use_default_colors function was added to support ded.   This  is  a
+       full-screen  application  which  uses curses to manage only part of the
        screen.  The bottom portion of the screen, which is of adjustable size,
        is left uncolored to display the results from shell commands.  The  top
        portion  of  the screen colors filenames using a scheme like the "color
@@ -129,12 +127,12 @@
 
        The  assume_default_colors  function  was  added  to  solve a different
        problem: support for applications which would use environment variables
-       and  other  configuration  to  bypass  curses' notion of the terminal's
+       and other configuration to bypass  curses'  notion  of  the  terminal's
        default colors, setting specific values.

                                          PORTABILITY

                                          -       These routines are specific to ncurses.  They  were  not  supported  on
+       These  routines  are  specific  to ncurses.  They were not supported on
        Version 7, BSD or System V implementations.  It is recommended that any
        code depending on them be conditioned using NCURSES_VERSION.
 
@@ -147,9 +145,7 @@

                                          SEE ALSO

                                                  ded(1), curs_color(3x)
 
-
-
-ncurses 6.5                       2024-04-13                default_colors(3x)
+ncurses 6.6                       2024-04-13                default_colors(3x)
                                            diff --git a/doc/html/man/define_key.3x.html b/doc/html/man/define_key.3x.html index d135e31..7152733 100644 --- a/doc/html/man/define_key.3x.html +++ b/doc/html/man/define_key.3x.html @@ -28,57 +28,65 @@ * authorization. * **************************************************************************** * Author: Thomas E. Dickey 1997 - * @Id: define_key.3x,v 1.42 2024/03/16 15:35:01 tom Exp @ + * @Id: define_key.3x,v 1.52 2024/12/28 21:26:21 tom Exp @ --> -define_key 3x 2024-03-16 ncurses 6.5 Library calls +define_key 3x 2024-12-28 ncurses 6.6 Library calls -

                                            define_key 3x 2024-03-16 ncurses 6.5 Library calls

                                            +

                                            define_key 3x 2024-12-28 ncurses 6.6 Library calls

                                             define_key(3x)                   Library calls                  define_key(3x)
 
 
-
-

                                            NAME

                                            -       define_key - define a curses keycode
+       define_key - define a curses function key code

                                            SYNOPSIS

                                                    #include <curses.h>
 
-       int define_key(const char *definition, int keycode);
+       int define_key(const char * definition, int key-code);

                                            DESCRIPTION

                                            -       This  is an extension to the curses library.  It permits an application
-       to define keycodes with their corresponding control  strings,  so  that
-       the ncurses library will interpret them just as it would the predefined
-       codes in the terminfo database.
+       The define_key ncurses extension permits a curses application to bind a
+       string  definition  to the function key key-code returned by wgetch(3x)
+       (wide-character API users: wget_wch(3x)) when keypad(3x) is enabled  in
+       a  window  and  a  function  key is pressed.  ncurses interprets such a
+       binding as it does  those  in  the  terminfo  database  entry  for  the
+       terminal type.
 
-       If definition is NULL, any existing one for  the  keycode  is  removed.
-       Similarly,  if  the  given  keycode  is  negative or zero, any existing
-       string for the given definition is removed.
+       A  definition  of  NULL  removes  any  existing  binding from key-code.
+       Similarly, a non-positive key-code  removes  an  existing  binding  for
+       definition, if any.

                                            RETURN VALUE

                                            -       Either keycode must be greater than zero, or definition  must  be  non-
-       NULL,  otherwise ERR is returned.  ERR may also be returned if there is
-       insufficient memory to allocate the data to store the  definition.   If
-       no error is detected, OK is returned.
+       define_key returns ERR if
+
+       o   definition is NULL and key-code is nonpositive, or
+
+       o   insufficient memory is available to bind definition to key-code.
+
+       Otherwise, define_key returns OK.
+
+
+

                                            EXTENSIONS

                                            +       define_key is an ncurses extension.

                                            PORTABILITY

                                            -       These  routines  are  specific  to ncurses.  They were not supported on
-       Version 7, BSD or System V implementations.  It is recommended that any
-       code depending on them be conditioned using NCURSES_VERSION.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
+
+       NetBSD curses since 2.0 (2004) supports define_key.

                                            AUTHORS

                                            @@ -86,11 +94,9 @@

                                            SEE ALSO

                                            -       keyok(3x), key_defined(3x)
+       curses(3x), keybound(3x), keyok(3x), key_defined(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-03-16                    define_key(3x)
+ncurses 6.6                       2024-12-28                    define_key(3x)
                                              @@ -98,6 +104,7 @@ ncurses 6.5 2024-03-16 SYNOPSIS
                                            • DESCRIPTION
                                            • RETURN VALUE
                                              • +
                                            • EXTENSIONS
                                            • PORTABILITY
                                            • AUTHORS
                                            • SEE ALSO
                                              • diff --git a/doc/html/man/form.3x.html b/doc/html/man/form.3x.html index fcdb7af..3f021e0 100644 --- a/doc/html/man/form.3x.html +++ b/doc/html/man/form.3x.html @@ -1,7 +1,7 @@ -form 3x 2024-03-16 ncurses 6.5 Library calls +form 3x 2025-11-11 ncurses 6.6 Library calls -

                                              form 3x 2024-03-16 ncurses 6.5 Library calls

                                              +

                                              form 3x 2025-11-11 ncurses 6.6 Library calls

                                               form(3x)                         Library calls                        form(3x)
 
 
-
-

                                              NAME

                                              -       form - curses extension for programming forms
+       form - present user-fillable forms in curses windows

                                              SYNOPSIS

                                              @@ -57,7 +55,7 @@

                                              DESCRIPTION

                                                      The form library provides terminal-independent facilities for composing
-       form screens on character-cell terminals.  The library includes:  field
+       form  screens on character-cell terminals.  The library includes: field
        routines, which create and modify form fields; and form routines, which
        group fields into forms,  display  forms  on  the  screen,  and  handle
        interaction with the user.
@@ -78,7 +76,7 @@

                                              Current Default Values for Field Attributes

                                                      The  form  library maintains a default value for field attributes.  You
        can get or  set  this  default  by  calling  the  appropriate  set_  or
-       retrieval  routine  with  a  NULL field pointer.  Changing this default
+       retrieval  routine  with  a  NULL field pointer.  Changing this default
        with a set_ function affects  future  field  creations,  but  does  not
        change the rendering of fields already created.
 
@@ -112,7 +110,6 @@
        field_term              form_hook(3x)
        field_type              form_field_validation(3x)
        field_userptr           form_field_userptr(3x)
-
        form_driver             form_driver(3x)
        form_driver_w           form_driver(3x)*
        form_fields             form_field(3x)
@@ -169,7 +166,7 @@

                                              RETURN VALUE

                                              -       Routines  that  return  pointers return NULL on error, and set errno to
+       Routines  that  return  pointers return NULL on error, and set errno to
        the  corresponding  error-code  returned  by  functions  returning   an
        integer.   Routines  that return an integer return one of the following
        error codes:
@@ -243,9 +240,7 @@
        curses(3x)  and  related  pages  whose names begin "form_" for detailed
        descriptions of the entry points.
 
-
-
-ncurses 6.5                       2024-03-16                          form(3x)
+ncurses 6.6                       2025-11-11                          form(3x)
                                                diff --git a/doc/html/man/form_cursor.3x.html b/doc/html/man/form_cursor.3x.html index 5844dd5..545e4af 100644 --- a/doc/html/man/form_cursor.3x.html +++ b/doc/html/man/form_cursor.3x.html @@ -35,18 +35,16 @@ -form_cursor 3x 2024-03-16 ncurses 6.5 Library calls +form_cursor 3x 2024-03-16 ncurses 6.6 Library calls -

                                                form_cursor 3x 2024-03-16 ncurses 6.5 Library calls

                                                +

                                                form_cursor 3x 2024-03-16 ncurses 6.6 Library calls

                                                 form_cursor(3x)                  Library calls                 form_cursor(3x)
 
 
-
-

                                                NAME

                                                        pos_form_cursor - position a form window cursor
 
@@ -60,7 +58,7 @@

                                                DESCRIPTION

                                                        The  function  pos_form_cursor  restores  the  cursor  to  the position
        required for the forms driver to continue processing requests.  This is
-       useful  after curses routines have been called to do screen-painting in
+       useful after curses routines have been called to do screen-painting  in
        response to a form operation.
 
 
@@ -80,7 +78,7 @@

                                                PORTABILITY

                                                -       These routines emulate the System  V  forms  library.   They  were  not
+       These  routines  emulate  the  System  V  forms library.  They were not
        supported on Version 7 or BSD versions.
 
 
@@ -92,9 +90,7 @@

                                                SEE ALSO

                                                        curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                   form_cursor(3x)
+ncurses 6.6                       2024-03-16                   form_cursor(3x)
                                                  diff --git a/doc/html/man/form_data.3x.html b/doc/html/man/form_data.3x.html index 2f1dc3b..0294d48 100644 --- a/doc/html/man/form_data.3x.html +++ b/doc/html/man/form_data.3x.html @@ -35,18 +35,16 @@ -form_data 3x 2024-03-16 ncurses 6.5 Library calls +form_data 3x 2024-03-16 ncurses 6.6 Library calls -

                                                  form_data 3x 2024-03-16 ncurses 6.5 Library calls

                                                  +

                                                  form_data 3x 2024-03-16 ncurses 6.6 Library calls

                                                   form_data(3x)                    Library calls                   form_data(3x)
 
 
-
-

                                                  NAME

                                                          data_ahead, data_behind - test for off-screen data in given forms
 
@@ -62,12 +60,12 @@
        The function data_ahead tests whether there is off-screen data ahead in
        the given form.  It returns TRUE (1) or FALSE (0).
 
-       The function data_behind tests whether there is off-screen data  behind
+       The  function data_behind tests whether there is off-screen data behind
        in the given form.  It returns TRUE (1) or FALSE (0).

                                                  PORTABILITY

                                                  -       These  routines  emulate  the  System  V  forms library.  They were not
+       These routines emulate the System  V  forms  library.   They  were  not
        supported on Version 7 or BSD versions.
 
 
@@ -79,9 +77,7 @@

                                                  SEE ALSO

                                                          curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     form_data(3x)
+ncurses 6.6                       2024-03-16                     form_data(3x)
                                                    diff --git a/doc/html/man/form_driver.3x.html b/doc/html/man/form_driver.3x.html index 859c291..7a082f6 100644 --- a/doc/html/man/form_driver.3x.html +++ b/doc/html/man/form_driver.3x.html @@ -1,7 +1,7 @@ -form_driver 3x 2024-04-20 ncurses 6.5 Library calls +form_driver 3x 2025-10-04 ncurses 6.6 Library calls -

                                                    form_driver 3x 2024-04-20 ncurses 6.5 Library calls

                                                    +

                                                    form_driver 3x 2025-10-04 ncurses 6.6 Library calls

                                                     form_driver(3x)                  Library calls                 form_driver(3x)
 
 
-
-

                                                    NAME

                                                            form_driver, form_driver_w - command-processing loop of the form system
 
@@ -64,21 +62,21 @@
        Once a form has been posted (displayed), you should funnel input events
        to it through form_driver.  This routine has three major input cases:
 
-       o   The input is a form navigation request.  Navigation  request  codes
-           are constants defined in <form.h>, which are distinct from the key-
+       o   The  input  is a form navigation request.  Navigation request codes
+           are constants defined in form.h, which are distinct from  the  key-
            and character codes returned by wgetch(3x).
 
-       o   The input is a printable character.   Printable  characters  (which
-           must  be  positive,  less  than  256)  are checked according to the
+       o   The  input  is  a printable character.  Printable characters (which
+           must be positive, less than  256)  are  checked  according  to  the
            program's locale settings.
 
-       o   The input is the KEY_MOUSE special key  associated  with  an  mouse
+       o   The  input  is  the  KEY_MOUSE special key associated with an mouse
            event.

                                                    form_driver_w

                                                    -       This  extension  simplifies  the  use  of  the forms library using wide
-       characters.  The input is either a key  code  (a  request)  or  a  wide
+       This extension simplifies the use  of  the  forms  library  using  wide
+       characters.   The  input  is  either  a  key code (a request) or a wide
        character returned by get_wch(3x).  The type must be passed as well, to
        enable the library  to  determine  whether  the  parameter  is  a  wide
        character or a request.
@@ -113,7 +111,6 @@
        REQ_LEFT_FIELD     Move left to a field.
        REQ_NEW_LINE       Insert or overlay a new line.
        REQ_NEXT_CHAR      Move to the next char.
-
        REQ_NEXT_CHOICE    Display next field choice.
        REQ_NEXT_FIELD     Move to the next field.
        REQ_NEXT_LINE      Move to the next line.
@@ -207,22 +204,22 @@
 
           o   the form cursor is positioned to that field.
 
-          o   If  you  double-click  a field, the form cursor is positioned to
+          o   If you double-click a field, the form cursor  is  positioned  to
               that field and E_UNKNOWN_COMMAND is returned.  This return value
               makes sense, because a double click usually means that an field-
-              specific action should be returned.  It is exactly  the  purpose
-              of  this  return  value  to  signal that an application specific
+              specific  action  should be returned.  It is exactly the purpose
+              of this return value to  signal  that  an  application  specific
               command should be executed.
 
-          o   If a translation into a request was  done,  form_driver  returns
+          o   If  a  translation  into a request was done, form_driver returns
               the result of this request.
 
-       If  you clicked outside the user window or the mouse event could not be
+       If you clicked outside the user window or the mouse event could not  be
        translated into a form request an E_REQUEST_DENIED is returned.

                                                    Application-defined Commands

                                                    -       If the second argument is neither printable nor one of the  above  pre-
+       If  the  second argument is neither printable nor one of the above pre-
        defined form requests, the driver assumes it is an application-specific
        command and returns  E_UNKNOWN_COMMAND.   Application-defined  commands
        should  be  defined relative to MAX_COMMAND, the maximum value of these
@@ -270,12 +267,10 @@

                                                    SEE ALSO

                                                    -       curses(3x),   form(3x),   form_fieldtype(3x),    form_field_buffer(3x),
+       curses(3x),    form(3x),   form_fieldtype(3x),   form_field_buffer(3x),
        form_field_validation(3x), form_variables(3x), getch(3x)
 
-
-
-ncurses 6.5                       2024-04-20                   form_driver(3x)
+ncurses 6.6                       2025-10-04                   form_driver(3x)
                                                      diff --git a/doc/html/man/form_field.3x.html b/doc/html/man/form_field.3x.html index 8eb58d4..614fc7e 100644 --- a/doc/html/man/form_field.3x.html +++ b/doc/html/man/form_field.3x.html @@ -28,25 +28,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_field.3x,v 1.34 2024/03/16 15:35:01 tom Exp @ + * @Id: form_field.3x,v 1.36 2024/12/28 21:26:21 tom Exp @ --> -form_field 3x 2024-03-16 ncurses 6.5 Library calls +form_field 3x 2024-12-28 ncurses 6.6 Library calls -

                                                      form_field 3x 2024-03-16 ncurses 6.5 Library calls

                                                      +

                                                      form_field 3x 2024-12-28 ncurses 6.6 Library calls

                                                       form_field(3x)                   Library calls                  form_field(3x)
 
 
-
-

                                                      NAME

                                                              form_field - make and break connections between fields and forms
 
@@ -62,7 +60,7 @@

                                                      DESCRIPTION

                                                              The  function  set_form_fields  changes  the field pointer array of the
-       given form.  The array must be terminated by a NULL.
+       given form.  The array must be terminated by a NULL.
 
        The function form_fields returns the field array of the given form.
 
@@ -73,10 +71,10 @@

                                                      RETURN VALUE

                                                      -       The  function  form_fields  returns  a pointer (which may be NULL).  It
+       The  function  form_fields  returns  a pointer (which may be NULL).  It
        does not set errno.
 
-       The function field_count returns ERR if the form parameter is NULL.
+       The function field_count returns ERR if the form parameter is NULL.
 
        The  functions  set_form_fields  and  move_field  return  one  of   the
        following codes on error:
@@ -112,9 +110,7 @@

                                                      SEE ALSO

                                                              curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                    form_field(3x)
+ncurses 6.6                       2024-12-28                    form_field(3x)
                                                        diff --git a/doc/html/man/form_field_attributes.3x.html b/doc/html/man/form_field_attributes.3x.html index 22afdc6..1280f7f 100644 --- a/doc/html/man/form_field_attributes.3x.html +++ b/doc/html/man/form_field_attributes.3x.html @@ -35,18 +35,16 @@ -form_field_attributes 3x 2024-03-16 ncurses 6.5 Library calls +form_field_attributes 3x 2024-03-16 ncurses 6.6 Library calls -

                                                        form_field_attributes 3x 2024-03-16 ncurses 6.5 Library calls

                                                        +

                                                        form_field_attributes 3x 2024-03-16 ncurses 6.6 Library calls

                                                         form_field_attributes(3x)        Library calls       form_field_attributes(3x)
 
 
-
-

                                                        NAME

                                                                form_field_attributes - color and attribute control for form fields
 
@@ -67,7 +65,7 @@

                                                        DESCRIPTION

                                                                The  function  set_field_fore  sets  the foreground attribute of field.
        This is the highlight used to display the field contents.  The function
-       field_fore   returns   the   foreground   attribute.   The  default  is
+       field_fore  returns  the  foreground   attribute.    The   default   is
        A_STANDOUT.
 
        The function set_field_back sets the background attribute of form. This
@@ -103,12 +101,10 @@

                                                        SEE ALSO

                                                        -       curses(3x)  and  related  pages  whose names begin "form_" for detailed
+       curses(3x) and related pages whose names  begin  "form_"  for  detailed
        descriptions of the entry points.
 
-
-
-ncurses 6.5                       2024-03-16         form_field_attributes(3x)
+ncurses 6.6                       2024-03-16         form_field_attributes(3x)
                                                          diff --git a/doc/html/man/form_field_buffer.3x.html b/doc/html/man/form_field_buffer.3x.html index 47d6c8b..0ef5234 100644 --- a/doc/html/man/form_field_buffer.3x.html +++ b/doc/html/man/form_field_buffer.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_field_buffer.3x,v 1.45 2024/03/16 15:35:01 tom Exp @ + * @Id: form_field_buffer.3x,v 1.47 2024/12/28 21:26:21 tom Exp @ --> -form_field_buffer 3x 2024-03-16 ncurses 6.5 Library calls +form_field_buffer 3x 2024-12-28 ncurses 6.6 Library calls -

                                                          form_field_buffer 3x 2024-03-16 ncurses 6.5 Library calls

                                                          +

                                                          form_field_buffer 3x 2024-12-28 ncurses 6.6 Library calls

                                                           form_field_buffer(3x)            Library calls           form_field_buffer(3x)
 
 
-
-

                                                          NAME

                                                                  form_field_buffer - field buffer control
 
@@ -87,12 +85,12 @@
 
           o   Editing  operations  are  based on the window which displays the
               field, rather than a string.  The window contains only printable
-              characters,  and  is  filled  with  blanks.  If you want the raw
-              data, you must write your own routine that copies the value  out
+              characters, and is filled with blanks.   If  you  want  the  raw
+              data,  you must write your own routine that copies the value out
               of the buffer and removes the leading and trailing spaces.
 
-          o   Because  editing  operations change the content of the buffer to
-              correspond to the window, you should not rely on  using  buffers
+          o   Because editing operations change the content of the  buffer  to
+              correspond  to  the window, you should not rely on using buffers
               for long-term storage of form data.
 
        The function set_field_status sets the associated status flag of field;
@@ -104,7 +102,7 @@

                                                          RETURN VALUE

                                                          -       The field_buffer  function  returns  NULL  on  error.   It  sets  errno
+       The field_buffer  function  returns  NULL  on  error.   It  sets  errno
        according to their success:
 
        E_OK The routine succeeded.
@@ -133,11 +131,11 @@

                                                          PORTABILITY

                                                          -       These routines emulate the System  V  forms  library.   They  were  not
+       These  routines  emulate  the  System  V  forms library.  They were not
        supported on Version 7 or BSD versions.
 
-       The   set_max_field   function   checks   for   an   ncurses  extension
-       O_INPUT_FIELD which allows a dynamic field to shrink if the  new  limit
+       The  set_max_field   function   checks   for   an   ncurses   extension
+       O_INPUT_FIELD  which  allows a dynamic field to shrink if the new limit
        is smaller than the current field size.
 
 
@@ -150,9 +148,7 @@
        curses(3x) and related pages whose names  begin  "form_"  for  detailed
        descriptions of the entry points.
 
-
-
-ncurses 6.5                       2024-03-16             form_field_buffer(3x)
+ncurses 6.6                       2024-12-28             form_field_buffer(3x)
                                                            diff --git a/doc/html/man/form_field_info.3x.html b/doc/html/man/form_field_info.3x.html index 2090ab6..f86c1b0 100644 --- a/doc/html/man/form_field_info.3x.html +++ b/doc/html/man/form_field_info.3x.html @@ -34,18 +34,16 @@ -form_field_info 3x 2024-03-16 ncurses 6.5 Library calls +form_field_info 3x 2024-03-16 ncurses 6.6 Library calls -

                                                            form_field_info 3x 2024-03-16 ncurses 6.5 Library calls

                                                            +

                                                            form_field_info 3x 2024-03-16 ncurses 6.6 Library calls

                                                             form_field_info(3x)              Library calls             form_field_info(3x)
 
 
-
-

                                                            NAME

                                                                    dynamic_field_info, field_info - retrieve field characteristics
 
@@ -87,11 +85,11 @@

                                                            PORTABILITY

                                                            -       These  routines  emulate  the  System  V  forms library.  They were not
+       These routines emulate the System  V  forms  library.   They  were  not
        supported on Version 7 or BSD versions.
 
-       A null (zero pointer) is accepted for any  of  the  return  values,  to
-       ignore  that  value.  Not all implementations allow this, e.g., Solaris
+       A  null  (zero  pointer)  is  accepted for any of the return values, to
+       ignore that value.  Not all implementations allow this,  e.g.,  Solaris
        2.7 does not.
 
 
@@ -104,9 +102,7 @@
        curses(3x)  and  related  pages  whose names begin "form_" for detailed
        descriptions of the entry points.
 
-
-
-ncurses 6.5                       2024-03-16               form_field_info(3x)
+ncurses 6.6                       2024-03-16               form_field_info(3x)
                                                              diff --git a/doc/html/man/form_field_just.3x.html b/doc/html/man/form_field_just.3x.html index f0bc457..c8a247b 100644 --- a/doc/html/man/form_field_just.3x.html +++ b/doc/html/man/form_field_just.3x.html @@ -34,18 +34,16 @@ -form_field_just 3x 2024-03-16 ncurses 6.5 Library calls +form_field_just 3x 2024-03-16 ncurses 6.6 Library calls -

                                                              form_field_just 3x 2024-03-16 ncurses 6.5 Library calls

                                                              +

                                                              form_field_just 3x 2024-03-16 ncurses 6.6 Library calls

                                                               form_field_just(3x)              Library calls             form_field_just(3x)
 
 
-
-

                                                              NAME

                                                                      set_field_just, field_just - retrieve field characteristics
 
@@ -90,12 +88,10 @@

                                                              SEE ALSO

                                                              -       curses(3x)  and  related  pages  whose names begin "form_" for detailed
+       curses(3x) and related pages whose names  begin  "form_"  for  detailed
        descriptions of the entry points.
 
-
-
-ncurses 6.5                       2024-03-16               form_field_just(3x)
+ncurses 6.6                       2024-03-16               form_field_just(3x)
                                                                diff --git a/doc/html/man/form_field_new.3x.html b/doc/html/man/form_field_new.3x.html index c7bedd9..3cfc745 100644 --- a/doc/html/man/form_field_new.3x.html +++ b/doc/html/man/form_field_new.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_field_new.3x,v 1.41 2024/03/16 15:35:01 tom Exp @ + * @Id: form_field_new.3x,v 1.43 2024/12/28 21:26:21 tom Exp @ --> -form_field_new 3x 2024-03-16 ncurses 6.5 Library calls +form_field_new 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                form_field_new 3x 2024-03-16 ncurses 6.5 Library calls

                                                                +

                                                                form_field_new 3x 2024-12-28 ncurses 6.6 Library calls

                                                                 form_field_new(3x)               Library calls              form_field_new(3x)
 
 
-
-

                                                                NAME

                                                                        new_field,  dup_field, link_field, free_field - create and destroy form
        fields
@@ -74,14 +72,14 @@
        character, options, and user pointer) are copied.  Field status and the
        field page bit are not copied.
 
-       The  function  link_field acts like dup_field, but the new field shares
+       The function link_field acts like dup_field, but the new  field  shares
        buffers with its parent.  Attribute data is separate.
 
        The function free_field de-allocates storage associated with a field.

                                                                RETURN VALUE

                                                                -       The functions new_field, dup_field, link_field return  NULL  on  error.
+       The  functions  new_field,  dup_field, link_field return NULL on error.
        They set errno according to their success:
 
        E_OK The routine succeeded.
@@ -104,11 +102,11 @@

                                                                PORTABILITY

                                                                -       These  routines  emulate  the  System  V  forms library.  They were not
+       These routines emulate the System  V  forms  library.   They  were  not
        supported on Version 7 or BSD versions.
 
-       It may be unwise to count on the set of attributes copied by  dup_field
-       being  portable;  the  System  V  forms  library documents are not very
+       It  may be unwise to count on the set of attributes copied by dup_field
+       being portable; the System V  forms  library  documents  are  not  very
        explicit about what gets copied and what does not.
 
 
@@ -120,9 +118,7 @@

                                                                SEE ALSO

                                                                        curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                form_field_new(3x)
+ncurses 6.6                       2024-12-28                form_field_new(3x)
                                                                  diff --git a/doc/html/man/form_field_opts.3x.html b/doc/html/man/form_field_opts.3x.html index 52fca0a..114d21e 100644 --- a/doc/html/man/form_field_opts.3x.html +++ b/doc/html/man/form_field_opts.3x.html @@ -1,6 +1,6 @@ -form_field_opts 3x 2024-03-16 ncurses 6.5 Library calls +form_field_opts 3x 2025-01-18 ncurses 6.6 Library calls -

                                                                  form_field_opts 3x 2024-03-16 ncurses 6.5 Library calls

                                                                  +

                                                                  form_field_opts 3x 2025-01-18 ncurses 6.6 Library calls

                                                                   form_field_opts(3x)              Library calls             form_field_opts(3x)
 
 
-
-

                                                                  NAME

                                                                          set_field_opts, field_opts_on, field_opts_off, field_opts - set and get
        field options
@@ -62,10 +60,10 @@

                                                                  DESCRIPTION

                                                                  -       The function set_field_opts sets all  the  given  field's  option  bits
-       (field option bits may be logically-OR'ed together).
+       The  function  set_field_opts  sets  all  the given field's option bits
+       (field option bits may be logically "or"-ed together).
 
-       The  function  field_opts_on turns on the given option bits, and leaves
+       The function field_opts_on turns on the given option bits,  and  leaves
        others alone.
 
        The function field_opts_off turns off the given option bits, and leaves
@@ -84,7 +82,7 @@
             Skip to the next field when this one fills.
 
        O_BLANK
-            The  field is cleared whenever a character is entered at the first
+            The field is cleared whenever a character is entered at the  first
             position.
 
        O_EDIT
@@ -100,15 +98,15 @@
             The field contents are displayed as data is entered.
 
        O_STATIC
-            Field buffers are fixed  to  field's  original  size.   Turn  this
+            Field  buffers  are  fixed  to  field's  original size.  Turn this
             option off to create a dynamic field.
 
        O_VISIBLE
-            The  field  is  displayed.   If this option is off, display of the
+            The field is displayed.  If this option is  off,  display  of  the
             field is suppressed.
 
        O_WRAP
-            Words that do not fit on a line are  wrapped  to  the  next  line.
+            Words  that  do  not  fit  on a line are wrapped to the next line.
             Words are blank-separated.
 
        These extension options are defined (extensions are off by default):
@@ -130,7 +128,7 @@
 
        O_INPUT_FIELD
             The set_max_field function checks for this extension, which allows
-            a dynamic field to shrink if the new limit  is  smaller  than  the
+            a  dynamic  field  to  shrink if the new limit is smaller than the
             current field size.
 
 
@@ -150,7 +148,7 @@

                                                                  PORTABILITY

                                                                  -       These  routines  emulate  the  System  V  forms library.  They were not
+       These routines emulate the System  V  forms  library.   They  were  not
        supported on Version 7 or BSD versions.
 
 
@@ -162,9 +160,7 @@

                                                                  SEE ALSO

                                                                          curses(3x), form(3x), form_field_just(3x)
 
-
-
-ncurses 6.5                       2024-03-16               form_field_opts(3x)
+ncurses 6.6                       2025-01-18               form_field_opts(3x)
                                                                    diff --git a/doc/html/man/form_field_userptr.3x.html b/doc/html/man/form_field_userptr.3x.html index 128698e..d42956c 100644 --- a/doc/html/man/form_field_userptr.3x.html +++ b/doc/html/man/form_field_userptr.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_field_userptr.3x,v 1.30 2024/03/16 15:35:01 tom Exp @ + * @Id: form_field_userptr.3x,v 1.32 2024/12/28 21:26:21 tom Exp @ --> -form_field_userptr 3x 2024-03-16 ncurses 6.5 Library calls +form_field_userptr 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                    form_field_userptr 3x 2024-03-16 ncurses 6.5 Library calls

                                                                    +

                                                                    form_field_userptr 3x 2024-12-28 ncurses 6.6 Library calls

                                                                     form_field_userptr(3x)           Library calls          form_field_userptr(3x)
 
 
-
-

                                                                    NAME

                                                                            set_field_userptr,  field_userptr  -  associate application data with a
        form field
@@ -65,7 +63,7 @@

                                                                    RETURN VALUE

                                                                    -       The function field_userptr returns a pointer (which may be  NULL).   It
+       The function field_userptr returns a pointer (which may be  NULL).   It
        does not set errno.
 
        The function set_field_userptr returns E_OK (success).
@@ -87,9 +85,7 @@

                                                                    SEE ALSO

                                                                            curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16            form_field_userptr(3x)
+ncurses 6.6                       2024-12-28            form_field_userptr(3x)
                                                                      diff --git a/doc/html/man/form_field_validation.3x.html b/doc/html/man/form_field_validation.3x.html index e66d71c..93e496e 100644 --- a/doc/html/man/form_field_validation.3x.html +++ b/doc/html/man/form_field_validation.3x.html @@ -1,6 +1,6 @@ -form_field_validation 3x 2024-03-16 ncurses 6.5 Library calls +form_field_validation 3x 2025-08-16 ncurses 6.6 Library calls -

                                                                      form_field_validation 3x 2024-03-16 ncurses 6.5 Library calls

                                                                      +

                                                                      form_field_validation 3x 2025-08-16 ncurses 6.6 Library calls

                                                                       form_field_validation(3x)        Library calls       form_field_validation(3x)
 
 
-
-

                                                                      NAME

                                                                              form_field_validation - data type validation for fields
 
@@ -57,7 +55,7 @@
        FIELDTYPE *field_type(const FIELD *field);
        int set_field_type(FIELD *field, FIELDTYPE *type, ...);
 
-       /* predefined field types */
+       /* field types */
        FIELDTYPE *TYPE_ALNUM;
        FIELDTYPE *TYPE_ALPHA;
        FIELDTYPE *TYPE_ENUM;
@@ -69,33 +67,31 @@

                                                                      DESCRIPTION

                                                                              By  default, no validation is done on form fields.  You can associate a
-       form with with a field type, making the form library validate input.
+       form with a field type, making the form library validate input.

                                                                      field_arg

                                                                              Returns a pointer to the field's argument block.  The argument block is
-       an  opaque  structure  containing a copy of the arguments provided in a
+       an opaque structure containing a copy of the arguments  provided  in  a
        set_field_type call.

                                                                      field_type

                                                                      -       Returns a pointer to the field type associated  with  the  form  field,
+       Returns  a  pointer  to  the field type associated with the form field,
        i.e., by calling set_field_type.

                                                                      set_field_type

                                                                      -       The  function  set_field_type associates a field type with a given form
-       field.  This is the type checked by validation functions.   Most  field
-       types  are  configurable,  via arguments which the caller provides when
+       The function set_field_type associates a field type with a  given  form
+       field.   This  is the type checked by validation functions.  Most field
+       types are configurable, via arguments which the  caller  provides  when
        calling set_field_type.
 
-       Several field types are predefined by the form library.
 
-
-

                                                                      PREDEFINED TYPES

                                                                      -       It is possible to set up new  programmer-defined  field  types.   Field
-       types  are implemented via the FIELDTYPE data structure, which contains
-       several pointers to functions.
+

                                                                      FIELD TYPES

                                                                      +       The form library defines several field types.  They are implemented via
+       the  FIELDTYPE  data  structure,  which  contains  several  pointers to
+       functions.
 
        See the form_fieldtype(3x) manual page, which describes functions which
        can be used to construct a field-type dynamically.
@@ -122,8 +118,8 @@
 
        o   a fourth int flag argument to enable case-sensitivity;
 
-       o   a  fifth  int flag argument specifying whether a partial match must
-           be a unique one.  If this flag is off, a prefix matches  the  first
+       o   a fifth int flag argument specifying whether a partial  match  must
+           be  a  unique one.  If this flag is off, a prefix matches the first
            of any set of more than one list elements with that prefix.
 
        The library copies the string list, so you may use a list that lives in
@@ -142,7 +138,7 @@
            ignored.
 
        On return, the field buffer is formatted according to the printf format
-       specification  ".*ld",  where  the  "*"  is  replaced  by the precision
+       specification ".*ld", where  the  "*"  is  replaced  by  the  precision
        argument.
 
        For details of the precision handling see printf(3).
@@ -155,9 +151,9 @@
 
        o   a fourth double argument constraining minimum value,
 
-       o   and a fifth double constraining  maximum  value.   If  your  system
-           supports  locales,  the  decimal  point  character  must be the one
-           specified by your locale.  If the maximum value  is  less  than  or
+       o   and  a  fifth  double  constraining  maximum value.  If your system
+           supports locales, the decimal  point  character  must  be  the  one
+           specified  by  your  locale.   If the maximum value is less than or
            equal to the minimum value, the range is simply ignored.
 
        On return, the field buffer is formatted according to the printf format
@@ -195,9 +191,11 @@
        This  is  an ncurses extension; this field type may not be available in
        other curses implementations.
 
+       It is possible to set up new programmer-defined field types.
+

                                                                      RETURN VALUE

                                                                      -       The functions field_type and  field_arg  return  NULL  on  error.   The
+       The functions field_type and  field_arg  return  NULL  on  error.   The
        function set_field_type returns one of the following:
 
        E_OK The routine succeeded.
@@ -219,9 +217,7 @@

                                                                      SEE ALSO

                                                                              curses(3x), form(3x), form_fieldtype(3x), form_variables(3x)
 
-
-
-ncurses 6.5                       2024-03-16         form_field_validation(3x)
+ncurses 6.6                       2025-08-16         form_field_validation(3x)
                                                                      -
                                                                    • PREDEFINED TYPES +
                                                                    • FIELD TYPES
                                                                      • TYPE_ALNUM
                                                                      • TYPE_ALPHA
                                                                        • diff --git a/doc/html/man/form_fieldtype.3x.html b/doc/html/man/form_fieldtype.3x.html index 369f25c..55035a0 100644 --- a/doc/html/man/form_fieldtype.3x.html +++ b/doc/html/man/form_fieldtype.3x.html @@ -1,6 +1,6 @@ -form_fieldtype 3x 2024-03-16 ncurses 6.5 Library calls +form_fieldtype 3x 2025-01-18 ncurses 6.6 Library calls -

                                                                        form_fieldtype 3x 2024-03-16 ncurses 6.5 Library calls

                                                                        +

                                                                        form_fieldtype 3x 2025-01-18 ncurses 6.6 Library calls

                                                                         form_fieldtype(3x)               Library calls              form_fieldtype(3x)
 
 
-
-

                                                                        NAME

                                                                                form_fieldtype - define validation-field types
 
@@ -92,12 +90,12 @@
 
        char_check
             This function validates input characters as they are entered.  The
-            form library passes it the character to be checked and  a  pointer
+            form  library  passes it the character to be checked and a pointer
             to an argument-block structure.

                                                                        free_fieldtype

                                                                        -       The  free_fieldtype  function  frees  the  space  allocated for a given
+       The free_fieldtype function frees  the  space  allocated  for  a  given
        validation type by new_fieldtype.
 
 
@@ -106,9 +104,9 @@
        functions with a field type:
 
        make_arg
-            This  function  is  automatically applied to the list of arguments
-            you give set_field_type when attaching validation to a field.   It
-            stores  the  arguments in an allocated argument-block object which
+            This function is automatically applied to the  list  of  arguments
+            you  give set_field_type when attaching validation to a field.  It
+            stores the arguments in an allocated argument-block  object  which
             is used when validating input.
 
        copy_arg
@@ -118,7 +116,7 @@
             Frees an argument-block structure.
 
        You must supply the make_arg function.  The other two are optional: you
-       may  supply NULL for them.  In this case, the form library assumes that
+       may  supply NULL for them.  In this case, the form library assumes that
        make_arg does not allocate memory but simply loads the argument into  a
        single scalar value.
 
@@ -136,11 +134,11 @@

                                                                        link_fieldtype

                                                                                The function link_fieldtype creates a new field type from the two given
-       types.  They are connected by an logical 'OR'.
+       types.  They are connected by a logical "or".

                                                                        RETURN VALUE

                                                                        -       The  pointer-valued  routines  return  NULL  on  error.  They set errno
+       The pointer-valued routines return  NULL  on  error.   They  set  errno
        according to their success:
 
        E_OK The routine succeeded.
@@ -169,7 +167,7 @@

                                                                        PORTABILITY

                                                                        -       These routines emulate the System  V  forms  library.   They  were  not
+       These  routines  emulate  the  System  V  forms library.  They were not
        supported on Version 7 or BSD versions.
 
 
@@ -181,9 +179,7 @@

                                                                        SEE ALSO

                                                                                curses(3x), form(3x), form_field_validation(3x)
 
-
-
-ncurses 6.5                       2024-03-16                form_fieldtype(3x)
+ncurses 6.6                       2025-01-18                form_fieldtype(3x)
                                                                          diff --git a/doc/html/man/form_hook.3x.html b/doc/html/man/form_hook.3x.html index 4845771..899ce02 100644 --- a/doc/html/man/form_hook.3x.html +++ b/doc/html/man/form_hook.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_hook.3x,v 1.37 2024/03/16 15:35:01 tom Exp @ + * @Id: form_hook.3x,v 1.39 2024/12/28 21:26:21 tom Exp @ --> -form_hook 3x 2024-03-16 ncurses 6.5 Library calls +form_hook 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                          form_hook 3x 2024-03-16 ncurses 6.5 Library calls

                                                                          +

                                                                          form_hook 3x 2024-12-28 ncurses 6.6 Library calls

                                                                           form_hook(3x)                    Library calls                   form_hook(3x)
 
 
-
-

                                                                          NAME

                                                                                  form_hook - set hooks for automatic invocation by applications
 
@@ -78,7 +76,7 @@

                                                                          field_init

                                                                          -       returns the current field init hook, if any (NULL if there is  no  such
+       returns the current field init hook, if any (NULL if there is  no  such
        hook).
 
 
@@ -88,7 +86,7 @@

                                                                          field_term

                                                                          -       returns the current field term hook, if any (NULL if there is  no  such
+       returns  the  current field term hook, if any (NULL if there is no such
        hook).
 
 
@@ -98,7 +96,7 @@

                                                                          form_init

                                                                          -       returns the current form init hook, if any (NULL if there  is  no  such
+       returns the current form init hook, if any (NULL if there  is  no  such
        hook).
 
 
@@ -108,12 +106,12 @@

                                                                          form_term

                                                                          -       returns the current form term hook, if any (NULL if there  is  no  such
+       returns the current form term hook, if any (NULL if there  is  no  such
        hook).

                                                                          RETURN VALUE

                                                                          -       Routines  that  return  pointers  return NULL on error.  Other routines
+       Routines  that  return  pointers  return NULL on error.  Other routines
        return one of the following:
 
        E_OK The routine succeeded.
@@ -135,9 +133,7 @@

                                                                          SEE ALSO

                                                                                  curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     form_hook(3x)
+ncurses 6.6                       2024-12-28                     form_hook(3x)
                                                                            diff --git a/doc/html/man/form_new.3x.html b/doc/html/man/form_new.3x.html index 7a1877c..78f7862 100644 --- a/doc/html/man/form_new.3x.html +++ b/doc/html/man/form_new.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_new.3x,v 1.32 2024/03/16 15:35:01 tom Exp @ + * @Id: form_new.3x,v 1.34 2024/12/28 21:26:21 tom Exp @ --> -form_new 3x 2024-03-16 ncurses 6.5 Library calls +form_new 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                            form_new 3x 2024-03-16 ncurses 6.5 Library calls

                                                                            +

                                                                            form_new 3x 2024-12-28 ncurses 6.6 Library calls

                                                                             form_new(3x)                     Library calls                    form_new(3x)
 
 
-
-

                                                                            NAME

                                                                                    new_form, free_form - create and destroy forms
 
@@ -59,14 +57,14 @@

                                                                            DESCRIPTION

                                                                                    The function new_form creates a new form connected to a specified field
-       pointer array (which must be NULL-terminated).
+       pointer array (which must be NULL-terminated).
 
-       The function free_form disconnects form from its field array and  frees
+       The  function free_form disconnects form from its field array and frees
        the storage allocated for the form.

                                                                            RETURN VALUE

                                                                            -       The  function  new_form returns NULL on error.  It sets errno according
+       The function new_form returns NULL on error.  It sets  errno  according
        to the function's success:
 
        E_OK The routine succeeded.
@@ -92,7 +90,7 @@

                                                                            PORTABILITY

                                                                            -       These routines emulate the System  V  forms  library.   They  were  not
+       These  routines  emulate  the  System  V  forms library.  They were not
        supported on Version 7 or BSD versions.
 
 
@@ -104,9 +102,7 @@

                                                                            SEE ALSO

                                                                                    curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                      form_new(3x)
+ncurses 6.6                       2024-12-28                      form_new(3x)
                                                                              diff --git a/doc/html/man/form_new_page.3x.html b/doc/html/man/form_new_page.3x.html index e8a18df..5505e4a 100644 --- a/doc/html/man/form_new_page.3x.html +++ b/doc/html/man/form_new_page.3x.html @@ -34,18 +34,16 @@ -form_new_page 3x 2024-03-16 ncurses 6.5 Library calls +form_new_page 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                              form_new_page 3x 2024-03-16 ncurses 6.5 Library calls

                                                                              +

                                                                              form_new_page 3x 2024-03-16 ncurses 6.6 Library calls

                                                                               form_new_page(3x)                Library calls               form_new_page(3x)
 
 
-
-

                                                                              NAME

                                                                                      set_new_page, new_page - form pagination functions
 
@@ -87,12 +85,10 @@

                                                                              SEE ALSO

                                                                              -       curses(3x)  and  related  pages  whose names begin "form_" for detailed
+       curses(3x) and related pages whose names  begin  "form_"  for  detailed
        descriptions of the entry points.
 
-
-
-ncurses 6.5                       2024-03-16                 form_new_page(3x)
+ncurses 6.6                       2024-03-16                 form_new_page(3x)
                                                                                diff --git a/doc/html/man/form_opts.3x.html b/doc/html/man/form_opts.3x.html index 63a9437..8a9f4c2 100644 --- a/doc/html/man/form_opts.3x.html +++ b/doc/html/man/form_opts.3x.html @@ -1,6 +1,6 @@ -form_opts 3x 2024-03-16 ncurses 6.5 Library calls +form_opts 3x 2025-01-18 ncurses 6.6 Library calls -

                                                                                form_opts 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                +

                                                                                form_opts 3x 2025-01-18 ncurses 6.6 Library calls

                                                                                 form_opts(3x)                    Library calls                   form_opts(3x)
 
 
-
-

                                                                                NAME

                                                                                        set_form_opts,  form_opts_on,  form_opts_off,  form_opts  - set and get
        form options
@@ -63,7 +61,7 @@

                                                                                DESCRIPTION

                                                                                        The function set_form_opts sets all the given form's option bits  (form
-       option bits may be logically-OR'ed together).
+       option bits may be logically "or"-ed together).
 
        The  function  form_opts_on  turns on the given option bits, and leaves
        others alone.
@@ -106,9 +104,7 @@

                                                                                SEE ALSO

                                                                                        curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     form_opts(3x)
+ncurses 6.6                       2025-01-18                     form_opts(3x)
                                                                                  diff --git a/doc/html/man/form_page.3x.html b/doc/html/man/form_page.3x.html index b882db2..89f8687 100644 --- a/doc/html/man/form_page.3x.html +++ b/doc/html/man/form_page.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_page.3x,v 1.37 2024/03/16 15:35:01 tom Exp @ + * @Id: form_page.3x,v 1.39 2024/12/28 21:26:21 tom Exp @ --> -form_page 3x 2024-03-16 ncurses 6.5 Library calls +form_page 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                  form_page 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                  +

                                                                                  form_page 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                   form_page(3x)                    Library calls                   form_page(3x)
 
 
-
-

                                                                                  NAME

                                                                                          form_page - set and get form page number
 
@@ -70,7 +68,7 @@
 
        The function unfocus_current_field removes the focus from  the  current
        field  of  the  form.  In such state, inquiries via current_field shall
-       return a NULL pointer.
+       return a NULL pointer.
 
        The function set_form_page sets the form's page number (goes to page  n
        of the form).
@@ -118,9 +116,7 @@

                                                                                  SEE ALSO

                                                                                          curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     form_page(3x)
+ncurses 6.6                       2024-12-28                     form_page(3x)
                                                                                    diff --git a/doc/html/man/form_post.3x.html b/doc/html/man/form_post.3x.html index 9f97d3e..de92b31 100644 --- a/doc/html/man/form_post.3x.html +++ b/doc/html/man/form_post.3x.html @@ -34,18 +34,16 @@ -form_post 3x 2024-03-16 ncurses 6.5 Library calls +form_post 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                                    form_post 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                    +

                                                                                    form_post 3x 2024-03-16 ncurses 6.6 Library calls

                                                                                     form_post(3x)                    Library calls                   form_post(3x)
 
 
-
-

                                                                                    NAME

                                                                                            post_form,   unpost_form   -  write  or  erase  forms  from  associated
        subwindows
@@ -60,7 +58,7 @@

                                                                                    DESCRIPTION

                                                                                            The function post_form displays a form to its associated subwindow.  To
-       trigger  physical  display  of  the  subwindow, use refresh(3x) or some
+       trigger physical display of the  subwindow,  use  refresh(3x)  or  some
        equivalent curses routine (the implicit doupdate triggered by an curses
        input request will do).
 
@@ -107,9 +105,7 @@

                                                                                    SEE ALSO

                                                                                            curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     form_post(3x)
+ncurses 6.6                       2024-03-16                     form_post(3x)
                                                                                      diff --git a/doc/html/man/form_requestname.3x.html b/doc/html/man/form_requestname.3x.html index ecb5992..b85a5d4 100644 --- a/doc/html/man/form_requestname.3x.html +++ b/doc/html/man/form_requestname.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_requestname.3x,v 1.35 2024/03/16 15:35:01 tom Exp @ + * @Id: form_requestname.3x,v 1.37 2024/12/28 21:26:21 tom Exp @ --> -form_requestname 3x 2024-03-16 ncurses 6.5 Library calls +form_requestname 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                      form_requestname 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                      +

                                                                                      form_requestname 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                       form_requestname(3x)             Library calls            form_requestname(3x)
 
 
-
-

                                                                                      NAME

                                                                                              form_request_by_name, form_request_name - handle printable form request
        names
@@ -59,22 +57,22 @@

                                                                                      DESCRIPTION

                                                                                      -       The function form_request_name returns the printable  name  of  a  form
-       request  code.  The function form_request_by_name searches in the name-
-       table for a request with the given name and returns its  request  code.
+       The  function  form_request_name  returns  the printable name of a form
+       request code.  The function form_request_by_name searches in the  name-
+       table  for  a request with the given name and returns its request code.
        Otherwise E_NO_MATCH is returned.

                                                                                      RETURN VALUE

                                                                                      -       form_request_name   returns   NULL   on   error   and   sets  errno  to
+       form_request_name  returns  NULL   on   error   and   sets   errno   to
        E_BAD_ARGUMENT.
 
-       form_request_by_name returns E_NO_MATCH on  error.   It  does  not  set
+       form_request_by_name  returns  E_NO_MATCH  on  error.   It does not set
        errno.

                                                                                      PORTABILITY

                                                                                      -       These  routines  are  specific  to ncurses.  They were not supported on
+       These routines are specific to ncurses.  They  were  not  supported  on
        Version 7, BSD or System V implementations.  It is recommended that any
        code depending on them be conditioned using NCURSES_VERSION.
 
@@ -87,9 +85,7 @@

                                                                                      SEE ALSO

                                                                                              curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16              form_requestname(3x)
+ncurses 6.6                       2024-12-28              form_requestname(3x)
                                                                                        diff --git a/doc/html/man/form_userptr.3x.html b/doc/html/man/form_userptr.3x.html index db79de2..d588598 100644 --- a/doc/html/man/form_userptr.3x.html +++ b/doc/html/man/form_userptr.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_userptr.3x,v 1.36 2024/03/16 15:35:01 tom Exp @ + * @Id: form_userptr.3x,v 1.38 2024/12/28 21:26:21 tom Exp @ --> -form_userptr 3x 2024-03-16 ncurses 6.5 Library calls +form_userptr 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                        form_userptr 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                        +

                                                                                        form_userptr 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                         form_userptr(3x)                 Library calls                form_userptr(3x)
 
 
-
-

                                                                                        NAME

                                                                                                set_form_userptr, form_userptr - associate application data with a form
        item
@@ -59,20 +57,20 @@

                                                                                        DESCRIPTION

                                                                                        -       Every form and every form item has a field that can  be  used  to  hold
-       application-specific  data  (that  is,  the  form-driver code leaves it
+       Every  form  and  every  form item has a field that can be used to hold
+       application-specific data (that is,  the  form-driver  code  leaves  it
        alone).  These functions get and set the form user pointer field.

                                                                                        RETURN VALUE

                                                                                        -       The function form_userptr returns a pointer (which may  be  NULL).   It
+       The  function  form_userptr  returns a pointer (which may be NULL).  It
        does not set errno.
 
        The function set_form_userptr returns E_OK (success).

                                                                                        PORTABILITY

                                                                                        -       These  routines  emulate  the  System  V  forms library.  They were not
+       These routines emulate the System  V  forms  library.   They  were  not
        supported on Version 7 or BSD versions.
 
        The user pointer is a void pointer.  We chose not to leave it as a char
@@ -87,9 +85,7 @@

                                                                                        SEE ALSO

                                                                                                curses(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                  form_userptr(3x)
+ncurses 6.6                       2024-12-28                  form_userptr(3x)
                                                                                          diff --git a/doc/html/man/form_variables.3x.html b/doc/html/man/form_variables.3x.html index 68c8e56..cd08872 100644 --- a/doc/html/man/form_variables.3x.html +++ b/doc/html/man/form_variables.3x.html @@ -34,18 +34,16 @@ -form_variables 3x 2024-03-16 ncurses 6.5 Library calls +form_variables 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                                          form_variables 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                          +

                                                                                          form_variables 3x 2024-03-16 ncurses 6.6 Library calls

                                                                                           form_variables(3x)               Library calls              form_variables(3x)
 
 
-
-

                                                                                          NAME

                                                                                                  TYPE_ALNUM,    TYPE_ALPHA,    TYPE_ENUM,    TYPE_INTEGER,    TYPE_IPV4,
        TYPE_NUMERIC, TYPE_REGEXP - form system global variables
@@ -106,9 +104,7 @@

                                                                                          SEE ALSO

                                                                                                  form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                form_variables(3x)
+ncurses 6.6                       2024-03-16                form_variables(3x)
                                                                                            diff --git a/doc/html/man/form_win.3x.html b/doc/html/man/form_win.3x.html index 976ef27..da9bbc1 100644 --- a/doc/html/man/form_win.3x.html +++ b/doc/html/man/form_win.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: form_win.3x,v 1.35 2024/03/16 15:35:01 tom Exp @ + * @Id: form_win.3x,v 1.37 2024/12/28 21:26:21 tom Exp @ --> -form_win 3x 2024-03-16 ncurses 6.5 Library calls +form_win 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                            form_win 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                            +

                                                                                            form_win 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                             form_win(3x)                     Library calls                    form_win(3x)
 
 
-
-

                                                                                            NAME

                                                                                                    form_win - make and break form window and subwindow associations
 
@@ -72,8 +70,8 @@
        necessary to set either window; by default, the driver code uses stdscr
        for both.
 
-       In the set_ functions, window argument of NULL is treated as though  it
-       were stsdcr.  A form argument of NULL is treated as a request to change
+       In  the set_ functions, window argument of NULL is treated as though it
+       were stsdcr.  A form argument of NULL is treated as a request to change
        the system default form window or subwindow.
 
        The function scale_form returns  the  minimum  size  required  for  the
@@ -81,7 +79,7 @@

                                                                                            RETURN VALUE

                                                                                            -       Routines  that  return  pointers  return  NULL on error.  Routines that
+       Routines  that  return  pointers  return  NULL on error.  Routines that
        return an integer return one of the following error codes:
 
        E_OK The routine succeeded.
@@ -112,9 +110,7 @@

                                                                                            SEE ALSO

                                                                                                    curses(3x), curs_variables(3x), form(3x)
 
-
-
-ncurses 6.5                       2024-03-16                      form_win(3x)
+ncurses 6.6                       2024-12-28                      form_win(3x)
                                                                                              diff --git a/doc/html/man/index.html b/doc/html/man/index.html index 07d986b..e50cd2f 100644 --- a/doc/html/man/index.html +++ b/doc/html/man/index.html @@ -1,7 +1,7 @@ - - + "HTML Tidy for HTML5 for Linux version 5.6.0"> NCURSES – Manual Pages -
                                                                                              • Programs: -
                                                                                              • Scripts: -
                                                                                                • adacurses*-config – - helper script for AdaCurses libraries
                                                                                                  • + configuration helper for AdaCurses libraries
                                                                                                • ncurses*-config - – helper script for ncurses libraries
                                                                                                  • + – configuration helper for ncurses libraries
                                                                                              • Libraries: -
                                                                                              • File formats: - +
                                                                                                • + +
                                                                                              • Other information: + diff --git a/doc/html/man/infocmp.1m.html b/doc/html/man/infocmp.1m.html index 44cb12f..b8fcd03 100644 --- a/doc/html/man/infocmp.1m.html +++ b/doc/html/man/infocmp.1m.html @@ -1,7 +1,7 @@ -infocmp 1m 2024-03-16 ncurses 6.5 User commands +infocmp 1m 2025-11-11 ncurses 6.6 User commands -

                                                                                                infocmp 1m 2024-03-16 ncurses 6.5 User commands

                                                                                                +

                                                                                                infocmp 1m 2025-11-11 ncurses 6.6 User commands

                                                                                                 infocmp(1m)                      User commands                     infocmp(1m)
 
 
-
-

                                                                                                NAME

                                                                                                        infocmp - compare or print out terminfo descriptions

                                                                                                SYNOPSIS

                                                                                                -       infocmp [-1cCdDeEFgGiIKlLnpqrtTuUVWx]
-             [-v n] [-s d| i| l| c] [-Q n] [-R subset]
-             [-w width] [-A directory] [-B directory]
-             [terminal-type ...]
+
+
+       infocmp   [-1cCdDeEFgGiIKlLnpqrtTuUVWx]  [-A directory]  [-B directory]
+              [-Q encoding]   [-R subset]   [-s key]   [-v level]   [-w width]
+              [terminal-type ... ]

                                                                                                DESCRIPTION

                                                                                                -       infocmp  can  be  used  to  compare  a binary terminfo entry with other
-       terminfo entries, rewrite a terminfo description to take  advantage  of
-       the  use=  terminfo field, or print out a terminfo description from the
-       binary file (term) in a variety of formats.  In all cases, the  Boolean
-       fields  will be printed first, followed by the numeric fields, followed
-       by the string fields.
+       infocmp  reports  a  human-readable  terminal  type  description from a
+       compiled entry in the terminfo database  in  a  variety  of  selectable
+       formats,  compares such entries to each other, and rewrites an entry to
+       replace  "use"  expressions  with  the  content  of  other  entries  by
+       reference.   A  terminfo entry comprises a list of one or more terminal
+       type identifiers, a human-readable description of  the  terminal  type,
+       and  a  list of terminal capabilities that characterize its programming
+       interface.   In  all  cases,   the   program   reports   Boolean-valued
+       capabilities  first,  followed  by numeric ones, and then string-valued
+       capabilities.

                                                                                                Default Options

                                                                                                -       If no  options  are  specified  and  zero  or  one  terminal-types  are
-       specified,  the  -I option will be assumed.  If more than one terminal-
-       type is specified, the -d option will be assumed.
-
-
-

                                                                                                Comparison Options [-d] [-c] [-n]

                                                                                                -       infocmp  compares  the  terminfo  description  of  the  first  terminal
-       terminal-type  with  each  of the descriptions given by the entries for
-       the other terminal's terminal-types.  If a capability  is  defined  for
-       only  one  of  the terminals, the value returned depends on the type of
-       the capability:
-
-       o   F for missing Boolean variables
-
-       o   NULL for missing integer or string variables
-
-       Use the -q option to show the distinction between absent and  cancelled
-       capabilities.
-
-       These  options  produce a list which you can use to compare two or more
-       terminal descriptions:
-
-       -d   produces a list of each capability that is different  between  two
-            entries.   Each  item  in  the list shows ":" after the capability
-            name, followed by the capability values, separated by a comma.
-
-       -c   produces a list of each capability that is common between  two  or
-            more entries.  Missing capabilities are ignored.  Each item in the
-            list  shows  "="  after  the  capability  name,  followed  by  the
-            capability value.
-
-            The  -u  option  provides  a  related  output,  showing  the first
-            terminal description rewritten to use the  second  as  a  building
-            block via the "use=" clause.
-
-       -n   produces  a  list  of each capability that is in none of the given
-            entries.  Each item in the list shows "!"  before  the  capability
-            name.
-
-            Normally only the conventional capabilities are shown.  Use the -x
-            option to add the BSD-compatibility capabilities  (names  prefixed
-            with "OT").
-
-            If  no  terminal-types  are  given,  infocmp  uses the environment
-            variable TERM for each of the terminal-types.
+       If  no  options  are  specified  and  zero  or  one  terminal-types  is
+       specified,  infocmp  assumes  the  -I  option.   If  more  than  one is
+       specified, the program assumes the -d option.

                                                                                                Source Listing Options [-I] [-L] [-C] [-r]

                                                                                                @@ -135,8 +96,8 @@
        output and commented out.  These should be edited by hand.
 
        For best results when converting to termcap format, you should use both
-       -C  and  -r.   Normally a termcap description is limited to 1023 bytes.
-       infocmp trims away less essential parts to make it  fit.   If  you  are
+       -C and -r.  Normally a termcap description is limited  to  1023  bytes.
+       infocmp  trims  away  less  essential parts to make it fit.  If you are
        converting to one of the (rare) termcap implementations which accept an
        unlimited size of termcap, you may want to add  the  -T  option.   More
        often  however,  you  must  help  the  termcap implementation, and trim
@@ -147,9 +108,9 @@
        Mandatory padding (padding information with a trailing "/") will become
        optional.
 
-       All  termcap  variables  no longer supported by terminfo, but which are
-       derivable from other terminfo  variables,  will  be  output.   Not  all
-       terminfo  capabilities  will  be translated; only those variables which
+       All termcap variables no longer supported by terminfo,  but  which  are
+       derivable  from  other  terminfo  variables,  will  be output.  Not all
+       terminfo capabilities will be translated; only  those  variables  which
        were part of termcap will normally be output.  Specifying the -r option
        will  take off this restriction, allowing all capabilities to be output
        in termcap form.  Normally you would use both the -C  and  -r  options.
@@ -162,10 +123,10 @@
        supported.   Because  termcap  strings  are  not as flexible, it is not
        always possible  to  convert  a  terminfo  string  capability  into  an
        equivalent termcap format.  A subsequent conversion of the termcap file
-       back into terminfo format will not necessarily reproduce  the  original
+       back  into  terminfo format will not necessarily reproduce the original
        terminfo source.
 
-       Some  common  terminfo  parameter sequences, their termcap equivalents,
+       Some common terminfo parameter sequences,  their  termcap  equivalents,
        and some terminal types which commonly have such sequences, are:
 
                  terminfo                   termcap   Terminal Types
@@ -178,8 +139,48 @@
                  %p2...%p1                  %r        hpgeneric
 
 
+

                                                                                                Entry Comparison Options [-d] [-c] [-n]

                                                                                                +       Given  -c,  -d, or -n, infocmp compares the terminfo description of the
+       first specified terminal-type with those  of  each  of  the  subsequent
+       operands.  If fewer terminal-types than required are specified, infocmp
+       uses the environment variable TERM in their place.
+
+       If  a  capability  is  defined  for  only  one terminal type, the value
+       reported depends on the capability's type:
+
+       o   F for missing Boolean variables
+
+       o   NULL for missing integer or string variables
+
+       The -c and -d options  report  string  capability  values  between  "'"
+       characters.   Use  the  -q  option  to  distinguish absent and canceled
+       capabilities; see terminfo(5).
+
+       The comparison option selects the form of report.
+
+       -d   lists each capability that  differs  between  two  entries.   Each
+            capability  name is followed by ":" and comma-separated capability
+            values, then a period.
+
+       -c   lists each capability that two entries have  in  common.   infocmp
+            ignores  capabilities  missing from either entry.  Each capability
+            name is followed by "=", a space, and the capability value, then a
+            period.
+
+            If the -u  option  is  further  specified,  infocmp  rewrites  the
+            description  of  the first type employing "use=" syntax to use the
+            second as a building block.
+
+       -n   lists capabilities that are in none of the  given  entries.   Each
+            capability name is preceded by "!"  and followed by a period.
+
+            Normally  only  conventional  capabilities  are shown.  Use the -x
+            option to add BSD-compatibility capabilities (names prefixed  with
+            "OT").
+
+

                                                                                                Use= Option [-u]

                                                                                                -       The -u option produces a  terminfo  source  description  of  the  first
+       The  -u  option  produces  a  terminfo  source description of the first
        terminal terminal-type which is relative to the sum of the descriptions
        given by the entries for the other terminal-types.   It  does  this  by
        analyzing  the  differences  between  the  first terminal-types and the
@@ -192,11 +193,11 @@
        relative to the other.
 
        A capability will be printed with an at-sign (@) if it no longer exists
-       in  the first terminal-type, but one of the other terminal-type entries
-       contains a value for it.  A capability's value will be printed  if  the
-       value  in  the  first  terminal-type  is  not found in any of the other
-       terminal-type entries, or if  the  first  of  the  other  terminal-type
-       entries  that  has  this  capability  gives  a  different value for the
+       in the first terminal-type, but one of the other terminal-type  entries
+       contains  a  value for it.  A capability's value will be printed if the
+       value in the first terminal-type is not  found  in  any  of  the  other
+       terminal-type  entries,  or  if  the  first  of the other terminal-type
+       entries that has this  capability  gives  a  different  value  for  the
        capability than that in the first terminal-type.
 
        The order of the other terminal-type entries is significant.  Since the
@@ -207,33 +208,34 @@
        between the other terminal-type entries as they are found.
 
        Alternatively, specifying a capability after a use= entry that contains
-       that capability will cause the  second  specification  to  be  ignored.
-       Using  infocmp  to recreate a description can be a useful check to make
-       sure that everything was specified correctly  in  the  original  source
+       that  capability  will  cause  the  second specification to be ignored.
+       Using infocmp to recreate a description can be a useful check  to  make
+       sure  that  everything  was  specified correctly in the original source
        description.
 
-       Another  error  that  does not cause incorrect compiled files, but will
-       slow down the compilation time, is specifying extra  use=  fields  that
+       Another error that does not cause incorrect compiled  files,  but  will
+       slow  down  the  compilation time, is specifying extra use= fields that
        are superfluous.  infocmp will flag any other terminal-type use= fields
        that were not needed.
 
-   Changing Databases [-A directory] [-B directory]
+
+

                                                                                                Changing Databases [-A directory] [-B directory]

                                                                                                        Like  other  ncurses  utilities,  infocmp  looks   for   the   terminal
        descriptions   in  several  places.   You  can  use  the  TERMINFO  and
        TERMINFO_DIRS environment variables to override the compiled-in default
-       list  of  places  to  search.   See curses(3x), as well as the Fetching
+       list of places to search.  See curses(3x),  as  well  as  the  Fetching
        Compiled Descriptions section in terminfo(5).
 
-       You can also use the options -A and -B to override the list  of  places
+       You  can  also use the options -A and -B to override the list of places
        to search when comparing terminal descriptions:
 
        o   The -A option sets the location for the first terminal-type
 
        o   The -B option sets the location for the other terminal-types.
 
-       Using  these  options,  it  is  possible  to compare descriptions for a
-       terminal with the same name located in two  different  databases.   For
-       instance,  you  can use this feature for comparing descriptions for the
+       Using these options, it is  possible  to  compare  descriptions  for  a
+       terminal  with  the  same name located in two different databases.  For
+       instance, you can use this feature for comparing descriptions  for  the
        same terminal created by different people.
 
 
@@ -251,17 +253,17 @@
        -D   tells infocmp to print the database locations that it knows about,
             and exit.
 
-       -E   Dump  the  capabilities of the given terminal as tables, needed in
-            the  C  initializer  for  a  TERMTYPE  structure   (the   terminal
-            capability  structure in the <term.h>).  This option is useful for
-            preparing versions of the curses library  hardwired  for  a  given
-            terminal  type.  The tables are all declared static, and are named
-            according to the type and the name of the  corresponding  terminal
+       -E   Dump the capabilities of the given terminal as tables,  needed  in
+            the   C   initializer  for  a  TERMTYPE  structure  (the  terminal
+            capability structure in the <term.h>).  This option is useful  for
+            preparing  versions  of  the  curses library hardwired for a given
+            terminal type.  The tables are all declared static, and are  named
+            according  to  the type and the name of the corresponding terminal
             entry.
 
-            Before  ncurses  5.0,  the split between the -e and -E options was
-            not needed; but support for extended  names  required  making  the
-            arrays   of  terminal  capabilities  separate  from  the  TERMTYPE
+            Before ncurses 5.0, the split between the -e and  -E  options  was
+            not  needed;  but  support  for extended names required making the
+            arrays  of  terminal  capabilities  separate  from  the   TERMTYPE
             structure.
 
        -e   Dump the capabilities of the given terminal as a C initializer for
@@ -270,31 +272,31 @@
             curses library hardwired for a given terminal type.
 
        -F   compare terminfo files.  This assumes that two following arguments
-            are filenames.   The  files  are  searched  for  pairwise  matches
-            between  entries,  with  two entries considered to match if any of
-            their names do.  The  report  printed  to  standard  output  lists
-            entries  with  no matches in the other file, and entries with more
-            than one match.  For entries with exactly one match it includes  a
-            difference  report.  Normally, to reduce the volume of the report,
-            use references are not resolved before  looking  for  differences,
+            are  filenames.   The  files  are  searched  for  pairwise matches
+            between entries, with two entries considered to match  if  any  of
+            their  names  do.   The  report  printed  to standard output lists
+            entries with no matches in the other file, and entries  with  more
+            than  one match.  For entries with exactly one match it includes a
+            difference report.  Normally, to reduce the volume of the  report,
+            use  references  are  not resolved before looking for differences,
             but resolution can be forced by also specifying -r.
 
-       -f   Display  complex terminfo strings which contain if/then/else/endif
+       -f   Display complex terminfo strings which contain  if/then/else/endif
             expressions indented for readability.
 
-       -G   Display constant  literals  in  decimal  form  rather  than  their
+       -G   Display  constant  literals  in  decimal  form  rather  than their
             character equivalents.
 
-       -g   Display  constant  character  literals  in quoted form rather than
+       -g   Display constant character literals in  quoted  form  rather  than
             their decimal equivalents.
 
-       -i   Analyze the initialization (is1, is2, is3), and reset  (rs1,  rs2,
-            rs3),   strings   in   the  entry,  as  well  as  those  used  for
-            starting/stopping cursor-positioning mode (smcup, rmcup)  as  well
+       -i   Analyze  the  initialization (is1, is2, is3), and reset (rs1, rs2,
+            rs3),  strings  in  the  entry,  as  well  as   those   used   for
+            starting/stopping  cursor-positioning  mode (smcup, rmcup) as well
             as starting/stopping keymap mode (smkx, rmkx).
 
-            For  each  string,  the  code  tries to analyze it into actions in
-            terms of the other capabilities in the  entry,  certain  X3.64/ISO
+            For each string, the code tries to  analyze  it  into  actions  in
+            terms  of  the  other capabilities in the entry, certain X3.64/ISO
             6429/ECMA-48 capabilities, and certain DEC VT-series private modes
             (the set of recognized special sequences  has  been  selected  for
             completeness  over  the  existing terminfo database).  Each report
@@ -313,7 +315,6 @@
                       LL            home-down
                       RSR           reset scroll region
                       -----------------------------------------
-
                       DECSTR        soft reset (VT320)
                       S7C1T         7-bit controls (VT220)
                       -----------------------------------------
@@ -378,41 +379,41 @@
                 and using "-" for absent capabilities, "@" for canceled rather
                 than "NULL".
 
-            o   However,   show   differences  between  absent  and  cancelled
+            o   However,  show  differences  between   absent   and   canceled
                 capabilities.
 
             o   Omit the "Reconstructed from" comment for source listings.
 
        -Rsubset
-            Restrict output to a given subset.  This option is  for  use  with
-            archaic  versions of terminfo like those on SVr1, Ultrix, or HP-UX
-            that do not support the full set of SVR4/XSI Curses terminfo;  and
-            variants  such  as AIX that have their own extensions incompatible
+            Restrict  output  to  a given subset.  This option is for use with
+            archaic versions of terminfo like those on SVr1, Ultrix, or  HP-UX
+            that  do not support the full set of SVR4/XSI Curses terminfo; and
+            variants such as AIX that have their own  extensions  incompatible
             with SVr4/XSI.
 
-            o   Available terminfo subsets are  "SVr1",  "Ultrix",  "HP",  and
+            o   Available  terminfo  subsets  are  "SVr1", "Ultrix", "HP", and
                 "AIX"; see terminfo(5) for details.
 
-            o   You  can  also  choose  the  subset  "BSD"  which selects only
+            o   You can also  choose  the  subset  "BSD"  which  selects  only
                 capabilities with termcap equivalents recognized by 4.4BSD.
 
-            o   If you select any other value for -R, it is  the  same  as  no
+            o   If  you  select  any  other value for -R, it is the same as no
                 subset, i.e., all capabilities are used.
 
-            A  few  options  override the subset selected with -R, if they are
+            A few options override the subset selected with -R,  if  they  are
             processed later in the command parameters:
 
-            -C   sets the "BSD" subset as a side-effect.
+            -C   sets the "BSD" subset as a side effect.
 
             -I   sets the subset to all capabilities.
 
             -r   sets the subset to all capabilities.
 
        -s [d|i|l|c]
-            The -s option sorts the fields within each type according  to  the
+            The  -s  option sorts the fields within each type according to the
             argument below:
 
-            d    leave  fields  in  the  order  that  they  are  stored in the
+            d    leave fields in  the  order  that  they  are  stored  in  the
                  terminfo database.
 
             i    sort by terminfo name.
@@ -421,24 +422,24 @@
 
             c    sort by the termcap name.
 
-            If the -s option is not given, the  fields  printed  out  will  be
-            sorted  alphabetically  by  the  terminfo  name  within each type,
-            except in the case of the -C or the -L options,  which  cause  the
-            sorting  to  be  done  by  the termcap name or the long C variable
+            If  the  -s  option  is  not given, the fields printed out will be
+            sorted alphabetically by  the  terminfo  name  within  each  type,
+            except  in  the  case of the -C or the -L options, which cause the
+            sorting to be done by the termcap name  or  the  long  C  variable
             name, respectively.
 
-       -T   eliminates size-restrictions  on  the  generated  text.   This  is
+       -T   eliminates  size-restrictions  on  the  generated  text.   This is
             mainly  useful  for  testing  and  analysis,  since  the  compiled
             descriptions  are  limited  (e.g.,  1023  for  termcap,  4096  for
             terminfo).
 
-       -t   tells  tic  to  discard commented-out capabilities.  Normally when
-            translating from terminfo to termcap, untranslatable  capabilities
+       -t   tells tic to discard commented-out  capabilities.   Normally  when
+            translating  from terminfo to termcap, untranslatable capabilities
             are commented-out.
 
-       -U   tells  infocmp  to  not  post-process  the  data after parsing the
+       -U   tells infocmp to not  post-process  the  data  after  parsing  the
             source  file.   This  feature  helps  when  comparing  the  actual
-            contents  of  two  source  files, since it excludes the inferences
+            contents of two source files, since  it  excludes  the  inferences
             that infocmp makes to fill in missing data.
 
        -V   reports the version of ncurses which was used in this program, and
@@ -449,10 +450,10 @@
 
             The optional parameter n is a number  from  1  to  10,  inclusive,
             indicating the desired level of detail of information.  If ncurses
-            is built  without  tracing  support,  the  optional  parameter  is
+            is  built  without  tracing  support,  the  optional  parameter is
             ignored.
 
-       -W   By  itself,  the  -w  option  will  not  force  long strings to be
+       -W   By itself, the -w  option  will  not  force  long  strings  to  be
             wrapped.  Use the -W option to do this.
 
        -w width
@@ -469,27 +470,26 @@

                                                                                                EXTENSIONS

                                                                                                -       The -0, -1, -E, -F, -G, -Q, -R, -T, -V, -a, -e, -f, -g, -i, -l, -p,  -q
-       and -t options are not supported in SVr4 curses.
-
-       SVr4   infocmp  does  not  distinguish  between  absent  and  cancelled
-       capabilities.  Also, it shows missing integer capabilities as  -1  (the
-       internal   value   used   to   represent   missing   integers).    This
-       implementation shows those as  "NULL",  for  consistency  with  missing
-       strings.
-
-       The  -r  option's  notion of "termcap" capabilities is System V Release
-       4's.  Actual BSD curses versions will have a more restricted  set.   To
-       see only the 4.4BSD set, use -r -RBSD.
+       The -0, -1, -a, -e, -E, -f, -F, -g, -G, -i, -l, -p, -q, -Q, -R, -t, -T,
+       and -V options are ncurses extensions.

                                                                                                PORTABILITY

                                                                                                -       X/Open  Curses,  Issue  7 (2009) provides a description of infocmp.  It
-       does not mention the options used for converting to termcap format.
+       X/Open Curses Issue 7 (2009) specifies infocmp.  It  does  not  mention
+       options for producing descriptions in termcap format.
+
+       SVr4   infocmp   does  not  distinguish  between  absent  and  canceled
+       capabilities.  It furthermore reports missing integer  capabilities  as
+       -1  (its  internal  representation).  ncurses shows these as "NULL" for
+       consistency with missing string capabilities.
+
+       The -r option of  ncurses  infocmp  uses  SVr4's  notion  of  "termcap"
+       capabilities.  BSD curses had a more restricted set.  To see only those
+       present in 4.4BSD, use "-r -RBSD".

                                                                                                HISTORY

                                                                                                -       Although System V Release 2 provided a  terminfo  library,  it  had  no
+       Although  System  V  Release  2  provided a terminfo library, it had no
        documented tool for decompiling the terminal descriptions.  Tony Hansen
        (AT&T) wrote the first infocmp in early 1984, for System V Release 3.
 
@@ -529,9 +529,7 @@
 
        https://invisible-island.net/ncurses/tctest.html
 
-
-
-ncurses 6.5                       2024-03-16                       infocmp(1m)
+ncurses 6.6                       2025-11-11                       infocmp(1m)
                                                                                                  @@ -540,9 +538,10 @@ ncurses 6.5 2024-03-16 DESCRIPTION diff --git a/doc/html/man/infotocap.1m.html b/doc/html/man/infotocap.1m.html index 4213f69..1a0bc14 100644 --- a/doc/html/man/infotocap.1m.html +++ b/doc/html/man/infotocap.1m.html @@ -1,6 +1,6 @@ -infotocap 1m 2024-03-16 ncurses 6.5 User commands +infotocap 1m 2025-10-04 ncurses 6.6 User commands -

                                                                                                  infotocap 1m 2024-03-16 ncurses 6.5 User commands

                                                                                                  +

                                                                                                  infotocap 1m 2025-10-04 ncurses 6.6 User commands

                                                                                                   infotocap(1m)                    User commands                   infotocap(1m)
 
 
-
-

                                                                                                  NAME

                                                                                                          infotocap - convert a terminfo description into a termcap description
 
@@ -58,7 +56,7 @@

                                                                                                  DESCRIPTION

                                                                                                          infotocap  translates  terminal  descriptions.   It looks in each given
-       text file for terminfo entries and, For each one found,  it  writes  an
+       text file for terminfo entries and,  for  each  one  found,  writes  an
        analogous  termcap description to the standard output stream.  terminfo
        "use" capabilities  translate  to  termcap  tc  capabilities.   Because
        termcap  is  a  less expressive format than terminfo, some capabilities
@@ -75,9 +73,13 @@
               compiled terminal description database
 
 
+

                                                                                                  EXTENSIONS

                                                                                                  +       This command is an ncurses extension.
+
+

                                                                                                  PORTABILITY

                                                                                                  -       None  of  X/Open  Curses, Issue 7 (2009), SVr4, or NetBSD document this
-       application.
+       X/Open  Curses  Issue 7 (2009) does not specify this command.  SVr4 and
+       NetBSD curses do not implement it.

                                                                                                  AUTHORS

                                                                                                  @@ -88,9 +90,7 @@

                                                                                                  SEE ALSO

                                                                                                          infocmp(1m), tic(1m), curses(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-03-16                     infotocap(1m)
+ncurses 6.6                       2025-10-04                     infotocap(1m)
                                                                                                    @@ -98,6 +98,7 @@ ncurses 6.5 2024-03-16 SYNOPSIS
                                                                                                  • DESCRIPTION
                                                                                                  • FILES
                                                                                                    • +
                                                                                                  • EXTENSIONS
                                                                                                  • PORTABILITY
                                                                                                  • AUTHORS
                                                                                                  • SEE ALSO
                                                                                                    • diff --git a/doc/html/man/key_defined.3x.html b/doc/html/man/key_defined.3x.html index 453decf..fd2b62d 100644 --- a/doc/html/man/key_defined.3x.html +++ b/doc/html/man/key_defined.3x.html @@ -1,6 +1,6 @@ -key_defined 3x 2024-03-16 ncurses 6.5 Library calls +key_defined 3x 2025-10-04 ncurses 6.6 Library calls -

                                                                                                    key_defined 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                    +

                                                                                                    key_defined 3x 2025-10-04 ncurses 6.6 Library calls

                                                                                                     key_defined(3x)                  Library calls                 key_defined(3x)
 
 
-
-

                                                                                                    NAME

                                                                                                    -       key_defined - test whether a curses keycode is defined
+       key_defined - obtain key code for an ncurses function key definition

                                                                                                    SYNOPSIS

                                                                                                            #include <curses.h>
 
-       int key_defined(const char *definition);
+       int key_defined(const char * definition);

                                                                                                    DESCRIPTION

                                                                                                    -       This  is an extension to the curses library.  It permits an application
-       to determine if a string is currently bound to any keycode.
+       The  key_defined  ncurses  extension  permits  a  curses application to
+       determine the function key code, if any, to which the string definition
+       is bound.

                                                                                                    RETURN VALUE

                                                                                                    -       If the string is bound to a keycode, its value (greater than  zero)  is
-       returned.   If  no  keycode  is bound, zero is returned.  If the string
-       conflicts with longer strings which are bound to keys, -1 is returned.
+       key_defined returns the first key code to which definition is bound  if
+       any  exists.  If none does, it returns 0.  If definition is a prefix of
+       another bound definition, key_defined returns -1.
+
+
+

                                                                                                    EXTENSIONS

                                                                                                    +       key_defined is an ncurses extension.

                                                                                                    PORTABILITY

                                                                                                    -       This routine is specific to ncurses.  It was not supported  on  Version
-       7,  BSD  or  System V implementations.  It is recommended that any code
-       depending on them be conditioned using NCURSES_VERSION.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.

                                                                                                    AUTHORS

                                                                                                    @@ -79,11 +81,9 @@

                                                                                                    SEE ALSO

                                                                                                    -       define_key(3x)
+       curses(3x), define_key(3x), keybound(3x), keyok(3x)
 
-
-
-ncurses 6.5                       2024-03-16                   key_defined(3x)
+ncurses 6.6                       2025-10-04                   key_defined(3x)
                                                                                                      @@ -91,6 +91,7 @@ ncurses 6.5 2024-03-16 SYNOPSIS
                                                                                                    • DESCRIPTION
                                                                                                    • RETURN VALUE
                                                                                                      • +
                                                                                                    • EXTENSIONS
                                                                                                    • PORTABILITY
                                                                                                    • AUTHORS
                                                                                                    • SEE ALSO
                                                                                                      • diff --git a/doc/html/man/keybound.3x.html b/doc/html/man/keybound.3x.html index e926e77..3987e53 100644 --- a/doc/html/man/keybound.3x.html +++ b/doc/html/man/keybound.3x.html @@ -28,53 +28,59 @@ * authorization. * **************************************************************************** * Author: Thomas E. Dickey 1999 - * @Id: keybound.3x,v 1.36 2024/03/16 15:35:01 tom Exp @ + * @Id: keybound.3x,v 1.42 2024/12/28 21:26:21 tom Exp @ --> -keybound 3x 2024-03-16 ncurses 6.5 Library calls +keybound 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                      keybound 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                      +

                                                                                                      keybound 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                       keybound(3x)                     Library calls                    keybound(3x)
 
 
-
-

                                                                                                      NAME

                                                                                                      -       keybound - get definition of curses keycode
+       keybound - get definition of a curses function key code

                                                                                                      SYNOPSIS

                                                                                                              #include <curses.h>
 
-       char * keybound(int keycode, int count);
+       char * keybound(int key-code, int count);

                                                                                                      DESCRIPTION

                                                                                                      -       This  is an extension to the curses library.  It permits an application
-       to determine the string which is defined in the terminfo  for  specific
-       keycodes.
+       The  keybound  ncurses extension permits a curses application to obtain
+       the value of the  string  bound  to  the  function  key  key-code;  see
+       wgetch(3x)  (wide-character API users: wget_wch(3x)).  By default, such
+       bindings are string  capabilities  from  the  terminfo  database  entry
+       corresponding   to   the  terminal  type.   The  application  can  non-
+       destructively   and   repeatedly   override   such   definitions   with
+       define_key(3x),  as  if  by  pushing new definitions onto a stack.  The
+       count parameter accesses the  nth  most  recently  defined  binding;  0
+       selects the binding that is used on input.

                                                                                                      RETURN VALUE

                                                                                                      -       The keycode parameter must be greater than zero, else NULL is returned.
-       If it does not correspond to a defined key, then NULL is returned.  The
-       count  parameter  is  used  to allow the application to iterate through
-       multiple  definitions,  counting  from  zero.   When  successful,   the
-       function returns a string which must be freed by the caller.
+       If key-code corresponds to a function key defined by the application or
+       the  terminal type in use, keybound allocates and returns a string that
+       must be freed by the application.  keybound returns NULL if key-code is
+       not positive or if it does not correspond to a key code definition.
+
+
+

                                                                                                      EXTENSIONS

                                                                                                      +       keybound is an ncurses extension.

                                                                                                      PORTABILITY

                                                                                                      -       This  routine  is specific to ncurses.  It was not supported on Version
-       7, BSD or System V implementations.  It is recommended  that  any  code
-       depending on them be conditioned using NCURSES_VERSION.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.

                                                                                                      AUTHORS

                                                                                                      @@ -82,11 +88,9 @@

                                                                                                      SEE ALSO

                                                                                                      -       define_key(3x), keyok(3x)
+       curses(3x), define_key(3x), keyok(3x), key_defined(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-03-16                      keybound(3x)
+ncurses 6.6                       2024-12-28                      keybound(3x)
                                                                                                        @@ -94,6 +98,7 @@ ncurses 6.5 2024-03-16 SYNOPSIS
                                                                                                      • DESCRIPTION
                                                                                                      • RETURN VALUE
                                                                                                        • +
                                                                                                      • EXTENSIONS
                                                                                                      • PORTABILITY
                                                                                                      • AUTHORS
                                                                                                      • SEE ALSO
                                                                                                        • diff --git a/doc/html/man/keyok.3x.html b/doc/html/man/keyok.3x.html index f94f82f..c03643d 100644 --- a/doc/html/man/keyok.3x.html +++ b/doc/html/man/keyok.3x.html @@ -1,6 +1,6 @@ -keyok 3x 2024-03-16 ncurses 6.5 Library calls +keyok 3x 2025-10-04 ncurses 6.6 Library calls -

                                                                                                        keyok 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                        +

                                                                                                        keyok 3x 2025-10-04 ncurses 6.6 Library calls

                                                                                                         keyok(3x)                        Library calls                       keyok(3x)
 
 
-
-

                                                                                                        NAME

                                                                                                        -       keyok - enable or disable a curses keycode
+       keyok - enable or disable an ncurses function key code

                                                                                                        SYNOPSIS

                                                                                                                #include <curses.h>
 
-       int keyok(int keycode, bool enable);
+       int keyok(int key-code, bool bf);

                                                                                                        DESCRIPTION

                                                                                                        -       This  is an extension to the curses library.  It permits an application
-       to disable specific keycodes, rather than use the  keypad  function  to
-       disable all keycodes.  Keys that have been disabled can be re-enabled.
+       The  keyok  ncurses extension permits a curses application to disable a
+       function key key-code returned by wgetch(3x) (wide-character API users:
+       wget_wch(3x)).  Key codes that have been disabled  can  be  re-enabled.
+       bf selects the desired enablement status.  This operation is more fine-
+       grained than calling keypad(3x), which affects all function keys.

                                                                                                        RETURN VALUE

                                                                                                        -       The  keycode  must  be  greater than zero, else ERR is returned.  If it
-       does not correspond to a defined key, then ERR  is  returned.   If  the
-       enable  parameter  is  true,  then the key must have been disabled, and
-       vice versa.  Otherwise, the function returns OK.
+       keyok returns ERR if
+
+       o   key-code is nonpositive,
+
+       o   key-code is not a recognized value, or
+
+       o   enablement of key-code is already in the desired state.
+
+       Otherwise, keyok returns OK.
+
+
+

                                                                                                        EXTENSIONS

                                                                                                        +       keyok is an ncurses extension.

                                                                                                        PORTABILITY

                                                                                                        -       This routine is specific to ncurses.  It was not supported  on  Version
-       7,  BSD  or  System V implementations.  It is recommended that any code
-       depending on them be conditioned using NCURSES_VERSION.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
+
+       NetBSD curses since 2.0 (2004) supports keyok.

                                                                                                        AUTHORS

                                                                                                        @@ -81,11 +91,9 @@

                                                                                                        SEE ALSO

                                                                                                        -       define_key(3x)
+       curses(3x), define_key(3x), keybound(3x), keyok(3x), key_defined(3x)
 
-
-
-ncurses 6.5                       2024-03-16                         keyok(3x)
+ncurses 6.6                       2025-10-04                         keyok(3x)
                                                                                                          @@ -93,6 +101,7 @@ ncurses 6.5 2024-03-16 SYNOPSIS
                                                                                                        • DESCRIPTION
                                                                                                        • RETURN VALUE
                                                                                                          • +
                                                                                                        • EXTENSIONS
                                                                                                        • PORTABILITY
                                                                                                        • AUTHORS
                                                                                                        • SEE ALSO
                                                                                                          • diff --git a/doc/html/man/legacy_coding.3x.html b/doc/html/man/legacy_coding.3x.html index f7b41ba..4591e0f 100644 --- a/doc/html/man/legacy_coding.3x.html +++ b/doc/html/man/legacy_coding.3x.html @@ -28,25 +28,23 @@ * authorization. * **************************************************************************** * Author: Thomas E. Dickey - * @Id: legacy_coding.3x,v 1.28 2024/04/20 19:13:50 tom Exp @ + * @Id: legacy_coding.3x,v 1.32 2024/09/14 20:06:50 tom Exp @ --> -legacy_coding 3x 2024-04-20 ncurses 6.5 Library calls +legacy_coding 3x 2024-09-14 ncurses 6.6 Library calls -

                                                                                                          legacy_coding 3x 2024-04-20 ncurses 6.5 Library calls

                                                                                                          +

                                                                                                          legacy_coding 3x 2024-09-14 ncurses 6.6 Library calls

                                                                                                           legacy_coding(3x)                Library calls               legacy_coding(3x)
 
 
-
-

                                                                                                          NAME

                                                                                                                  use_legacy_coding - override curses locale encoding checks
 
@@ -58,15 +56,15 @@

                                                                                                          DESCRIPTION

                                                                                                          -       use_legacy_coding is an extension to the curses library.  It allows the
-       caller to change the result of unctrl(3x), suppressing isprint(3)-based
+       use_legacy_coding,  an ncurses extension to the curses library, permits
+       customiztion  of  unctrl(3x)  behavior,  suppressing   isprint(3)-based
        checks  within  the  library  that  would  normally  cause  nonprinting
        characters to be rendered in visible form.  The alteration affects only
-       eight-bit characters.
+       byte-wide characters with the most significant bit set.
 
        The level parameter controls the result.
 
-              0    The   library  functions  normally,  rendering  nonprinting
+              0    The  library  functions  normally,  rendering   nonprinting
                    characters as described in unctrl(3x),
 
               1    the library ignores isprint for codes in the range 160-255.
@@ -77,28 +75,33 @@

                                                                                                          RETURN VALUE

                                                                                                          -       If the screen has not been initialized, or the level parameter  is  out
-       of  range,  use_legacy_coding  returns  ERR.  Otherwise, it returns the
-       previous level: 0, 1, or 2.
+       If  the  curses screen has not been initialized, or the level parameter
+       is out of range, use_legacy_coding returns ERR.  Otherwise, it  returns
+       the previous level.
+
+
+

                                                                                                          EXTENSIONS

                                                                                                          +       use_legacy_coding is an ncurses extension.

                                                                                                          PORTABILITY

                                                                                                          -       use_legacy_coding is specific to ncurses.   It  was  not  supported  on
-       Version  7,  BSD  or  System V implementations.  Applications employing
-       ncurses extensions should condition their use on the visibility of  the
-       NCURSES_VERSION preprocessor macro.
+       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
+
+
+

                                                                                                          HISTORY

                                                                                                          +       ncurses  5.6  (2006)  introduced use_legacy_coding to support lynx(1)'s
+       font-switching feature.

                                                                                                          AUTHORS

                                                                                                          -       Thomas Dickey (to support lynx(1)'s font-switching feature).
+       Thomas Dickey

                                                                                                          SEE ALSO

                                                                                                                  unctrl(3x)
 
-
-
-ncurses 6.5                       2024-04-20                 legacy_coding(3x)
+ncurses 6.6                       2024-09-14                 legacy_coding(3x)
                                                                                                          diff --git a/doc/html/man/menu.3x.html b/doc/html/man/menu.3x.html index a499cf1..c10c583 100644 --- a/doc/html/man/menu.3x.html +++ b/doc/html/man/menu.3x.html @@ -1,7 +1,7 @@ -menu 3x 2024-03-16 ncurses 6.5 Library calls +menu 3x 2025-11-11 ncurses 6.6 Library calls -

                                                                                                          menu 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                          +

                                                                                                          menu 3x 2025-11-11 ncurses 6.6 Library calls

                                                                                                           menu(3x)                         Library calls                        menu(3x)
 
 
-
-

                                                                                                          NAME

                                                                                                          -       menu - curses extension for programming menus
+       menu - present menus in curses windows

                                                                                                          SYNOPSIS

                                                                                                          @@ -57,9 +55,9 @@

                                                                                                          DESCRIPTION

                                                                                                                  The menu library provides terminal-independent facilities for composing
-       menu systems on character-cell terminals.  The library  includes:  item
-       routines,  which create and modify menu items; and menu routines, which
-       group items into  menus,  display  menus  on  the  screen,  and  handle
+       menu  systems  on character-cell terminals.  The library includes: item
+       routines, which create and modify menu items; and menu routines,  which
+       group  items  into  menus,  display  menus  on  the  screen, and handle
        interaction with the user.
 
        The menu library uses the curses libraries, and a curses initialization
@@ -71,7 +69,7 @@

                                                                                                          Current Default Values for Item Attributes

                                                                                                                  The menu library maintains a default value for  item  attributes.   You
        can  get  or  set  this default by calling the appropriate get_ or set_
-       routine with a NULL item pointer.  Changing this default  with  a  set_
+       routine with a NULL item pointer.  Changing this default  with  a  set_
        function  affects  future  item  creations,  but  does  not  change the
        rendering of items already created.
 
@@ -112,7 +110,6 @@
        menu_pattern           menu_pattern(3x)
        menu_request_by_name   menu_requestname(3x)
        menu_request_name      menu_requestname(3x)
-
        menu_spacing           menu_spacing(3x)
        menu_sub               menu_win(3x)
        menu_term              menu_hook(3x)
@@ -150,7 +147,7 @@

                                                                                                          RETURN VALUE

                                                                                                          -       Routines  that  return  pointers  return  NULL on error.  Routines that
+       Routines  that  return  pointers  return  NULL on error.  Routines that
        return an integer return one of the following error codes:
 
        E_OK The routine succeeded.
@@ -218,9 +215,7 @@
        curses(3x)  and  related  pages  whose names begin "menu_" for detailed
        descriptions of the entry points.
 
-
-
-ncurses 6.5                       2024-03-16                          menu(3x)
+ncurses 6.6                       2025-11-11                          menu(3x)
                                                                                                            diff --git a/doc/html/man/menu_attributes.3x.html b/doc/html/man/menu_attributes.3x.html index 3b3f6ea..17ddc2c 100644 --- a/doc/html/man/menu_attributes.3x.html +++ b/doc/html/man/menu_attributes.3x.html @@ -34,18 +34,16 @@ -menu_attributes 3x 2024-03-16 ncurses 6.5 Library calls +menu_attributes 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                                                            menu_attributes 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                            +

                                                                                                            menu_attributes 3x 2024-03-16 ncurses 6.6 Library calls

                                                                                                             menu_attributes(3x)              Library calls             menu_attributes(3x)
 
 
-
-

                                                                                                            NAME

                                                                                                                    menu_back,     menu_fore,     menu_grey,    menu_pad,    set_menu_back,
        set_menu_fore,  set_menu_grey,  set_menu_pad  -  color  and   attribute
@@ -79,7 +77,7 @@
        default is A_NORMAL.
 
        The function set_menu_grey sets the grey attribute of menu. This is the
-       highlight  used  for un-selectable menu items in menus that permit more
+       highlight used for un-selectable menu items in menus that  permit  more
        than one selection.  The function menu_grey returns the grey attribute.
        The default is A_UNDERLINE.
 
@@ -111,12 +109,10 @@

                                                                                                            SEE ALSO

                                                                                                            -       curses(3x)  and  related  pages  whose names begin "menu_" for detailed
+       curses(3x) and related pages whose names  begin  "menu_"  for  detailed
        descriptions of the entry points.
 
-
-
-ncurses 6.5                       2024-03-16               menu_attributes(3x)
+ncurses 6.6                       2024-03-16               menu_attributes(3x)
                                                                                                              diff --git a/doc/html/man/menu_cursor.3x.html b/doc/html/man/menu_cursor.3x.html index 0003bcd..65a7f97 100644 --- a/doc/html/man/menu_cursor.3x.html +++ b/doc/html/man/menu_cursor.3x.html @@ -34,18 +34,16 @@ -menu_cursor 3x 2024-03-16 ncurses 6.5 Library calls +menu_cursor 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                                                              menu_cursor 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                              +

                                                                                                              menu_cursor 3x 2024-03-16 ncurses 6.6 Library calls

                                                                                                               menu_cursor(3x)                  Library calls                 menu_cursor(3x)
 
 
-
-

                                                                                                              NAME

                                                                                                                      pos_menu_cursor - position a menu's cursor
 
@@ -91,9 +89,7 @@

                                                                                                              SEE ALSO

                                                                                                                      curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                   menu_cursor(3x)
+ncurses 6.6                       2024-03-16                   menu_cursor(3x)
                                                                                                                diff --git a/doc/html/man/menu_driver.3x.html b/doc/html/man/menu_driver.3x.html index d82a7f5..669aa1e 100644 --- a/doc/html/man/menu_driver.3x.html +++ b/doc/html/man/menu_driver.3x.html @@ -1,6 +1,6 @@ -menu_driver 3x 2024-03-16 ncurses 6.5 Library calls +menu_driver 3x 2025-10-04 ncurses 6.6 Library calls -

                                                                                                                menu_driver 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                +

                                                                                                                menu_driver 3x 2025-10-04 ncurses 6.6 Library calls

                                                                                                                 menu_driver(3x)                  Library calls                 menu_driver(3x)
 
 
-
-

                                                                                                                NAME

                                                                                                                        menu_driver - command-processing loop of the menu system
 
@@ -60,15 +58,15 @@
        Once a menu has been posted (displayed), you should funnel input events
        to it through menu_driver.  This routine has three major input cases:
 
-       o   The input is a form navigation request.  Navigation  request  codes
-           are constants defined in <form.h>, which are distinct from the key-
+       o   The  input  is a menu navigation request.  Navigation request codes
+           are constants defined in menu.h, which are distinct from  the  key-
            and character codes returned by wgetch(3x).
 
-       o   The input is a printable character.   Printable  characters  (which
-           must  be  positive,  less  than  256)  are checked according to the
+       o   The  input  is  a printable character.  Printable characters (which
+           must be positive, less than  256)  are  checked  according  to  the
            program's locale settings.
 
-       o   The input is the KEY_MOUSE special key  associated  with  an  mouse
+       o   The  input  is  the  KEY_MOUSE special key associated with an mouse
            event.
 
        The menu driver requests are as follows:
@@ -129,13 +127,13 @@
        new pattern.  If there is no such match, menu_driver returns E_NO_MATCH
        and deletes the appended character from the buffer.
 
-       If the second argument is one of the above  pre-defined  requests,  the
+       If  the  second  argument is one of the above pre-defined requests, the
        corresponding action is performed.

                                                                                                                Mouse Handling

                                                                                                                -       If  the  second  argument  is the KEY_MOUSE special key, the associated
-       mouse event is translated into one of the above  pre-defined  requests.
+       If the second argument is the KEY_MOUSE  special  key,  the  associated
+       mouse  event  is translated into one of the above pre-defined requests.
        Currently only clicks in the user window (e.g., inside the menu display
        area or the decoration window) are handled.
 
@@ -165,16 +163,16 @@
            should be returned.  It is exactly the purpose of this return value
            to signal that an application specific command should be executed.
 
-       o   If a translation into a request was done, menu_driver  returns  the
+       o   If  a  translation into a request was done, menu_driver returns the
            result of this request.
 
-       If  you clicked outside the user window or the mouse event could not be
+       If you clicked outside the user window or the mouse event could not  be
        translated into a menu request an E_REQUEST_DENIED is returned.

                                                                                                                Application-defined Commands

                                                                                                                -       If the second argument is neither printable nor one of the  above  pre-
-       defined  menu  requests  or  KEY_MOUSE,  the  drive  assumes  it  is an
+       If  the  second argument is neither printable nor one of the above pre-
+       defined menu  requests  or  KEY_MOUSE,  the  drive  assumes  it  is  an
        application-specific    command    and    returns    E_UNKNOWN_COMMAND.
        Application-defined commands should be defined relative to MAX_COMMAND,
        the maximum value of these pre-defined requests.
@@ -221,9 +219,7 @@

                                                                                                                SEE ALSO

                                                                                                                        curses(3x), getch(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                   menu_driver(3x)
+ncurses 6.6                       2025-10-04                   menu_driver(3x)
                                                                                                                  diff --git a/doc/html/man/menu_format.3x.html b/doc/html/man/menu_format.3x.html index ddd934c..8e49fe5 100644 --- a/doc/html/man/menu_format.3x.html +++ b/doc/html/man/menu_format.3x.html @@ -34,18 +34,16 @@ -menu_format 3x 2024-03-16 ncurses 6.5 Library calls +menu_format 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                                                                  menu_format 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                  +

                                                                                                                  menu_format 3x 2024-03-16 ncurses 6.6 Library calls

                                                                                                                   menu_format(3x)                  Library calls                 menu_format(3x)
 
 
-
-

                                                                                                                  NAME

                                                                                                                          set_menu_format, menu_format - set and get menu sizes
 
@@ -59,17 +57,17 @@

                                                                                                                  DESCRIPTION

                                                                                                                          The function set_menu_format sets the maximum display size of the given
-       menu.  If this size is too small to display all menu  items,  the  menu
-       will  be  made  scrollable.   If  this  size  is  larger than the menus
-       subwindow and the subwindow is too small to  display  all  menu  items,
+       menu.   If  this  size is too small to display all menu items, the menu
+       will be made scrollable.   If  this  size  is  larger  than  the  menus
+       subwindow  and  the  subwindow  is too small to display all menu items,
        post_menu will fail.
 
-       The  default format is 16 rows, 1 column.  Calling set_menu_format with
-       a null menu pointer will change this default.  A  zero  row  or  column
-       argument  to  set_menu_format is interpreted as a request not to change
+       The default format is 16 rows, 1 column.  Calling set_menu_format  with
+       a  null  menu  pointer  will change this default.  A zero row or column
+       argument to set_menu_format is interpreted as a request not  to  change
        the current value.
 
-       The function menu_format returns the maximum-size constraints  for  the
+       The  function  menu_format returns the maximum-size constraints for the
        given menu into the storage addressed by rows and cols.
 
 
@@ -92,7 +90,7 @@

                                                                                                                  PORTABILITY

                                                                                                                  -       These  routines  emulate  the  System  V  menu  library.  They were not
+       These routines emulate the  System  V  menu  library.   They  were  not
        supported on Version 7 or BSD versions.
 
 
@@ -104,9 +102,7 @@

                                                                                                                  SEE ALSO

                                                                                                                          curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                   menu_format(3x)
+ncurses 6.6                       2024-03-16                   menu_format(3x)
                                                                                                                    diff --git a/doc/html/man/menu_hook.3x.html b/doc/html/man/menu_hook.3x.html index ca1810c..cd1e5f0 100644 --- a/doc/html/man/menu_hook.3x.html +++ b/doc/html/man/menu_hook.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_hook.3x,v 1.32 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_hook.3x,v 1.34 2024/12/28 21:26:21 tom Exp @ --> -menu_hook 3x 2024-03-16 ncurses 6.5 Library calls +menu_hook 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                    menu_hook 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                    +

                                                                                                                    menu_hook 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                     menu_hook(3x)                    Library calls                   menu_hook(3x)
 
 
-
-

                                                                                                                    NAME

                                                                                                                            menu_hook - set hooks for automatic invocation by applications
 
@@ -73,27 +71,27 @@
 
        The  function  set_item_init sets a hook to be called at menu-post time
        and each time the selected item changes (after the change).   item_init
-       returns  the  current  item init hook, if any (NULL if there is no such
+       returns  the  current  item init hook, if any (NULL if there is no such
        hook).
 
        The function set_item_term sets a hook to be called at menu-unpost time
        and each time the selected item changes (before the change).  item_term
-       returns the current item term hook, if any (NULL if there  is  no  such
+       returns the current item term hook, if any (NULL if there  is  no  such
        hook).
 
        The  function  set_menu_init sets a hook to be called at menu-post time
        and just after the top row on the  menu  changes  once  it  is  posted.
-       menu_init  returns the current menu init hook, if any (NULL if there is
+       menu_init  returns the current menu init hook, if any (NULL if there is
        no such hook).
 
        The function set_menu_term sets a hook to be called at menu-unpost time
-       and  just  before  the  top  row on the menu changes once it is posted.
-       menu_term returns the current menu term hook, if any (NULL if there  is
+       and just before the top row on the menu  changes  once  it  is  posted.
+       menu_term  returns the current menu term hook, if any (NULL if there is
        no such hook).

                                                                                                                    RETURN VALUE

                                                                                                                    -       Routines  that  return  pointers  return NULL on error.  Other routines
+       Routines that return pointers return NULL  on  error.   Other  routines
        return one of the following:
 
        E_OK The routine succeeded.
@@ -103,7 +101,7 @@

                                                                                                                    PORTABILITY

                                                                                                                    -       These routines emulate the  System  V  menu  library.   They  were  not
+       These  routines  emulate  the  System  V  menu  library.  They were not
        supported on Version 7 or BSD versions.
 
 
@@ -115,9 +113,7 @@

                                                                                                                    SEE ALSO

                                                                                                                            curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     menu_hook(3x)
+ncurses 6.6                       2024-12-28                     menu_hook(3x)
                                                                                                                      diff --git a/doc/html/man/menu_items.3x.html b/doc/html/man/menu_items.3x.html index 7f1c082..943ac12 100644 --- a/doc/html/man/menu_items.3x.html +++ b/doc/html/man/menu_items.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_items.3x,v 1.34 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_items.3x,v 1.36 2024/12/28 21:26:21 tom Exp @ --> -menu_items 3x 2024-03-16 ncurses 6.5 Library calls +menu_items 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                      menu_items 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                      +

                                                                                                                      menu_items 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                       menu_items(3x)                   Library calls                  menu_items(3x)
 
 
-
-

                                                                                                                      NAME

                                                                                                                              set_menu_items,  menu_items,  item_count  -  make and break connections
        between items and menus
@@ -61,7 +59,7 @@

                                                                                                                      DESCRIPTION

                                                                                                                              The function set_menu_items changes the item pointer array of the given
-       menu.  The array must be terminated by a NULL.
+       menu.  The array must be terminated by a NULL.
 
        The function menu_items returns the item array of the given menu.
 
@@ -69,11 +67,11 @@

                                                                                                                      RETURN VALUE

                                                                                                                      -       The function menu_items returns a pointer (which may be NULL).  It does
+       The function menu_items returns a pointer (which may be NULL).  It does
        not set errno.
 
        The function item_count returns ERR (the general  curses  error  return
-       value) if its menu parameter is NULL.
+       value) if its menu parameter is NULL .
 
        The  function  set_menu_items  returns  one  of  the following codes on
        error:
@@ -109,9 +107,7 @@

                                                                                                                      SEE ALSO

                                                                                                                              curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                    menu_items(3x)
+ncurses 6.6                       2024-12-28                    menu_items(3x)
                                                                                                                        diff --git a/doc/html/man/menu_mark.3x.html b/doc/html/man/menu_mark.3x.html index 1cdb2b0..ea695e2 100644 --- a/doc/html/man/menu_mark.3x.html +++ b/doc/html/man/menu_mark.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_mark.3x,v 1.35 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_mark.3x,v 1.37 2024/12/28 21:26:21 tom Exp @ --> -menu_mark 3x 2024-03-16 ncurses 6.5 Library calls +menu_mark 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                        menu_mark 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                        +

                                                                                                                        menu_mark 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                         menu_mark(3x)                    Library calls                   menu_mark(3x)
 
 
-
-

                                                                                                                        NAME

                                                                                                                                set_menu_mark, menu_mark - get and set the menu mark string
 
@@ -62,20 +60,20 @@
        highlighting or color capability, the menu library marks selected items
        in a menu with a prefix string.
 
-       The  function  set_menu_mark  sets  the mark string for the given menu.
-       Calling set_menu_mark with a null  menu  item  will  abolish  the  mark
-       string.   Note  that  changing the length of the mark string for a menu
+       The function set_menu_mark sets the mark string  for  the  given  menu.
+       Calling  set_menu_mark  with  a  null  menu  item will abolish the mark
+       string.  Note that changing the length of the mark string  for  a  menu
        while the menu is posted is likely to produce unhelpful behavior.
 
-       The default string is "-" (a dash).  Calling set_menu_mark with a  non-
-       NULL menu argument will change this default.
+       The  default string is "-" (a dash).  Calling set_menu_mark with a non-
+       NULL menu argument will change this default.
 
-       The function menu_mark returns the menu's mark string (or NULL if there
+       The function menu_mark returns the menu's mark string (or NULL if there
        is none).

                                                                                                                        RETURN VALUE

                                                                                                                        -       The function menu_mark returns a pointer (which may be NULL).  It  does
+       The function menu_mark returns a pointer (which may be NULL).  It  does
        not set errno.
 
        The function set_menu_mark may return the following error codes:
@@ -102,9 +100,7 @@

                                                                                                                        SEE ALSO

                                                                                                                                curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     menu_mark(3x)
+ncurses 6.6                       2024-12-28                     menu_mark(3x)
                                                                                                                          diff --git a/doc/html/man/menu_new.3x.html b/doc/html/man/menu_new.3x.html index e53eacb..87178bf 100644 --- a/doc/html/man/menu_new.3x.html +++ b/doc/html/man/menu_new.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_new.3x,v 1.35 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_new.3x,v 1.37 2024/12/28 21:26:21 tom Exp @ --> -menu_new 3x 2024-03-16 ncurses 6.5 Library calls +menu_new 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                          menu_new 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                          +

                                                                                                                          menu_new 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                           menu_new(3x)                     Library calls                    menu_new(3x)
 
 
-
-

                                                                                                                          NAME

                                                                                                                                  new_menu, free_menu - create and destroy menus
 
@@ -59,14 +57,14 @@

                                                                                                                          DESCRIPTION

                                                                                                                                  The  function new_menu creates a new menu connected to a specified item
-       pointer array (which must be NULL-terminated).
+       pointer array (which must be NULL-terminated).
 
        The function free_menu disconnects menu from its item array  and  frees
        the storage allocated for the menu.

                                                                                                                          RETURN VALUE

                                                                                                                          -       The  function  new_menu returns NULL on error.  It sets errno according
+       The  function  new_menu returns NULL on error.  It sets errno according
        to the function's failure:
 
        E_NOT_CONNECTED
@@ -102,9 +100,7 @@

                                                                                                                          SEE ALSO

                                                                                                                                  curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                      menu_new(3x)
+ncurses 6.6                       2024-12-28                      menu_new(3x)
                                                                                                                            diff --git a/doc/html/man/menu_opts.3x.html b/doc/html/man/menu_opts.3x.html index 453526a..b0d9485 100644 --- a/doc/html/man/menu_opts.3x.html +++ b/doc/html/man/menu_opts.3x.html @@ -1,6 +1,6 @@ -menu_opts 3x 2024-03-16 ncurses 6.5 Library calls +menu_opts 3x 2025-01-18 ncurses 6.6 Library calls -

                                                                                                                            menu_opts 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                            +

                                                                                                                            menu_opts 3x 2025-01-18 ncurses 6.6 Library calls

                                                                                                                             menu_opts(3x)                    Library calls                   menu_opts(3x)
 
 
-
-

                                                                                                                            NAME

                                                                                                                                    set_menu_opts,  menu_opts_on,  menu_opts_off,  menu_opts  - set and get
        menu options
@@ -63,7 +61,7 @@

                                                                                                                            DESCRIPTION

                                                                                                                                    The function set_menu_opts sets all the given menu's option bits  (menu
-       option bits may be logically-OR'ed together).
+       option bits may be logically "or"-ed together).
 
        The  function  menu_opts_on  turns on the given option bits, and leaves
        others alone.
@@ -126,9 +124,7 @@

                                                                                                                            SEE ALSO

                                                                                                                                    curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     menu_opts(3x)
+ncurses 6.6                       2025-01-18                     menu_opts(3x)
                                                                                                                              diff --git a/doc/html/man/menu_pattern.3x.html b/doc/html/man/menu_pattern.3x.html index 34d6f98..cc6fa5e 100644 --- a/doc/html/man/menu_pattern.3x.html +++ b/doc/html/man/menu_pattern.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_pattern.3x,v 1.38 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_pattern.3x,v 1.40 2024/12/28 21:26:21 tom Exp @ --> -menu_pattern 3x 2024-03-16 ncurses 6.5 Library calls +menu_pattern 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                              menu_pattern 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                              +

                                                                                                                              menu_pattern 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                               menu_pattern(3x)                 Library calls                menu_pattern(3x)
 
 
-
-

                                                                                                                              NAME

                                                                                                                                      set_menu_pattern, menu_pattern - set and get a menu's pattern buffer
 
@@ -70,8 +68,8 @@

                                                                                                                              RETURN VALUE

                                                                                                                              -       The  function menu_pattern returns a pointer, which is NULL if the menu
-       parameter is NULL.  Otherwise, it is a pointer to  a  string  which  is
+       The  function menu_pattern returns a pointer, which is NULL if the menu
+       parameter is NULL.  Otherwise, it is a pointer to  a  string  which  is
        empty if no pattern has been set.  It does not set errno.
 
        The function set_menu_pattern may return the following error codes:
@@ -107,9 +105,7 @@

                                                                                                                              SEE ALSO

                                                                                                                                      curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                  menu_pattern(3x)
+ncurses 6.6                       2024-12-28                  menu_pattern(3x)
                                                                                                                                diff --git a/doc/html/man/menu_post.3x.html b/doc/html/man/menu_post.3x.html index 6d48f77..6e67aab 100644 --- a/doc/html/man/menu_post.3x.html +++ b/doc/html/man/menu_post.3x.html @@ -34,18 +34,16 @@ -menu_post 3x 2024-03-16 ncurses 6.5 Library calls +menu_post 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                                                                                menu_post 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                +

                                                                                                                                menu_post 3x 2024-03-16 ncurses 6.6 Library calls

                                                                                                                                 menu_post(3x)                    Library calls                   menu_post(3x)
 
 
-
-

                                                                                                                                NAME

                                                                                                                                        post_menu,   unpost_menu   -  write  or  erase  menus  from  associated
        subwindows
@@ -60,7 +58,7 @@

                                                                                                                                DESCRIPTION

                                                                                                                                        The function post_menu displays a menu to its associated subwindow.  To
-       trigger  physical  display  of  the  subwindow, use refresh(3x) or some
+       trigger physical display of the  subwindow,  use  refresh(3x)  or  some
        equivalent curses routine (the implicit doupdate triggered by an curses
        input  request  will do).  post_menu resets the selection status of all
        items.
@@ -109,9 +107,7 @@

                                                                                                                                SEE ALSO

                                                                                                                                        curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     menu_post(3x)
+ncurses 6.6                       2024-03-16                     menu_post(3x)
                                                                                                                                  diff --git a/doc/html/man/menu_requestname.3x.html b/doc/html/man/menu_requestname.3x.html index 0a06ada..afcd06b 100644 --- a/doc/html/man/menu_requestname.3x.html +++ b/doc/html/man/menu_requestname.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_requestname.3x,v 1.33 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_requestname.3x,v 1.35 2024/12/28 21:26:21 tom Exp @ --> -menu_requestname 3x 2024-03-16 ncurses 6.5 Library calls +menu_requestname 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                  menu_requestname 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                  +

                                                                                                                                  menu_requestname 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                   menu_requestname(3x)             Library calls            menu_requestname(3x)
 
 
-
-

                                                                                                                                  NAME

                                                                                                                                          menu_request_by_name, menu_request_name - handle printable menu request
        names
@@ -59,22 +57,22 @@

                                                                                                                                  DESCRIPTION

                                                                                                                                  -       The function menu_request_name returns the printable  name  of  a  menu
+       The  function  menu_request_name  returns  the printable name of a menu
        request code.
-       The  function  menu_request_by_name  searches  in  the name-table for a
-       request with the given name and returns its  request  code.   Otherwise
+       The function menu_request_by_name searches  in  the  name-table  for  a
+       request  with  the  given name and returns its request code.  Otherwise
        E_NO_MATCH is returned.

                                                                                                                                  RETURN VALUE

                                                                                                                                  -       menu_request_name   returns   NULL   on   error   and   sets  errno  to
+       menu_request_name  returns  NULL   on   error   and   sets   errno   to
        E_BAD_ARGUMENT.
-       menu_request_by_name returns E_NO_MATCH on  error.   It  does  not  set
+       menu_request_by_name  returns  E_NO_MATCH  on  error.   It does not set
        errno.

                                                                                                                                  PORTABILITY

                                                                                                                                  -       These  routines  are  specific  to ncurses.  They were not supported on
+       These routines are specific to ncurses.  They  were  not  supported  on
        Version 7, BSD or System V implementations.  It is recommended that any
        code depending on them be conditioned using NCURSES_VERSION.
 
@@ -87,9 +85,7 @@

                                                                                                                                  SEE ALSO

                                                                                                                                          curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16              menu_requestname(3x)
+ncurses 6.6                       2024-12-28              menu_requestname(3x)
                                                                                                                                    diff --git a/doc/html/man/menu_spacing.3x.html b/doc/html/man/menu_spacing.3x.html index 5526b4d..8c9a834 100644 --- a/doc/html/man/menu_spacing.3x.html +++ b/doc/html/man/menu_spacing.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_spacing.3x,v 1.37 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_spacing.3x,v 1.39 2024/12/28 21:26:21 tom Exp @ --> -menu_spacing 3x 2024-03-16 ncurses 6.5 Library calls +menu_spacing 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                    menu_spacing 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                    +

                                                                                                                                    menu_spacing 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                     menu_spacing(3x)                 Library calls                menu_spacing(3x)
 
 
-
-

                                                                                                                                    NAME

                                                                                                                                            set_menu_spacing,  menu_spacing  -  set  and  get  spacing between menu
        items.
@@ -70,24 +68,24 @@
        columns).
 
        spc_description
-              controls the number of spaces between an item name and  an  item
-              description.   It  must  not  be  larger than TABSIZE.  The menu
+              controls  the  number of spaces between an item name and an item
+              description.  It must not be  larger  than  TABSIZE.   The  menu
               system  puts  in  the  middle  of  this  spacing  area  the  pad
               character.  The remaining parts are filled with spaces.
 
        spc_rows
-              controls  the number of rows that are used for an item.  It must
-              not be larger than 3.  The menu system inserts the  blank  lines
+              controls the number of rows that are used for an item.  It  must
+              not  be  larger than 3.  The menu system inserts the blank lines
               between item rows, these lines will contain the pad character in
               the appropriate positions.
 
        spc_columns
               controls the number of blanks between columns of items.  It must
-              not  be  larger  than TABSIZE.  A value of 0 for all the spacing
+              not be larger than TABSIZE.  A value of 0 for  all  the  spacing
               values resets them to the default, which is 1 for all of them.
 
        The function menu_spacing returns the spacing information for the menu.
-       If  a  pointer  is  NULL,  the  corresponding information is simply not
+       If  a  pointer  is  NULL,  the  corresponding information is simply not
        returned.
 
 
@@ -98,7 +96,7 @@

                                                                                                                                    PORTABILITY

                                                                                                                                    -       These routines are specific to ncurses.  They  were  not  supported  on
+       These  routines  are  specific  to ncurses.  They were not supported on
        Version 7, BSD or System V implementations.  It is recommended that any
        code depending on them be conditioned using NCURSES_VERSION.
 
@@ -111,9 +109,7 @@

                                                                                                                                    SEE ALSO

                                                                                                                                            curses(3x), curs_variables(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                  menu_spacing(3x)
+ncurses 6.6                       2024-12-28                  menu_spacing(3x)
                                                                                                                                      diff --git a/doc/html/man/menu_userptr.3x.html b/doc/html/man/menu_userptr.3x.html index d2b52f1..65e4b74 100644 --- a/doc/html/man/menu_userptr.3x.html +++ b/doc/html/man/menu_userptr.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_userptr.3x,v 1.33 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_userptr.3x,v 1.35 2024/12/28 21:26:21 tom Exp @ --> -menu_userptr 3x 2024-03-16 ncurses 6.5 Library calls +menu_userptr 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                      menu_userptr 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                      +

                                                                                                                                      menu_userptr 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                       menu_userptr(3x)                 Library calls                menu_userptr(3x)
 
 
-
-

                                                                                                                                      NAME

                                                                                                                                              set_menu_userptr, menu_userptr - associate application data with a menu
        item
@@ -59,20 +57,20 @@

                                                                                                                                      DESCRIPTION

                                                                                                                                      -       Every menu and every menu item has a field that can  be  used  to  hold
-       application-specific  data  (that  is,  the  menu-driver code leaves it
+       Every  menu  and  every  menu item has a field that can be used to hold
+       application-specific data (that is,  the  menu-driver  code  leaves  it
        alone).  These functions get and set the menu user pointer field.

                                                                                                                                      RETURN VALUE

                                                                                                                                      -       menu_userptr returns a pointer (which may be NULL).  It  does  not  set
+       menu_userptr  returns  a  pointer (which may be NULL).  It does not set
        errno.
 
        set_menu_userptr returns E_OK (success).

                                                                                                                                      PORTABILITY

                                                                                                                                      -       These  routines  emulate  the  System  V  menu  library.  They were not
+       These routines emulate the  System  V  menu  library.   They  were  not
        supported on Version 7 or BSD versions.
 
        The user pointer is a void pointer.  We chose not to leave it as a char
@@ -87,9 +85,7 @@

                                                                                                                                      SEE ALSO

                                                                                                                                              curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                  menu_userptr(3x)
+ncurses 6.6                       2024-12-28                  menu_userptr(3x)
                                                                                                                                        diff --git a/doc/html/man/menu_win.3x.html b/doc/html/man/menu_win.3x.html index 9688e0f..27d2885 100644 --- a/doc/html/man/menu_win.3x.html +++ b/doc/html/man/menu_win.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: menu_win.3x,v 1.32 2024/03/16 15:35:01 tom Exp @ + * @Id: menu_win.3x,v 1.34 2024/12/28 21:26:21 tom Exp @ --> -menu_win 3x 2024-03-16 ncurses 6.5 Library calls +menu_win 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                        menu_win 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                        +

                                                                                                                                        menu_win 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                         menu_win(3x)                     Library calls                    menu_win(3x)
 
 
-
-

                                                                                                                                        NAME

                                                                                                                                                menu_win - make and break menu window and subwindow associations
 
@@ -72,8 +70,8 @@
        necessary to set either window; by default, the driver code uses stdscr
        for both.
 
-       In the set_ functions, window argument of NULL is treated as though  it
-       were stsdcr.  A menu argument of NULL is treated as a request to change
+       In  the set_ functions, window argument of NULL is treated as though it
+       were stsdcr.  A menu argument of NULL is treated as a request to change
        the system default menu window or subwindow.
 
        The function scale_menu returns  the  minimum  size  required  for  the
@@ -81,7 +79,7 @@

                                                                                                                                        RETURN VALUE

                                                                                                                                        -       Routines  that  return  pointers  return  NULL on error.  Routines that
+       Routines  that  return  pointers  return  NULL on error.  Routines that
        return an integer return one of the following error codes:
 
        E_OK The routine succeeded.
@@ -112,9 +110,7 @@

                                                                                                                                        SEE ALSO

                                                                                                                                                curses(3x), curs_variables(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                      menu_win(3x)
+ncurses 6.6                       2024-12-28                      menu_win(3x)
                                                                                                                                          diff --git a/doc/html/man/mitem_current.3x.html b/doc/html/man/mitem_current.3x.html index ea8a33f..161e989 100644 --- a/doc/html/man/mitem_current.3x.html +++ b/doc/html/man/mitem_current.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: mitem_current.3x,v 1.37 2024/03/16 15:35:01 tom Exp @ + * @Id: mitem_current.3x,v 1.39 2024/12/28 21:26:21 tom Exp @ --> -mitem_current 3x 2024-03-16 ncurses 6.5 Library calls +mitem_current 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                          mitem_current 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                          +

                                                                                                                                          mitem_current 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                           mitem_current(3x)                Library calls               mitem_current(3x)
 
 
-
-

                                                                                                                                          NAME

                                                                                                                                                  mitem_current - set and get current_menu_item
 
@@ -68,21 +66,21 @@
        current item in the given menu.
 
        The function set_top_row sets the top row of the menu to show the given
-       row (the top row is initially 0, and is reset to  this  value  whenever
-       the  O_ROWMAJOR option is toggled).  The item leftmost on the given row
-       becomes current.  The function top_row returns the number  of  the  top
+       row  (the  top  row is initially 0, and is reset to this value whenever
+       the O_ROWMAJOR option is toggled).  The item leftmost on the given  row
+       becomes  current.   The  function top_row returns the number of the top
        menu row being displayed.
 
-       The  function item_index returns the (zero-origin) index of item in the
+       The function item_index returns the (zero-origin) index of item in  the
        menu's item pointer list.

                                                                                                                                          RETURN VALUE

                                                                                                                                          -       current_item returns a pointer (which may be NULL).  It  does  not  set
+       current_item  returns  a  pointer (which may be NULL).  It does not set
        errno.
 
-       top_row  and  item_index return ERR (the general curses error value) if
-       their menu parameter is NULL.
+       top_row and item_index return ERR (the general curses error  value)  if
+       their menu parameter is NULL.
 
        set_current_item and set_top_row return one of the following:
 
@@ -102,10 +100,10 @@

                                                                                                                                          PORTABILITY

                                                                                                                                          -       These routines emulate the  System  V  menu  library.   They  were  not
+       These  routines  emulate  the  System  V  menu  library.  They were not
        supported on Version 7 or BSD versions.
 
-       The   SVr4   menu  library  documentation  specifies  the  top_row  and
+       The  SVr4  menu  library  documentation  specifies  the   top_row   and
        index_item error value as -1 (which is the value of ERR).
 
 
@@ -117,9 +115,7 @@

                                                                                                                                          SEE ALSO

                                                                                                                                                  curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                 mitem_current(3x)
+ncurses 6.6                       2024-12-28                 mitem_current(3x)
                                                                                                                                            diff --git a/doc/html/man/mitem_name.3x.html b/doc/html/man/mitem_name.3x.html index 1ff53c8..e96ac6f 100644 --- a/doc/html/man/mitem_name.3x.html +++ b/doc/html/man/mitem_name.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: mitem_name.3x,v 1.31 2024/03/16 15:35:01 tom Exp @ + * @Id: mitem_name.3x,v 1.33 2024/12/28 21:26:21 tom Exp @ --> -mitem_name 3x 2024-03-16 ncurses 6.5 Library calls +mitem_name 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                            mitem_name 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                            +

                                                                                                                                            mitem_name 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                             mitem_name(3x)                   Library calls                  mitem_name(3x)
 
 
-
-

                                                                                                                                            NAME

                                                                                                                                                    item_name, item_description - get menu item name and description fields
 
@@ -64,12 +62,12 @@

                                                                                                                                            RETURN VALUE

                                                                                                                                            -       These routines return a pointer (which may be NULL).  They do  not  set
+       These  routines  return a pointer (which may be NULL).  They do not set
        errno.

                                                                                                                                            PORTABILITY

                                                                                                                                            -       These  routines  emulate  the  System  V  menu  library.  They were not
+       These routines emulate the  System  V  menu  library.   They  were  not
        supported on Version 7 or BSD versions.
 
 
@@ -81,9 +79,7 @@

                                                                                                                                            SEE ALSO

                                                                                                                                                    curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                    mitem_name(3x)
+ncurses 6.6                       2024-12-28                    mitem_name(3x)
                                                                                                                                              diff --git a/doc/html/man/mitem_new.3x.html b/doc/html/man/mitem_new.3x.html index b4ed667..bb1f258 100644 --- a/doc/html/man/mitem_new.3x.html +++ b/doc/html/man/mitem_new.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: mitem_new.3x,v 1.36 2024/03/16 15:35:01 tom Exp @ + * @Id: mitem_new.3x,v 1.38 2024/12/28 21:26:21 tom Exp @ --> -mitem_new 3x 2024-03-16 ncurses 6.5 Library calls +mitem_new 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                              mitem_new 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                              +

                                                                                                                                              mitem_new 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                               mitem_new(3x)                    Library calls                   mitem_new(3x)
 
 
-
-

                                                                                                                                              NAME

                                                                                                                                                      new_item, free_item - create and destroy menu items
 
@@ -69,7 +67,7 @@

                                                                                                                                              RETURN VALUE

                                                                                                                                              -       The  function  new_item returns NULL on error.  It sets errno according
+       The  function  new_item returns NULL on error.  It sets errno according
        to the function's failure:
 
        E_BAD_ARGUMENT
@@ -105,9 +103,7 @@

                                                                                                                                              SEE ALSO

                                                                                                                                                      curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                     mitem_new(3x)
+ncurses 6.6                       2024-12-28                     mitem_new(3x)
                                                                                                                                                diff --git a/doc/html/man/mitem_opts.3x.html b/doc/html/man/mitem_opts.3x.html index 537a913..6375a78 100644 --- a/doc/html/man/mitem_opts.3x.html +++ b/doc/html/man/mitem_opts.3x.html @@ -1,6 +1,6 @@ -mitem_opts 3x 2024-03-16 ncurses 6.5 Library calls +mitem_opts 3x 2025-01-18 ncurses 6.6 Library calls -

                                                                                                                                                mitem_opts 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                +

                                                                                                                                                mitem_opts 3x 2025-01-18 ncurses 6.6 Library calls

                                                                                                                                                 mitem_opts(3x)                   Library calls                  mitem_opts(3x)
 
 
-
-

                                                                                                                                                NAME

                                                                                                                                                        set_item_opts,  item_opts_on,  item_opts_off,  item_opts  - set and get
        menu item options
@@ -63,7 +61,7 @@

                                                                                                                                                DESCRIPTION

                                                                                                                                                        The function set_item_opts sets all the given item's option bits  (menu
-       option bits may be logically-OR'ed together).
+       option bits may be logically "or"-ed together).
 
        The  function  item_opts_on  turns on the given option bits, and leaves
        others alone.
@@ -100,9 +98,7 @@

                                                                                                                                                SEE ALSO

                                                                                                                                                        curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                    mitem_opts(3x)
+ncurses 6.6                       2025-01-18                    mitem_opts(3x)
                                                                                                                                                  diff --git a/doc/html/man/mitem_userptr.3x.html b/doc/html/man/mitem_userptr.3x.html index afb442d..6178989 100644 --- a/doc/html/man/mitem_userptr.3x.html +++ b/doc/html/man/mitem_userptr.3x.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: mitem_userptr.3x,v 1.34 2024/03/16 15:35:01 tom Exp @ + * @Id: mitem_userptr.3x,v 1.36 2024/12/28 21:26:21 tom Exp @ --> -mitem_userptr 3x 2024-03-16 ncurses 6.5 Library calls +mitem_userptr 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                                  mitem_userptr 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                  +

                                                                                                                                                  mitem_userptr 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                                   mitem_userptr(3x)                Library calls               mitem_userptr(3x)
 
 
-
-

                                                                                                                                                  NAME

                                                                                                                                                          set_item_userptr, item_userptr - associate application data with a menu
        item
@@ -59,20 +57,20 @@

                                                                                                                                                  DESCRIPTION

                                                                                                                                                  -       Every menu item has a field that  can  be  used  to  hold  application-
-       specific  data  (that is, the menu-driver code leaves it alone).  These
+       Every  menu  item  has  a  field  that can be used to hold application-
+       specific data (that is, the menu-driver code leaves it  alone).   These
        functions get and set that field.

                                                                                                                                                  RETURN VALUE

                                                                                                                                                  -       The function item_userptr returns a pointer (possibly NULL).   It  does
+       The  function  item_userptr returns a pointer (possibly NULL).  It does
        not set errno.
 
        The set_item_userptr always returns E_OK (success).

                                                                                                                                                  PORTABILITY

                                                                                                                                                  -       These  routines  emulate  the  System  V  menu  library.  They were not
+       These routines emulate the  System  V  menu  library.   They  were  not
        supported on Version 7 or BSD versions.
 
        The user pointer is a void pointer.  We chose not to leave it as a char
@@ -87,9 +85,7 @@

                                                                                                                                                  SEE ALSO

                                                                                                                                                          curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                 mitem_userptr(3x)
+ncurses 6.6                       2024-12-28                 mitem_userptr(3x)
                                                                                                                                                    diff --git a/doc/html/man/mitem_value.3x.html b/doc/html/man/mitem_value.3x.html index 01ce5d5..f9ed1b0 100644 --- a/doc/html/man/mitem_value.3x.html +++ b/doc/html/man/mitem_value.3x.html @@ -34,18 +34,16 @@ -mitem_value 3x 2024-03-16 ncurses 6.5 Library calls +mitem_value 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                                                                                                    mitem_value 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                    +

                                                                                                                                                    mitem_value 3x 2024-03-16 ncurses 6.6 Library calls

                                                                                                                                                     mitem_value(3x)                  Library calls                 mitem_value(3x)
 
 
-
-

                                                                                                                                                    NAME

                                                                                                                                                            set_item_value, item_value - set and get menu item values
 
@@ -59,7 +57,7 @@

                                                                                                                                                    DESCRIPTION

                                                                                                                                                            If you turn off the menu option O_ONEVALUE (e.g., with set_menu_opts or
-       menu_opts_off; see menu_opts(3x)), the menu becomes multi-valued;  that
+       menu_opts_off;  see menu_opts(3x)), the menu becomes multi-valued; that
        is, more than one item may simultaneously be selected.
 
        In a multi_valued menu, you can used set_item_value to select the given
@@ -92,9 +90,7 @@

                                                                                                                                                    SEE ALSO

                                                                                                                                                            curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                   mitem_value(3x)
+ncurses 6.6                       2024-03-16                   mitem_value(3x)
                                                                                                                                                      diff --git a/doc/html/man/mitem_visible.3x.html b/doc/html/man/mitem_visible.3x.html index 8224323..be2159d 100644 --- a/doc/html/man/mitem_visible.3x.html +++ b/doc/html/man/mitem_visible.3x.html @@ -34,18 +34,16 @@ -mitem_visible 3x 2024-03-16 ncurses 6.5 Library calls +mitem_visible 3x 2024-03-16 ncurses 6.6 Library calls -

                                                                                                                                                      mitem_visible 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                      +

                                                                                                                                                      mitem_visible 3x 2024-03-16 ncurses 6.6 Library calls

                                                                                                                                                       mitem_visible(3x)                Library calls               mitem_visible(3x)
 
 
-
-

                                                                                                                                                      NAME

                                                                                                                                                              item_visible - check visibility of a menu item
 
@@ -75,9 +73,7 @@

                                                                                                                                                      SEE ALSO

                                                                                                                                                              curses(3x), menu(3x)
 
-
-
-ncurses 6.5                       2024-03-16                 mitem_visible(3x)
+ncurses 6.6                       2024-03-16                 mitem_visible(3x)
                                                                                                                                                        diff --git a/doc/html/man/ncurses.3x.html b/doc/html/man/ncurses.3x.html index 9b061ac..b27c838 100644 --- a/doc/html/man/ncurses.3x.html +++ b/doc/html/man/ncurses.3x.html @@ -1,7 +1,7 @@ -ncurses 3x 2024-04-27 ncurses 6.5 Library calls +ncurses 3x 2025-11-11 ncurses 6.6 Library calls -

                                                                                                                                                        ncurses 3x 2024-04-27 ncurses 6.5 Library calls

                                                                                                                                                        +

                                                                                                                                                        ncurses 3x 2025-11-11 ncurses 6.6 Library calls

                                                                                                                                                         ncurses(3x)                      Library calls                     ncurses(3x)
 
 
-
-

                                                                                                                                                        NAME

                                                                                                                                                                ncurses - character-cell terminal interface with optimized output
 
@@ -57,24 +55,23 @@

                                                                                                                                                        DESCRIPTION

                                                                                                                                                                The  "new  curses" library offers the programmer a terminal-independent
-       means of reading keyboard and mouse input and  updating  character-cell
-       terminals  with  output  optimized to minimize screen updates.  ncurses
+       means of reading keyboard and mouse input and writing to character-cell
+       displays with output optimized to  minimize  screen  updates.   ncurses
        replaces the curses libraries from System V Release 4 Unix ("SVr4") and
        4.4BSD  Unix,  the  development  of  which  ceased  in the 1990s.  This
-       document describes ncurses version 6.5 (patch 20240427).
+       document describes ncurses version 6.6 (patch 20251230).
 
        ncurses permits control of the terminal screen's contents;  abstraction
-       and  subdivision thereof with windows and pads; the reading of terminal
-       input; control of terminal input and output options; environment  query
-       routines;  color  manipulation;  the  definition  and use of soft label
-       keys; terminfo capability access; a  termcap  compatibility  interface;
-       and  an  abstraction  of the system's API for manipulating the terminal
-       (such as termios(3)).
+       and  subdivision thereof with windows and pads; acquisition of keyboard
+       and mouse events; selection of color and rendering attributes (such  as
+       bold  or  underline); the definition and use of soft label keys; access
+       to the terminfo terminal capability database; a  termcap  compatibility
+       interface;  and an abstraction of the system's API for manipulating the
+       terminal (such as termios(3)).
 
-       ncurses implements the standard interface described  by  X/Open  Curses
-       Issue 7.   In  many  behavioral  details  not  standardized  by X/Open,
-       ncurses emulates the curses  library  of  SVr4  and  provides  numerous
-       useful extensions.
+       ncurses implements the interface described by  X/Open  Curses  Issue 7.
+       In many behavioral details not standardized by X/Open, ncurses emulates
+       the curses library of SVr4 and provides numerous useful extensions.
 
        ncurses  man  pages employ several sections to clarify matters of usage
        and interoperability with other curses implementations.
@@ -84,8 +81,8 @@
            underlying integral type or  the  availability  of  a  preprocessor
            macro  exclusive  of  a  function  definition  (which  prevents its
            address  from  being   taken).    This   section   also   describes
-           implementation  details  that will be significant to the programmer
-           but which are not standardized.
+           implementation  details of significance to the programmer but which
+           are not standardized.
 
        o   "EXTENSIONS" presents ncurses innovations beyond the X/Open  Curses
            standard  and/or  the  SVr4 curses implementation.  They are termed
@@ -97,7 +94,7 @@
            that should be considered when writing to a curses standard, or for
            multiple implementations.
 
-       o   "HISTORY" examines points of detail in  ncurses  and  other  curses
+       o   "HISTORY"  examines  points  of  detail in ncurses and other curses
            implementations over the decades of their development, particularly
            where precedent or inertia have frustrated better design (and, in a
            few cases, where such inertia has been overcome).
@@ -106,94 +103,100 @@
        option to your compiler or linker.  A debugging version of the  library
        may  be available; if so, link with it using -lncurses_g.  (Your system
        integrator may have installed these libraries such that you can use the
-       options  -lcurses and -lcurses_g, respectively.)  The ncurses_g library
-       generates trace logs (in a file called trace in the current  directory)
-       that  describe ncurses actions.  See section "ALTERNATE CONFIGURATIONS"
-       below.
+       options -lcurses and -lcurses_g, respectively.)  The ncurses_g  library
+       logs  events  describing  ncurses actions to a file called trace in the
+       application's working directory at  startup.   See  section  "ALTERNATE
+       CONFIGURATIONS" below.

                                                                                                                                                        Application Structure

                                                                                                                                                        -       A  curses  application  uses  information  from  the   system   locale;
+       A   curses   application  uses  information  from  the  system  locale;
        setlocale(3) prepares it for curses library calls.
 
            setlocale(LC_ALL, "");
 
-       If  the  locale  is  not  thus  initialized,  the  library assumes that
-       characters are printable as in ISO 8859-1, to work with certain  legacy
-       programs.   You  should initialize the locale; do not expect consistent
+       If the locale  is  not  thus  initialized,  the  library  assumes  that
+       characters  are printable as in ISO 8859-1, to work with certain legacy
+       programs.  You should initialize the locale; do not  expect  consistent
        behavior from the library when the locale has not been set up.
 
-       initscr(3x) or newterm(3x) must be called to initialize  curses  before
-       use of any functions that deal with windows and screens.
+       initscr(3x)  or  newterm(3x) must be called to initialize curses before
+       use of any functions that access or manipulate windows or screens.
 
-       To  get  character-at-a-time  input  without echoing--most interactive,
-       screen-oriented programs want this--use the following sequence.
+       To get character-at-a-time input without echoing --  most  interactive,
+       screen-oriented programs want this -- use the following sequence.
 
            initscr(); cbreak(); noecho();
 
-       Most applications perform further setup as follows.
+       Most applications would perform further setup as follows.
 
-           intrflush(stdscr, FALSE);
+           noqiflush();
            keypad(stdscr, TRUE);
 
-       A curses program then often enters an event loop of  some  sort.   Call
+       A  curses  program  then  often  enters  an  event-handling loop.  Call
        endwin(3x) before exiting.

                                                                                                                                                        Overview

                                                                                                                                                        -       A  curses  library abstracts the terminal screen by representing all or
-       part of it as a WINDOW data structure.  A window is a rectangular  grid
-       of  character  cells,  addressed  by row and column coordinates (y, x),
-       with the upper left corner as (0, 0).  A window called stdscr, the same
-       size  as  the terminal screen, is always available.  Create others with
-       newwin(3x).
+       A curses library abstracts the terminal with a SCREEN  data  structure,
+       and  represents  all  or  part  of  its display with WINDOW structures.
+       Distinct properties apply to each; for example, the line discipline  of
+       a  typical  Unix terminal driver is in one of three modes: raw, cbreak,
+       or canonical ("cooked").  In curses, the line discipline is a  property
+       of the screen, applying identically to all windows associated with it.
 
-       A curses library does not manage overlapping windows (but  see  below).
-       You  can either use stdscr to manage one screen-filling window, or tile
-       the screen into non-overlapping windows and  not  use  stdscr  at  all.
-       Mixing  the  two  approaches will result in unpredictable and undesired
+       A  window  is  a rectangular grid of character cells, addressed by line
+       and column coordinates (y, x), with the upper left corner as (0, 0).  A
+       window called stdscr, by default the same size as the terminal  screen,
+       is always available.  Create others with newwin(3x).
+
+       A  curses  library does not manage overlapping windows (but see below).
+       You can either use stdscr to manage one screen-filling window, or  tile
+       the  screen  into  non-overlapping  windows  and not use stdscr at all.
+       Mixing the two approaches will result in  unpredictable  and  undesired
        effects.
 
-       Functions permit manipulation of a window and  the  cursor  identifying
-       the  cell  within  it  at  which  the next output operation will occur.
-       Among those, the most basic are move(3x) and addch(3x): these place the
-       cursor and write a character to stdscr, respectively.
+       Functions  permit  manipulation  of a window and the cursor identifying
+       the cell within it at which  the  next  operation  will  occur.   Among
+       those,  the  most  basic  are  move(3x)  and addch(3x): these place the
+       cursor within and write a character to stdscr, respectively.
 
        Frequent changes to the terminal screen can cause unpleasant flicker or
-       inefficient use of the communication channel  to  the  device,  so  the
-       library  does  not generally update it automatically.  Therefore, after
+       inefficient use of the communication channel to the  device,  so  as  a
+       rule  the  library  does not update it automatically.  Therefore, after
        using curses functions to accumulate a set of desired updates that make
        sense to present together, call refresh(3x) to tell the library to make
        the user's screen look like stdscr.  The library optimizes  its  output
-       by  computing  a minimal number of operations to mutate the screen from
+       by  computing  a minimal volume of operations to mutate the screen from
        its  state  at  the  previous  refresh  to  the  new  one.    Effective
        optimization  demands  accurate  information about the terminal device:
        the management of such information is the province of the  terminfo(3x)
        API, a feature of every standard curses implementation.
 
-       Special windows called pads may also be manipulated.  These are windows
-       that are not constrained to the size of the terminal screen  and  whose
-       contents need not be completely displayed.  See curs_pad(3x).
+       Special  windows  called  pads  may also be manipulated.  These are not
+       constrained to the size of the terminal screen and their contents  need
+       not be completely displayed.  See curs_pad(3x).
 
-       In  addition  to drawing characters on the screen, rendering 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.  See curs_attr(3x).
+       Many  terminals  support configuration of character cell foreground and
+       background colors as well as  attributes,  which  cause  characters  to
+       render  in  such  modes  as boldfaced, underlined, or in reverse video.
+       See curs_color(3x) and curs_attr(3x).
 
-       curses predefines constants for a small set of  forms-drawing  graphics
-       corresponding  to  the  DEC Alternate Character Set (ACS), a feature of
-       VT100 and other terminals.  See waddch(3x).
+       curses defines constants to simplify access to a small  set  of  forms-
+       drawing  graphics  corresponding  to  the  DEC  Alternate Character Set
+       (ACS), a feature of VT100 and other terminals.  See addch(3x).
 
-       curses is implemented using the  operating  system's  terminal  driver;
-       keystroke  events are received not as scan codes but as byte sequences.
-       Graphical keycaps (alphanumeric and punctuation keys,  and  the  space)
-       appear  as-is.   Everything  else,  including  the  tab,  enter/return,
-       keypad, arrow, and function keys, appears as a control character  or  a
-       multibyte  escape  sequence.   curses  translates these into unique key
-       codes.  See getch(3x).
+       curses is implemented using the operating system's terminal driver; key
+       events are received not as scan  codes  but  as  byte  sequences.   The
+       driver  reports  graphical  keycaps (alphanumeric and punctuation keys,
+       and  the  space)  as-is.    Everything   else,   including   the   tab,
+       enter/return,  keypad, arrow, and function keys, appears to curses as a
+       control character or a multibyte escape sequence.  curses can translate
+       the latter into unique key codes.  See keypad(3x) and getch(3x).
 
        ncurses provides reimplementations of the SVr4 panel(3x), form(3x), and
-       menu(3x) libraries to ease construction of user interfaces with curses.
+       menu(3x)  libraries;  they  permit   overlapping   windows   and   ease
+       construction of user interfaces with curses.

                                                                                                                                                        Initialization

                                                                                                                                                        @@ -203,20 +206,20 @@
        automatically;  tset(1)  may   assist   with   troubleshooting   exotic
        situations.
 
-       If  you  change the terminal type, export the TERM environment variable
-       in the shell, then  run  tset(1)  or  the  "tput  init"  command.   See
-       subsection "Tabs and Initialization" of terminfo(5).
+       If  you  change  the  terminal type from a shell, export TERM, then run
+       tset(1)  or  the  "tput  init"  command.   See  subsection  "Tabs   and
+       Initialization" of terminfo(5).
 
        If  the  environment  variables  LINES  and  COLUMNS are set, or if the
        curses program is executing in a graphical windowing  environment,  the
        information  obtained  thence  overrides that obtained by terminfo.  An
-       ncurses extension supports resizable terminals; see wresize(3x).
+       ncurses   extension   supports   resizable   terminal   displays;   see
+       wresize(3x).
 
-       If the environment variable  TERMINFO  is  defined,  a  curses  program
-       checks  first  for  a  terminal  type  description  in  the location it
-       identifies.   TERMINFO  is  useful  for  developing  experimental  type
-       descriptions  or  when  write  permission to /usr/share/terminfo is not
-       available.
+       If  the  environment  variable  TERMINFO  is  defined, a curses program
+       checks first for  a  terminal  type  description  in  the  location  it
+       identifies.   TERMINFO  is  useful  for developing type descriptions or
+       when write permission to /usr/share/terminfo is not available.
 
        See section "ENVIRONMENT" below.
 
@@ -226,61 +229,92 @@
        alternatives  to the name of an elemental one.  Those prefixed with "w"
        require a WINDOW pointer argument;  those  with  a  "mv"  prefix  first
        perform cursor movement using wmove(3x); a "mvw" prefix indicates both.
-       The "w" function is typically the elemental one; the  removal  of  this
+       The  "w"  function  is typically the elemental one; the removal of this
        prefix usually indicates operation on stdscr.
 
-       Four functions prefixed with "p" require a pad argument.
+       Four functions prefixed with "p" require a pad argument; see below.
 
-       In  function  synopses,  ncurses man pages apply the following names to
-       parameters.
+       In function synopses, ncurses man pages apply the  following  names  to
+       parameters.  We introduce the character types in the next subsection.
 
-                       bf    bool (TRUE or FALSE)
-                       c     a char or int
-                       ch    a chtype
-                       wc    a wchar_t or wint_t
-                       wch   a cchar_t
-                       win   pointer to a WINDOW
-                       pad   pointer to a WINDOW that is a pad
+                bf     a bool (TRUE or FALSE)
+                c      a char or int
+                ch     a chtype
+                wc     a wchar_t or wint_t
+                wch    a cchar_t
+                win    pointer to a WINDOW
+                pad    pointer to a WINDOW that is a pad
+                pair   a foreground/background color pair identifier

                                                                                                                                                        Wide and Non-wide Character Configurations

                                                                                                                                                        -       This manual page describes functions that appear in  any  configuration
-       of  the  library.   There  are  two  common configurations; see section
-       "ALTERNATE CONFIGURATIONS" below.
+       This   man   page  primarily  surveys  functions  that  appear  in  any
+       configuration of the library.  There are two common configurations; for
+       others, see section "ALTERNATE CONFIGURATIONS" below.
 
        ncurses   is the library in its "non-wide" configuration, handling only
-                 eight-bit  characters.   It  stores a character combined with
-                 attributes in a chtype datum, which is often an alias of int.
+                 eight-bit characters.  It stores a  character  combined  with
+                 attributes  and  a  color  pair identifier in a chtype datum,
+                 which  is  often  an  alias  of  int.   A  string  of  curses
+                 characters  is  similar  to  a C char string; a chtype string
+                 ends with an integral 0, the null curses character.
 
-                 Attributes alone (with no  corresponding  character)  can  be
-                 stored  in  variables  of  chtype  or attr_t type.  In either
-                 case, they are represented as an integral bit mask.
+                 Attributes and a color pair identifier (with no corresponding
+                 character) can be stored in variables  of  chtype  or  attr_t
+                 type.   In either case, they are accessed via an integral bit
+                 mask.
 
-                 Each cell of a WINDOW is stored as a chtype.
+                 ncurses stores each cell of a WINDOW  as  a  chtype.   X/Open
+                 Curses  does  not  specify the sizes of the character code or
+                 color pair identifier, nor the quantity of attribute bits, in
+                 chtype; these  are  implementation-dependent.   ncurses  uses
+                 eight  bits for the character code.  An application requiring
+                 a wider character type, for instance  to  represent  Unicode,
+                 should use the wide-character API.
 
-       ncursesw  is the library in its  "wide"  configuration,  which  handles
+       ncursesw  is  the  library  in  its "wide" configuration, which handles
                  character encodings requiring a larger data type than char (a
-                 byte-sized type) can represent.  It adds about one third more
-                 calls  using  additional  data  types  that  can  store  such
-                 multibyte characters.
+                 byte-sized  type)  can  represent.   It  provides  additional
+                 functions that complement those in the non-wide library where
+                 the  size of the underlying character type is significant.  A
+                 somewhat regular naming convention relates many of  the  wide
+                 variants  to  their  non-wide  counterparts; where a non-wide
+                 function name contains "ch" or "str", prefix it with "_w"  to
+                 obtain  the  wide  counterpart.   For example, waddch becomes
+                 wadd_wch.  An exception  is  ins_nwstr  (and  its  variants),
+                 spelled  thus  instead  of "insn_wstr".  (Exceptions that add
+                 only "w" comprise addwstr, inwstr, and their variants.)
 
-                 cchar_t  corresponds to the non-wide configuration's  chtype.
-                          It  always  a structure type, because it stores more
-                          data than  fit  into  a  standard  scalar  type.   A
-                          character  code  may not be representable as a char,
-                          and moreover more than one character  may  occupy  a
-                          cell  (as  with  accent marks and other diacritics).
-                          Each  character  is  of  type  wchar_t;  a   complex
-                          character contains one spacing character and zero or
-                          more non-spacing characters (see below).  Attributes
-                          and  color data are stored in separate fields of the
-                          structure, not combined as in chtype.
+                 This convention is inapplicable  to  some  non-wide  function
+                 names,  so  other  transformations  are  used  for  the  wide
+                 configuration:  the  window  background  management  function
+                 "bkgd"   becomes  "bkgrnd";  the  window  border-drawing  and
+                 -clearing functions are suffixed with "_set";  and  character
+                 attribute   manipulation   functions   like  "attron"  become
+                 "attr_on".
 
-                 Each cell of a WINDOW is stored as a cchar_t.
+                 cchar_t  is a curses complex character and corresponds to the
+                          non-wide-character configuration's chtype.  It is  a
+                          structure type because it requires more storage than
+                          a standard scalar type offers.  A character code may
+                          not  be  representable  as a char, and moreover more
+                          than one character may occupy a cell (as with accent
+                          marks and other diacritics).  Each character  is  of
+                          type  wchar_t;  a  complex  character  contains  one
+                          spacing  character  and  zero  or  more  non-spacing
+                          characters   (see   below).   A  string  of  complex
+                          characters ends with a cchar_t whose wchar_t  member
+                          is  the null wide character.  Attributes and a color
+                          pair identifier are stored in separate fields of the
+                          structure,  not  combined  into  an  integer  as  in
+                          chtype.
 
+                 ncurses   stores   each  cell  of  a  WINDOW  as  a  cchar_t.
                  setcchar(3x) and  getcchar(3x)  store  and  retrieve  cchar_t
-                 data.   The  wide  library API of ncurses depends on two data
-                 types standardized by ISO C95.
+                 data.
+
+                 The  wide  library  API  of ncurses depends on two data types
+                 standardized by ISO C95.
 
                  wchar_t  stores a wide character.  Like chtype, it may be  an
                           alias  of int.  Depending on the character encoding,
@@ -292,36 +326,18 @@
                           base  glyph  with  which  it combines, and typically
                           does not advance the cursor.
 
-                 wint_t   can  store  a  wchar_t   or   the   constant   WEOF,
+                 wint_t   can  store  a  wchar_t   or   the   constant   WEOF,
                           analogously  to the int-sized character manipulation
-                          functions of ISO C and its constant EOF.
-
-                 The  wide  library   provides   additional   functions   that
-                 complement  those  in  the non-wide library where the size of
-                 the underlying character type  is  significant.   A  somewhat
-                 regular  naming  convention relates many of the wide variants
-                 to their non-wide counterparts;  where  a  non-wide  function
-                 name  contains  "ch"  or "str", prefix it with "_w" to obtain
-                 the wide counterpart.  For example, waddch becomes  wadd_wch.
-                 (Exceptions  that  add only "w" comprise addwstr, inwstr, and
-                 their variants.)
-
-                 This convention is inapplicable  to  some  non-wide  function
-                 names,  so  other  transformations  are  used  for  the  wide
-                 configuration:  the  window  background  management  function
-                 "bkgd"   becomes  "bkgrnd";  the  window  border-drawing  and
-                 -clearing functions are suffixed with "_set";  and  character
-                 attribute   manipulation   functions   like  "attron"  become
-                 "attr_on".
+                          functions of ISO C and its constant EOF.

                                                                                                                                                        Function Name Index

                                                                                                                                                                The following table lists the curses functions provided in the non-wide
-       and  wide  APIs  and  the  corresponding  man pages that describe them.
-       Those flagged with  "*"  are  ncurses-specific,  neither  described  by
+       and wide APIs and the  corresponding  man  pages  that  describe  them.
+       Those  flagged  with  "*"  are  ncurses-specific,  neither described by
        X/Open Curses nor present in SVr4.
 
-                    curses Function Name     Man Page
+                    curses Function Name     Man Page
                     ---------------------------------------------
                     COLOR_PAIR               curs_color(3x)
                     PAIR_NUMBER              curs_color(3x)
@@ -380,7 +396,6 @@
                     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)
@@ -446,7 +461,6 @@
                     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)
@@ -506,13 +520,12 @@
                     mvaddstr                 curs_addstr(3x)
                     mvaddwstr                curs_addwstr(3x)
                     mvchgat                  curs_attr(3x)
-                    mvcur                    curs_terminfo(3x)
+                    mvcur                    curs_kernel(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)
@@ -578,7 +591,6 @@
                     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)
@@ -644,7 +656,6 @@
                     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)
@@ -710,7 +721,6 @@
                     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)
@@ -776,7 +786,6 @@
                     wscanw                   curs_scanw(3x)
                     wscrl                    curs_scroll(3x)
                     wsetscrreg               curs_outopts(3x)
-
                     wstandend                curs_attr(3x)
                     wstandout                curs_attr(3x)
                     wsyncdown                curs_window(3x)
@@ -787,38 +796,40 @@
                     wvline                   curs_border(3x)
                     wvline_set               curs_border_set(3x)
 
-       ncurses's    screen-pointer   extension   adds   additional   functions
-       corresponding to many of the above, each  with  an  "_sp"  suffix;  see
+       ncurses's   screen-pointer   extension   adds   additional    functions
+       corresponding  to  many  of  the  above, each with an "_sp" suffix; see
        curs_sp_funcs(3x).
 
-       The  availability  of  some  extensions is configurable when ncurses is
-       compiled; see  sections  "ALTERNATE  CONFIGURATIONS"  and  "EXTENSIONS"
+       The availability of some extensions is  configurable  when  ncurses  is
+       compiled;  see  sections  "ALTERNATE  CONFIGURATIONS"  and "EXTENSIONS"
        below.

                                                                                                                                                        RETURN VALUE

                                                                                                                                                        -       Unless  otherwise  noted, functions that return an integer return OK on
-       success and ERR on failure.  Functions that return pointers return NULL
-       on  failure.   Typically,  ncurses  treats  a  null pointer passed as a
-       function parameter as a failure.  Functions prefixed  with  "mv"  first
-       perform  cursor movement and fail if the position (y, x) is outside the
-       window boundaries.
+       Unless otherwise noted,  functions  that  return  integers  return  the
+       constants  OK  on  success  and ERR on failure; see curs_variables(3x).
+       Functions that return  pointers  return  a  null  pointer  on  failure.
+       Typically, ncurses treats a null pointer passed as a function parameter
+       as  a  failure.   Functions  prefixed  with  "mv"  first perform cursor
+       movement and fail  if  the  position  (y,  x)  is  outside  the  window
+       boundaries.

                                                                                                                                                        ENVIRONMENT

                                                                                                                                                        -       The following  symbols  from  the  process  environment  customize  the
-       runtime   behavior   of  ncurses  applications.   The  library  may  be
-       configured  to  disregard  the   variables   TERMINFO,   TERMINFO_DIRS,
-       TERMPATH,  and  HOME,  if  the  user  is  the  superuser (root), or the
+       The  following  symbols  from  the  process  environment  customize the
+       runtime  behavior  of  ncurses  applications.   The  library   may   be
+       configured   to   disregard   the  variables  TERMINFO,  TERMINFO_DIRS,
+       TERMPATH, and HOME, if  the  user  is  the  superuser  (root),  or  the
        application uses setuid(2) or setgid(2).

                                                                                                                                                        BAUDRATE

                                                                                                                                                        -       The debugging library checks this variable  when  the  application  has
-       redirected  output  to a file.  Its integral value is used for the baud
-       rate.  If that value is absent or invalid,  ncurses  uses  9600.   This
-       feature  allows  testers  to  construct repeatable test cases that take
-       into account optimization decisions that depend on baud rate.
+       The  debugging  library  checks  this variable when the application has
+       redirected output to a file.  ncurses interprets its integral value  as
+       the  terminal's line speed in bits per second.  If that value is absent
+       or invalid, ncurses uses  9600.   This  feature  allows  developers  to
+       construct  repeatable  test  cases  that take into account optimization
+       decisions that depend on the terminal's line speed.

                                                                                                                                                        CC (command character)

                                                                                                                                                        @@ -826,16 +837,17 @@
        terminfo entries changes to the value of this variable.  Very few term-
        info entries provide this feature.
 
-       Because this name is also used in development environments to represent
-       the  C  compiler's  name,  ncurses  ignores  its value if it is not one
-       character in length.
+       Because this name is also used in development environments to store the
+       C compiler's name, ncurses ignores its value if it is not one character
+       in length.

                                                                                                                                                        COLUMNS

                                                                                                                                                        -       This  variable  specifies  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 COLUMNS
-       is not defined and the terminal's screen size is not available from the
+       This  variable  specifies  the  width of the screen in character cells.
+       Applications running in a windowing environment  usually  are  able  to
+       obtain  the  width  of the window in which they are executing.  ncurses
+       enforces an upper limit of 512 when reading the value.  If  COLUMNS  is
+       not  defined  and  the terminal's screen size is not available from the
        terminal driver, ncurses uses the size specified by the columns  (cols)
        capability  of  the  terminal type's entry in the terminfo database, if
        any.
@@ -863,17 +875,20 @@
        For curses to distinguish the ESC character  resulting  from  a  user's
        press  of  the  "Escape"  key on the input device from one beginning an
        escape sequence (as commonly produced by function keys), it waits after
-       receiving  the  escape  character  to  see  if  further  characters are
-       available on the input  stream  within  a  short  interval.   A  global
-       variable  ESCDELAY  stores  this interval in milliseconds.  The default
+       receiving the  escape  character  to  see  if  further  characters  are
+       available  on  the  input  stream  within  a  short interval.  A global
+       variable ESCDELAY stores this interval in  milliseconds.   The  default
        value of 1000 (one second) is adequate for most uses.  This environment
-       variable overrides it.
+       variable  overrides  it;  ncurses enforces an upper limit of 30,000 (30
+       seconds) when reading the value.
 
-       The  most common instance where you may wish to change this value is to
+       The most common instance where you may wish to change this value is  to
        work with a remote host over a slow communication channel.  If the host
        running  a  curses  application  does  not receive the characters of an
        escape sequence in a timely manner, the library can interpret  them  as
-       multiple key stroke events.
+       multiple key stroke events.  Conversely, a fast typist on a low-latency
+       connection  who  happens  to  input  an ESC followed by characters that
+       match an escape sequence may experience confusing application behavior.
 
        xterm(1) mouse events are a form of escape sequence; therefore, if your
        application makes heavy use  of  multiple-clicking,  you  may  wish  to
@@ -884,8 +899,9 @@
        either  form,  but  setting  the  environment  variable rather than the
        global variable does not create problems when compiling an application.
 
-       If keypad(3x) is disabled for the  curses  window  receiving  input,  a
-       program must disambiguate escape sequences itself.
+       If keypad(3x) is  disabled  for  the  curses  window  receiving  input,
+       ESCDELAY is irrelevant and a program must disambiguate escape sequences
+       itself.

                                                                                                                                                        HOME

                                                                                                                                                        @@ -917,8 +933,10 @@
 
        For  example,  to tell ncurses not to assume anything about the colors,
        use a value of "-1,-1".  To make the  default  color  scheme  green  on
-       black,  use  "2,0".   ncurses accepts integral values from -1 up to the
-       value of the terminfo max_colors (colors) capability.
+       black   on  a  terminal  that  uses  ANSI X3.64/ECMA-48/ISO 6429  color
+       assignments, use "2,0".  ncurses accepts integral values from -1 up  to
+       the  value  of  the  terminfo  max_colors  (colors)  capability for the
+       selected terminal type.

                                                                                                                                                        NCURSES_CONSOLE2

                                                                                                                                                        @@ -932,29 +950,31 @@

                                                                                                                                                        NCURSES_GPM_TERMS

                                                                                                                                                                (Linux  only) When ncurses is configured to use the GPM interface, this
-       variable may list one or more terminal names  against  which  the  TERM
-       variable  (see  below)  is  matched.   An  empty value disables the GPM
-       interface,  using  ncurses's  built-in  support  for   xterm(1)   mouse
-       protocols instead.  If the variable is absent, ncurses attempts to open
-       GPM if TERM contains "linux".
+       variable may list  one  or  more  terminal  type  names,  delimited  by
+       vertical  bars  (|) or colons (:), against which the TERM variable (see
+       below) is matched.  An empty value disables the  GPM  interface,  using
+       ncurses's  built-in  support  for xterm(1) mouse protocols instead.  If
+       the variable is absent, ncurses attempts to open GPM if  TERM  contains
+       "linux".

                                                                                                                                                        NCURSES_NO_HARD_TABS

                                                                                                                                                        -       ncurses may use tab characters in  cursor  movement  optimization.   In
-       some  cases,  your  terminal  driver may not handle them properly.  Set
+       ncurses  may  use  tab  characters in cursor movement optimization.  In
+       some cases, your terminal driver may not  handle  them  properly.   Set
        this environment variable to any value to disable the feature.  You can
        also adjust your stty(1) settings to avoid the problem.

                                                                                                                                                        NCURSES_NO_MAGIC_COOKIE

                                                                                                                                                        -       Many  terminals  store  video  attributes  as a property of a character
+       Many  terminals  store  video  attributes  as properties of a character
        cell, as curses does.  Historically, some  recorded  changes  in  video
-       attributes  as  data  that  logically  occupies  character cells on the
-       display, switching attributes on or off, similarly to tags in a  markup
-       language;  these  are  termed "magic cookies", and must be subsequently
-       overprinted.  If the terminfo entry for your  terminal  type  does  not
-       adequately describe its handling of magic cookies, set this variable to
-       any value to instruct ncurses to disable attributes entirely.
+       attributes  as  data  that logically (but invisibly) occupied character
+       cells on the display, switching attributes on or off, similarly to tags
+       in a markup language, which then had to be overprinted  to  depict  the
+       cells'  desired  contents;  these  are  termed "magic cookies".  If the
+       terminfo entry for your terminal type does not adequately describe  its
+       handling  of  magic cookies, set this variable to any value to instruct
+       ncurses to disable attributes entirely.

                                                                                                                                                        NCURSES_NO_PADDING

                                                                                                                                                        @@ -964,47 +984,49 @@
        programs  can  duplicate  all  of  the important features of a hardware
        terminal, but often lack their limitations.  Chief among  these  absent
        drawbacks is the problem of data flow management; that is, limiting the
-       speed of communication to what the hardware  could  handle.   Unless  a
-       hardware  terminal  is  interfaced  into a terminal concentrator (which
-       does flow control), an application must manage flow control  itself  to
-       prevent overruns and data loss.
+       speed  of  communication  to  what the hardware could handle.  Unless a
+       hardware terminal is interfaced into  a  terminal  concentrator  (which
+       does  flow  control), an application must manage flow itself to prevent
+       overruns and data loss.
 
-       A  solution  that  comes  at  no hardware cost is for an application to
-       pause after directing a  terminal  to  execute  an  operation  that  it
-       performs  slowly,  such  as  clearing  the display.  Many terminal type
-       descriptions, including that for the VT100, embed delay  specifications
-       in  capabilities.   You  may  wish  to  use these terminal descriptions
-       without paying the performance penalty.  Set NCURSES_NO_PADDING to  any
-       value  to disable all but mandatory padding.  Mandatory padding is used
-       by such terminal capabilities as flash_screen (flash).
+       A solution that comes at no hardware cost  is  for  an  application  to
+       pause  transmission  after directing a terminal to execute an operation
+       that it performs slowly, such as clearing the display.   Many  terminal
+       type   descriptions,   including   that  for  the  VT100,  embed  delay
+       specifications in capabilities.  You may wish  to  use  these  terminal
+       descriptions    without    paying   the   performance   penalty.    Set
+       NCURSES_NO_PADDING to any value to disable all but  mandatory  padding.
+       Mandatory padding is used by such terminal capabilities as flash_screen
+       (flash).

                                                                                                                                                        NCURSES_NO_SETBUF

                                                                                                                                                        -       (Obsolete) Prior to internal changes developed in ncurses 5.9  (patches
-       20120825  through 20130126), the library used setbuf(3) to enable fully
-       buffered output when initializing the terminal.  This was done,  as  in
-       SVr4  curses,  to  increase performance.  For testing purposes, both of
-       ncurses and of certain applications, this feature  was  made  optional.
-       Setting  this  variable  disabled  output buffering, leaving the output
+       (Obsolete)  Prior to internal changes developed in ncurses 5.9 (patches
+       20120825 through 20130126), the library used setbuf(3) to enable  fully
+       buffered  output  when initializing the terminal.  This was done, as in
+       SVr4 curses, to increase performance.  For testing  purposes,  both  of
+       ncurses  and  of  certain applications, this feature was made optional.
+       Setting this variable disabled output  buffering,  leaving  the  output
        stream in the original (usually line-buffered) mode.
 
-       Nowadays, ncurses performs its own buffering and does not require  this
-       workaround;  it  does  not  modify the buffering of the standard output
-       stream.  This approach makes signal handling, as for  interrupts,  more
-       robust.   A  drawback  is  that  certain  unconventional programs mixed
-       stdio(3) calls with ncurses calls and (usually) got the  behavior  they
-       expected.   This  is  no longer the case; ncurses does not write to the
-       standard output file descriptor through a stdio-buffered stream.
+       Nowadays,  ncurses performs its own buffering and does not require this
+       workaround; it does not modify the buffering  of  the  standard  output
+       stream.   This  approach  makes  the  library's  handling  of keyboard-
+       initiated  signals  more  robust.    A   drawback   is   that   certain
+       unconventional  programs  mixed  stdio(3)  calls with ncurses calls and
+       (usually) got the behavior they expected.  This is no longer the  case;
+       ncurses does not write to the standard output file descriptor through a
+       stdio-buffered stream.
 
-       As a special case, low-level API calls such as putp(3x) still  use  the
-       standard  output stream.  High-level curses calls such as printw(3x) do
+       As  a  special case, low-level API calls such as putp(3x) still use the
+       standard output stream.  High-level curses calls such as printw(3x)  do
        not.

                                                                                                                                                        NCURSES_NO_UTF8_ACS

                                                                                                                                                        -       At initialization, ncurses inspects the TERM environment  variable  for
-       special   cases   where   VT100   forms-drawing   characters  (and  the
-       corresponding alternate character set terminfo capabilities) are  known
+       At  initialization,  ncurses inspects the TERM environment variable for
+       special  cases  where   VT100   forms-drawing   characters   (and   the
+       corresponding  alternate character set terminfo capabilities) are known
        to  be  unsupported  by  terminal  types  that  otherwise  claim  VT100
        compatibility.  Specifically, when running in a UTF-8 locale, the Linux
        virtual  console device and the GNU screen(1) program ignore them.  Set
@@ -1012,10 +1034,10 @@
        terminal's ACS support is broken; the library then outputs Unicode code
        points that correspond to the forms-drawing characters.  Set it to zero
        (or a non-integer) to disable the special check for terminal type names
-       matching "linux" or "screen", directing ncurses to assume that the  ACS
+       matching  "linux" or "screen", directing ncurses to assume that the ACS
        feature works if the terminal type description advertises it.
 
-       As  an  alternative  to  use  of  this  variable, ncurses checks for an
+       As an alternative to use  of  this  variable,  ncurses  checks  for  an
        extended terminfo numeric capability U8 that can be compiled using "tic
        -x".  Examples follow.
 
@@ -1071,8 +1093,8 @@
        the default location.
 
        o   Descriptions  in terminfo format are normally stored in a directory
-           tree using subdirectories named by the common first letters of  the
-           terminal types named therein.  This is the scheme used in System V.
+           tree using subdirectories named for the common first letters of the
+           terminal types named therein.  System V used this scheme.
 
        o   If ncurses is configured to use hashed databases, then TERMINFO may
            name its location,  such  as  /usr/share/terminfo.db,  rather  than
@@ -1080,8 +1102,7 @@
 
        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, and read it directly rather than using the terminfo
-       API.
+       the directory tree and read it directly, ignoring the terminfo API.
 
        o   If ncurses is configured with termcap support,  this  variable  may
            contain the location of a termcap file.
@@ -1093,10 +1114,10 @@
                   TERMINFO=$(infocmp -0 -Q2 -q)
                   export TERMINFO
 
-           The  compiled  description  is  used  only if it corresponds to the
+           ncurses uses the compiled description only if it corresponds to the
            terminal type identified by TERM.
 
-       Setting TERMINFO is the simplest, but  not  the  only,  way  to  direct
+       Setting  TERMINFO  is  the  simplest,  but  not the only, way to direct
        ncurses to a terminal database.  The search path is as follows.
 
        o   the last terminal database to which the running ncurses application
@@ -1110,7 +1131,7 @@
 
        o   location(s) configured and compiled into ncurses
 
-          o   /usr/share/terminfo
+           o   /usr/share/terminfo

                                                                                                                                                        TERMINFO_DIRS

                                                                                                                                                        @@ -1123,7 +1144,7 @@

                                                                                                                                                        TERMPATH

                                                                                                                                                                If TERMCAP does not hold a terminal type description or file name, then
-       ncurses  checks  the contents of TERMPATH, a list of locations, akin to
+       ncurses checks the contents of TERMPATH, a list of locations,  akin  to
        PATH, in which it searches for termcap terminal type descriptions.  The
        list items are separated by colons on Unix and semicolons on OS/2 EMX.
 
@@ -1139,93 +1160,103 @@
        particular significance to the application developer employing ncurses.
 
        --disable-overwrite
-            The standard include for ncurses is as noted in SYNOPSIS:
+            Avoid file name conflicts between ncurses and an  existing  curses
+            installation on the system.  The standard C preprocessor inclusion
+            for the curses library is as follows.
 
                 #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.,
+            If  ncurses  is  installed disabling overwrite, it puts its header
+            files in a subdirectory.  Here is an example.
 
                 #include <ncurses/curses.h>
 
-            It  also  omits  a  symbolic  link  which  would  allow you to use
-            -lcurses to build executables.
+            With --disable-overwrite, installation also omits a symbolic  link
+            that  would  cause  the  compiler's -lcurses option to link object
+            files with ncurses instead of the system curses library.
+
+            The directory used by this configuration of ncurses  is  shown  in
+            section "SYNOPSIS" above.
 
        --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
+            (default  for  ABI 6+  since  2023-10-21)  Enable support for wide
+            characters.  The configure script renames the ncurses library (and
+            the tinfo library, if --with-termlib is also specified), appending
+            "w".  An application desirous of wide-character support then  uses
+            -lncursesw  (or -ltinfow) instead of -lncurses (or -ltinfo) as its
+            linker option.  The ncurses++, panel, form, and menu libraries are
+            renamed similarly.
 
-                -lncurses
+            An application must also define certain C preprocessor symbols  to
+            enable  wide-character  features in curses header files to use the
+            extended (wide-character)  functions.   The  symbol  that  enables
+            these features has changed since X/Open Curses Issue 4.
 
-            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 X/Open Curses, Issue 4:
-
-            o   Originally, the wide-character  feature  required  the  symbol
-                _XOPEN_SOURCE_EXTENDED  but  that  was  only  valid  for  XPG4
+            o   Originally,  the  wide-character  feature  required the symbol
+                _XOPEN_SOURCE_EXTENDED, but  that  was  valid  only  for  XPG4
                 (1996).
 
-            o   Later, that was deemed conflicting with _XOPEN_SOURCE  defined
-                to 500.
+            o   Later, that was deemed conflicting with an _XOPEN_SOURCE value
+                of 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   As  of  mid-2018,  no ncurses feature requires a _XOPEN_SOURCE
+                value 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
+            o   Alternatively,  you  can  enable  the  feature   by   defining
+                NCURSES_WIDECHAR  with  the caveat that some header file other
+                than curses.h may require a specific value  for  _XOPEN_SOURCE
                 (or a system-specific symbol).
 
-            The curses.h header file installed for the wide-character  library
-            is  designed  to be compatible with the non-wide library's header.
-            Only the size of the WINDOW structure  differs;  few  applications
-            require more than pointers to WINDOWs.
+            The  curses.h header file installed for the wide-character library
+            is designed to be compatible with the non-wide  library's  header.
+            Only  the  size  of the WINDOW structure differs; few applications
+            require more than pointers to WINDOW.
 
-            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.
+            If ncurses's header files are installed  allowing  overwrite  (the
+            default,  but  see  --disable-overwrite above), the wide-character
+            library's headers should be installed last  by  packaging  systems
+            and  similar,  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).
+            Enable support for  multi-threaded  applications.   The  configure
+            script  renames  the  ncurses  library  (and the tinfo library, if
+            --with-termlib is also specified), appending "t" (before  any  "w"
+            added  by --enable-widec).  An application desirous of support for
+            multiple threads of execution then uses, for  example,  -lncursest
+            (or  -ltinfot)  instead  of  -lncurses  (or -ltinfo) as its linker
+            option.  The  ncurses++,  panel,  form,  and  menu  libraries  are
+            renamed similarly.
 
-            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
+            ncursest and ncursestw replace global variables such as LINES with
+            macros  allowing read-only access.  At the same time, they provide
+            functions to set these  values.   Very  few  applications  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.
+            Mandate compilation of the ncurses library (and the tinfo library,
+            if  --with-termlib is also specified) in the specified forms.  The
+            shared and normal (static) library names differ by their suffixes,
+            as  with  libncurses.so  and  libncurses.a.   The  debugging   and
+            profiling  libraries  add  a "_g" and a "_p" to the roots of these
+            respective names, forming libncurses_g.so and libncurses_p.a,  for
+            example.   The ncurses++, panel, form, and menu libraries are made
+            available similarly.
 
        --with-termlib
-            Low-level functions which do not depend upon whether  the  library
-            supports wide-characters, are provided in the tinfo library.
+            Provide ncurses's lower-level terminal interface functions  (those
+            that  do  not  depend  on the SCREEN and WINDOW abstractions) in a
+            library named tinfo.  This arrangement  reduces  an  application's
+            linking  and/or  loading  times  when it does not require curses's
+            higher-level features.
 
-            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.
+            The following pages document curses functions provided by tinfo.
 
-            Those functions are described in these pages:
-
-            o   curs_extend(3x) - miscellaneous curses extensions
+            o   curs_extend(3x) - miscellaneous ncurses extensions
 
             o   curs_inopts(3x) - curses input options
 
@@ -1240,10 +1271,13 @@
             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.
+            Expose the curses_trace(3x) function in the ncurses(w) shared  and
+            static libraries.  Normally, it is available only in the debugging
+            library.   (If  --with-termlib  is also specified, tinfo(w) rather
+            than ncurses(w) supplies the deprecated trace(3x)  function.)   An
+            application's configuration script should check for the function's
+            existence  rather  than  assuming its confinement to the debugging
+            library.

                                                                                                                                                        FILES

                                                                                                                                                        @@ -1265,7 +1299,7 @@
        o   to  reuse functions (for example, those that move the cursor before
            another operation), and
 
-       o   a few special cases.
+       o   in a few special cases.
 
        If the standard  output  file  descriptor  of  an  ncurses  program  is
        redirected  to  something  that  is  not a terminal device, the library
@@ -1277,7 +1311,7 @@

                                                                                                                                                        EXTENSIONS

                                                                                                                                                        -       ncurses enables an application  to  capture  mouse  events  on  certain
+       ncurses enables an application to capture  mouse  events  from  certain
        terminals, including xterm(1); see curs_mouse(3x).
 
        ncurses  provides  a  means of responding to window resizing events, as
@@ -1299,40 +1333,40 @@
        to  draw colored text on a background whose color is set independently,
        providing better control over color contrasts.  See default_colors(3x).
 
-       An  ncurses  application  can  eschew  knowledge  of  WINDOW  structure
-       internals, instead using accessor functions such as is_scrollok(3x).
+       An ncurses application  can  eschew  knowledge  of  SCREEN  and  WINDOW
+       structure   internals,   instead   using  accessor  functions  such  as
+       is_cbreak(3x) and is_scrollok(3x).
 
-       ncurses  enables  an  application  to  direct  application  output to a
-       printer attached to the terminal device; see curs_print(3x).
+       ncurses enables an application  to  direct  its  output  to  a  printer
+       attached to the terminal device; see curs_print(3x).
 
-       ncurses offers slk_attr(3x) as a counterpart of attr_get(3x) for  soft-
-       label  key lines, and extended_slk_color(3x) as a form of slk_color(3x)
-       that can gather color  information  from  them  when  many  colors  are
+       ncurses  offers slk_attr(3x) as a counterpart of attr_get(3x) for soft-
+       label key lines, and extended_slk_color(3x) as a form of  slk_color(3x)
+       that  can  gather  color  information  from  them  when many colors are
        supported.
 
-       Some  extensions  are available only if ncurses permits modification of
-       unctrl(3x)'s behavior; see use_legacy_coding(3x).  ncurses is  compiled
-       to support them; section "ALTERNATE CONFIGURATIONS" describes how.
+       ncurses   permits   modification   of   unctrl(3x)'s   behavior;    see
+       use_legacy_coding(3x).
 
-       o   Rudimentary   support   for   multi-threaded  applications  may  be
-           available; see curs_threads(3x).
+       Rudimentary  support  for multi-threaded applications may be available;
+       see curs_threads(3x).
 
-       o   Functions that ease the  management  of  multiple  screens  can  be
-           exposed; see curs_sp_funcs(3x).
+       Functions that ease the management of multiple screens can be  exposed;
+       see curs_sp_funcs(3x).
 
-       o   To aid applications to debug their memory usage, ncurses optionally
-           offers functions to more aggressively free  memory  it  dynamically
-           allocates itself; see curs_memleaks(3x).
+       To  aid  applications  to  debug their memory usage, ncurses optionally
+       offers functions  to  more  aggressively  free  memory  it  dynamically
+       allocates itself; see curs_memleaks(3x).
 
-       o   The   library  facilitates  auditing  and  troubleshooting  of  its
-           behavior; see curs_trace(3x).
+       The  library  facilitates auditing and troubleshooting of its behavior;
+       see curs_trace(3x).
 
-       o   The compiler option -DUSE_GETCAP causes the library to fall back to
-           reading /etc/termcap if the terminal setup code cannot find a term-
-           info 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  a  cost  in  memory  usage  and
-           application launch latency.
+       Compiling ncurses with the option -DUSE_GETCAP causes it to  fall  back
+       to  reading /etc/termcap if the terminal setup code cannot find a term-
+       info  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 a cost in  memory  usage  and  application
+       launch latency.
 
        PDCurses   and  NetBSD  curses  incorporate  some  ncurses  extensions.
        Individual man pages indicate where this is the case.
@@ -1343,7 +1377,7 @@
        The latter includes several additional features, such as wide-character
        and color support.  ncurses intends base-level conformance with  X/Open
        Curses,  and  supports  all  features  of its enhanced level except the
-       untic utility.
+       untic utility.
 
        Differences between X/Open Curses and ncurses  are  documented  in  the
        "PORTABILITY" sections of applicable man pages.
@@ -1357,14 +1391,14 @@
        as  those to WINDOW structures, to ensure that they are not null.  This
        is done primarily 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 occurred.  Relying on  this  (or  some
-       other)   extension   adversely   affects   the  portability  of  curses
-       applications.
+       which  of several possible errors occurred.  An application that relies
+       on ncurses to check its function parameters  for  validity  limits  its
+       portability and robustness.

                                                                                                                                                        Padding Differences

                                                                                                                                                        -       In historical curses implementations, delays embedded in  the  terminfo
-       capabilities  carriage_return  (cr),  scroll_forward (ind), cursor_left
+       In  historical  curses implementations, delays embedded in the terminfo
+       capabilities carriage_return (cr),  scroll_forward  (ind),  cursor_left
        (cub1), form_feed (ff), and tab (ht) activated corresponding delay bits
        in  the  Unix terminal driver.  ncurses performs all padding by sending
        NUL bytes to the device.  This method is slightly more  expensive,  but
@@ -1383,65 +1417,62 @@
 
        but does not finish the story.  A more complete account follows.
 
-       o   Starting with 4BSD curses (1980) all implementations have  provided
-           a curses.h file.
+       o   The first curses, in 4BSD, provided a curses.h file.
 
-           BSD  curses  code  included  curses.h and unctrl.h from an internal
+           BSD curses code included curses.h and  unctrl.h  from  an  internal
            header file curses.ext, where "ext" abbreviated "externs".
 
-           The implementations of printw and scanw used undocumented  internal
-           functions  of  the  standard I/O library (_doprnt and _doscan), but
+           The  implementations of printw and scanw used undocumented internal
+           functions of the standard I/O library (_doprnt  and  _doscan),  but
            nothing in curses.h itself relied upon stdio.h.
 
-       o   SVr2 curses added newterm, which relies upon  stdio.h  because  its
+       o   SVr2  curses  added  newterm, which relies upon stdio.h because its
            function prototype employs the FILE type.
 
            SVr4 curses added putwin and getwin, which also use stdio.h.
 
            X/Open Curses specifies all three of these functions.
 
-           SVr4  curses  and  X/Open  Curses  do  not require the developer to
-           include stdio.h before curses.h.  Both document use  of  curses  as
+           SVr4 curses and X/Open Curses  do  not  require  the  developer  to
+           include  stdio.h  before  curses.h.  Both document use of curses as
            requiring only curses.h.
 
            As a result, standard curses.h always includes stdio.h.
 
-       o   X/Open  Curses  and  SVr4  curses  are inconsistent with respect to
+       o   X/Open Curses and SVr4 curses  are  inconsistent  with  respect  to
            unctrl.h.
 
-           As noted in curs_util(3x), ncurses includes unctrl.h from  curses.h
+           As  noted in curs_util(3x), ncurses includes unctrl.h from curses.h
            (as SVr4 does).
 
-       o   X/Open  Curses's  comments  about term.h and termios.h may refer to
+       o   X/Open Curses'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
+           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
+           AIX curses includes  term.h  and  termios.h.   Again,  ncurses  and
            Solaris curses do not.
 
-       o   X/Open Curses says that curses.h may include term.h, but  does  not
+       o   X/Open  Curses  says that curses.h may include term.h, but does not
            require it to do so.
 
-           Some  programs  use functions declared in both curses.h and term.h,
-           and must include both header files in the same  module.   Very  old
-           versions  of  AIX  curses  required  inclusion  of  curses.h before
-           term.h.
+           Some programs use functions declared in both curses.h  and  term.h,
+           and must include both header files in the same translation unit.
 
-           The header files supplied by ncurses include the  standard  library
-           headers  required  for  its  declarations,  so ncurses's own header
-           files can be included in  any  order.   But  for  portability,  you
-           should include curses.h before term.h.
+           The  header  files supplied by ncurses include the standard library
+           headers required for its  declarations,  so  ncurses's  own  header
+           files  can  be  included in any order.  For portability even to old
+           AIX systems, include curses.h before term.h.
 
-       o   X/Open  Curses  says  "may make visible" because including a header
-           file does not necessarily make visible all of  the  symbols  in  it
+       o   X/Open Curses says "may make visible" because  including  a  header
+           file  does  not  necessarily  make visible all of the symbols in it
            (consider #ifdef and similar).
 
-           For  instance, ncurses's curses.h may include wchar.h if the proper
-           symbol is defined, and if ncurses is configured for  wide-character
-           support.   If  wchar.h is included, its symbols may be made visible
-           depending on the value of the _XOPEN_SOURCE feature test macro.
+           For instance, ncurses's curses.h may include wchar.h if the  proper
+           symbol  is defined, and if ncurses is configured for wide-character
+           support.  If wchar.h is included, its symbols may be  made  visible
+           depending on the value of the _XOPEN_SOURCE feature test macro.
 
        o   X/Open Curses mandates an application's inclusion of one standard C
            library  header  in  a  special  case:  stdarg.h before curses.h to
@@ -1462,7 +1493,7 @@
 
            No   conforming   implementations   of  X/Open  Curses  require  an
            application to include stdarg.h before curses.h because they either
-           have  allowed  for  a  special type, or, like ncurses, they include
+           have allowed for a special type, or,  like  ncurses,  they  include
            stdarg.h themselves to provide a portable interface.
 
 
@@ -1474,9 +1505,7 @@

                                                                                                                                                        SEE ALSO

                                                                                                                                                                curs_variables(3x), terminfo(5), user_caps(5)
 
-
-
-ncurses 6.5                       2024-04-27                       ncurses(3x)
+ncurses 6.6                       2025-11-11                       ncurses(3x)
                                                                                                                                                          diff --git a/doc/html/man/ncursesw6-config.1.html b/doc/html/man/ncursesw6-config.1.html index 6380a6d..b340e73 100644 --- a/doc/html/man/ncursesw6-config.1.html +++ b/doc/html/man/ncursesw6-config.1.html @@ -27,25 +27,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: MKncu_config.in,v 1.24 2024/04/20 21:13:38 tom Exp @ + * @Id: MKncu_config.in,v 1.25 2024/05/11 20:39:53 tom Exp @ --> -ncursesw6-config 1 2024-04-20 ncurses 6.5 User commands +ncursesw6\-config 1 2024-05-11 ncurses 6.6 User commands -

                                                                                                                                                          ncursesw6-config 1 2024-04-20 ncurses 6.5 User commands

                                                                                                                                                          +

                                                                                                                                                          ncursesw6\-config 1 2024-05-11 ncurses 6.6 User commands

                                                                                                                                                           ncursesw6-config(1)              User commands             ncursesw6-config(1)
 
 
-
-

                                                                                                                                                          NAME

                                                                                                                                                                  ncursesw6-config - configuration helper for ncurses libraries
 
@@ -96,7 +94,7 @@
                          /usr/share/terminfo.
 
        --termpath        reports the TERMPATH supplemental search path for the
-                         termcap  database,  if   support   for   termcap   is
+                         termcap   database,   if   support   for  termcap  is
                          configured.
 
        The following options cause all others to be ignored.
@@ -110,9 +108,7 @@

                                                                                                                                                          SEE ALSO

                                                                                                                                                                  curses(3x)
 
-
-
-ncurses 6.5                       2024-04-20               ncursesw6-config(1)
+ncurses 6.6                       2024-05-11               ncursesw6-config(1)
                                                                                                                                                            diff --git a/doc/html/man/new_pair.3x.html b/doc/html/man/new_pair.3x.html index 3cc73d6..feabc87 100644 --- a/doc/html/man/new_pair.3x.html +++ b/doc/html/man/new_pair.3x.html @@ -1,6 +1,6 @@ -new_pair 3x 2024-03-16 ncurses 6.5 Library calls +new_pair 3x 2025-08-16 ncurses 6.6 Library calls -

                                                                                                                                                            new_pair 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                            +

                                                                                                                                                            new_pair 3x 2025-08-16 ncurses 6.6 Library calls

                                                                                                                                                             new_pair(3x)                     Library calls                    new_pair(3x)
 
 
-
-

                                                                                                                                                            NAME

                                                                                                                                                                    alloc_pair,  find_pair,  free_pair  - dynamically allocate curses color
        pairs
@@ -62,16 +60,16 @@

                                                                                                                                                            DESCRIPTION

                                                                                                                                                                    These functions are an extension to the curses library.  They permit an
-       application   to   dynamically   allocate   a   color  pair  using  the
-       foreground/background colors rather than  assign  a  fixed  color  pair
+       application  to  dynamically  allocate   a   color   pair   using   the
+       foreground/background  colors  rather  than  assign  a fixed color pair
        number, and return an unused pair to the pool.
 
-       The  number  of  colors  may be related to the number of possible color
+       The number of colors may be related to the  number  of  possible  color
        pairs for a given terminal, or it may not:
 
-       o   While almost all  terminals  allow  setting  the  color  attributes
-           independently,  it  is  unlikely  that  your terminal allows you to
-           modify the attributes of a given character cell  without  rewriting
+       o   While  almost  all  terminals  allow  setting  the color attributes
+           independently, it is unlikely that  your  terminal  allows  you  to
+           modify  the  attributes of a given character cell without rewriting
            it.  That is, the foreground and background colors are applied as a
            pair.
 
@@ -91,10 +89,10 @@
                ( COLORS + 1 ) * ( COLORS + 1 )
 
        o   An application might use up to a few dozen color pairs to implement
-           a predefined color scheme.
+           a color scheme.
 
-           Beyond that lies in the realm of programs using the foreground  and
-           background  colors  for  "ASCII  art"  (or  some  other non-textual
+           Beyond  that lies in the realm of programs using the foreground and
+           background colors  for  "ASCII  art"  (or  some  other  non-textual
            application).
 
            Also beyond those few dozen pairs, the required size for a table to
@@ -107,7 +105,7 @@

                                                                                                                                                            alloc_pair

                                                                                                                                                                    The   alloc_pair   function   accepts  parameters  for  foreground  and
-       background color, and checks  if  that  color  combination  is  already
+       background color, and checks whether that color combination is  already
        associated with a color pair.
 
        o   If  the combination already exists, alloc_pair returns the existing
@@ -116,20 +114,20 @@
        o   If the combination does not exist, alloc_pair allocates a new color
            pair and returns that.
 
-       o   If  the  table  fills  up,  alloc_pair  discards the least-recently
+       o   If the table  fills  up,  alloc_pair  discards  the  least-recently
            allocated entry using free_pair and allocates a new color pair.
 
-       All of the color pairs are allocated from a  table  of  possible  color
-       pairs.   The  size  of  the  table  is determined by the terminfo pairs
-       capability.  The table is shared with  init_pair;  in  fact  alloc_pair
-       calls  init_pair after updating the ncurses library's fast index to the
+       All  of  the  color  pairs are allocated from a table of possible color
+       pairs.  The size of the table  is  determined  by  the  terminfo  pairs
+       capability.   The  table  is  shared with init_pair; in fact alloc_pair
+       calls init_pair after updating the ncurses library's fast index to  the
        colors versus color pairs.

                                                                                                                                                            find_pair

                                                                                                                                                                    The find_pair function accepts parameters for foreground and background
-       color,  and checks if that color combination is already associated with
-       a color pair, returning the pair  number  if  it  has  been  allocated.
+       color,  and checks whether that color combination is already associated
+       with a color pair, returning the pair number if it has been  allocated.
        Otherwise it returns -1.
 
 
@@ -163,9 +161,7 @@

                                                                                                                                                            SEE ALSO

                                                                                                                                                                    curs_color(3x)
 
-
-
-ncurses 6.5                       2024-03-16                      new_pair(3x)
+ncurses 6.6                       2025-08-16                      new_pair(3x)
                                                                                                                                                              diff --git a/doc/html/man/panel.3x.html b/doc/html/man/panel.3x.html index 58ad42d..71bcce9 100644 --- a/doc/html/man/panel.3x.html +++ b/doc/html/man/panel.3x.html @@ -27,27 +27,25 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: panel.3x,v 1.63 2024/03/16 15:35:01 tom Exp @ + * @Id: panel.3x,v 1.68 2024/12/28 21:26:21 tom Exp @ --> -panel 3x 2024-03-16 ncurses 6.5 Library calls +panel 3x 2024-12-28 ncurses 6.6 Library calls -

                                                                                                                                                              panel 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                              +

                                                                                                                                                              panel 3x 2024-12-28 ncurses 6.6 Library calls

                                                                                                                                                               panel(3x)                        Library calls                       panel(3x)
 
 
-
-

                                                                                                                                                              NAME

                                                                                                                                                              -       panel - panel stack extension for curses
+       panel - manage overlapping curses windows

                                                                                                                                                              SYNOPSIS

                                                                                                                                                              @@ -141,7 +139,7 @@

                                                                                                                                                              panel_below

                                                                                                                                                                      panel_below(pan) returns a pointer to the panel just below pan.  If the
-       panel argument is "(PANEL *)0", it returns a pointer to the  top  panel
+       panel  argument  is "(PANEL *)0", it returns a pointer to the top panel
        in the stack.
 
 
@@ -172,7 +170,7 @@

                                                                                                                                                              show_panel

                                                                                                                                                              -       show_panel(pan)  makes  a  hidden panel visible by placing it on top of
+       show_panel(pan) makes a hidden panel visible by placing it  on  top  of
        the panels in the panel stack.  See "PORTABILITY" below.
 
 
@@ -187,21 +185,21 @@
        refresh the physical screen.  Use this function and not wrefresh(3x) or
        wnoutrefresh(3x).
 
-       update_panels may be called more than once before a call  to  doupdate,
-       but  doupdate  is  the  function  responsible for updating the physical
+       update_panels  may  be called more than once before a call to doupdate,
+       but doupdate is the function  responsible  for  updating  the  physical
        screen.

                                                                                                                                                              RETURN VALUE

                                                                                                                                                              -       Each routine that returns a pointer returns NULL if  an  error  occurs.
-       Each  routine  that  returns  an  int  value  returns OK if it executes
+       Each  routine  that  returns a pointer returns NULL if an error occurs.
+       Each routine that returns an  int  value  returns  OK  if  it  executes
        successfully and ERR if not.
 
-       Except as noted, the pan and window parameters must  be  non-null.   If
+       Except  as  noted,  the pan and window parameters must be non-null.  If
        either is null, an error is returned.
 
-       The  move_panel  function uses mvwin(3x), and returns an error if mvwin
-       returns an error.
+       The move_panel function  uses  mvwin(3x),  and  returns  ERR  if  mvwin
+       returns ERR.

                                                                                                                                                              NOTES

                                                                                                                                                              @@ -209,8 +207,8 @@

                                                                                                                                                              PORTABILITY

                                                                                                                                                              -       Reasonable care has been taken to ensure compatibility with the  native
-       panel  facility  introduced  in System V; inspection of the SVr4 manual
+       Reasonable  care has been taken to ensure compatibility with the native
+       panel facility introduced in System V; inspection of  the  SVr4  manual
        pages suggests the programming interface never changed.  The PANEL data
        structures  are  merely  similar.   The  programmer is cautioned not to
        directly use PANEL fields.
@@ -236,24 +234,24 @@
            library.
 
        o   ncurses (since version 0.6 in 1993) and PDCurses (since version 2.2
-           in  1995) provide a panel library whose common ancestor is a public
-           domain implementation by Warren Tucker published  in  u386mon  2.20
+           in 1995) provide a panel library whose common ancestor is a  public
+           domain  implementation  by  Warren Tucker published in u386mon 2.20
            (1990).
 
-           According  to Tucker, the System V panel library was first released
-           in SVr3.2 (1988), and his implementation  helped  with  a  port  to
+           According to Tucker, the System V panel library was first  released
+           in  SVr3.2  (1988),  and  his  implementation helped with a port to
            SVr3.1 (1987).
 
-           Several  developers have improved each of these; they are no longer
+           Several developers have improved each of these; they are no  longer
            the same as Tucker's implementation.
 
-       o   NetBSD 8 (2018) has a panel library  begun  by  Valery  Ushakov  in
+       o   NetBSD  8  (2018)  has  a  panel library begun by Valery Ushakov in
            2015, based on the System V documentation.

                                                                                                                                                              AUTHORS

                                                                                                                                                                      Warren   Tucker   <wht@n4hgf.mt-park.ga.us>   originally   wrote   this
-       implementation, primarily to  assist  in  porting  u386mon  to  systems
+       implementation,  primarily  to  assist  in  porting  u386mon to systems
        without a native panel library.
 
        Zeyd ben-Halim repackaged it for ncurses.
@@ -264,9 +262,7 @@

                                                                                                                                                              SEE ALSO

                                                                                                                                                                      curses(3x), curs_variables(3x)
 
-
-
-ncurses 6.5                       2024-03-16                         panel(3x)
+ncurses 6.6                       2024-12-28                         panel(3x)
                                                                                                                                                                diff --git a/doc/html/man/resizeterm.3x.html b/doc/html/man/resizeterm.3x.html index 2349146..b0c0159 100644 --- a/doc/html/man/resizeterm.3x.html +++ b/doc/html/man/resizeterm.3x.html @@ -1,6 +1,6 @@ -resizeterm 3x 2024-03-16 ncurses 6.5 Library calls +resizeterm 3x 2025-07-05 ncurses 6.6 Library calls -

                                                                                                                                                                resizeterm 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                                +

                                                                                                                                                                resizeterm 3x 2025-07-05 ncurses 6.6 Library calls

                                                                                                                                                                 resizeterm(3x)                   Library calls                  resizeterm(3x)
 
 
-
-

                                                                                                                                                                NAME

                                                                                                                                                                        is_term_resized,   resize_term,   resizeterm   -  manage  the  terminal
        dimensions understood by curses
@@ -62,21 +60,21 @@

                                                                                                                                                                DESCRIPTION

                                                                                                                                                                        This is an extension to the curses library.  It provides callers with a
-       hook  into  the  ncurses  data  to resize windows, primarily for use by
-       programs running in  an  X  Window  terminal  (e.g.,  xterm)  when  the
+       hook into the ncurses data to resize  windows,  primarily  for  use  by
+       programs  running  in  an  X  Window  terminal  (e.g.,  xterm) when the
        terminal's screen size is changed by the user:
 
-       o   curses  windows  cannot extend outside the screen.  If the terminal
+       o   curses windows cannot extend outside the screen.  If  the  terminal
            is shrunk, curses windows must be shrunk to fit.
 
-       o   If the terminal is stretched, rows and/or columns can be  added  to
+       o   If  the  terminal is stretched, rows and/or columns can be added to
            existing  windows.   The  added  cells  should  match  the  current
            attributes of the windows.
 
-       If the calling program has not set up a handler for  SIGWINCH  when  it
-       initializes  ncurses  (e.g.,  using  initscr(3x)  or newterm(3x)), then
-       ncurses sets a handler for SIGWINCH which notifies the library  when  a
-       window-size   event   has   occurred.   The  library  checks  for  this
+       If  the  application  has  not  set  up  a handler for SIGWINCH when it
+       initializes ncurses  (by  calling  initscr(3x)  or  newterm(3x)),  then
+       ncurses establishes a SIGWINCH handler that notifies the library when a
+       window-resizing  event  has  occurred.   The  library  checks  for this
        notification
 
        o   when reading input data,
@@ -89,36 +87,34 @@
        When the library has found that the terminal's window-size has changed,
        it calls resizeterm to update its data structures.
 
-       An application which establishes its  own  SIGWINCH  handler  can  call
-       resizeterm,  but  in  that case, the library will not see SIGWINCH, and
+       An application which establishes its  own  SIGWINCH  handler  can  call
+       resizeterm,  but  in  that case, the library will not see SIGWINCH, and
        proper layout will rely upon the application.
 
 
-

                                                                                                                                                                FUNCTIONS

                                                                                                                                                                -

                                                                                                                                                                resizeterm

                                                                                                                                                                        The function resizeterm resizes the standard and current windows (i.e.,
-       stdscr  and  curscr)  to  the  specified  dimensions, and adjusts other
-       bookkeeping data used by the ncurses library  that  record  the  window
+       stdscr and curscr) to  the  specified  dimensions,  and  adjusts  other
+       bookkeeping  data  used  by  the ncurses library that record the window
        dimensions such as the LINES and COLS variables.

                                                                                                                                                                resize_term

                                                                                                                                                                -       Most  of  the  work  for  resizeterm  is  done  by  the  inner function
-       resize_term.  The outer function resizeterm adds  bookkeeping  for  the
-       SIGWINCH  handler,  as  well  as  repainting  the  soft-key  area  (see
+       Most of  the  work  for  resizeterm  is  done  by  the  inner  function
+       resize_term.   The  outer  function resizeterm adds bookkeeping for the
+       SIGWINCH  handler,  as  well  as  repainting  the  soft-key  area  (see
        slk_touch(3x)).
 
-       The resize_term function attempts to resize all  windows.   This  helps
+       The  resize_term  function  attempts to resize all windows.  This helps
        with simple applications.  However:
 
        o   It is not possible to automatically resize pads.
 
        o   Applications  which  have  complicated  layouts  should  check  for
-           KEY_RESIZE returned from wgetch, and  adjust  their  layout,  e.g.,
+           KEY_RESIZE  returned  from  wgetch,  and adjust their layout, e.g.,
            using wresize and mvwin, or by recreating the windows.
 
-       When  resizing  windows,  resize_term  recursively  adjusts subwindows,
+       When resizing  windows,  resize_term  recursively  adjusts  subwindows,
        keeping them within the updated parent window's limits.  If a top-level
        window  happens  to extend to the screen's limits, then on resizing the
        window, resize_term will keep the window extending to the corresponding
@@ -134,19 +130,19 @@

                                                                                                                                                                RETURN VALUE

                                                                                                                                                                        Except  as  noted,  these functions return the integer ERR upon failure
        and OK on success.  They will fail if either of the dimensions are less
-       than  or  equal  to  zero,  or  if an error occurs while (re)allocating
+       than or equal to zero, or  if  an  error  occurs  while  (re)allocating
        memory for the windows.

                                                                                                                                                                NOTES

                                                                                                                                                                -       While these functions are intended to  be  used  to  support  a  signal
-       handler  (i.e.,  for  SIGWINCH), care should be taken to avoid invoking
-       them in a context where malloc or realloc may  have  been  interrupted,
+       While  these  functions  are  intended  to  be used to support a signal
+       handler (i.e., for SIGWINCH), care should be taken  to  avoid  invoking
+       them  in  a  context where malloc or realloc may have been interrupted,
        since it uses those functions.
 
-       If ncurses is configured to supply its own SIGWINCH handler,
+       If ncurses is configured to supply its own SIGWINCH handler,
 
-       o   on receipt of a SIGWINCH, the handler sets a flag
+       o   on receipt of a SIGWINCH, the handler sets a flag
 
        o   which is tested in wgetch(3x), doupdate(3x) and restartterm(3x),
 
@@ -160,12 +156,12 @@
            that cannot be done automatically.
 
            Calling resizeterm or resize_term directly from a signal handler is
-           unsafe.   This  indirect  method  is  used to provide a safe way to
+           unsafe.  This indirect method is used to  provide  a  safe  way  to
            resize the ncurses data structures.
 
-       If the environment variables LINES or COLUMNS are set,  this  overrides
-       the  library's  use  of  the  window  size  obtained from the operating
-       system.  Thus, even if a SIGWINCH is received, no  screen  size  change
+       If  the  environment variables LINES or COLUMNS are set, this overrides
+       the library's use of  the  window  size  obtained  from  the  operating
+       system.   Thus,  even  if a SIGWINCH is received, no screen size change
        may be recorded.
 
 
@@ -178,28 +174,25 @@
 
        Doing that clears the screen and is visually distracting.
 
-       This  extension  of ncurses was introduced in mid-1995.  It was adopted
-       in NetBSD curses (2001) and PDCurses (2003).
+       ncurses introduced this extension in mid-1995.  NetBSD  curses  adopted
+       it in 2001 and PDCurses in 2003.

                                                                                                                                                                AUTHORS

                                                                                                                                                                -       Thomas Dickey (from an equivalent function  written  in  1988  for  BSD
+       Thomas  Dickey  (from  an  equivalent  function written in 1988 for BSD
        curses)

                                                                                                                                                                SEE ALSO

                                                                                                                                                                        curs_getch(3x), curs_variables(3x), wresize(3x)
 
-
-
-ncurses 6.5                       2024-03-16                    resizeterm(3x)
+ncurses 6.6                       2025-07-05                    resizeterm(3x)
                                                                                                                                                                • NAME
                                                                                                                                                                • SYNOPSIS
                                                                                                                                                                  • -
                                                                                                                                                                • DESCRIPTION
                                                                                                                                                                  • -
                                                                                                                                                                • FUNCTIONS +
                                                                                                                                                                • DESCRIPTION
                                                                                                                                                                  • resizeterm
                                                                                                                                                                  • resize_term
                                                                                                                                                                    • diff --git a/doc/html/man/scr_dump.5.html b/doc/html/man/scr_dump.5.html index a963425..55785fe 100644 --- a/doc/html/man/scr_dump.5.html +++ b/doc/html/man/scr_dump.5.html @@ -1,6 +1,6 @@ -scr_dump 5 2024-03-23 ncurses 6.5 File formats +scr_dump 5 2025-04-05 ncurses 6.6 File formats -

                                                                                                                                                                    scr_dump 5 2024-03-23 ncurses 6.5 File formats

                                                                                                                                                                    +

                                                                                                                                                                    scr_dump 5 2025-04-05 ncurses 6.6 File formats

                                                                                                                                                                     scr_dump(5)                      File formats                      scr_dump(5)
 
 
-
-

                                                                                                                                                                    NAME

                                                                                                                                                                            scr_dump - curses screen dump
 
@@ -108,7 +106,7 @@

                                                                                                                                                                    ncurses5 (Legacy)

                                                                                                                                                                            The screen-dump feature was added to ncurses in June 1995.  While there
-       were fixes and improvements in succeeding years, the basic  scheme  was
+       were  fixes  and improvements in succeeding years, the basic scheme was
        unchanged:
 
        o   The WINDOW structure was written in binary form.
@@ -130,18 +128,18 @@

                                                                                                                                                                    X/Open Curses

                                                                                                                                                                    -       X/Open Curses, Issue 7 specifies little.  It  says  (boldface  emphasis
+       X/Open  Curses  Issue 7  specifies  little.  It says (boldface emphasis
        added)
 
-          "[t]he  getwin()  function  reads  window-related data stored in the
-          file by putwin().  The function then creates and initializes  a  new
+          "[t]he getwin() function reads window-related  data  stored  in  the
+          file  by  putwin().  The function then creates and initializes a new
           window using that data.
 
-          The  putwin()  function writes all data associated with win into the
-          stdio stream to which filep points,  using  an  unspecified  format.
+          The putwin() function writes all data associated with win  into  the
+          stdio  stream  to  which  filep points, using an unspecified format.
           This information can be retrieved later using getwin()."
 
-       In  the  mid-1990s  when  the X/Open Curses document was written, there
+       In the mid-1990s when the X/Open Curses  document  was  written,  there
        were still System V systems using older, less capable curses libraries.
        BSD  curses  was  not  relevant  to  X/Open because it did not meet the
        criteria for base-level conformance; see ncurses(3x).
@@ -162,14 +160,14 @@
            #define SVR3_DUMP_MAGIC_NUMBER  0434
 
        That is, the feature was likely introduced in SVr2 (1984), and improved
-       in  SVr3  (1987).   Solaris curses has no magic number for SVr4 (1989).
-       Other System V operating systems (AIX and HP-UX)  use  a  magic  number
+       in SVr3 (1987).  Solaris curses has no magic number  for  SVr4  (1989).
+       Other  System V  operating  systems  (AIX and HP-UX) use a magic number
        that would correspond to the following.
 
            /* curses screen dump magic number */
            #define SVR4_DUMP_MAGIC_NUMBER  0435
 
-       That  octal  number in bytes is 001, 035.  Because most Unix vendors at
+       That octal number in bytes is 001, 035.  Because most Unix  vendors  at
        the time used big-endian hardware, the magic number is written with the
        high-order byte first.
 
@@ -182,7 +180,7 @@
 
        Nor do they use an identical format, even  with  the  System V  family.
        The ncurses savescreen test program was used to collect information for
-       this manual page.  It produced dumps of different size (all  on  64-bit
+       this  manual  page.  It produced dumps of different size (all on 64-bit
        hardware, on 40x80 screens):
 
        o   AIX (51817 bytes)
@@ -195,29 +193,29 @@

                                                                                                                                                                    Solaris

                                                                                                                                                                    -       As  noted  above,  Solaris  curses has no magic number corresponding to
+       As noted above, Solaris curses has no  magic  number  corresponding  to
        SVr4 curses.  This is odd, since Solaris was the first operating system
        to meet the SVr4 guidelines.  Solaris furthermore supplies two versions
        of curses.
 
        o   The default curses library uses the SVr3 magic number.
 
-       o   An alternate curses library (which we term xcurses),  available  in
+       o   An  alternate  curses library (which we term xcurses), available in
            /usr/xpg4, uses a textual format with no magic number.
 
            According  to  its  copyright  notice,  this  xcurses  library  was
            developed by MKS (Mortice Kern Systems) from 1990 to 1995.
 
-           Like ncurses6,  it  includes  a  header  with  parameters.   Unlike
-           ncurses6,  the  contents  of the window are written piecemeal, with
-           coordinates and attributes for  each  chunk  of  text  rather  than
+           Like  ncurses6,  it  includes  a  header  with  parameters.  Unlike
+           ncurses6, the contents of the window are  written  piecemeal,  with
+           coordinates  and  attributes  for  each  chunk  of text rather than
            writing the whole window from top to bottom.

                                                                                                                                                                    PDCurses

                                                                                                                                                                    -       PDCurses  added  support  for screen dumps in version 2.7 (2005).  Like
-       System V and ncurses5, it writes the WINDOW structure  in  binary,  but
-       begins  the  file  with  its three-byte identifier "PDC", followed by a
+       PDCurses added support for screen dumps in version  2.7  (2005).   Like
+       System V  and  ncurses5,  it writes the WINDOW structure in binary, but
+       begins the file with its three-byte identifier  "PDC",  followed  by  a
        single-byte version number.
 
                 "PDC\001"
@@ -227,7 +225,7 @@
        As  of  April  2017,  NetBSD  curses  does  not  support  scr_dump  and
        scr_restore (or scr_init, scr_set), although it has putwin and getwin.
 
-       Like  ncurses5, NetBSD putwin does not identify its dumps with a useful
+       Like ncurses5, NetBSD putwin does not identify its dumps with a  useful
        magic number.  It writes
 
        o   the curses shared library major and minor versions as the first two
@@ -300,13 +298,13 @@
 
        o   The actual color pair values are not written to the file.
 
-       o   All characters are shown in printable  form;  spaces  are  "\s"  to
+       o   All  characters  are  shown  in  printable form; spaces are "\s" to
            ensure they are not overlooked.
 
-       o   Attributes  are  written  in escaped curly braces, e.g., "\{BOLD}",
+       o   Attributes are written in escaped curly  braces,  e.g.,  "\{BOLD}",
            and may include a color pair (C1 or C2 in this example).
 
-       o   The parameters in the header are  written  out  only  if  they  are
+       o   The  parameters  in  the  header  are  written out only if they are
            nonzero.  When reading back, order does not matter.
 
        Running the same program with Solaris xpg4 curses gives this dump:
@@ -345,12 +343,12 @@
            9,19,0,0,
            CUR=11,5
 
-       Solaris  getwin  requires  that  all parameters are present, and in the
-       same order.  The xpg4 curses library does not know about the bce  (back
+       Solaris getwin requires that all parameters are  present,  and  in  the
+       same  order.  The xpg4 curses library does not know about the bce (back
        color erase) capability, and does not color the window background.
 
-       On  the  other  hand,  the  SVr4  curses  library  does  know about the
-       background color.  However, its screen dumps are in  binary.   Here  is
+       On the other  hand,  the  SVr4  curses  library  does  know  about  the
+       background  color.   However,  its screen dumps are in binary.  Here is
        the corresponding dump (using "od -t x1"):
 
            0000000 1c 01 c3 d6 f3 58 05 00 0b 00 0a 00 14 00 00 00
@@ -388,9 +386,7 @@

                                                                                                                                                                    SEE ALSO

                                                                                                                                                                            curs_scr_dump(3x), curs_util(3x)
 
-
-
-ncurses 6.5                       2024-03-23                       scr_dump(5)
+ncurses 6.6                       2025-04-05                       scr_dump(5)
                                                                                                                                                                      diff --git a/doc/html/man/tabs.1.html b/doc/html/man/tabs.1.html index 5a548fa..dd2f6f2 100644 --- a/doc/html/man/tabs.1.html +++ b/doc/html/man/tabs.1.html @@ -1,6 +1,6 @@ -tabs 1 2024-04-20 ncurses 6.5 User commands +tabs 1 2025-08-16 ncurses 6.6 User commands -

                                                                                                                                                                      tabs 1 2024-04-20 ncurses 6.5 User commands

                                                                                                                                                                      +

                                                                                                                                                                      tabs 1 2025-08-16 ncurses 6.6 User commands

                                                                                                                                                                       tabs(1)                          User commands                         tabs(1)
 
 
-
-

                                                                                                                                                                      NAME

                                                                                                                                                                              tabs - set terminal tab stops
 
@@ -132,8 +130,8 @@
        which is equivalent to the 1,6,11,16,21 example.
 
 
-

                                                                                                                                                                      Predefined Tab Stops

                                                                                                                                                                      -       POSIX defines several predefined lists of tab stops.
+

                                                                                                                                                                      Standard Tab Stops

                                                                                                                                                                      +       POSIX defines several lists of tab stops.
 
        -a   Assembler, IBM S/370, first format
             1,10,16,36,72
@@ -180,7 +178,7 @@
                 on each line.  The terminal's left margin is not modified.
 
             If the margin parameter is omitted, the default is 10.  Use +m0 to
-            reset the left margin, that is, to make it the left  edge  of  the
+            reset  the  left  margin, that is, to make it the left edge of the
             terminal's display.  Before setting a left margin, tabs resets the
             margin to reduce problems that might arise from moving the  cursor
             to the left of the current left margin.
@@ -195,70 +193,67 @@

                                                                                                                                                                      PORTABILITY

                                                                                                                                                                      -       IEEE  Std  1003.1/The  Open   Group   Base   Specifications   Issue   7
-       (POSIX.1-2008) describes a tabs utility.  However,
+       IEEE  Std   1003.1/The   Open   Group   Base   Specifications   Issue 7
+       (POSIX.1-2008) describes a tabs utility.  However,
 
        o   this  standard  describes  a  +m  option  to  set a terminal's left
            margin.  Very few of the entries in the terminal  database  provide
            the   set_left_margin   (smgl)   or   set_left_margin_parm  (smglp)
            capabilities needed to support the feature.
 
-       o   There is no counterpart in X/Open Curses Issue 7 for this  utility,
-           unlike tput(1).
+       o   Unlike tput, tabs has no specification in X/Open Curses Issue 7.
 
-       The  -d  (debug)  and  -n  (no-op)  options  are ncurses extensions not
+       The -d (debug) and  -n  (no-op)  options  are  ncurses  extensions  not
        provided by other implementations.

                                                                                                                                                                      HISTORY

                                                                                                                                                                      -       A tabs utility appeared in PWB/Unix  1.0  (1977).   A  reduced  version
-       shipped  in  Seventh  Edition  Unix (early 1979) and in 3BSD (later the
-       same year); it supported a "-n" option to set the first tab stop at the
-       left margin.  That option is not specified by POSIX.
+       A  tabs  utility  appeared  in  PWB/Unix 1.0 (1977).  A reduced version
+       shipped in Seventh Edition Unix (early 1979) and  in  3BSD  (later  the
+       same  year);  it  supported an option "-n" to set the first tab stop at
+       the left margin.  That option is not specified by POSIX.
 
-       The  PWB/Unix  tabs  utility  returned  in  System III (1980), and used
-       built-in tables to support a  half-dozen  hardcopy  terminal  (printer)
-       types.   It  also had logic to support setting the left margin, as well
+       The PWB/Unix tabs utility returned  in  System  III  (1980),  and  used
+       built-in  tables  to  support  a half-dozen hardcopy terminal (printer)
+       types.  It also had logic to support setting the left margin,  as  well
        as a feature for copying the tab settings from a file.
 
-       Versions of the program in later releases of AT&T Unix, such  as  SVr4,
-       added  support  for  the  terminal database, but retained the tables to
-       support the printers.  By this time, System V tput had incorporated the
-       tab  stop  initialization feature of BSD's tset from 1982, but employed
+       Versions  of  the program in later releases of AT&T Unix, such as SVr4,
+       added support for the terminal database, but  retained  the  tables  to
+       support the printers.  By this time, System V tput had incorporated the
+       tab  stop  initialization feature of BSD's tset from 1982, but employed
        the terminfo database to do so.
 
-       The +m option was documented in the POSIX Base Specifications  Issue  5
+       The +m option was documented in the POSIX Base  Specifications  Issue 5
        (Unix98,  1997), then omitted in Issue 6 (Unix03, 2004) without express
        motivation, though an introductory comment "and optionally adjusts  the
-       margin"   remains,   overlooked  in  the  removal.   The  tabs  utility
+       margin"   remains,   overlooked  in  the  removal.   The  tabs  utility
        documented in Issues 6 and later has no mechanism for setting  margins.
-       The  +m  option  in ncurses tabs differs from the SVr4 feature by using
-       terminal capabilities rather than built-in tables.
+       The +m option in ncurses's implementation differs from the SVr4 feature
+       by using terminal capabilities rather than built-in tables.
 
-       POSIX  documents  no  limit  on  the  number  of  tab   stops.    Other
-       implementations impose one; the limit is 20 in PWB/Unix's tabs utility.
+       POSIX   documents   no  limit  on  the  number  of  tab  stops.   Other
+       implementations impose one; the limit is 20 in PWB/Unix's tabs utility.
        While some terminals may not accept an arbitrary number of  tab  stops,
-       ncurses  tabs  attempts  to set tab stops up to the right margin if the
-       list thereof is sufficiently long.
+       ncurses  attempts  to  set tab stops up to the right margin if the list
+       thereof is sufficiently long.
 
-       The "Rationale" section of the Issue 6 tabs reference page details  how
-       the  committee  considered  redesigning  the  tabs  and tput utilities,
+       The "Rationale" section of the Issue 6 tabs reference page details  how
+       the  committee  considered  redesigning  the  tabs  and tput utilities,
        without settling on an improved solution.  It claims that
 
-           "no known historical version of tabs  supports  the  capability  of
-           setting arbitrary tab stops."
+           no known historical version of  tabs  supports  the  capability  of
+           setting arbitrary tab stops.
 
        The   feature  described  in  subsection  "Explicit  Lists"  above  was
-       implemented in PWB/Unix, and permitted  the  setting  of  abitrary  tab
+       implemented in PWB/Unix, and permitted the  setting  of  arbitrary  tab
        stops nevertheless.

                                                                                                                                                                      SEE ALSO

                                                                                                                                                                              infocmp(1m), tset(1), curses(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-04-20                           tabs(1)
+ncurses 6.6                       2025-08-16                           tabs(1)
                                                                                                                                                                      diff --git a/doc/html/man/term.5.html b/doc/html/man/term.5.html index 9c9b5b8..b2675ae 100644 --- a/doc/html/man/term.5.html +++ b/doc/html/man/term.5.html @@ -1,7 +1,7 @@ -term 5 2024-04-20 ncurses 6.5 File formats +term 5 2025-08-16 ncurses 6.6 File formats -

                                                                                                                                                                      term 5 2024-04-20 ncurses 6.5 File formats

                                                                                                                                                                      +

                                                                                                                                                                      term 5 2025-08-16 ncurses 6.6 File formats

                                                                                                                                                                       term(5)                          File formats                          term(5)
 
 
-
-

                                                                                                                                                                      NAME

                                                                                                                                                                              term - compiled terminfo terminal description
 
 
-

                                                                                                                                                                      SYNOPSIS

                                                                                                                                                                      -       term
-
-

                                                                                                                                                                      DESCRIPTION

                                                                                                                                                                      +       tic(1) compiles a terminfo terminal type description, and setupterm(3x)
+       reads  it.   A  compiled  description  may  be stored in a file or in a
+       database of, potentially, many such descriptions.  Further, a  compiled
+       description  may  be in one of two formats: one similar to that used by
+       System V, and  a  newer,  extensible  format  employed  exclusively  by
+       ncurses.
+

                                                                                                                                                                      Storage Location

                                                                                                                                                                      -       Compiled   terminfo   descriptions   are  placed  under  the  directory
-       /usr/share/terminfo.  Two configurations are supported  (when  building
-       the ncurses libraries):
+       Compiled   terminfo   descriptions   are  placed  under  the  directory
+       /usr/share/terminfo.   One  of  two  configurations  is  selected  when
+       building the ncurses libraries.
 
        directory tree
             A two-level scheme is used to avoid a linear search of a huge Unix
-            system directory: /usr/share/terminfo/c/name  where  name  is  the
+            system  directory:  /usr/share/terminfo/c/name  where  name is the
             name of the terminal, and c is the first character of name.  Thus,
-            act4  can  be  found  in  the   file   /usr/share/terminfo/a/act4.
-            Synonyms  for  the same terminal are implemented by multiple links
-            to the same compiled file.
+            the compiled description of terminal type "act4" is found  in  the
+            file  /usr/share/terminfo/a/act4.   Synonyms for the same terminal
+            are implemented by multiple links to the same compiled file.
 
        hashed database
-            Using Berkeley database, two types  of  records  are  stored:  the
-            terminfo  data  in  the  same format as stored in a directory tree
-            with the terminfo's primary name as a key, and records  containing
-            only aliases pointing to the primary name.
+            Using the Berkeley database API, two types of records are  stored:
+            the terminfo data in the same format as that stored in a directory
+            tree  with  the terminal's primary type name as a key, and records
+            containing only aliases pointing to the primary name.
 
-            If  built  to  write  hashed  databases,  ncurses  can  still read
-            terminfo databases organized as a directory tree, but cannot write
-            entries  into  the  directory  tree.   It  can  write (or rewrite)
+            If built to write hashed databases, ncurses can still  read  term-
+            info  databases  organized  as  a directory tree, but cannot write
+            entries into the  directory  tree.   It  can  write  (or  rewrite)
             entries in the hashed database.
 
-            ncurses  distinguishes  the  two  cases  in   the   TERMINFO   and
-            TERMINFO_DIRS  environment  variable  by assuming a directory tree
-            for entries that correspond to an existing directory,  and  hashed
+            ncurses   distinguishes   the   two  cases  in  the  TERMINFO  and
+            TERMINFO_DIRS environment variable by assuming  a  directory  tree
+            for entries that correspond to an existing directory, and a hashed
             database otherwise.

                                                                                                                                                                      Legacy Storage Format

                                                                                                                                                                              The format has been chosen so that it will be the same on all hardware.
-       An 8 or more bit  byte  is  assumed,  but  no  assumptions  about  byte
-       ordering or sign extension are made.
+       A  byte  of  at  least eight bits' width is assumed, but no assumptions
+       about bit ordering or sign extension are made.
 
-       The  compiled  file  is  created  with the tic program, and read by the
-       routine setupterm(3x).  The file is divided into six parts:
+       The file is divided into six parts:
 
-            a) header,
+            (a) header,
 
-            b) terminal names,
+            (b) terminal names,
 
-            c) Boolean flags,
+            (c) Boolean flags,
 
-            d) numbers,
+            (d) numbers,
 
-            e) strings, and
+            (e) strings, and
 
-            f) string table.
+            (f) a string table.
 
        The header section begins the file.  This section  contains  six  short
        integers in the format described below.  These integers are
 
-            (1) the magic number (octal 0432);
+            (1) the magic number
+                 (octal 0432);
 
-            (2) the size, in bytes, of the terminal names section;
+            (2) the size,
+                 in bytes, of the terminal names section;
 
             (3) the number of bytes in the Boolean flags section;
 
             (4) the number of short integers in the numbers section;
 
-            (5) the number of offsets (short integers) in the strings section;
+            (5) the number of offsets
+                 (short integers) in the strings section;
 
-            (6) the size, in bytes, of the string table.
+            (6) the size,
+                 in bytes, of the string table.
 
        The  capabilities  in  the Boolean flags, numbers, and strings sections
-       are in the same order as the file <term.h>.
+       are in the same order as in the header file term.h.
 
-       Short integers are signed, in the range  -32768  to  32767.   They  are
-       stored  as  two  8-bit  bytes.   The  first  byte  contains  the  least
-       significant 8 bits of the value, and the second byte contains the  most
-       significant 8 bits.  (Thus, the value represented is 256*second+first.)
-       This format corresponds to the hardware of the VAX and PDP-11 (that is,
-       little-endian  machines).   Machines  where this does not correspond to
-       the hardware must read the  integers  as  two  bytes  and  compute  the
-       little-endian value.
+       Short integers are signed, in the range -32768 to 32767, and stored  in
+       little-endian format.
 
        Numbers  in  a  terminal  description,  whether they are entries in the
        numbers or strings table, are positive  integers.   Boolean  flags  are
        treated  as  positive  one-byte integers.  In each case, those positive
-       integers represent a terminal capability.  The  terminal  compiler  tic
+       integers represent a terminal capability.  The  terminal  compiler  tic
        uses  negative  integers  to handle the cases where a capability is not
        available:
 
-       o   If a capability is absent from this terminal, tic stores  a  -1  in
+       o   If a capability is absent from this terminal, tic stores  a  -1  in
            the corresponding table.
 
            The integer value -1 is represented by two bytes 0377, 0377.
            Absent Boolean values are represented by the byte 0 (false).
 
-       o   If  a capability has been canceled from this terminal, tic stores a
+       o   If  a capability has been canceled from this terminal, tic stores a
            -2 in the corresponding table.
 
            The integer value -2 is represented by two bytes 0377, 0376.
@@ -156,7 +154,7 @@
        o   Other negative values are illegal.
 
        The terminal names section comes after the  header.   It  contains  the
-       first  line  of the terminfo description, listing the various names for
+       first  line  of the terminfo description, listing the various names for
        the terminal, separated by  the  "|"  character.   The  terminal  names
        section is terminated with an ASCII NUL character.
 
@@ -164,41 +162,41 @@
        capabilities are either 1 or 0 (true or false) according to whether the
        terminal supports the given capability or not.
 
-       Between  the  Boolean flags section and the number section, a null byte
-       will be inserted, if necessary,  to  ensure  that  the  number  section
-       begins  on  an even byte This is a relic of the PDP-11's word-addressed
-       architecture, originally designed to avoid traps induced by  addressing
-       a  word  on  an odd byte boundary.  All short integers are aligned on a
+       Between the Boolean flags section and the number section, a  null  byte
+       will  be  inserted,  if  necessary,  to  ensure that the number section
+       begins on an even byte This is a relic of the  PDP-11's  word-addressed
+       architecture,  originally designed to avoid traps induced by addressing
+       a word on an odd byte boundary.  All short integers are  aligned  on  a
        short word boundary.
 
-       The numbers section is similar to  the  Boolean  flags  section.   Each
-       capability  takes  up two bytes, and is stored as a little-endian short
+       The  numbers  section  is  similar  to the Boolean flags section.  Each
+       capability takes up two bytes, and is stored as a  little-endian  short
        integer.
 
-       The strings section is also similar.  Each capability is  stored  as  a
+       The  strings  section  is also similar.  Each capability is stored as a
        short integer.  The capability value is an index into the string table.
 
        The string table is the last section.  It contains all of the values of
        string capabilities referenced in the strings section.  Each string  is
        null-terminated.  Special characters in ^X or \c notation are stored in
-       their interpreted  form,  not  the  printing  representation.   Padding
-       information  $<nn>  and  parameter  information %x are stored intact in
+       their  interpreted  form,  not  the  printing  representation.  Padding
+       information $<nn> and parameter information %x  are  stored  intact  in
        uninterpreted form.

                                                                                                                                                                      Extended Storage Format

                                                                                                                                                                      -       The previous section describes the conventional terminfo binary format.
+       The previous section describes the conventional terminfo binary format.
        With  some  minor variations of the offsets (see PORTABILITY), the same
        binary format is used in all modern Unix systems.  Each system  uses  a
-       predefined set of Boolean, number or string capabilities.
+       standard set of Boolean, numeric, or string capabilities.
 
-       The ncurses libraries and applications support extended terminfo binary
-       format, allowing users to  define  capabilities  which  are  loaded  at
-       runtime.   This  extension  is made possible by using the fact that the
-       other implementations stop reading the terminfo  data  when  they  have
-       reached  the  end  of the size given in the header.  ncurses checks the
-       size, and if it exceeds that due to the predefined data,  continues  to
-       parse according to its own scheme.
+       The ncurses libraries and applications support extended terminfo binary
+       format,  allowing  users  to  define  capabilities  that  are loaded at
+       runtime.  This extension is made possible by using the  fact  that  the
+       other  implementations  stop  reading the terminfo data when they reach
+       the end of the size given in the header.  ncurses checks the size,  and
+       if  it  exceeds  that  specified  in  the  header,  continues  to parse
+       according to its own scheme.
 
        First, it reads the extended header (5 short integers):
 
@@ -212,7 +210,7 @@
 
             (5)  size of the extended string table in bytes
 
-       The  count-  and  size-values for the extended string table include the
+       The count- and size-values for the extended string  table  include  the
        extended capability names as well as extended capability values.
 
        Using the counts and sizes, ncurses allocates arrays and reads data for
@@ -220,24 +218,22 @@
 
        The  extended  string  table  contains  values for string capabilities.
        After the end of these values, it contains the names for  each  of  the
-       extended  capabilities  in  order,  e.g.,  Booleans,  then  numbers and
-       finally strings.
+       extended capabilities in order: Boolean, numeric, and string.
 
-       By storing terminal descriptions  in  this  way,  ncurses  is  able  to
+       By  storing  terminal  descriptions  in  this  way,  ncurses is able to
        provide  a  database  useful  with  legacy  applications,  as  well  as
-       providing data for applications which need  more  than  the  predefined
-       capabilities.  See user_caps(5) for an overview of the way ncurses uses
-       this extended information.
+       providing  data  for applications that require more information about a
+       terminal type than was anticipated by X/Open Curses.  See  user_caps(5)
+       for an overview of the way ncurses uses this extended information.
 
-       Applications which manipulate terminal data  can  use  the  definitions
-       described  in  term_variables(3x)  which  associate the long capability
-       names with members of a TERMTYPE structure.
+       Applications  that  manipulate  terminal  data  can use the definitions
+       described in term_variables(3x) associating the long  capability  names
+       with members of a TERMTYPE structure.

                                                                                                                                                                      Extended Number Format

                                                                                                                                                                      -       On occasion, 16-bit signed integers are not large enough.  With ncurses
-       6.1,  a new format was introduced by making a few changes to the legacy
-       format:
+       On  occasion, 16-bit signed integers are not large enough.  ncurses 6.1
+       introduced a new format by making a few changes to the legacy format:
 
        o   a different magic number (octal 01036)
 
@@ -245,10 +241,10 @@
            to signed 32-bit integers.
 
        To   maintain   compatibility,  the  library  presents  the  same  data
-       structures to direct users of the TERMTYPE  structure  as  in  previous
+       structures to direct users of the TERMTYPE  structure  as  in  previous
        formats.   However,  that  cannot  provide  callers  with  the extended
        numbers.   The  library  uses  a  similar  but  hidden  data  structure
-       TERMTYPE2 to provide data for the terminfo functions.
+       TERMTYPE2 to provide data for the terminfo functions.

                                                                                                                                                                      FILES

                                                                                                                                                                      @@ -265,71 +261,71 @@
        (resulting in extra unrecognized entries in the file)  or  the  program
        may  have  been  recompiled more recently than the database was updated
        (resulting in missing entries).  The routine setupterm must be prepared
-       for  both  possibilities  -  this  is  why  the  numbers  and sizes are
-       included.  Also, new capabilities must always be added at  the  end  of
+       for both possibilities  -  this  is  why  the  numbers  and  sizes  are
+       included.   Also,  new  capabilities must always be added at the end of
        the lists of Boolean, number, and string capabilities.

                                                                                                                                                                      Binary Format

                                                                                                                                                                      -       X/Open  Curses  does  not  specify  a format for the terminfo database.
-       System V curses used a directory-tree of binary files, one per terminal
+       X/Open Curses does not specify a  format  for  the  terminfo  database.
+       System V curses used a directory-tree of binary files, one per terminal
        description.
 
-       Despite  the  consistent  use  of  little-endian  for  numbers  and the
-       otherwise  self-describing  format,  it  is  not  wise  to   count   on
-       portability   of   binary  terminfo  entries  between  commercial  Unix
-       versions.  The problem is that there are at  least  three  versions  of
-       terminfo  (under  HP-UX,  AIX,  and OSF/1) which diverged from System V
-       terminfo after SVr1, and  have  added  extension  capabilities  to  the
-       string  table  that  (in  the  binary format) collide with System V and
-       X/Open Curses extensions.  See terminfo(5) for detailed  discussion  of
-       terminfo source compatibility issues.
+       Despite  the  consistent use of little-endian numbers and the otherwise
+       self-describing format, it is not  wise  to  count  on  portability  of
+       binary  terminfo entries between commercial Unix versions.  The problem
+       is that there are at least three versions  of  terminfo  (under  HP-UX,
+       AIX,  and  OSF/1)  each  of which diverged from System V terminfo after
+       SVr1, and added extension capabilities to the string table that (in the
+       binary format) collide with System V and X/Open Curses extensions.  See
+       terminfo(5) for detailed discussion of  terminfo  source  compatibility
+       issues.
 
-       This  implementation  is by default compatible with the binary terminfo
-       format used by Solaris curses, except in a few less-used details  where
+       This  implementation  is by default compatible with the binary terminfo
+       format used by Solaris curses, except in a few less-used details  where
        it  was  found that the latter did not match X/Open Curses.  The format
        used by the other Unix versions can be matched by building ncurses with
        different configuration options.

                                                                                                                                                                      Magic Codes

                                                                                                                                                                      -       The  magic  number  in a binary terminfo file is the first 16-bits (two
-       bytes).  Besides making it more reliable for the library to check  that
-       a  file  is  terminfo,  utilities such as file(1) also use that to tell
-       what the file-format is.  System V defined more than one magic  number,
+       The magic number in a binary terminfo file is the first  16  bits  (two
+       bytes).   Besides making it more reliable for the library to check that
+       a file is terminfo, utilities such as file(1) also  use  that  to  tell
+       what  the file-format is.  System V defined more than one magic number,
        with 0433, 0435 as screen-dumps (see scr_dump(5)).  This implementation
        uses 01036 as a continuation of that sequence,  but  with  a  different
        high-order byte to avoid confusion.
 
-   The TERMTYPE Structure
-       Direct  access  to  the  TERMTYPE  structure  is  provided  for  legacy
-       applications.  Portable  applications  should  use  the  tigetflag  and
-       related  functions  described in curs_terminfo(3x) for reading terminal
-       capabilities.
+
+

                                                                                                                                                                      The TERMTYPE Structure

                                                                                                                                                                      +       Direct  access  to  the  TERMTYPE  structure  is  provided  for  legacy
+       applications.   Portable  applications  should  use  tigetflag(3x)  and
+       related functions to read terminal capabilities.

                                                                                                                                                                      Mixed-case Terminal Names

                                                                                                                                                                      -       A small number of terminal descriptions  use  uppercase  characters  in
-       their  names.   If  the  underlying  filesystem  ignores the difference
-       between  uppercase  and  lowercase,  ncurses  represents   the   "first
-       character"  of  the  terminal  name used as the intermediate level of a
+       A  small  number  of  terminal descriptions use uppercase characters in
+       their names.  If the underlying  file  system  ignores  the  difference
+       between   uppercase   and  lowercase,  ncurses  represents  the  "first
+       character" of the terminal name used as the  intermediate  level  of  a
        directory tree in (two-character) hexadecimal form.

                                                                                                                                                                      Limits

                                                                                                                                                                              ncurses stores compiled terminal descriptions in three related formats,
-       described in the sections
+       described in the subsections
 
-       o   LEGACY STORAGE FORMAT, and
+       o   Legacy Storage Format, and
 
-       o   EXTENDED STORAGE FORMAT, and
+       o   Extended Storage Format, and
 
-       o   EXTENDED NUMBER FORMAT.
+       o   Extended Number Format.
 
        The  legacy storage format and the extended number format differ by the
-       types of numeric capability which they can store (i.e.,  16-bit  versus
-       32-bit  integers).   The  extended storage format introduced by ncurses
-       5.0 adds data to either of these formats.
+       types of numeric capability that  they  can  store  (for  example,  16-
+       versus  32-bit  integers).   The  extended storage format introduced by
+       ncurses 5.0 adds data to either of these formats.
 
        Some limitations apply:
 
@@ -348,8 +344,8 @@

                                                                                                                                                                      EXAMPLES

                                                                                                                                                                      -       As  an  example,  here  is  a description for the Lear-Siegler ADM-3, a
-       popular though rather stupid early terminal:
+       Here  is  a  terminfo  description of the Lear-Siegler ADM-3, a popular
+       though rather stupid early terminal.
 
        adm3a|lsi adm3a,
                am,
@@ -358,7 +354,8 @@
                cuf1=^L, cup=\E=%p1%{32}%+%c%p2%{32}%+%c, cuu1=^K,
                home=^^, ind=^J,
 
-       and a hexadecimal dump of the compiled terminal description:
+       A hexadecimal dump of its  compiled  terminal  description  (in  legacy
+       format) follows.
 
        0000  1a 01 10 00 02 00 03 00  82 00 31 00 61 64 6d 33  ........ ..1.adm3
        0010  61 7c 6c 73 69 20 61 64  6d 33 61 00 00 01 50 00  a|lsi ad m3a...P.
@@ -386,25 +383,22 @@

                                                                                                                                                                      AUTHORS

                                                                                                                                                                              Thomas E. Dickey
-       extended terminfo format for ncurses 5.0
+       extended terminfo format for ncurses 5.0
        hashed database support for ncurses 5.6
        extended number support for ncurses 6.1
 
        Eric S. Raymond
-       documented legacy terminfo format, e.g., from pcurses.
+       documented legacy terminfo format (that used by pcurses).

                                                                                                                                                                      SEE ALSO

                                                                                                                                                                              curses(3x), curs_terminfo(3x), terminfo(5), user_caps(5)
 
-
-
-ncurses 6.5                       2024-04-20                           term(5)
+ncurses 6.6                       2025-08-16                           term(5)
                                                                                                                                                                      • NAME
                                                                                                                                                                        • -
                                                                                                                                                                      • SYNOPSIS
                                                                                                                                                                      • DESCRIPTION diff --git a/doc/html/man/term.7.html b/doc/html/man/term.7.html index 9a88588..b119732 100644 --- a/doc/html/man/term.7.html +++ b/doc/html/man/term.7.html @@ -1,6 +1,6 @@ -term 7 2024-03-16 ncurses 6.5 Miscellaneous +term 7 2025-08-16 ncurses 6.6 Miscellaneous -

                                                                                                                                                                        term 7 2024-03-16 ncurses 6.5 Miscellaneous

                                                                                                                                                                        +

                                                                                                                                                                        term 7 2025-08-16 ncurses 6.6 Miscellaneous

                                                                                                                                                                         term(7)                          Miscellaneous                         term(7)
 
 
-
-

                                                                                                                                                                        NAME

                                                                                                                                                                                term - conventions for naming terminal types
 
@@ -76,69 +74,69 @@
 
        In any case, you are free to override the system TERM setting  to  your
        taste in your shell profile.  The tset(1) utility may be of assistance;
-       you can give it a set of rules for deducing or  requesting  a  terminal
+       you  can  give  it a set of rules for deducing or requesting a terminal
        type based on the tty device and baud rate.
 
-       Setting  your  own  TERM value may also be useful if you have created a
-       custom entry incorporating options (such as  visual  bell  or  reverse-
-       video)  which  you  wish  to  override the system default type for your
+       Setting your own TERM value may also be useful if you  have  created  a
+       custom  entry  incorporating  options  (such as visual bell or reverse-
+       video) which you wish to override the  system  default  type  for  your
        line.
 
-       Terminal type descriptions are  stored  as  files  of  capability  data
-       underneath /usr/share/terminfo.  To browse a list of all terminal names
+       Terminal  type  descriptions  are  stored  as  files of capability data
+       underneath /usr/share/terminfo.  To browse a list of all terminal names
        recognized by the system, do
 
                toe | more
 
        from your shell.   These  capability  files  are  in  a  binary  format
        optimized for retrieval speed (unlike the old text-based termcap format
-       they replace); to examine  an  entry,  you  must  use  the  infocmp(1m)
+       they  replace);  to  examine  an  entry,  you  must use the infocmp(1m)
        command.  Invoke it as follows:
 
                infocmp entry_name
 
-       where  entry_name  is the name of the type you wish to examine (and the
-       name of its capability file  the  subdirectory  of  /usr/share/terminfo
-       named  for  its first letter).  This command dumps a capability file in
+       where entry_name is the name of the type you wish to examine  (and  the
+       name  of  its  capability  file the subdirectory of /usr/share/terminfo
+       named for its first letter).  This command dumps a capability  file  in
        the text format described by terminfo(5).
 
-       The first line of a terminfo(5) description gives the  names  by  which
-       terminfo  knows a terminal, separated by "|" (pipe-bar) characters with
+       The  first  line  of a terminfo(5) description gives the names by which
+       terminfo knows a terminal, separated by "|" (pipe-bar) characters  with
        the last name field terminated by a comma.  The first name field is the
        type's primary name, and is the one to use when setting TERM.  The last
-       name field (if distinct from the first) is actually  a  description  of
-       the  terminal  type  (it  may contain blanks; the others must be single
-       words).  Name fields between  the  first  and  last  (if  present)  are
+       name  field  (if  distinct from the first) is actually a description of
+       the terminal type (it may contain blanks; the  others  must  be  single
+       words).   Name  fields  between  the  first  and  last (if present) are
        aliases  for  the  terminal,  usually  historical  names  retained  for
        compatibility.
 
-       There are some conventions for how to  choose  terminal  primary  names
-       that  help  keep  them  informative and unique.  Here is a step-by-step
+       There  are  some  conventions  for how to choose terminal primary names
+       that help keep them informative and unique.   Here  is  a  step-by-step
        guide to naming terminals that also explains how to parse them:
 
-       First, choose a root name.  The  root  will  consist  of  a  lower-case
-       letter  followed by up to seven lower-case letters or digits.  You need
-       to avoid using punctuation characters in root names, because  they  are
+       First,  choose  a  root  name.   The  root will consist of a lower-case
+       letter followed by up to seven lower-case letters or digits.  You  need
+       to  avoid  using punctuation characters in root names, because they are
        used and interpreted as filenames and shell meta-characters (such as !,
        $, *, ?, etc.) embedded in them may cause odd and  unhelpful  behavior.
        The  slash  (/),  or  any  other  character  that may be interpreted by
        anyone's file system (\, $, [, ]), is especially dangerous (terminfo is
-       platform-independent,  and choosing names with special characters could
-       someday make life difficult for users of a future port).  The  dot  (.)
-       character  is  relatively safe as long as there is at most one per root
+       platform-independent, and choosing names with special characters  could
+       someday  make  life difficult for users of a future port).  The dot (.)
+       character is relatively safe as long as there is at most one  per  root
        name; some historical terminfo names use it.
 
-       The root name for a terminal or workstation console type should  almost
-       always  begin  with a vendor prefix (such as hp for Hewlett-Packard, wy
-       for Wyse, or att for AT&T terminals), or a common name of the  terminal
-       line  (vt  for  the  VT  series  of  terminals from DEC, or sun for Sun
-       Microsystems workstation  consoles,  or  regent  for  the  ADDS  Regent
-       series.   You  can  list  the  terminfo  tree  to see what prefixes are
-       already in common use.  The root name prefix should  be  followed  when
+       The  root name for a terminal or workstation console type should almost
+       always begin with a vendor prefix (such as hp for  Hewlett-Packard,  wy
+       for  Wyse, or att for AT&T terminals), or a common name of the terminal
+       line (vt for the VT series of  terminals  from  DEC,  or  sun  for  Sun
+       Microsystems  workstation  consoles,  or  regent  for  the  ADDS Regent
+       series.  You can list the  terminfo  tree  to  see  what  prefixes  are
+       already  in  common  use.  The root name prefix should be followed when
        appropriate by a model number; thus vt100, hp2621, wy50.
 
-       The  root  name for a PC-Unix console type should be the OS name, i.e.,
-       linux, bsdos, freebsd, netbsd.  It should not be console or  any  other
+       The root name for a PC-Unix console type should be the OS  name,  i.e.,
+       linux,  bsdos,  freebsd, netbsd.  It should not be console or any other
        generic that might cause confusion in a multi-platform environment!  If
        a model number follows, it should indicate either the OS release  level
        or the console driver release level.
@@ -161,7 +159,7 @@
 
        -m   Mono mode - suppress color support.
 
-       -na  No  arrow  keys  -  termcap  ignores arrow keys which are actually
+       -na  No arrow keys - termcap ignores  arrow  keys  which  are  actually
             there on the terminal, so the user can use the arrow keys locally.
 
        -nam No auto-margin - suppress am capability.
@@ -180,13 +178,13 @@
 
        -w   Wide; terminal is in 132-column mode.
 
-       Conventionally, if your terminal type is a variant intended to  specify
-       a  line  height,  that  suffix should go first.  So, for a hypothetical
-       FuBarCo model 2317 terminal in 30-line mode with  reverse  video,  best
+       Conventionally,  if your terminal type is a variant intended to specify
+       a line height, that suffix should go first.   So,  for  a  hypothetical
+       FuBarCo  model  2317  terminal in 30-line mode with reverse video, best
        form would be fubar-30-rv (rather than, say, "fubar-rv-30").
 
-       Terminal  types  that are written not as standalone entries, but rather
-       as components to be plugged into other entries  via  use  capabilities,
+       Terminal types that are written not as standalone entries,  but  rather
+       as  components  to  be plugged into other entries via use capabilities,
        are distinguished by using embedded plus signs rather than dashes.
 
        Commands which use a terminal type to control display often accept a -T
@@ -214,9 +212,7 @@

                                                                                                                                                                        SEE ALSO

                                                                                                                                                                                curses(3x), term(5), terminfo(5)
 
-
-
-ncurses 6.5                       2024-03-16                           term(7)
+ncurses 6.6                       2025-08-16                           term(7)
                                                                                                                                                                          diff --git a/doc/html/man/term_variables.3x.html b/doc/html/man/term_variables.3x.html index 99b6786..84d85ca 100644 --- a/doc/html/man/term_variables.3x.html +++ b/doc/html/man/term_variables.3x.html @@ -1,6 +1,6 @@ -term_variables 3x 2024-03-16 ncurses 6.5 Library calls +term_variables 3x 2025-11-11 ncurses 6.6 Library calls -

                                                                                                                                                                          term_variables 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                                          +

                                                                                                                                                                          term_variables 3x 2025-11-11 ncurses 6.6 Library calls

                                                                                                                                                                           term_variables(3x)               Library calls              term_variables(3x)
 
 
-
-

                                                                                                                                                                          NAME

                                                                                                                                                                                  SP,  acs_map,  boolcodes,  boolfnames,  boolnames,  cur_term, numcodes,
        numfnames, numnames, strcodes, strfnames, strnames, ttytype -  terminfo
@@ -78,105 +76,102 @@

                                                                                                                                                                          DESCRIPTION

                                                                                                                                                                          -       This  page  summarizes  variables provided by the curses library's low-
-       level terminfo interface.  A more complete description is given in  the
+       This  page summarizes variables provided by the curses library's lower-
+       level terminfo interface.  Locate a more complete  description  in  the
        curs_terminfo(3x) manual page.
 
-       Depending  on  the  configuration,  these  may  be actual variables, or
-       macros  (see  curs_threads(3x))  which  provide  read-only  access   to
-       curses's  state.   In  either  case,  applications should treat them as
-       read-only to avoid confusing the library.
+       Depending  on  ncurses's  build-time configuration, these may be actual
+       variables, or macros  (see  curs_threads(3x))  that  provide  read-only
+       access  to  curses's  state.  In either case, applications should treat
+       them as read-only to avoid confusing the library.

                                                                                                                                                                          Alternate Character Set Mapping

                                                                                                                                                                          -       After initializing the curses or terminfo interfaces, the acs_map array
-       holds  information  used to translate cells with the A_ALTCHARSET video
+       After initializing the curses or terminfo interfaces, the acs_map array
+       holds information used to translate cells with the  A_ALTCHARSET  video
        attribute into line-drawing characters.
 
        The encoding of the information in this array has changed periodically.
        Application  developers  need  only know that it is used for the "ACS_"
-       constants in <curses.h>.
+       constants in curses.h.
 
-       The comparable  data  for  the  wide-character  library  is  a  private
-       variable.
+       The comparable data for the wide-character library are not  exposed  as
+       symbols in the API.

                                                                                                                                                                          Current Terminal Data

                                                                                                                                                                          -       After  initializing  the  curses  or  terminfo interfaces, the cur_term
-       contains data describing the current terminal.  This variable  is  also
-       set as a side-effect of set_term(3x) and delscreen(3x).
+       After initializing the curses or terminfo interfaces, cur_term contains
+       data  describing  the  current  terminal.  It is also updated as a side
+       effect of set_term(3x) and delscreen(3x).
 
-       It  is  possible  to  save  a value of cur_term for subsequent use as a
-       parameter to set_term, for switching between  screens.   Alternatively,
-       one can save the return value from newterm or setupterm(3x) to reuse in
-       set_term.
+       It is possible to save a value of cur_term  for  subsequent  use  as  a
+       parameter    to    set_term(3x)    for   switching   between   screens.
+       Alternatively, one can  save  the  return  value  from  newterm(3x)  or
+       setupterm(3x) to reuse in set_term(3x).

                                                                                                                                                                          terminfo Lookup Tables

                                                                                                                                                                          -       The tic(1) and infocmp(1) programs use lookup tables for the  long  and
-       short  names  of  terminfo  capabilities,  as well as the corresponding
-       names  for  termcap  capabilities.   These  are  available   to   other
-       applications, although the hash-tables used by the terminfo and termcap
-       functions are not available.
+       The  tic(1)  and infocmp(1) programs use lookup tables for the long and
+       short names of terminfo capabilities,  as  well  as  the  corresponding
+       names   for   termcap  capabilities.   These  are  available  to  other
+       applications, though the hash tables used by the terminfo  and  termcap
+       functions are not.
 
-       The long terminfo capability names use a  "f"  (eff)  in  their  names:
-       boolfnames, numfnames, and strfnames.
-
-       These  are  the  short  names  for  terminfo  capabilities:  boolnames,
-       numnames, and strnames.
-
-       These are  the  corresponding  names  used  for  termcap  descriptions:
-       boolcodes, numcodes, and strcodes.
+       terminfo  stores  capability names in arrays with an "f" (eff) in their
+       names: boolfnames, numfnames, and strfnames.   It  stores  the  briefer
+       capability  codes  in  arrays without the "f": boolnames, numnames, and
+       strnames.  The corresponding termcap capability  codes  are  stored  in
+       boolcodes, numcodes, and strcodes.  terminfo(5) catalogs these.

                                                                                                                                                                          Terminal Type

                                                                                                                                                                                  A terminal description begins with one or more terminal names separated
-       by "|" (vertical bars).  On initialization of the  curses  or  terminfo
-       interfaces,  setupterm(3x)  copies  the  terminal  names  to  the array
+       by  "|"  (vertical  bars).  On initialization of the curses or terminfo
+       interfaces,  setupterm(3x)  copies  the  terminal  name  to  the  array
        ttytype.

                                                                                                                                                                          terminfo Names

                                                                                                                                                                          -       In addition to the variables, <term.h> also defines a symbol  for  each
-       terminfo  capability  long name.  These are in terms of the symbol CUR,
-       which is defined
+       In  addition  to  the  variables, term.h also defines a symbol for each
+       terminfo capability name.  These are in terms of the symbol CUR,  which
+       is defined
 
-       #define CUR ((TERMTYPE *)(cur_term))->
+              #define CUR ((TERMTYPE *)(cur_term))->
 
-       These  symbols  provide  a  faster   method   of   accessing   terminfo
-       capabilities than using tigetstr(3x), etc.
+       These   symbols   provide   a   faster  method  of  accessing  terminfo
+       capabilities than using, for example, tigetstr(3x).
 
-       The  actual definition of CUR depends upon the implementation, but each
-       terminfo library provides these long names defined to  point  into  the
-       current terminal description loaded into memory.
+       The definition of CUR is implementation-dependent,  but  each  terminfo
+       library  defines these names to point into the in-memory description of
+       the  current  terminal.   For  example,  in  ncurses,  the  expressions
+       tigetstr("key_dc") and "CUR Strings[59]" are equivalent.
 
 
-

                                                                                                                                                                          NOTES

                                                                                                                                                                          -       The  low-level  terminfo  interface is initialized using setupterm(3x).
-       The upper-level curses interface uses the low-level terminfo interface,
-       internally.
+

                                                                                                                                                                          terminfo and curses

                                                                                                                                                                          +       setupterm(3x)  initializes  the  lower-level  terminfo  interface.  The
+       higher-level curses interface uses the terminfo  interface  internally;
+       the symbol SP bridges the curses SCREEN type with the terminfo TERMINAL
+       type.

                                                                                                                                                                          PORTABILITY

                                                                                                                                                                          -       X/Open Curses does not describe any of these except for cur_term.  (The
-       inclusion  of  cur_term  appears  to  be  an  oversight,  since   other
-       comparable low-level information is omitted by X/Open).
+       X/Open  Curses  does  not  describe  any  of  these  symbols except for
+       cur_term.  (The inclusion of cur_term appears to be an oversight, since
+       other comparable low-level information is omitted by X/Open.)
 
-       Other    implementations   may   have   comparable   variables.    Some
+       Other   implementations   may   have   comparable   variables.     Some
        implementations provide the variables in their libraries, but omit them
        from the header files.
 
-       All  implementations  which provide terminfo interfaces add definitions
-       as described in the Terminfo Names section.  Most, but  not  all,  base
-       the definition upon the cur_term variable.
+       All implementations that provide terminfo interfaces add definitions as
+       described  in  the  "terminfo Names" section above.  Most, but not all,
+       base the definition upon the cur_term variable.

                                                                                                                                                                          SEE ALSO

                                                                                                                                                                                  curses(3x), curs_terminfo(3x), curs_threads(3x), terminfo(5)
 
-
-
-ncurses 6.5                       2024-03-16                term_variables(3x)
+ncurses 6.6                       2025-11-11                term_variables(3x)
                                                                                                                                                                          -
                                                                                                                                                                        • NOTES
                                                                                                                                                                        • PORTABILITY
                                                                                                                                                                        • SEE ALSO
                                                                                                                                                                        diff --git a/doc/html/man/terminfo.5.html b/doc/html/man/terminfo.5.html index 6706114..0fe0194 100644 --- a/doc/html/man/terminfo.5.html +++ b/doc/html/man/terminfo.5.html @@ -1,11 +1,14 @@ -terminfo 5 2024-04-20 ncurses 6.5 File formats +terminfo 5 2025-08-16 ncurses 6.6 File formats -

                                                                                                                                                                        terminfo 5 2024-04-20 ncurses 6.5 File formats

                                                                                                                                                                        +

                                                                                                                                                                        terminfo 5 2025-08-16 ncurses 6.6 File formats

                                                                                                                                                                         terminfo(5)                      File formats                      terminfo(5)
 
 
-
-

                                                                                                                                                                        NAME

                                                                                                                                                                                terminfo - terminal capability database
 
@@ -71,7 +72,7 @@
        have, by specifying how to perform screen operations, and by specifying
        padding requirements and initialization sequences.
 
-       This document describes ncurses version 6.5 (patch 20240427).
+       This document describes ncurses version 6.6 (patch 20251230).

                                                                                                                                                                        terminfo Entry Syntax

                                                                                                                                                                        @@ -107,10 +108,10 @@
 
            This implementation is not so strict; it allows mixed case  in  the
            primary name and aliases.  If the last name has no embedded blanks,
-           it allows that to be both an alias and a  verbose  name  (but  will
+           it  allows  that  to  be both an alias and a verbose name (but will
            warn about this ambiguity).
 
-       o   Lines  beginning  with  a  "#"  in  the first column are treated as
+       o   Lines beginning with a "#" in  the  first  column  are  treated  as
            comments.
 
            While comment lines are valid at any point, the output of captoinfo
@@ -121,8 +122,8 @@
        using  the  following  conventions.   The  particular piece of hardware
        making up the terminal should have a root name,  thus  "hp2621".   This
        name should not contain hyphens.  Modes that the hardware can be in, or
-       user preferences, should be indicated by appending a hyphen and a  mode
-       suffix.   Thus,  a  vt100  in  132-column  mode  would be vt100-w.  The
+       user  preferences, should be indicated by appending a hyphen and a mode
+       suffix.  Thus, a vt100  in  132-column  mode  would  be  vt100-w.   The
        following suffixes should be used where possible:
 
        Suffix   Example     Meaning
@@ -145,51 +146,51 @@

                                                                                                                                                                        terminfo Capabilities Syntax

                                                                                                                                                                        -       The terminfo entry consists of  several  capabilities,  i.e.,  features
-       that  the  terminal  has,  or  methods  for  exercising  the terminal's
+       The  terminfo  entry  consists  of several capabilities, i.e., features
+       that the  terminal  has,  or  methods  for  exercising  the  terminal's
        features.
 
        After the first field (giving the name(s) of the terminal entry), there
        should be one or more capability fields.  These are Boolean, numeric or
        string names with corresponding values:
 
-       o   Boolean capabilities are true  when  present,  false  when  absent.
+       o   Boolean  capabilities  are  true  when  present, false when absent.
            There is no explicit value for Boolean capabilities.
 
-       o   Numeric  capabilities  have  a  "#"  following  the  name,  then an
+       o   Numeric capabilities  have  a  "#"  following  the  name,  then  an
            unsigned decimal integer value.
 
-       o   String capabilities have a "=" following the name, then  an  string
+       o   String  capabilities  have a "=" following the name, then an string
            of characters making up the capability value.
 
-           String  capabilities  can be split into multiple lines, just as the
-           fields comprising a terminal  entry  can  be  split  into  multiple
-           lines.   While  blanks  between fields are ignored, blanks embedded
-           within a string value are retained, except for leading blanks on  a
+           String capabilities can be split into multiple lines, just  as  the
+           fields  comprising  a  terminal  entry  can  be split into multiple
+           lines.  While blanks between fields are  ignored,  blanks  embedded
+           within  a string value are retained, except for leading blanks on a
            line.
 
-       Any  capability  can  be  canceled,  i.e., suppressed from the terminal
+       Any capability can be canceled,  i.e.,  suppressed  from  the  terminal
        entry, by following its name with "@" rather than a capability value.

                                                                                                                                                                        Similar Terminals

                                                                                                                                                                        -       If there are two very similar  terminals,  one  (the  variant)  can  be
-       defined   as  being  just  like  the  other  (the  base)  with  certain
-       exceptions.  In the definition of the variant,  the  string  capability
+       If  there  are  two  very  similar  terminals, one (the variant) can be
+       defined  as  being  just  like  the  other  (the  base)  with   certain
+       exceptions.   In  the  definition of the variant, the string capability
        use can be given with the name of the base terminal:
 
-       o   The  capabilities  given before use override those in the base type
+       o   The capabilities given before use override those in the  base  type
            named by use.
 
-       o   If there are multiple use capabilities, they are merged in  reverse
-           order.   That  is,  the rightmost use reference is processed first,
+       o   If  there are multiple use capabilities, they are merged in reverse
+           order.  That is, the rightmost use reference  is  processed  first,
            then the one to its left, and so forth.
 
-       o   Capabilities given explicitly in the entry override  those  brought
+       o   Capabilities  given  explicitly in the entry override those brought
            in by use references.
 
-       A  capability  can  be  canceled  by placing xx@ to the left of the use
-       reference that imports it, where xx is the  capability.   For  example,
+       A capability can be canceled by placing xx@ to  the  left  of  the  use
+       reference  that  imports  it, where xx is the capability.  For example,
        the entry
 
               2621-nl, smkx@, rmkx@, use=2621,
@@ -200,15 +201,15 @@
        user preferences.
 
        An entry included via use can contain canceled capabilities, which have
-       the  same  effect as if those cancels were inline in the using terminal
+       the same effect as if those cancels were inline in the  using  terminal
        entry.
 
 
-

                                                                                                                                                                        Predefined Capabilities

                                                                                                                                                                        -       Tables of capabilities ncurses recognizes in a terminfo  terminal  type
+

                                                                                                                                                                        Standard Capabilities

                                                                                                                                                                        +       Tables  of  capabilities ncurses recognizes in a terminfo terminal type
        description and available to terminfo-using code follow.
 
-       o   The  capability  name identifies the symbol by which the programmer
+       o   The capability name identifies the symbol by which  the  programmer
            using the terminfo API accesses the capability.
 
        o   The TI (terminfo) code is the short name used by a person composing
@@ -219,38 +220,36 @@
            uses identical or very similar names).  Semantics are also intended
            to match those of the specification.
 
-           terminfo codes have no hard length limit, but ncurses maintains  an
-           informal  one  of  5 characters to keep them short and to allow the
-           tabs in the source file Caps to line  up  nicely.   (Some  standard
+           terminfo  codes have no hard length limit, but ncurses maintains an
+           informal one of 5 characters to keep them short and  to  allow  the
+           tabs  in  the  source  file Caps to line up nicely.  (Some standard
            codes exceed this limit regardless.)
 
-       o   The  TC  (termcap)  code  is  that used by the corresponding API of
-           ncurses.  (Some capabilities are  new,  and  have  names  that  BSD
+       o   The TC (termcap) code is that used  by  the  corresponding  API  of
+           ncurses.   (Some  capabilities  are  new,  and  have names that BSD
            termcap did not originate.)
 
-       o   The   description   field   attempts  to  convey  the  capability's
+       o   The  description  field  attempts  to   convey   the   capability's
            semantics.
 
        The description field employs a handful of notations.
 
        (P)    indicates that padding may be specified.
 
-       (P*)   indicates that padding may vary in proportion to the  number  of
+       (P*)   indicates  that  padding may vary in proportion to the number of
               output lines affected.
 
-       #i     indicates   the  ith  parameter  of  a  string  capability;  the
-              programmer  should  pass  the  string  to  tparm(3x)  with   the
+       #i     indicates  the  ith  parameter  of  a  string  capability;   the
+              programmer   should  pass  the  string  to  tparm(3x)  with  the
               parameters listed.
 
-              If  the  description  lists no parameters, passing the string to
-              tparm(3x) may produce unexpected behavior, for instance  if  the
+              If the description lists no parameters, passing  the  string  to
+              tparm(3x)  may  produce unexpected behavior, for instance if the
               string contains percent signs.
 
                                       Code
        Boolean Capability Name    TI        TC  Description
        ------------------------------------------------------------------------
-
-
        auto_left_margin           bw        bw  cub1 wraps from column 0 to
                                                 last column
        auto_right_margin          am        am  terminal has automatic margins
@@ -316,7 +315,6 @@
                                                 resolution
 
                                       Code
-
        Numeric Capability Name    TI        TC  Description
        ------------------------------------------------------------------------
        columns                    cols      co  number of columns in a line
@@ -382,7 +380,6 @@
        wide_char_size             widcs     Yn  character step size when in
                                                 double wide mode
        buttons                    btns      BT  number of buttons on mouse
-
        bit_image_entwining        bitwin    Yo  number of passes for each bit-
                                                 image row
        bit_image_type             bitype    Yp  type of bit-image device
@@ -448,7 +445,6 @@
                                                 cup
        exit_delete_mode           rmdc      ed  end delete mode
        exit_insert_mode           rmir      ei  exit insert mode
-
        exit_standout_mode         rmso      se  exit standout mode
        exit_underline_mode        rmul      ue  exit underline mode
        flash_screen               flash     vb  visible bell (may not move
@@ -471,7 +467,6 @@
        key_dc                     kdch1     kD  delete-character key
        key_dl                     kdl1      kL  delete-line key
        key_down                   kcud1     kd  down-arrow key
-
        key_eic                    krmir     kM  sent by rmir or smir in insert
                                                 mode
        key_eol                    kel       kE  clear-to-end-of-line key
@@ -499,8 +494,8 @@
        key_sr                     kri       kR  scroll-backward key
        key_stab                   khts      kT  set-tab key
        key_up                     kcuu1     ku  up-arrow key
-       keypad_local               rmkx      ke  leave keyboard transmit mode
-       keypad_xmit                smkx      ks  enter keyboard transmit mode
+       keypad_local               rmkx      ke  leave keypad transmit mode
+       keypad_xmit                smkx      ks  enter keypad transmit mode
        lab_f0                     lf0       l0  label on function key f0 if
                                                 not f0
        lab_f1                     lf1       l1  label on function key f1 if
@@ -513,8 +508,6 @@
                                                 not f3
        lab_f4                     lf4       l4  label on function key f4 if
                                                 not f4
-
-
        lab_f5                     lf5       l5  label on function key f5 if
                                                 not f5
        lab_f6                     lf6       l6  label on function key f6 if
@@ -525,6 +518,7 @@
                                                 not f8
        lab_f9                     lf9       l9  label on function key f9 if
                                                 not f9
+
        meta_off                   rmm       mo  turn off meta mode
        meta_on                    smm       mm  turn on meta mode (8th-bit on)
        newline                    nel       nw  newline (behave like cr
@@ -554,7 +548,6 @@
        repeat_char                rep       rp  repeat char #1 #2 times (P*)
        reset_1string              rs1       r1  reset string
        reset_2string              rs2       r2  reset string
-
        reset_3string              rs3       r3  reset string
        reset_file                 rf        rf  name of reset file
        restore_cursor             rc        rc  restore cursor to position of
@@ -580,7 +573,6 @@
        init_prog                  iprog     iP  path name of program for
                                                 initialization
        key_a1                     ka1       K1  upper left of keypad
-
        key_a3                     ka3       K3  upper right of keypad
        key_b2                     kb2       K2  center of keypad
        key_c1                     kc1       K4  lower left of keypad
@@ -630,7 +622,6 @@
        key_save                   ksav      &6  save key
        key_suspend                kspd      &7  suspend key
        key_undo                   kund      &8  undo key
-
        key_sbeg                   kBEG      &9  shifted begin key
        key_scancel                kCAN      &0  shifted cancel key
        key_scommand               kCMD      *1  shifted command key
@@ -646,7 +637,6 @@
        key_sfind                  kFND      *0  shifted find key
        key_shelp                  kHLP      #1  shifted help key
        key_shome                  kHOM      #2  shifted home key
-
        key_sic                    kIC       #3  shifted insert-character key
        key_sleft                  kLFT      #4  shifted left-arrow key
        key_smessage               kMSG      %a  shifted message key
@@ -696,7 +686,6 @@
        key_f40                    kf40      FU  F40 function key
        key_f41                    kf41      FV  F41 function key
        key_f42                    kf42      FW  F42 function key
-
        key_f43                    kf43      FX  F43 function key
        key_f44                    kf44      FY  F44 function key
        key_f45                    kf45      FZ  F45 function key
@@ -712,7 +701,6 @@
        key_f55                    kf55      Fj  F55 function key
        key_f56                    kf56      Fk  F56 function key
        key_f57                    kf57      Fl  F57 function key
-
        key_f58                    kf58      Fm  F58 function key
        key_f59                    kf59      Fn  F59 function key
        key_f60                    kf60      Fo  F60 function key
@@ -776,9 +764,7 @@
        define_char                defc      ZE  Define a character #1, #2 dots
                                                 wide, descender #3
        enter_doublewide_mode      swidm     ZF  Enter double-wide mode
-
        enter_draft_quality        sdrfq     ZG  Enter draft-quality mode
-
        enter_italics_mode         sitm      ZH  Enter italic mode
        enter_leftward_mode        slm       ZI  Start leftward carriage motion
        enter_micro_mode           smicm     ZJ  Start micro-motion mode
@@ -863,6 +849,7 @@
                                                 using ANSI escape
        set_a_background           setab     AB  Set background color to #1,
                                                 using ANSI escape
+
        pkey_plab                  pfxl      xl  Program function key #1 to
                                                 type string #2 and show string
                                                 #3
@@ -910,7 +897,6 @@
        binary-compatible with System V terminfo entries after SVr4.1; beware!
 
                                       Code
-
        String Capability Name     TI        TC  Description
        ------------------------------------------------------------------------
        enter_horizontal_hl_mode   ehhlm     Xh  Enter horizontal highlight
@@ -929,51 +915,54 @@

                                                                                                                                                                        User-Defined Capabilities

                                                                                                                                                                        -       The  preceding  section  listed the predefined capabilities.  They deal
-       with some special features for terminals no longer (or possibly  never)
-       produced.   Occasionally  there are special features of newer terminals
-       which are awkward or impossible to represent by reusing the  predefined
-       capabilities.
+       The preceding section  listed  the  standard  capabilities.   Some  are
+       esoteric,  supporting  functionality  that  terminal  emulators  do not
+       implement, or may never have been realized  in  manufactured  hardware.
+       Occasionally,  emulators  have  special  features  that  are awkward or
+       impossible to represent via standard capabilities.
 
-       ncurses    addresses   this   limitation   by   allowing   user-defined
-       capabilities.  The tic and infocmp programs provide the -x  option  for
-       this purpose.  When -x is set, tic treats unknown capabilities as user-
-       defined.  That is, if tic encounters a capability name  which  it  does
-       not  recognize, it infers its type (Boolean, number or string) from the
-       syntax and makes an extended table  entry  for  that  capability.   The
-       use_extended_names(3x)  function  makes  this information conditionally
-       available to applications.   The  ncurses  library  provides  the  data
-       leaving most of the behavior to applications:
+       ncurses   addresses   this   limitation   by   allowing    user-defined
+       capabilities.   The  tic  and infocmp programs provide an -x option for
+       this purpose.  When -x is used,  tic  treats  unknown  capabilities  as
+       user-defined.   That  is,  if  tic encounters a capability name that it
+       does not recognize, the program infers the capability's type  (Boolean,
+       numeric,  or  string) from the syntax of the capability value and makes
+       an extended table entry for  that  capability.   use_extended_names(3x)
+       makes   this   information  conditionally  available  to  applications.
+       ncurses library functions supply  callers  with  capability  data,  the
+       interpretation of which is mostly up to the application.
 
-       o   User-defined  capability  strings  whose  name  begins with "k" are
-           treated as function keys.
+       o   ncurses  treats  user-defined string capabilities whose names begin
+           with "k" as function keys.
 
-       o   The types (Boolean,  number,  string)  determined  by  tic  can  be
-           inferred by successful calls on tigetflag, etc.
+       o   Capability types (Boolean, numeric, or string)  determined  by  tic
+           can  be  inferred  by  successful  tigetflag(3x), tigetnum(3x), and
+           tigetstr(3x) calls.
 
        o   If the capability name happens to be two characters, the capability
            is also available through the termcap interface.
 
-       While termcap is said to be  extensible  because  it  does  not  use  a
-       predefined  set of capabilities, in practice it has been limited to the
-       capabilities defined by terminfo implementations.   As  a  rule,  user-
-       defined capabilities intended for use by termcap applications should be
-       limited to Booleans and numbers to avoid running  past  the  1023  byte
-       limit  assumed  by  termcap implementations and their applications.  In
-       particular, providing extended sets  of  function  keys  (past  the  60
-       numbered keys and the handful of special named keys) is best done using
-       the longer names available using terminfo.
+       While  termcap  is  said  to  be  extensible  because  it  mandates  no
+       capabilities, in practice it has been limited to those defined by term-
+       info implementations.  As a rule, employ only user-defined capabilities
+       of  Boolean  and  numeric  type  with  termcap  applications  to  avoid
+       overrunning the 1023 byte limit assumed by termcap implementations  and
+       their   applications.   Specifically,  support  for  extended  sets  of
+       function keys (past the 60 numbered keys and  the  handful  of  special
+       named  keys)  is  better achieved with longer names available via term-
+       info.
 
        The ncurses library uses a few of these user-defined  capabilities,  as
-       described  in user_caps(5).  Other user-defined capabilities (including
-       function keys) are described in the terminal database, in  the  section
-       on NCURSES USER-DEFINABLE CAPABILITIES
+       described   in  user_caps(5).   For  other  user-defined  capabilities,
+       including function keys,  consult  the  source  form  of  the  terminal
+       database,  terminfo.src,  under  the  heading  "NCURSES  USER-DEFINABLE
+       CAPABILITIES".

                                                                                                                                                                        A Sample Entry

                                                                                                                                                                        -       The   following   entry,   describing  an  ANSI-standard  terminal,  is
-       representative of what a terminfo entry for a modern terminal typically
-       looks like.
+       The following entry, describing an ANSI X3.64- (or ECMA-48-)  -standard
+       terminal (henceforth "ANSI-standard" for brevity), is representative of
+       what a terminfo entry for a modern terminal typically looks like.
 
        ansi|ansi/pc-term compatible with color,
                am, mc5i, mir, msgr,
@@ -1016,7 +1005,7 @@
        o   numeric capabilities giving the size of the terminal or the size of
            particular delays, and
 
-       o   string  capabilities,  which  give  a sequence which can be used to
+       o   string capabilities, which give a sequence which  can  be  used  to
            perform particular terminal operations.
 
 
@@ -1027,15 +1016,15 @@
        am.   Hence  the description of ansi includes am.  Numeric capabilities
        are followed by the character "#" and  then  a  positive  value.   Thus
        cols, which indicates the number of columns the terminal has, gives the
-       value "80" for ansi.  Values for numeric capabilities may be  specified
-       in  decimal,  octal,  or  hexadecimal, using the C programming language
+       value  "80" for ansi.  Values for numeric capabilities may be specified
+       in decimal, octal, or hexadecimal, using  the  C  programming  language
        conventions (e.g., 255, 0377 and 0xff or 0xFF).
 
-       Finally, string valued capabilities, such as el (clear to end  of  line
-       sequence)  are  given  by  the  two-character  code, an "=", and then a
+       Finally,  string  valued capabilities, such as el (clear to end of line
+       sequence) are given by the two-character  code,  an  "=",  and  then  a
        string ending at the next following ",".
 
-       A number  of  escape  sequences  are  provided  in  the  string  valued
+       A  number  of  escape  sequences  are  provided  in  the  string valued
        capabilities for easy encoding of characters there:
 
        o   Both \E and \e map to an ESCAPE character,
@@ -1055,8 +1044,8 @@
        X/Open Curses does not say what "appropriate x" might be.  In practice,
        that is a printable ASCII graphic character.  The special case "^?"  is
        interpreted  as  DEL (127).  In all other cases, the character value is
-       AND'd with 0x1f, mapping to ASCII control codes in the range 0  through
-       31.
+       logically "and"-ed with 0x1f, mapping to ASCII  control  codes  in  the
+       range 0 through 31.
 
        Other escapes include
 
@@ -1071,28 +1060,28 @@
        o   and \0 for null.
 
            \0 will produce \200, which does not terminate a string but behaves
-           as a null character on most terminals, providing CS7 is  specified.
+           as  a null character on most terminals, providing CS7 is specified.
            See stty(1).
 
-           The  reason  for  this quirk is to maintain binary compatibility of
-           the compiled terminfo files with other implementations,  e.g.,  the
-           SVr4  systems,  which  document  this.  Compiled terminfo files use
-           null-terminated strings, with no  lengths.   Modifying  this  would
-           require  a  new  binary  format,  which  would  not work with other
+           The reason for this quirk is to maintain  binary  compatibility  of
+           the  compiled  terminfo files with other implementations, e.g., the
+           SVr4 systems, which document this.   Compiled  terminfo  files  use
+           null-terminated  strings,  with  no  lengths.  Modifying this would
+           require a new binary  format,  which  would  not  work  with  other
            implementations.
 
        Finally, characters may be given as three octal digits after a \.
 
-       A delay in milliseconds may appear anywhere  in  a  string  capability,
-       enclosed  in  $<..>  brackets, as in el=\EK$<5>, and padding characters
+       A  delay  in  milliseconds  may appear anywhere in a string capability,
+       enclosed in $<..> brackets, as in el=\EK$<5>,  and  padding  characters
        are supplied by tputs(3x) to provide this delay.
 
-       o   The delay must be a number  with  at  most  one  decimal  place  of
+       o   The  delay  must  be  a  number  with  at most one decimal place of
            precision; it may be followed by suffixes "*" or "/" or both.
 
-       o   A  "*"  indicates  that the padding required is proportional to the
-           number of lines affected by the operation, and the amount given  is
-           the  per-affected-unit  padding  required.   (In the case of insert
+       o   A "*" indicates that the padding required is  proportional  to  the
+           number  of lines affected by the operation, and the amount given is
+           the per-affected-unit padding required.  (In  the  case  of  insert
            character, the factor is still the number of lines affected.)
 
            Normally, padding is advisory if the device has the xon capability;
@@ -1102,37 +1091,37 @@
            delay of the given number of milliseconds even on devices for which
            xon is present to indicate flow control.
 
-       Sometimes  individual  capabilities must be commented out.  To do this,
-       put a period before the capability name.  For example, see  the  second
+       Sometimes individual capabilities must be commented out.  To  do  this,
+       put  a  period before the capability name.  For example, see the second
        ind in the example above.

                                                                                                                                                                        Fetching Compiled Descriptions

                                                                                                                                                                        -       Terminal  descriptions  in  ncurses  are  stored in terminal databases.
-       These databases, which are found by their pathname, may  be  configured
+       Terminal descriptions in ncurses  are  stored  in  terminal  databases.
+       These  databases,  which are found by their pathname, may be configured
        either as directory trees or hashed databases (see term(5)),
 
-       The  library  uses  a  compiled-in  list  of  pathnames,  which  can be
+       The library  uses  a  compiled-in  list  of  pathnames,  which  can  be
        overridden  by  environment  variables.   Before  starting  to  search,
-       ncurses  checks  the  search list, eliminating duplicates and pathnames
-       where no terminal database is found.  The  ncurses  library  reads  the
+       ncurses checks the search list, eliminating  duplicates  and  pathnames
+       where  no  terminal  database  is found.  The ncurses library reads the
        first description which passes its consistency checks.
 
-       o   The  environment variable TERMINFO is checked first, for a terminal
+       o   The environment variable TERMINFO is checked first, for a  terminal
            database containing the terminal description.
 
        o   Next, ncurses looks in $HOME/.terminfo for a compiled description.
 
-           This is an optional feature which may be omitted entirely from  the
+           This  is an optional feature which may be omitted entirely from the
            library,  or  limited  to  prevent  accidental  use  by  privileged
            applications.
 
-       o   Next, if the environment variable  TERMINFO_DIRS  is  set,  ncurses
-           interprets  the  contents  of  that  variable  as  a list of colon-
+       o   Next,  if  the  environment  variable TERMINFO_DIRS is set, ncurses
+           interprets the contents of  that  variable  as  a  list  of  colon-
            separated pathnames of terminal databases to be searched.
 
-           An empty pathname (i.e., if the variable  begins  or  ends  with  a
-           colon,  or  contains  adjacent colons) is interpreted as the system
+           An  empty  pathname  (i.e.,  if  the variable begins or ends with a
+           colon, or contains adjacent colons) is interpreted  as  the  system
            location /usr/share/terminfo.
 
        o   Finally, ncurses searches these compiled-in locations:
@@ -1161,8 +1150,8 @@
        effective  way  to  prepare  a terminal description is by imitating the
        description of a similar  terminal  in  terminfo  and  to  build  up  a
        description gradually, using partial descriptions with vi or some other
-       screen-oriented program to check that they are correct.  Be aware  that
-       a  very  unusual terminal may expose deficiencies in the ability of the
+       screen-oriented  program to check that they are correct.  Be aware that
+       a very unusual terminal may expose deficiencies in the ability  of  the
        terminfo file to describe it or bugs in the screen-handling code of the
        test program.
 
@@ -1182,13 +1171,13 @@
        can clear its screen, leaving the cursor in  the  home  position,  then
        this  is  given  by  the  clear  string  capability.   If  the terminal
        overstrikes (rather than clearing a position when a character is struck
-       over)  then  it  should  have  the os capability.  If the terminal is a
+       over) then it should have the os capability.   If  the  terminal  is  a
        printing terminal, with no soft copy unit, give it both hc and os.  (os
        applies  to  storage scope terminals, such as TEKTRONIX 4010 series, as
        well as hard copy and APL terminals.)  If there is a code to  move  the
-       cursor to the left edge of the current row, give this as cr.  (Normally
-       this will be carriage return,  control/M.)   If  there  is  a  code  to
-       produce an audible signal (bell, beep, etc) give this as bel.
+       cursor  to  the  left  edge  of  the  current  line,  give  this as cr.
+       (Normally this will be carriage return, control/M.)  If there is a code
+       to produce an audible signal (bell, beep, etc) give this as bel.
 
        If there is a code to move the cursor one position to the left (such as
        backspace) that capability should be given as cub1.   Similarly,  codes
@@ -1198,7 +1187,7 @@
        space would erase the character moved over.
 
        A very important point here is that the local cursor motions encoded in
-       terminfo  are  undefined  at  the left and top edges of a CRT terminal.
+       terminfo are undefined at the left and top edges  of  a  CRT  terminal.
        Programs should never attempt to backspace around the left edge, unless
        bw  is given, and never attempt to go up locally off the top.  In order
        to scroll text up, a program will go to the bottom left corner  of  the
@@ -1208,17 +1197,17 @@
        screen and sends the ri (reverse index) string.  The strings ind and ri
        are undefined when not on their respective corners of the screen.
 
-       Parameterized  versions  of  the  scrolling  sequences are indn and rin
-       which have the same semantics as ind and ri except that they  take  one
-       parameter,  and scroll that many lines.  They are also undefined except
+       Parameterized versions of the scrolling  sequences  are  indn  and  rin
+       which  have  the same semantics as ind and ri except that they take one
+       parameter, and scroll that many lines.  They are also undefined  except
        at the appropriate edge of the screen.
 
-       The am capability tells whether the cursor sticks at the right edge  of
-       the  screen when text is output, but this does not necessarily apply to
-       a cuf1 from the last column.  The only local motion  which  is  defined
-       from  the  left  edge is if bw is given, then a cub1 from the left edge
-       will move to the right edge of the previous row.  If bw is  not  given,
-       the  effect  is undefined.  This is useful for drawing a box around the
+       The  am capability tells whether the cursor sticks at the right edge of
+       the screen when text is output, but this does not necessarily apply  to
+       a  cuf1  from  the last column.  The only local motion which is defined
+       from the left edge is if bw is given, then a cub1 from  the  left  edge
+       will  move to the right edge of the previous line.  If bw is not given,
+       the effect is undefined.  This is useful for drawing a box  around  the
        edge of the screen, for example.  If the terminal has switch selectable
        automatic  margins,  the terminfo file usually assumes that this is on;
        i.e., am.  If the terminal has a  command  which  moves  to  the  first
@@ -1244,17 +1233,17 @@
        Cursor  addressing  and  other  strings  requiring  parameters  in  the
        terminal are described  by  a  parameterized  string  capability,  with
        printf-like  escapes  such  as  %x  in it.  For example, to address the
-       cursor, the cup capability is given, using two parameters: the row  and
-       column  to  address  to.   (Rows and columns are numbered from zero and
-       refer to the physical screen visible to the user,  not  to  any  unseen
-       memory.)   If  the terminal has memory relative cursor addressing, that
+       cursor, the cup capability is given, using two parameters: the line and
+       column to address to.  (Lines and columns are numbered  from  zero  and
+       refer  to  the  physical  screen visible to the user, not to any unseen
+       memory.)  If the terminal has memory relative cursor  addressing,  that
        can be indicated by mrcup.
 
-       The parameter mechanism uses a stack and special % codes to  manipulate
-       it.   Typically  a  sequence  will  push one of the parameters onto the
-       stack and then print it in  some  format.   Print  (e.g.,  "%d")  is  a
-       special  case.  Other operations, including "%t" pop their operand from
-       the stack.   It  is  noted  that  more  complex  operations  are  often
+       The  parameter mechanism uses a stack and special % codes to manipulate
+       it.  Typically a sequence will push one  of  the  parameters  onto  the
+       stack  and  then  print  it  in  some  format.  Print (e.g., "%d") is a
+       special case.  Other operations, including "%t" pop their operand  from
+       the  stack.   It  is  noted  that  more  complex  operations  are often
        necessary, e.g., in the sgr string.
 
        The % encodings have the following meanings:
@@ -1262,7 +1251,7 @@
        %%   outputs "%"
 
        %[[:]flags][width[.precision]][doxXs]
-            as  in  printf(3),  flags are [-+#] and space.  Use a ":" to allow
+            as in printf(3), flags are [-+#] and space.  Use a  ":"  to  allow
             the next character to be a "-" flag, avoiding interpreting "%-" as
             an operator.
 
@@ -1287,7 +1276,7 @@
 
             The  terms  "static"  and "dynamic" are misleading.  Historically,
             these are simply two different sets of variables, whose values are
-            not  reset  between calls to tparm(3x).  However, that fact is not
+            not reset between calls to tparm(3x).  However, that fact  is  not
             documented in other implementations.  Relying on it will adversely
             impact portability to other implementations:
 
@@ -1332,13 +1321,14 @@
             arithmetic (%m is mod): push(pop() op pop())
 
        %&, %|, %^
-            bit operations (AND, OR and exclusive-OR): push(pop() op pop())
+            bit operations ("and", "or" and  exclusive  "or"):  push(pop()  op
+            pop())
 
        %=, %>, %<
             logical operations: push(pop() op pop())
 
        %A, %O
-            logical AND and OR operations (for conditionals)
+            logical "and" and "or" operations (for conditionals)
 
        %!, %~
             unary operations (logical and bit complement): push(op pop())
@@ -1347,8 +1337,8 @@
 
        %? expr %t thenpart %e elsepart %;
             This forms an if-then-else.  The %e elsepart is optional.  Usually
-            the %? expr part pushes a value onto the stack,  and  %t  pops  it
-            from  the  stack,  testing if it is nonzero (true).  If it is zero
+            the  %?  expr  part  pushes a value onto the stack, and %t pops it
+            from the stack, testing if it is nonzero (true).  If  it  is  zero
             (false), control passes to the %e (else) part.
 
             It is possible to form else-if's a la Algol 68:
@@ -1356,7 +1346,7 @@
 
             where ci are conditions, bi are bodies.
 
-            Use the -f option of tic or infocmp to see the  structure  of  if-
+            Use  the  -f  option of tic or infocmp to see the structure of if-
             then-else's.  Some strings, e.g., sgr can be very complicated when
             written on one line.  The -f option splits the string  into  lines
             with the parts indented.
@@ -1365,25 +1355,25 @@
        order.  That is, to get x-5 one  would  use  "%gx%{5}%-".   %P  and  %g
        variables are persistent across escape-string evaluations.
 
-       Consider  the HP2645, which, to get to row 3 and column 12, needs to be
-       sent \E&a12c03Y padded for 6 milliseconds.  The order of the  rows  and
-       columns  is  inverted  here,  and the row and column are printed as two
+       Consider the HP2645, which, to get to line 3 and column 12, needs to be
+       sent  \E&a12c03Y padded for 6 milliseconds.  The order of the lines and
+       columns is inverted here, and the lines and column are printed  as  two
        digits.  The corresponding terminal description is expressed thus:
               cup=\E&a%p2%dc%p1%dY$<6>,
 
-       The Microterm ACT-IV needs the current row and column sent preceded  by
-       a ^T, with the row and column simply encoded in binary,
+       The Microterm ACT-IV needs the current line and column sent preceded by
+       a ^T, with the line and column simply encoded in binary,
               cup=^T%p1%c%p2%c
 
        Terminals  which  use  "%c"  need  to  be  able to backspace the cursor
        (cub1), and to move the cursor up one line on the screen (cuu1).   This
        is necessary because it is not always safe to transmit \n ^D and \r, as
-       the system may change or discard them.  (The library  routines  dealing
-       with  terminfo  set tty modes so that tabs are never expanded, so \t is
+       the  system  may change or discard them.  (The library routines dealing
+       with terminfo set tty modes so that tabs are never expanded, so  \t  is
        safe to send.  This turns out to be essential for the Ann Arbor 4080.)
 
-       A final example is the LSI ADM-3a, which uses row and column offset  by
-       a blank character, thus
+       A final example is the LSI ADM-3A, which uses line and column offset by
+       a space, thus
               cup=\E=%p1%' '%+%c%p2%' '%+%c
 
        After  sending "\E=", this pushes the first parameter, pushes the ASCII
@@ -1404,8 +1394,8 @@
        corner of the screen, not of memory.  (Thus, the  \EH  sequence  on  HP
        terminals cannot be used for home.)
 
-       If the terminal has row or column absolute cursor addressing, these can
-       be given as single  parameter  capabilities  hpa  (horizontal  position
+       If  the  terminal  has line or column absolute cursor addressing, these
+       can be given as single parameter capabilities hpa (horizontal  position
        absolute)  and  vpa  (vertical position absolute).  Sometimes these are
        shorter than the more general  two  parameter  sequence  (as  with  the
        hp2645)   and  can  be  used  in  preference  to  cup.   If  there  are
@@ -1416,10 +1406,10 @@
 
        If  the  terminal  needs to be in a special mode when running a program
        that uses these capabilities, the codes to enter and exit this mode can
-       be  given as smcup and rmcup.  This arises, for example, from terminals
-       like the Concept with more than one page of memory.   If  the  terminal
-       has  only  memory  relative  cursor  addressing and not screen relative
-       cursor addressing, a one screen-sized window must  be  fixed  into  the
+       be given as smcup and rmcup.  This arises, for example, from  terminals
+       like  the  Concept  with more than one page of memory.  If the terminal
+       has only memory relative cursor  addressing  and  not  screen  relative
+       cursor  addressing,  a  one  screen-sized window must be fixed into the
        terminal for cursor addressing to work properly.  This is also used for
        the TEKTRONIX 4025, where smcup sets the command character  to  be  the
        one  used  by  terminfo.   If  the  smcup sequence will not restore the
@@ -1433,7 +1423,7 @@
        were intended for use with printers.
 
        o   The two terminal capabilities assume that the terminal may have the
-           capability of setting the left and/or right margin at  the  current
+           capability  of  setting the left and/or right margin at the current
            cursor column position.
 
        o   The printer capabilities assume that the printer may have two types
@@ -1442,22 +1432,22 @@
            o   the ability to set a top and/or bottom margin using the current
                line position, and
 
-           o   parameterized  capabilities  for setting the top, bottom, left,
-               right margins given the number of rows or columns.
+           o   parameterized capabilities for setting the top,  bottom,  left,
+               right margins given the number of lines or columns.
 
-       In practice, the categorization into "terminal" and  "printer"  is  not
+       In  practice,  the  categorization into "terminal" and "printer" is not
        suitable:
 
-       o   The  AT&T  SVr4  terminal  database  uses smgl four times, for AT&T
+       o   The AT&T SVr4 terminal database uses  smgl  four  times,  for  AT&T
            hardware.
 
-           Three of the four are printers.   They  lack  the  ability  to  set
+           Three  of  the  four  are  printers.   They lack the ability to set
            left/right margins by specifying the column.
 
-       o   Other  (non-AT&T) terminals may support margins but using different
+       o   Other (non-AT&T) terminals may support margins but using  different
            assumptions from AT&T.
 
-           For instance, the DEC VT420 supports left/right margins,  but  only
+           For  instance,  the DEC VT420 supports left/right margins, but only
            using a column parameter.  As an added complication, the VT420 uses
            two settings to fully enable left/right margins (left/right  margin
            mode,  and  origin  mode).   The  former enables the margins, which
@@ -1466,7 +1456,7 @@
 
        o   Both  DEC  VT420  left/right  margins are set with a single control
            sequence.  If either is omitted, the corresponding margin is set to
-           the  left  or  right  edge  of the display (rather than leaving the
+           the left or right edge of the  display  (rather  than  leaving  the
            margin unmodified).
 
        These are the margin-related capabilities:
@@ -1484,15 +1474,15 @@
                  smglr   Set both left and right margins to L and R
                  smgtb   Set both top and bottom margins to T and B
 
-       When writing an application that uses these  string  capabilities,  the
-       pairs  should be first checked to see if each capability in the pair is
+       When  writing  an  application that uses these string capabilities, the
+       pairs should be first checked to see if each capability in the pair  is
        set or only one is set:
 
-       o   If both smglp and smgrp  are  set,  each  is  used  with  a  single
-           argument,  N,  that  gives  the column number of the left and right
+       o   If  both  smglp  and  smgrp  are  set,  each  is used with a single
+           argument, N, that gives the column number of  the  left  and  right
            margin, respectively.
 
-       o   If both smgtp and smgbp are set, each is used to set  the  top  and
+       o   If  both  smgtp  and smgbp are set, each is used to set the top and
            bottom margin, respectively:
 
            o   smgtp is used with a single argument, N, the line number of the
@@ -1500,12 +1490,12 @@
 
            o   smgbp is used with two arguments, N and M, that give  the  line
                number of the bottom margin, the first counting from the top of
-               the page  and  the  second  counting  from  the  bottom.   This
-               accommodates  the two styles of specifying the bottom margin in
+               the  page  and  the  second  counting  from  the  bottom.  This
+               accommodates the two styles of specifying the bottom margin  in
                different manufacturers' printers.
 
-           When designing a terminfo entry for a printer that has  a  settable
-           bottom  margin,  only  the first or second argument should be used,
+           When  designing  a terminfo entry for a printer that has a settable
+           bottom margin, only the first or second argument  should  be  used,
            depending on the printer.  When developing an application that uses
            smgbp to set the bottom margin, both arguments must be given.
 
@@ -1515,8 +1505,8 @@
            arguments, the column number of the left and right margins, in that
            order.
 
-       o   Likewise,  if  only  one of smgtp and smgbp is set, then it is used
-           with two arguments that give the top and bottom  margins,  in  that
+       o   Likewise, if only one of smgtp and smgbp is set, then  it  is  used
+           with  two  arguments  that give the top and bottom margins, in that
            order, counting from the top of the page.
 
            When designing a terminfo entry for a printer that requires setting
@@ -1527,22 +1517,22 @@
        Except for very old terminal descriptions, e.g.,  those  developed  for
        SVr4,  the  scheme  just  described  should be considered obsolete.  An
        improved set of capabilities was added late in the SVr4 releases (smglr
-       and  smgtb),  which  explicitly  use  two  parameters  for  setting the
+       and smgtb),  which  explicitly  use  two  parameters  for  setting  the
        left/right or top/bottom margins.
 
        When setting margins, the line- and column-values are zero-based.
 
-       The mgc string capability should  be  defined.   Applications  such  as
+       The  mgc  string  capability  should  be defined.  Applications such as
        tabs(1) rely upon this to reset all margins.

                                                                                                                                                                        Area Clears

                                                                                                                                                                        -       If  the  terminal can clear from the current position to the end of the
-       line, leaving the cursor where it is, this should be given as  el.   If
-       the  terminal  can  clear from the beginning of the line to the current
-       position inclusive, leaving the cursor where  it  is,  this  should  be
-       given  as  el1.  If the terminal can clear from the current position to
-       the end of the display, then this should be given as ed.   Ed  is  only
+       If the terminal can clear from the current position to the end  of  the
+       line,  leaving  the cursor where it is, this should be given as el.  If
+       the terminal can clear from the beginning of the line  to  the  current
+       position  inclusive,  leaving  the  cursor  where it is, this should be
+       given as el1.  If the terminal can clear from the current  position  to
+       the  end  of  the display, then this should be given as ed.  Ed is only
        defined from the first column of a line.  (Thus, it can be simulated by
        a request to delete a large number of  lines,  if  a  true  ed  is  not
        available.)
@@ -1563,8 +1553,8 @@
        takes two parameters: the top and bottom lines of the scrolling region.
        The cursor position is, alas, undefined after using this command.
 
-       It  is possible to get the effect of insert or delete line using csr on
-       a properly chosen region; the sc  and  rc  (save  and  restore  cursor)
+       It is possible to get the effect of insert or delete line using csr  on
+       a  properly  chosen  region;  the  sc  and rc (save and restore cursor)
        commands may be useful for ensuring that your synthesized insert/delete
        string does not move the cursor.  (Note that  the  ncurses(3x)  library
        does   this   synthesis   automatically,   so   you  need  not  compose
@@ -1587,13 +1577,13 @@
        off the bottom of the region by the ri re-appears,  then  scrolling  is
        non-destructive.  System V and X/Open Curses expect that ind, ri, indn,
        and  rin  will  simulate  destructive  scrolling;  their  documentation
-       cautions  you  not  to  define  csr  unless  this is true.  This curses
-       implementation is more  liberal  and  will  do  explicit  erases  after
+       cautions you not to define  csr  unless  this  is  true.   This  curses
+       implementation  is  more  liberal  and  will  do  explicit erases after
        scrolling if ndsrc is defined.
 
-       If  the  terminal has the ability to define a window as part of memory,
-       which all commands affect, it should  be  given  as  the  parameterized
-       string  wind.  The four parameters are the starting and ending lines in
+       If the terminal has the ability to define a window as part  of  memory,
+       which  all  commands  affect,  it  should be given as the parameterized
+       string wind.  The four parameters are the starting and ending lines  in
        memory and the starting and ending columns in memory, in that order.
 
        If the terminal can retain display memory above, then the da capability
@@ -1634,49 +1624,49 @@
        Terminfo  can  describe  both  terminals which have an insert mode, and
        terminals which send a simple sequence to open a blank position on  the
        current line.  Give as smir the sequence to get into insert mode.  Give
-       as rmir the sequence to leave  insert  mode.   Now  give  as  ich1  any
-       sequence  needed  to  be  sent  just before sending the character to be
-       inserted.  Most terminals with a true insert mode will not  give  ich1;
-       terminals  which  send a sequence to open a screen position should give
+       as  rmir  the  sequence  to  leave  insert  mode.  Now give as ich1 any
+       sequence needed to be sent just before  sending  the  character  to  be
+       inserted.   Most  terminals with a true insert mode will not give ich1;
+       terminals which send a sequence to open a screen position  should  give
        it here.
 
-       If your terminal has both, insert mode is usually preferable  to  ich1.
-       Technically,  you  should  not  give  both unless the terminal actually
-       requires both to be used in combination.  Accordingly, some  non-curses
-       applications  get  confused if both are present; the symptom is doubled
-       characters in an update using insert.  This requirement  is  now  rare;
-       most  ich  sequences do not require previous smir, and most smir insert
-       modes do not require ich1 before each character.   Therefore,  the  new
-       curses  actually  assumes this is the case and uses either rmir/smir or
-       ich/ich1 as appropriate (but not both).  If you have to write an  entry
-       to  be  used  under  new curses for a terminal old enough to need both,
+       If  your  terminal has both, insert mode is usually preferable to ich1.
+       Technically, you should not give  both  unless  the  terminal  actually
+       requires  both to be used in combination.  Accordingly, some non-curses
+       applications get confused if both are present; the symptom  is  doubled
+       characters  in  an  update using insert.  This requirement is now rare;
+       most ich sequences do not require previous smir, and most  smir  insert
+       modes  do  not  require ich1 before each character.  Therefore, the new
+       curses actually assumes this is the case and uses either  rmir/smir  or
+       ich/ich1  as appropriate (but not both).  If you have to write an entry
+       to be used under new curses for a terminal old  enough  to  need  both,
        include the rmir/smir sequences in ich1.
 
        If post insert padding is needed, give this as a number of milliseconds
        in  ip (a string option).  Any other sequence which may need to be sent
        after an insert of a single character may also be given in ip.  If your
-       terminal  needs  both  to be placed into an "insert mode" and a special
-       code to precede each inserted character, then both smir/rmir  and  ich1
-       can  be  given,  and  both  will be used.  The ich capability, with one
+       terminal needs both to be placed into an "insert mode"  and  a  special
+       code  to  precede each inserted character, then both smir/rmir and ich1
+       can be given, and both will be used.   The  ich  capability,  with  one
        parameter, n, will repeat the effects of ich1 n times.
 
-       If padding is necessary between characters typed while  not  in  insert
+       If  padding  is  necessary between characters typed while not in insert
        mode, give this as a number of milliseconds padding in rmp.
 
-       It  is  occasionally  necessary  to move around while in insert mode to
-       delete characters on the same line (e.g., if there is a tab  after  the
-       insertion  position).   If  your terminal allows motion while in insert
-       mode you can give the capability mir to  speed  up  inserting  in  this
-       case.   Omitting  mir  will affect only speed.  Some terminals (notably
-       Datamedia's) must not have mir because of the  way  their  insert  mode
+       It is occasionally necessary to move around while  in  insert  mode  to
+       delete  characters  on the same line (e.g., if there is a tab after the
+       insertion position).  If your terminal allows motion  while  in  insert
+       mode  you  can  give  the  capability mir to speed up inserting in this
+       case.  Omitting mir will affect only speed.   Some  terminals  (notably
+       Datamedia's)  must  not  have  mir because of the way their insert mode
        works.
 
-       Finally,  you  can  specify dch1 to delete a single character, dch with
-       one parameter, n, to delete ncharacters, and delete mode by giving smdc
-       and  rmdc to enter and exit delete mode (any mode the terminal needs to
-       be placed in for dch1 to work).
+       Finally, you can specify dch1 to delete a single  character,  dch  with
+       one  parameter,  n,  to  delete n characters, and delete mode by giving
+       smdc and rmdc to enter and exit delete  mode  (any  mode  the  terminal
+       needs to be placed in for dch1 to work).
 
-       A command to erase n characters  (equivalent  to  outputting  n  blanks
+       A  command  to  erase  n  characters (equivalent to outputting n blanks
        without moving the cursor) can be given as ech with one parameter.
 
 
@@ -1704,8 +1694,8 @@
        mode) and rmacs (exit alternate character set mode).  Turning on any of
        these modes singly may or may not turn off other modes.
 
-       If there is a sequence to set arbitrary  combinations  of  modes,  this
-       should  be  given  as  sgr (set attributes), taking 9 parameters.  Each
+       If  there  is  a  sequence to set arbitrary combinations of modes, this
+       should be given as sgr (set attributes),  taking  9  parameters.   Each
        parameter is either zero (0) or nonzero, as the corresponding attribute
        is  on  or  off.   The 9 parameters are, in order: standout, underline,
        reverse, blink, dim, bold, blank,  protect,  alternate  character  set.
@@ -1765,30 +1755,30 @@
        string.  The only drawback to adding an sgr string is that termcap also
        assumes that sgr0 does not exit alternate character set mode.
 
-       Terminals  with  the  "magic  cookie"  glitch  (xmc)  deposit   special
-       "cookies"  when  they  receive mode-setting sequences, which affect the
-       display algorithm rather than having extra  bits  for  each  character.
-       Some  terminals, such as the HP 2621, automatically leave standout mode
-       when they move to a new line or  the  cursor  is  addressed.   Programs
-       using  standout mode should exit standout mode before moving the cursor
-       or sending a newline, unless the msgr capability, asserting that it  is
+       Terminals   with  the  "magic  cookie"  glitch  (xmc)  deposit  special
+       "cookies" when they receive mode-setting sequences,  which  affect  the
+       display  algorithm  rather  than  having extra bits for each character.
+       Some terminals, such as the HP 2621, automatically leave standout  mode
+       when  they  move  to  a  new line or the cursor is addressed.  Programs
+       using standout mode should exit standout mode before moving the  cursor
+       or  sending a newline, unless the msgr capability, asserting that it is
        safe to move in standout mode, is present.
 
-       If  the  terminal has a way of flashing the screen to indicate an error
-       quietly (a bell replacement) then this can be given as flash;  it  must
+       If the terminal has a way of flashing the screen to indicate  an  error
+       quietly  (a  bell replacement) then this can be given as flash; it must
        not move the cursor.
 
-       If  the cursor needs to be made more visible than normal when it is not
+       If the cursor needs to be made more visible than normal when it is  not
        on the bottom line (to make, for example, a non-blinking underline into
        an  easier  to  find block or blinking underline) give this sequence as
        cvvis.  If there is a way to make the cursor completely invisible, give
-       that  as  civis.  The capability cnorm should be given which undoes the
+       that as civis.  The capability cnorm should be given which  undoes  the
        effects of both of these modes.
 
-       If your terminal correctly generates  underlined  characters  (with  no
-       special  codes  needed)  even  though  it does not overstrike, then you
-       should give the capability ul.  If  a  character  overstriking  another
-       leaves  both  characters  on the screen, specify the capability os.  If
+       If  your  terminal  correctly  generates underlined characters (with no
+       special codes needed) even though it  does  not  overstrike,  then  you
+       should  give  the  capability  ul.  If a character overstriking another
+       leaves both characters on the screen, specify the  capability  os.   If
        overstrikes are erasable with a blank, then this should be indicated by
        giving eo.
 
@@ -1797,12 +1787,12 @@
        If  the  terminal  has  a keypad that transmits codes when the keys are
        pressed, this information can be given.  Note that it is  not  possible
        to handle terminals where the keypad only works in local (this applies,
-       for example, to the unshifted HP 2621 keys).  If the keypad can be  set
-       to  transmit  or  not  transmit,  give  these  codes  as smkx and rmkx.
+       for  example, to the unshifted HP 2621 keys).  If the keypad can be set
+       to transmit or not  transmit,  give  these  codes  as  smkx  and  rmkx.
        Otherwise the keypad is assumed to always transmit.
 
-       The codes sent by the left arrow, right arrow, up  arrow,  down  arrow,
-       and  home  keys  can  be given as kcub1, kcuf1, kcuu1, kcud1, and khome
+       The  codes  sent  by the left arrow, right arrow, up arrow, down arrow,
+       and home keys can be given as kcub1, kcuf1,  kcuu1,  kcud1,  and  khome
        respectively.  If there are function keys such as f0, f1, ..., f10, the
        codes  they  send  can  be given as kf0, kf1, ..., kf10.  If these keys
        have labels other than the default f0 through f10, the  labels  can  be
@@ -1850,8 +1840,8 @@
        directional pad are needed.
 
        Strings to program function keys can be given as pfkey, pfloc, and pfx.
-       A  string to program screen labels should be specified as pln.  Each of
-       these strings takes two parameters: the function key number to  program
+       A string to program screen labels should be specified as pln.  Each  of
+       these  strings takes two parameters: the function key number to program
        (from 0 to 10) and the string to program it with.  Function key numbers
        out of this range may program undefined keys in  a  terminal  dependent
        manner.   The  difference between the capabilities is that pfkey causes
@@ -1867,41 +1857,45 @@

                                                                                                                                                                        Tabs and Initialization

                                                                                                                                                                        -       A few capabilities are used only for tabs:
+       A few capabilities are used only to manage tab stops.
 
-       o   If the terminal has hardware tabs, the command to  advance  to  the
-           next tab stop can be given as ht (usually control/I).
+       o   If the terminal has hardware tabs, specify the  character  sequence
+           that  advances  to  the  next tab stop as the value of the tab (ht)
+           string capability (usually Control+I).
 
-       o   A "back-tab" command which moves leftward to the preceding tab stop
-           can be given as cbt.
+       o   Specify a character sequence that retreats (moves leftward) to  the
+           preceding  tab  stop  as  the  value  of  the back_tab (cbt) string
+           capability.
 
-           By convention, if the teletype modes indicate that tabs  are  being
-           expanded  by  the  computer rather than being sent to the terminal,
-           programs should not use ht or cbt even if they are  present,  since
-           the user may not have the tab stops properly set.
+           By convention, if the terminal modes are configured such that  tabs
+           are  expanded by the host rather than terminal, applications should
+           not employ the tab (ht) or back_tab (cbt) capabilities even if they
+           are present, since the user may not have  the  tab  stops  properly
+           set.
 
-       o   If  the  terminal has hardware tabs which are initially set every n
-           spaces when the terminal is powered up, the numeric parameter it is
-           given, showing the number of spaces the tabs are set to.
+       o   If  the  terminal  has  hardware  tab stops that are set at every n
+           character cells when the terminal is powered up, specify n  as  the
+           value of the the numeric capability init_tabs (it).
 
-           The it capability is normally used by the tset command to determine
-           whether to set the mode for hardware tab expansion, and whether  to
-           set the tab stops.  If the terminal has tab stops that can be saved
-           in non-volatile memory, the terminfo description  can  assume  that
-           they are properly set.
+           The  tset  and  "tput  init" commands interpret the presence of the
+           init_tabs  (it)  capability  as  implying  that  the  terminal   is
+           responsible for tab stop expansion as well as an instruction to set
+           the tab stops to its value.  If the terminal has tab stops that can
+           be  saved in non-volatile memory, its terminfo type description can
+           assume that they are properly set.
 
        Other capabilities include
 
        o   is1, is2, and is3, initialization strings for the terminal,
 
-       o   iprog,  the  path  name  of  a  program to be run to initialize the
+       o   iprog, the path name of a program  to  be  run  to  initialize  the
            terminal,
 
        o   and if, the name of a file containing long initialization strings.
 
-       These strings are expected to set the terminal  into  modes  consistent
-       with  the  rest of the terminfo description.  They are normally sent to
-       the terminal, by the init option of the tput  program,  each  time  the
+       These  strings  are  expected to set the terminal into modes consistent
+       with the rest of the terminfo description.  They are normally  sent  to
+       the  terminal,  by  the  init option of the tput program, each time the
        user logs in.  They will be printed in the following order:
 
               run the program
@@ -1925,30 +1919,30 @@
               and finally output
                      is3.
 
-       Most  initialization  is  done with is2.  Special terminal modes can be
-       set up without duplicating strings by putting the common  sequences  in
+       Most initialization is done with is2.  Special terminal  modes  can  be
+       set  up  without duplicating strings by putting the common sequences in
        is2 and special cases in is1 and is3.
 
-       A  set  of  sequences  that  does a harder reset from a totally unknown
+       A set of sequences that does a harder  reset  from  a  totally  unknown
        state can be given as rs1, rs2, rf and rs3, analogous to is1 , is2 , if
        and  is3  respectively.   These  strings  are output by reset option of
        tput, or by the reset program (an alias of tset), which  is  used  when
        the terminal gets into a wedged state.  Commands are normally placed in
        rs1, rs2 rs3 and rf only if they produce annoying effects on the screen
        and are not necessary when logging in.  For example, the command to set
-       the vt100 into 80-column mode would normally be part  of  is2,  but  it
-       causes  an  annoying  glitch  of  the screen and is not normally needed
+       the  vt100  into  80-column  mode would normally be part of is2, but it
+       causes an annoying glitch of the screen  and  is  not  normally  needed
        since the terminal is usually already in 80-column mode.
 
-       The reset program writes strings including iprog,  etc.,  in  the  same
-       order  as  the  init program, using rs1, etc., instead of is1, etc.  If
-       any of rs1, rs2, rs3, or rf reset capability strings are  missing,  the
-       reset   program   falls  back  upon  the  corresponding  initialization
+       The  reset  program  writes  strings including iprog, etc., in the same
+       order as the init program, using rs1, etc., instead of  is1,  etc.   If
+       any  of  rs1, rs2, rs3, or rf reset capability strings are missing, the
+       reset  program  falls  back  upon  the   corresponding   initialization
        capability string.
 
-       If there are commands to set and clear tab stops, they can be given  as
+       If  there are commands to set and clear tab stops, they can be given as
        tbc (clear all tab stops) and hts (set a tab stop in the current column
-       of every row).  If a more complex sequence is needed to  set  the  tabs
+       of every line).  If a more complex sequence is needed to set  the  tabs
        than can be described by this, the sequence can be placed in is2 or if.
 
        The  tput  reset  command uses the same capability strings as the reset
@@ -1961,11 +1955,11 @@
        o   Almost all hardware terminals (at least those which supported tabs)
            initialized those to every eight columns:
 
-           The  only  exception  was  the  AT&T 2300 series, which set tabs to
+           The only exception was the AT&T 2300  series,  which  set  tabs  to
            every five columns.
 
-       o   In particular, developers  of  the  hardware  terminals  which  are
-           commonly  used  as  models  for  modern terminal emulators provided
+       o   In  particular,  developers  of  the  hardware  terminals which are
+           commonly used as models  for  modern  terminal  emulators  provided
            documentation demonstrating that eight columns were the standard.
 
        o   Because of this, the terminal initialization programs tput and tset
@@ -1981,36 +1975,36 @@
        characters after certain cursor motions and screen changes.
 
        If the terminal uses xon/xoff handshaking for flow control (that is, it
-       automatically  emits  ^S  back  to  the host when its input buffers are
-       close to full), set xon.  This capability suppresses  the  emission  of
-       padding.   You  can  also  set  it  for  memory-mapped  console devices
+       automatically emits ^S back to the host  when  its  input  buffers  are
+       close  to  full),  set xon.  This capability suppresses the emission of
+       padding.  You  can  also  set  it  for  memory-mapped  console  devices
        effectively that do not have a speed limit.  Padding information should
        still  be  included  so  that  routines can make better decisions about
        relative costs, but actual pad characters will not be transmitted.
 
        If pb (padding baud rate) is given, padding is suppressed at baud rates
-       below  the  value  of  pb.  If the entry has no padding baud rate, then
+       below the value of pb.  If the entry has no  padding  baud  rate,  then
        whether padding is emitted or not is completely controlled by xon.
 
-       If the terminal requires other than a null (zero) character as  a  pad,
-       then  this  can  be  given as pad.  Only the first character of the pad
+       If  the  terminal requires other than a null (zero) character as a pad,
+       then this can be given as pad.  Only the first  character  of  the  pad
        string is used.

                                                                                                                                                                        Status Lines

                                                                                                                                                                        -       Some terminals have an extra "status line" which is not  normally  used
+       Some  terminals  have an extra "status line" which is not normally used
        by software (and thus not counted in the terminal's lines capability).
 
-       The  simplest case is a status line which is cursor-addressable but not
+       The simplest case is a status line which is cursor-addressable but  not
        part of the main scrolling region on the screen; the Heathkit H19 has a
        status  line  of  this  kind,  as  would a 24-line VT100 with a 23-line
        scrolling region set up on initialization.  This situation is indicated
        by the hs capability.
 
-       Some  terminals  with status lines need special sequences to access the
-       status line.  These may be expressed as a string with single  parameter
-       tsl  which takes the cursor to a given zero-origin column on the status
-       line.  The  capability  fsl  must  return  to  the  main-screen  cursor
+       Some terminals with status lines need special sequences to  access  the
+       status  line.  These may be expressed as a string with single parameter
+       tsl which takes the cursor to a given zero-origin column on the  status
+       line.   The  capability  fsl  must  return  to  the  main-screen cursor
        positions before the last tsl.  You may need to embed the string values
        of sc (save  cursor)  and  rc  (restore  cursor)  in  tsl  and  fsl  to
        accomplish this.
@@ -2050,7 +2044,6 @@
        ACS_BOARD     0x68      h      #  board of squares
        ACS_LANTERN   0x69      i      #  lantern symbol
        ACS_LRCORNER  0x6a      j      +  lower right corner
-
        ACS_URCORNER  0x6b      k      +  upper right corner
        ACS_ULCORNER  0x6c      l      +  upper left corner
        ACS_LLCORNER  0x6d      m      +  lower left corner
@@ -2089,43 +2082,48 @@
            presumably  they  were  used in the AT&T terminal: board of squares
            replaces the VT100 newline symbol, while  lantern  symbol  replaces
            the VT100 vertical tab symbol.  The other VT100 symbols for control
-           characters (horizontal tab, carriage return and line-feed) are  not
+           characters  (horizontal tab, carriage return and line-feed) are not
            (re)used in curses.
 
-       The  best  way to define a new device's graphics set is to add a column
-       to a copy of this table for your terminal, giving the  character  which
-       (when  emitted  between  smacs/rmacs  switches) will be rendered as the
+       The best way to define a new device's graphics set is to add  a  column
+       to  a  copy of this table for your terminal, giving the character which
+       (when emitted between smacs/rmacs switches) will  be  rendered  as  the
        corresponding graphic.  Then read off the VT100/your terminal character
        pairs right to left in sequence; these become the ACSC string.

                                                                                                                                                                        Color Handling

                                                                                                                                                                        -       The  curses  library  functions init_pair and init_color manipulate the
-       color  pairs  and  color  values  discussed  in   this   section   (see
-       curs_color(3x) for details on these and related functions).
+       The  curses  library  functions init_pair and init_color manipulate the
+       color pairs and colors (color  values  or  indices,  such  as  "1=red")
+       discussed  in this section (see curs_color(3x) for details on these and
+       related functions).
 
-       Most color terminals are either "Tektronix-like" or "HP-like":
+       Most color terminals are either "Tektronix-like" or "HP-like" in  their
+       approach to color management.
 
-       o   Tektronix-like terminals have a predefined set of N colors (where N
-           is usually 8), and can set character-cell foreground and background
-           characters independently, mixing them into N * N color pairs.
+       o   Tektronix-like  terminals  define  a  set  of  n colors (where n is
+           usually 8), and can alter character-cell foreground and  background
+           colors  independently,  mixing  them  into  nxn color pairs.  ANSI-
+           standard terminals are Tektronix-like.
 
-       o   On  HP-like  terminals,  the  user  must  set  each  color  pair up
-           separately  (foreground  and  background  are   not   independently
-           settable).   Up  to  M color pairs may be set up from 2*M different
-           colors.  ANSI-compatible terminals are Tektronix-like.
+       o   On HP-like  terminals,  the  user  must  set  up  each  color  pair
+           separately;   foreground   and  background  are  not  independently
+           alterable.  Up  to  m  color  pairs  may  be  configured  from  2xm
+           different colors.
 
-       Some basic color capabilities are independent of the color method.  The
-       numeric  capabilities  colors  and pairs specify the maximum numbers of
-       colors and color pairs that can be displayed  simultaneously.   The  op
-       (original pair) string resets foreground and background colors to their
-       default values for the terminal.  The oc string resets  all  colors  or
-       color  pairs  to their default values for the terminal.  Some terminals
+       Some  basic  color management capabilities are independent of the color
+       encoding method.  The  numeric  capabilities  max_colors  (colors)  and
+       max_pairs (pairs) specify the maximum numbers of colors and color pairs
+       that  the  device  can  display  simultaneously.   The  orig_pair  (op)
+       ("original pair") string capability resets  foreground  and  background
+       colors  to their default values for the terminal.  The orig_colors (oc)
+       ("original colors") string capability resets all colors or color  pairs
+       to  their  default  values  for  the  terminal.   Some  terminal  types
        (including many PC terminal emulators)  erase  screen  areas  with  the
        current  background  color rather than the power-up default background;
-       these should have the Boolean capability bce.
+       these should declare the Boolean capability back_color_erase (bce).
 
-       While the  curses  library  works  with  color  pairs  (reflecting  the
+       While the  curses  library  works  with  color  pairs  (reflecting  the
        inability  of  some  devices  to  set  foreground and background colors
        independently), there  are  separate  capabilities  for  setting  these
        features:
@@ -2134,17 +2132,17 @@
            Tektronix-type terminal, use setaf (set ANSI foreground) and  setab
            (set  ANSI  background)  or  setf  (set  foreground)  and setb (set
            background).  These take one parameter, the color number.  The SVr4
-           documentation  describes only setaf/setab; the XPG4 draft says that
-           "If the terminal supports ANSI escape sequences to  set  background
-           and   foreground,   they  should  be  coded  as  setaf  and  setab,
+           documentation describes only setaf/setab; the XPG4 draft says  that
+           "If  the  terminal supports ANSI escape sequences to set background
+           and  foreground,  they  should  be  coded  as  setaf   and   setab,
            respectively.
 
-       o   If the terminal supports other escape sequences to  set  background
-           and   foreground,   they   should   be  coded  as  setf  and  setb,
-           respectively.  The vidputs and the refresh(3x)  functions  use  the
+       o   If  the  terminal supports other escape sequences to set background
+           and  foreground,  they  should  be  coded   as   setf   and   setb,
+           respectively.   The  vidputs  and the refresh(3x) functions use the
            setaf and setab capabilities if they are defined.
 
-       The  setaf/setab  and  setf/setb  capabilities  take  a  single numeric
+       The setaf/setab  and  setf/setb  capabilities  take  a  single  numeric
        argument each.  Argument values 0-7 of setaf/setab are portably defined
        as  follows (the middle column is the symbolic #define available in the
        header for the curses or ncurses libraries).  The terminal hardware  is
@@ -2176,32 +2174,32 @@
                    yellow    COLOR_YELLOW      6     max, max, 0
                    white     COLOR_WHITE       7     max, max, max
 
-       It  is  important  to  not  confuse the two sets of color capabilities;
+       It is important to not confuse the  two  sets  of  color  capabilities;
        otherwise red/blue will be interchanged on the display.
 
-       On an HP-like terminal, use scp with a color pair number  parameter  to
+       On  an  HP-like terminal, use scp with a color pair number parameter to
        set which color pair is current.
 
        Some terminals allow the color values to be modified:
 
-       o   On  a Tektronix-like terminal, the capability ccc may be present to
-           indicate that colors can be modified.  If so, the initc  capability
+       o   On a Tektronix-like terminal, the capability ccc may be present  to
+           indicate  that colors can be modified.  If so, the initc capability
            will take a color number (0 to colors - 1)and three more parameters
            which describe the color.  These three parameters default to  being
            interpreted  as  RGB  (Red,  Green,  Blue)  values.  If the Boolean
            capability hls is present, they are instead as HLS (Hue, Lightness,
            Saturation) indices.  The ranges are terminal-dependent.
 
-       o   On  an HP-like terminal, initp may give a capability for changing a
-           color pair value.  It will take  seven  parameters;  a  color  pair
-           number  (0  to  max_pairs  -  1),  and two triples describing first
-           background and then foreground colors.  These  parameters  must  be
-           (Red,  Green,  Blue)  or  (Hue, Lightness, Saturation) depending on
+       o   On an HP-like terminal, initp may give a capability for changing  a
+           color  pair  value.   It  will  take seven parameters; a color pair
+           number (0 to max_pairs -  1),  and  two  triples  describing  first
+           background  and  then  foreground colors.  These parameters must be
+           (Red, Green, Blue) or (Hue,  Lightness,  Saturation)  depending  on
            hls.
 
-       On some color terminals,  colors  collide  with  highlights.   You  can
-       register  these collisions with the ncv capability.  This is a bit mask
-       of  attributes  not  to  be  used  when  colors   are   enabled.    The
+       On  some  color  terminals,  colors  collide  with highlights.  You can
+       register these collisions with the ncv capability.  This is a bit  mask
+       of   attributes   not   to  be  used  when  colors  are  enabled.   The
        correspondence with the attributes understood by curses is as follows:
 
                          Attribute     Bit   Decimal   Set by
@@ -2223,17 +2221,17 @@
                         A_VERTICAL     14     16384    sgr1
                         A_ITALIC       15     32768    sitm
 
-       For  example, on many IBM PC consoles, the underline attribute collides
-       with the foreground color blue and is  not  available  in  color  mode.
+       For example, on many IBM PC consoles, the underline attribute  collides
+       with  the  foreground  color  blue  and is not available in color mode.
        These should have an ncv capability of 2.
 
-       SVr4  curses does nothing with ncv, ncurses recognizes it and optimizes
+       SVr4 curses does nothing with ncv, ncurses recognizes it and  optimizes
        the output in favor of colors.

                                                                                                                                                                        Miscellaneous

                                                                                                                                                                        -       If the terminal requires other than a null (zero) character as  a  pad,
-       then  this  can  be  given as pad.  Only the first character of the pad
+       If  the  terminal requires other than a null (zero) character as a pad,
+       then this can be given as pad.  Only the first  character  of  the  pad
        string is used.  If the terminal does not have a pad character, specify
        npc.   Note that ncurses implements the termcap-compatible PC variable;
        though the application may set this value to  something  other  than  a
@@ -2246,17 +2244,17 @@
        hard-copy terminal can eject to the next page (form feed), give this as
        ff (usually control/L).
 
-       If there is a command to repeat a given character  a  given  number  of
-       times   (to   save  time  transmitting  a  large  number  of  identical
-       characters) this can be indicated with the  parameterized  string  rep.
-       The  first  parameter is the character to be repeated and the second is
+       If  there  is  a  command to repeat a given character a given number of
+       times  (to  save  time  transmitting  a  large  number   of   identical
+       characters)  this  can  be indicated with the parameterized string rep.
+       The first parameter is the character to be repeated and the  second  is
        the number of times to repeat it.  Thus, tparm(repeat_char, 'x', 10) is
        the same as "xxxxxxxxxx".
 
        If the terminal has a settable command character, such as the TEKTRONIX
-       4025, this can be indicated with cmdch.  A prototype command  character
-       is  chosen  which is used in all capabilities.  This character is given
-       in the cmdch capability to identify it.  The  following  convention  is
+       4025,  this can be indicated with cmdch.  A prototype command character
+       is chosen which is used in all capabilities.  This character  is  given
+       in  the  cmdch  capability to identify it.  The following convention is
        supported on some Unix systems: The environment is to be searched for a
        CC variable, and if found, all occurrences of the  prototype  character
        are replaced with the character in the environment variable.
@@ -2269,9 +2267,9 @@
        known.)
 
        If the terminal has a "meta key" which acts as a shift key, setting the
-       8th  bit  of any character transmitted, this fact can be indicated with
-       km.  Otherwise, software will assume that the 8th bit is parity and  it
-       will  usually be cleared.  If strings exist to turn this "meta mode" on
+       8th bit of any character transmitted, this fact can be  indicated  with
+       km.   Otherwise, software will assume that the 8th bit is parity and it
+       will usually be cleared.  If strings exist to turn this "meta mode"  on
        and off, they can be given as smm and rmm.
 
        If the terminal has more lines of memory than will fit on the screen at
@@ -2279,16 +2277,16 @@
        of lm#0 indicates that the number of lines is not fixed, but that there
        is still more memory than fits on the screen.
 
-       If  the terminal is one of those supported by the Unix virtual terminal
+       If the terminal is one of those supported by the Unix virtual  terminal
        protocol, the terminal number can be given as vt.
 
-       Media copy strings which control an auxiliary printer connected to  the
-       terminal  can  be  given as mc0: print the contents of the screen, mc4:
-       turn off the printer, and mc5: turn on the printer.  When  the  printer
-       is  on,  all text sent to the terminal will be sent to the printer.  It
-       is undefined whether the text is also displayed on the terminal  screen
-       when  the  printer  is  on.   A variation mc5p takes one parameter, and
-       leaves the printer on for as  many  characters  as  the  value  of  the
+       Media  copy strings which control an auxiliary printer connected to the
+       terminal can be given as mc0: print the contents of  the  screen,  mc4:
+       turn  off  the printer, and mc5: turn on the printer.  When the printer
+       is on, all text sent to the terminal will be sent to the  printer.   It
+       is  undefined whether the text is also displayed on the terminal screen
+       when the printer is on.  A variation  mc5p  takes  one  parameter,  and
+       leaves  the  printer  on  for  as  many  characters as the value of the
        parameter, then turns the printer off.  The parameter should not exceed
        255.  All text, including mc4, is transparently passed to  the  printer
        while an mc5p is in effect.
@@ -2305,27 +2303,27 @@
        normal text on top of it), xhp should be given.
 
        Teleray terminals, where tabs turn all characters moved over to blanks,
-       should  indicate  xt (destructive tabs).  Note: the variable indicating
-       this  is  now  "dest_tabs_magic_smso";  in  older  versions,   it   was
-       teleray_glitch.   This  glitch  is  also  taken  to mean that it is not
-       possible to position the cursor on top of a  "magic  cookie",  that  to
-       erase  standout  mode  it is instead necessary to use delete and insert
+       should indicate xt (destructive tabs).  Note: the  variable  indicating
+       this   is   now  "dest_tabs_magic_smso";  in  older  versions,  it  was
+       teleray_glitch.  This glitch is also taken  to  mean  that  it  is  not
+       possible  to  position  the  cursor on top of a "magic cookie", that to
+       erase standout mode it is instead necessary to use  delete  and  insert
        line.  The ncurses implementation ignores this glitch.
 
-       The Beehive Superbee, which is unable to correctly transmit the  escape
-       or  control/C  characters,  has xsb, indicating that the f1 key is used
-       for escape and f2 for control/C.  (Only  certain  Superbees  have  this
-       problem,  depending on the ROM.)  Note that in older terminfo versions,
+       The  Beehive Superbee, which is unable to correctly transmit the escape
+       or control/C characters, has xsb, indicating that the f1  key  is  used
+       for  escape  and  f2  for control/C.  (Only certain Superbees have this
+       problem, depending on the ROM.)  Note that in older terminfo  versions,
        this capability was called "beehive_glitch"; it is now "no_esc_ctl_c".
 
-       Other specific terminal  problems  may  be  corrected  by  adding  more
+       Other  specific  terminal  problems  may  be  corrected  by adding more
        capabilities of the form xx.

                                                                                                                                                                        Pitfalls of Long Entries

                                                                                                                                                                        -       Long  terminfo  entries are unlikely to be a problem; to date, no entry
-       has  even  approached  terminfo's   4096-byte   string-table   maximum.
-       Unfortunately,  the termcap translations are much more strictly limited
+       Long terminfo entries are unlikely to be a problem; to date,  no  entry
+       has   even   approached   terminfo's  4096-byte  string-table  maximum.
+       Unfortunately, the termcap translations are much more strictly  limited
        (to 1023 bytes), thus termcap translations of long terminfo entries can
        cause problems.
 
@@ -2348,15 +2346,15 @@
        Some application programs allocate more than the recommended 1K for the
        termcap entry; others do not.
 
-       Each termcap entry has two important sizes associated with  it:  before
-       "tc"  expansion, and after "tc" expansion.  "tc" is the capability that
+       Each  termcap  entry has two important sizes associated with it: before
+       "tc" expansion, and after "tc" expansion.  "tc" is the capability  that
        tacks on another termcap entry to the end of the current one, to add on
        its capabilities.  If a termcap entry does not use the "tc" capability,
        then of course the two lengths are the same.
 
-       The "before tc expansion" length is the most important one, because  it
-       affects  more than just users of that particular terminal.  This is the
-       length of the entry as it exists in /etc/termcap, minus the  backslash-
+       The  "before tc expansion" length is the most important one, because it
+       affects more than just users of that particular terminal.  This is  the
+       length  of the entry as it exists in /etc/termcap, minus the backslash-
        newline pairs, which tgetent strips out while reading it.  Some termcap
        libraries strip off the final newline, too (GNU termcap does not).  Now
        suppose:
@@ -2365,25 +2363,25 @@
 
        o   and the application has only allocated a 1k buffer,
 
-       o   and  the termcap library (like the one in BSD/OS 1.1 and GNU) reads
-           the whole entry into the buffer, no matter what its length, to  see
+       o   and the termcap library (like the one in BSD/OS 1.1 and GNU)  reads
+           the  whole entry into the buffer, no matter what its length, to see
            if it is the entry it wants,
 
-       o   and  tgetent  is  searching  for a terminal type that either is the
-           long entry, appears in the termcap file after the  long  entry,  or
-           does  not  appear in the file at all (so that tgetent has to search
+       o   and tgetent is searching for a terminal type  that  either  is  the
+           long  entry,  appears  in the termcap file after the long entry, or
+           does not appear in the file at all (so that tgetent has  to  search
            the whole termcap file).
 
-       Then tgetent will overwrite memory, perhaps  its  stack,  and  probably
-       core   dump   the  program.   Programs  like  telnet  are  particularly
-       vulnerable; modern telnets pass along values  like  the  terminal  type
-       automatically.   The  results  are almost as undesirable with a termcap
-       library, like SunOS 4.1.3 and Ultrix 4.4, that prints warning  messages
-       when  it  reads  an  overly  long  termcap entry.  If a termcap library
-       truncates long entries, like OSF/1 3.0, it is immune to dying here  but
+       Then  tgetent  will  overwrite  memory, perhaps its stack, and probably
+       core  dump  the  program.   Programs  like  telnet   are   particularly
+       vulnerable;  modern  telnets  pass  along values like the terminal type
+       automatically.  The results are almost as undesirable  with  a  termcap
+       library,  like SunOS 4.1.3 and Ultrix 4.4, that prints warning messages
+       when it reads an overly long  termcap  entry.   If  a  termcap  library
+       truncates  long entries, like OSF/1 3.0, it is immune to dying here but
        will return incorrect data for the terminal.
 
-       The  "after  tc  expansion"  length  will  have a similar effect to the
+       The "after tc expansion" length will  have  a  similar  effect  to  the
        above, but only for people who actually set TERM to that terminal type,
        since  tgetent  only  does "tc" expansion once it is found the terminal
        type it was looking for, not while searching.
@@ -2422,53 +2420,53 @@
        turned off.
 
        The ncurses library handles insert-character and insert-character modes
-       in  a  slightly  non-standard way to get better update efficiency.  See
+       in a slightly non-standard way to get better  update  efficiency.   See
        the Insert/Delete Character subsection above.
 
-       The parameter substitutions for set_clock  and  display_clock  are  not
-       documented  in  SVr4  or  X/Open  Curses.   They  are  deduced from the
+       The  parameter  substitutions  for  set_clock and display_clock are not
+       documented in SVr4  or  X/Open  Curses.   They  are  deduced  from  the
        documentation for the AT&T 505 terminal.
 
-       Be careful assigning the kmous capability.  The ncurses  library  wants
-       to  interpret  it as KEY_MOUSE, for use by terminals and emulators like
-       xterm that can return mouse-tracking information in the  keyboard-input
+       Be  careful  assigning the kmous capability.  The ncurses library wants
+       to interpret it as KEY_MOUSE, for use by terminals and  emulators  like
+       xterm  that can return mouse-tracking information in the keyboard-input
        stream.
 
-       X/Open  Curses  does  not  mention italics.  Portable applications must
-       assume that  numeric  capabilities  are  signed  16-bit  values.   This
-       includes  the  no_color_video  (ncv)  capability.  The 32768 mask value
-       used for italics with ncv can be confused with an absent  or  cancelled
-       ncv.   If  italics  should work with colors, then the ncv value must be
+       X/Open Curses does not mention  italics.   Portable  applications  must
+       assume  that  numeric  capabilities  are  signed  16-bit  values.  This
+       includes the no_color_video (ncv) capability.   The  32768  mask  value
+       used  for  italics  with ncv can be confused with an absent or canceled
+       ncv.  If italics should work with colors, then the ncv  value  must  be
        specified, even if it is zero.
 
-       Different commercial ports of terminfo  and  curses  support  different
-       subsets  of  X/Open  Curses  and  (in some cases) different extensions.
-       Here is a summary,  accurate  as  of  October  1995,  after  which  the
+       Different  commercial  ports  of  terminfo and curses support different
+       subsets of X/Open Curses and  (in  some  cases)  different  extensions.
+       Here  is  a  summary,  accurate  as  of  October  1995, after which the
        commercial Unix market contracted and lost diversity.
 
        o   SVr4, Solaris, and ncurses support all SVr4 capabilities.
 
-       o   IRIX  supports  the  SVr4  set  and  adds one undocumented extended
+       o   IRIX supports the SVr4  set  and  adds  one  undocumented  extended
            string capability (set_pglen).
 
-       o   SVr1  and  Ultrix  support  a   restricted   subset   of   terminfo
-           capabilities.   The  Booleans  end with xon_xoff; the numerics with
+       o   SVr1   and   Ultrix   support   a  restricted  subset  of  terminfo
+           capabilities.  The Booleans end with xon_xoff;  the  numerics  with
            width_status_line; and the strings with prtr_non.
 
-       o   HP/UX  supports  the  SVr1  subset,  plus  the  SVr[234]   numerics
-           num_labels,   label_height,  label_width,  plus  function  keys  11
-           through 63, plus plab_norm, label_on, and label_off, plus a  number
+       o   HP/UX   supports  the  SVr1  subset,  plus  the  SVr[234]  numerics
+           num_labels,  label_height,  label_width,  plus  function  keys   11
+           through  63, plus plab_norm, label_on, and label_off, plus a number
            of incompatible string table extensions.
 
-       o   AIX  supports  the  SVr1  subset, plus function keys 11 through 63,
+       o   AIX supports the SVr1 subset, plus function  keys  11  through  63,
            plus a number of incompatible string table extensions.
 
        o   OSF/1 supports both the SVr4 set and the AIX extensions.

                                                                                                                                                                        PORTABILITY

                                                                                                                                                                        -       Do not count on  compiled  (binary)  terminfo  entries  being  portable
-       between  commercial  Unix  systems.   At  least  two implementations of
+       Do  not  count  on  compiled  (binary)  terminfo entries being portable
+       between commercial Unix  systems.   At  least  two  implementations  of
        terminfo (those of HP-UX and AIX) diverged from those of other System V
        Unices  after  SVr1,  adding extension capabilities to the string table
        that (in the binary format) collide with subsequent System V and X/Open
@@ -2485,9 +2483,7 @@
        curs_terminfo(3x),  curs_variables(3x),  printf(3), term_variables(3x),
        term(5), user_caps(5)
 
-
-
-ncurses 6.5                       2024-04-20                       terminfo(5)
+ncurses 6.6                       2025-08-16                       terminfo(5)
                                                                                                                                                                          @@ -2498,7 +2494,7 @@ ncurses 6.5 2024-04-20 terminfo Entry Syntax
                                                                                                                                                                        • terminfo Capabilities Syntax
                                                                                                                                                                        • Similar Terminals
                                                                                                                                                                          • -
                                                                                                                                                                        • Predefined Capabilities
                                                                                                                                                                          • +
                                                                                                                                                                        • Standard Capabilities
                                                                                                                                                                        • User-Defined Capabilities
                                                                                                                                                                        • A Sample Entry
                                                                                                                                                                        • Types of Capabilities
                                                                                                                                                                          • diff --git a/doc/html/man/tic.1m.html b/doc/html/man/tic.1m.html index e5e6107..e66e2c3 100644 --- a/doc/html/man/tic.1m.html +++ b/doc/html/man/tic.1m.html @@ -1,6 +1,6 @@ -tic 1m 2024-04-27 ncurses 6.5 User commands +tic 1m 2025-11-11 ncurses 6.6 User commands -

                                                                                                                                                                          tic 1m 2024-04-27 ncurses 6.5 User commands

                                                                                                                                                                          +

                                                                                                                                                                          tic 1m 2025-11-11 ncurses 6.6 User commands

                                                                                                                                                                           tic(1m)                          User commands                         tic(1m)
 
 
-
-

                                                                                                                                                                          NAME

                                                                                                                                                                                  tic - compile terminal descriptions for terminfo or termcap
 
@@ -56,20 +54,19 @@

                                                                                                                                                                          DESCRIPTION

                                                                                                                                                                          -       The tic command translates a terminfo  file  from  source  format  into
-       compiled  format.   The  compiled  format is necessary for use with the
-       library routines in ncurses(3x).
+       tic translates a terminfo file from source  format  into  the  compiled
+       format used by the ncurses(3x) library.
 
-       As described in term(5), the database may be either  a  directory  tree
-       (one  file  per  terminal  entry)  or a hashed database (one record per
-       entry).  The tic command writes only one type of  entry,  depending  on
-       how it was built:
+       As  described  in  term(5), the database may be either a directory tree
+       (one file per terminal entry) or a  hashed  database  (one  record  per
+       entry).   The  tic  command writes only one type of entry, depending on
+       how it was built.
 
-       o   For    directory    trees,    the    top-level   directory,   e.g.,
-           /usr/share/terminfo, specifies the location of the database.
+       o   For   directory   trees,   the   top-level   directory,   such   as
+           /usr/share/terminfo, specifies the location of the database.
 
-       o   For hashed databases, a filename is needed.  If the given  file  is
-           not  found  by  that  name,  but  can be found by adding the suffix
+       o   For  hashed  databases, a filename is needed.  If the given file is
+           not found by that name, but can  be  found  by  adding  the  suffix
            ".db", then that is used.
 
            The default name for the hashed database is the same as the default
@@ -77,108 +74,105 @@
 
        In  either  case  (directory  or  hashed database), tic will create the
        container if it does not exist.  For a directory,  this  would  be  the
-       "terminfo" leaf, versus a "terminfo.db" file.
+       "terminfo" leaf, versus a terminfo.db file.
 
-       The  results  are  normally  placed  in  the  system  terminfo database
-       /usr/share/terminfo.  The compiled terminal description can  be  placed
-       in a different terminfo database.  There are two ways to achieve this:
+       The  results  are  normally  placed  in  the  system  terminfo database
+       /usr/share/terminfo.  The compiled terminal description can  be  placed
+       in a different terminfo database.  There are two ways to achieve this:
 
        o   First,  you  may override the system default either by using the -o
-           option,  or  by  setting  the  variable  TERMINFO  in  your   shell
+           option,  or  by  setting  the  variable  TERMINFO  in  the  process
            environment to a valid database location.
 
        o   Secondly,  if  tic  cannot  write  in  /usr/share/terminfo  or  the
            location specified using your TERMINFO variable, it looks  for  the
-           directory  $HOME/.terminfo (or hashed database $HOME/.terminfo.db);
+           directory  $HOME/.terminfo (or hashed database $HOME/.terminfo.db);
            if that location exists, the entry is placed there.
 
-       Libraries  that  read  terminfo  entries  are  expected  to  check   in
+       Libraries  that  read  terminfo  entries  are  expected  to  check   in
        succession
 
-       o   a location specified with the TERMINFO environment variable,
+       o   a location specified by the TERMINFO environment variable,
 
        o   $HOME/.terminfo,
 
        o   directories listed in the TERMINFO_DIRS environment variable,
 
-       o   a compiled-in list of directories (/usr/share/terminfo), and
+       o   a compiled-in list of directories (/usr/share/terminfo), and
 
-       o   the system terminfo database (/usr/share/terminfo).
+       o   the system terminfo database (/usr/share/terminfo).
 
-       The  Fetching  Compiled  Descriptions section in the terminfo(5) manual
-       goes into further detail.
+       Section  "Fetching  Compiled  Descriptions"  in  terminfo(5)  goes into
+       further detail.

                                                                                                                                                                          Aliases

                                                                                                                                                                          -       This is the same program as infotocap and captoinfo; usually those  are
-       linked to, or copied from this program:
+       tic is the same program as infotocap and captoinfo; usually  those  are
+       linked to, or copied from, this program.
 
-       o   When invoked as infotocap, tic sets the -I option.
+       o   When invoked as infotocap, tic sets the -I option.
 
-       o   When invoked as captoinfo, tic sets the -C option.
+       o   When invoked as captoinfo, tic sets the -C option.

                                                                                                                                                                          OPTIONS

                                                                                                                                                                          -       -0     restricts the output to a single line
+       -0     restricts the output to a single line.
 
-       -1     restricts the output to a single column
+       -1     restricts the output to a single column.
 
        -a     tells  tic  to  retain  commented-out  capabilities  rather than
               discarding them.  Capabilities are commented by  prefixing  them
-              with  a  period.  This sets the -x option, because it treats the
-              commented-out entries as user-defined names.  If the  source  is
-              termcap,  accept  the  2-character  names required by version 6.
+              with a period.  -a implies -x, because tic treats the commented-
+              out  entries as user-defined names.  If the source is in termcap
+              format, tic accepts the 2-character names required by version 6.
               Otherwise these are ignored.
 
-       -C     Force source translation to termcap format.  Note: this  differs
-              from  the  -C  option  of infocmp(1m) in that it does not merely
-              translate capability names, but also translates terminfo strings
-              to  termcap  format.  Capabilities that are not translatable are
-              left in the entry under their terminfo names but  commented  out
-              with  two  preceding  dots.  The actual format used incorporates
-              some improvements for escaped characters from  terminfo  format.
-              For a stricter BSD-compatible translation, add the -K option.
+       -C     Force source translation to termcap format.  Note:  this  option
+              differs  from  the  -C option of infocmp(1m) in that it does not
+              merely translate capability names, but also translates  terminfo
+              string   capability   values  to  termcap  format.   tic  leaves
+              capabilities that are not translatable in the entry under  their
+              terminfo  names, but commented out with two preceding dots.  The
+              actual format used incorporates some  improvements  for  escaped
+              characters  from terminfo format.  For a stricter BSD-compatible
+              translation, specify -K as well.
 
-              If  this  is  combined  with  -c, tic makes additional checks to
-              report cases where the terminfo values  do  not  have  an  exact
-              equivalent in termcap form.  For example:
+              If  -C  is  combined  with  -c,  tic  makes  additional  checks,
+              reporting  cases where terminfo capability values do not have an
+              exact equivalent in termcap syntax.  For example:
 
-              o   sgr  usually  will  not  convert,  because termcap lacks the
-                  ability to work with more than two parameters,  and  because
-                  termcap  lacks many of the arithmetic/logical operators used
-                  in terminfo.
+              o   sgr usually does not convert, because termcap is  unable  to
+                  work  with  more than two parameters, and because termcap 's
+                  language for encoding parameterized capabilities lacks  many
+                  of terminfo's arithmetic and logical operators.
 
-              o   capabilities with more than one delay or with delays  before
-                  the end of the string will not convert completely.
-
-       -c     tells  tic  to  only  check  file  for  errors, including syntax
-              problems and bad use-links.  If you specify -C  (-I)  with  this
-              option,  the code will print warnings about entries which, after
-              use resolution, are more than 1023 (4096) bytes long.  Due to  a
-              fixed buffer length in older termcap libraries, as well as buggy
-              checking for the  buffer  length  (and  a  documented  limit  in
-              terminfo),  these  entries  may  cause  core  dumps  with  other
+       -c     tells  tic to perform only validation of file , including syntax
+              problems and invalid "use" references; no  output  is  produced.
+              If you specify -C (-I) with this option, tic warns about entries
+              that,  after "use" resolution, exceed 1023 (4096) bytes.  Due to
+              a fixed buffer length in older termcap  libraries,  as  well  as
+              buggy  checking  of the buffer length (and a documented limit in
+              terminfo),  these  entries  may  cause  core  dumps  with  other
               implementations.
 
               tic  checks  string  capabilities  to  ensure  that  those  with
-              parameters  will  be valid expressions.  It does this check only
-              for the predefined string capabilities; those which are  defined
-              with the -x option are ignored.
+              parameters are valid expressions.  It  validates  only  standard
+              string capabilities, ignoring those defined with the -x option.
 
        -D     tells  tic  to print the database locations that it knows about,
               and exit.  The first location shown is the one to which it would
-              write  compiled  terminal  descriptions.   If tic is not able to
+              write compiled terminal descriptions.  If tic  is  not  able  to
               find  a  writable  database  location  according  to  the  rules
-              summarized  above,  it  will print a diagnostic and exit with an
+              summarized above, it will print a diagnostic and  exit  with  an
               error rather than printing a list of database locations.
 
        -e list
-              Limit writes and translations to  the  comma-separated  list  of
-              terminal  types.  If any name or alias of a terminal matches one
-              of the  names  in  the  list,  the  entry  will  be  written  or
+              Limit  writes  and  translations  to the comma-separated list of
+              terminal types.  If any name or alias of a terminal matches  one
+              of  the  names  in  the  list,  the  entry  will  be  written or
               translated as normal.  Otherwise no output will be generated for
               it.  The option value is interpreted as a  file  containing  the
-              list  if  it  contains  a  '/'.  (Note: depending on how tic was
+              list  if  it  contains  a  '/'.  (Note: depending on how tic was
               compiled, this option may require -I or -C.)
 
        -f     Display    complex    terminfo     strings     which     contain
@@ -195,7 +189,7 @@
        -K     Suppress some longstanding ncurses extensions to termcap format,
               e.g., "\s" for space.
 
-       -L     Force source translation to terminfo format  using  the  long  C
+       -L     Force  source  translation  to  terminfo format using the long C
               variable names listed in <term.h>
 
        -N     Disable smart defaults.  Normally, when translating from termcap
@@ -203,7 +197,7 @@
               the    defaults    of    string    capabilities   reset1_string,
               carriage_return, cursor_left, cursor_down, scroll_forward,  tab,
               newline, key_backspace, key_left, and key_down, then attempts to
-              use obsolete termcap capabilities to deduce correct values.   It
+              use  obsolete termcap capabilities to deduce correct values.  It
               also normally suppresses output of obsolete termcap capabilities
               such as bs.  This option forces a more literal translation  that
               also preserves the obsolete capabilities.
@@ -228,7 +222,7 @@
               Restrict  output to a given subset.  This option is for use with
               archaic versions of terminfo like those on SVr1, Ultrix, or  HP-
               UX that do not support the full set of SVR4/XSI Curses terminfo;
-              and outright broken ports like  AIX  3.x  that  have  their  own
+              and  outright  broken  ports  like  AIX  3.x that have their own
               extensions incompatible with SVr4/XSI.
 
               Available subsets are
@@ -236,40 +230,40 @@
 
               See terminfo(5) for details.
 
-       -r     Force   entry   resolution   (so   there  are  no  remaining  tc
-              capabilities) even when doing  translation  to  termcap  format.
-              This  may  be  needed  if you are preparing a termcap file for a
-              termcap library (such as GNU termcap through version 1.3 or  BSD
+       -r     Force  entry  resolution  (so  there   are   no   remaining   tc
+              capabilities)  even  when  doing  translation to termcap format.
+              This may be needed if you are preparing a  termcap  file  for  a
+              termcap  library (such as GNU termcap through version 1.3 or BSD
               termcap  through  4.3BSD)  that  does  not  handle  multiple  tc
               capabilities per entry.
 
-       -s     Summarize the compile by  showing  the  database  location  into
-              which  entries  are written, and the number of entries which are
+       -s     Summarize  the  compile  by  showing  the database location into
+              which entries are written, and the number of entries  which  are
               compiled.
 
-       -T     eliminates size-restrictions on the  generated  text.   This  is
-              mainly  useful  for  testing  and  analysis,  since the compiled
-              descriptions are limited  (e.g.,  1023  for  termcap,  4096  for
+       -T     eliminates  size-restrictions  on  the  generated text.  This is
+              mainly useful for  testing  and  analysis,  since  the  compiled
+              descriptions  are  limited  (e.g.,  1023  for  termcap, 4096 for
               terminfo).
 
-       -t     tells  tic to discard commented-out capabilities.  Normally when
-              translating   from   terminfo   to    termcap,    untranslatable
+       -t     tells tic to discard commented-out capabilities.  Normally  when
+              translating    from    terminfo   to   termcap,   untranslatable
               capabilities are commented-out.
 
-       -U     tells  tic to not post-process the data after parsing the source
-              file.  Normally, it infers data which  is  commonly  missing  in
+       -U     tells tic to not post-process the data after parsing the  source
+              file.   Normally,  it  infers  data which is commonly missing in
               older terminfo data, or in termcaps.
 
-       -V     reports  the  version of ncurses which was used in this program,
+       -V     reports the version of ncurses which was used in  this  program,
               and exits.
 
-       -vn    specifies that (verbose) output be  written  to  standard  error
+       -vn    specifies  that  (verbose)  output  be written to standard error
               trace information showing tic's progress.
 
-              The  optional  parameter  n  is a number from 1 to 9, inclusive,
+              The optional parameter n is a number from  1  to  9,  inclusive,
               indicating the desired level of detail of information.
 
-              o   If ncurses is built without tracing  support,  the  optional
+              o   If  ncurses  is  built without tracing support, the optional
                   parameter is ignored.
 
               o   If n is omitted, the default level is 1.
@@ -316,36 +310,39 @@

                                                                                                                                                                          Parameters

                                                                                                                                                                          -       file   contains  one  or  more terminfo terminal descriptions in source
-              format  [see  terminfo(5)].   Each  description  in   the   file
-              describes the capabilities of a particular terminal.
+       file   contains  one  or  more terminfo terminal descriptions in source
+              format; see terminfo(5).  Each description in the file describes
+              the capabilities of a particular terminal type.
 
-              If  file  is "-", then the data is read from the standard input.
-              The file parameter may also be the path of a character-device.
+              If file is "-", the  data  are  read  from  the  standard  input
+              stream.   The file parameter may also be the path of a character
+              device.

                                                                                                                                                                          Processing

                                                                                                                                                                          -       All but one of the capabilities recognized by  tic  are  documented  in
-       terminfo(5).  The exception is the use capability.
+       terminfo(5) documents all but one of  the  capabilities  recognized  by
+       tic.   The  exception  is  the use capability, which enables a terminal
+       type description to incorporate others by reference.
 
-       When a use=entry-name field is discovered in a terminal entry currently
-       being compiled, tic reads in the  binary  from  /usr/share/terminfo  to
-       complete  the  entry.   (Entries  created from file will be used first.
-       tic duplicates the capabilities in entry-name for  the  current  entry,
-       with the exception of those capabilities that explicitly are defined in
-       the current entry.
+       tic serially reads and compiles  terminal  type  descriptions;  at  any
+       given  time,  the program compiles at most one current entry.  When tic
+       encounters a use=entry-name field in the current entry,  it  reads  the
+       compiled description of entry-name from /usr/share/terminfo to complete
+       the current entry.  If tic has already compiled a description of entry-
+       name  preceding  the current entry in file, tic uses it preferentially.
+       tic duplicates the capabilities in entry-name for  the  current  entry,
+       excepting  those  that  the  current  entry  explicitly  defines.   The
+       foregoing has implications for capability cancellation.   When  entry-1
+       declares  "use=entry-2", any canceled capabilities in entry-2 must also
+       appear in entry-1 prior to "use=entry-2" for these capabilities  to  be
+       canceled in entry-1.
 
-       When an entry, e.g., entry_name_1, contains a  use=entry_name_2  field,
-       any   canceled   capabilities  in  entry_name_2  must  also  appear  in
-       entry_name_1 before use= for  these  capabilities  to  be  canceled  in
-       entry_name_1.
-
-       Total  compiled  entries cannot exceed 4096 bytes in the legacy storage
-       format, or 32768 using the extended  number  format.   The  name  field
-       cannot  exceed  512  bytes.  Terminal names exceeding the maximum alias
-       length (32 characters on systems with  long  filenames,  14  characters
-       otherwise)  will be truncated to the maximum alias length and a warning
-       message will be printed.
+       Compiled entries cannot exceed 4096 bytes in the legacy storage format,
+       or  32768  using  the  extended  number  format.  The name field cannot
+       exceed 512 bytes.  Terminal names exceeding the  maximum  alias  length
+       (32 characters on systems with long filenames, 14 characters otherwise)
+       will  be  truncated  to  the maximum alias length and a warning message
+       will be printed.

                                                                                                                                                                          FILES

                                                                                                                                                                          @@ -362,48 +359,49 @@

                                                                                                                                                                          EXTENSIONS

                                                                                                                                                                          -       Unlike the SVr4 tic command, this implementation can  actually  compile
-       termcap  sources.   In fact, entries in terminfo and termcap syntax can
-       be mixed in a single source file.  See  terminfo(5)  for  the  list  of
-       termcap names taken to be equivalent to terminfo names.
+       Unlike  the  SVr4 tic command, ncurses tic can compile termcap sources.
+       In fact, entries in terminfo and termcap  syntax  can  be  mixed  in  a
+       single source file.  See terminfo(5) for the list of termcap capability
+       names ncurses tic treats as equivalent to terminfo names.
 
-       The  SVr4  manual  pages  are not clear on the resolution rules for use
-       capabilities.   This  implementation  of  tic  will  find  use  targets
-       anywhere  in  the  source  file, or anywhere in the file tree rooted at
-       TERMINFO (if TERMINFO is defined), or  in  the  user's  $HOME/.terminfo
-       database  (if  it  exists),  or (finally) anywhere in the system's file
-       tree of compiled entries.
+       The  SVr4  man  pages  are  not clear on the resolution rules for "use"
+       capabilities.  ncurses's tic finds "use" targets anywhere in the source
+       file, or anywhere in the file  tree  rooted  at  the  location  in  the
+       TERMINFO  environment  variable  (if  TERMINFO  is  defined), or in the
+       user's $HOME/.terminfo database (if it exists), or  (finally)  anywhere
+       in the system's collection of compiled entries.
 
-       The error messages from this tic have the same format as  GNU  C  error
-       messages, and can be parsed by GNU Emacs's compile facility.
+       The error messages from ncurses tic have the same format as GNU C error
+       messages, and can be parsed by GNU Emacs's "compile" facility.
 
-       Aside from -c and -v, options are not portable:
+       Aside from -c and -v, options are not portable.
 
-       o   Most of tic's options are not supported by SVr4 tic:
+       o   Most of ncurses tic's options are not supported by SVr4 tic.
 
-           -0 -1 -C -G -I -N -R -T -V -a -e -f -g -o -r -s -t -x
+              -0 -1 -C -G -I -N -R -T -V -a -e -f -g -o -r -s -t -x
 
-       o   The NetBSD tic supports a few of the ncurses options
+       o   NetBSD tic supports a few of the ncurses tic options.
 
-           -a -o -x
+              -a -o -x
 
-           and  adds  -S  (a feature which does the same thing as infocmp's -e
-           and -E options).
+       o   NetBSD  tic  also  adds  -S, a feature which does the same thing as
+           ncurses infocmp's -e and -E options.
 
-       The SVr4 -c mode does not report bad "use=" links.
+       SVr4 tic's -c mode does not report bad "use" links.
 
-       System V does  not  compile  entries  to  or  read  entries  from  your
-       $HOME/.terminfo database unless TERMINFO is explicitly set to it.
+       SVr4  does  not  compile  entries  to  or  read   entries   from   your
+       $HOME/.terminfo  database  unless  the TERMINFO environment variable is
+       explicitly set to it.

                                                                                                                                                                          PORTABILITY

                                                                                                                                                                          -       X/Open  Curses, Issue 7 (2009) provides a brief description of tic.  It
-       lists one option: -c.  The omission of -v is  unexpected.   The  change
-       history  states  that the description is derived from Tru64.  According
+       X/Open Curses Issue 7 (2009) provides a brief description of  tic.   It
+       lists  one  option:  -c.  The omission of -v is unexpected.  The change
+       history states that the description is derived from  Tru64.   According
        to its manual pages, that system also supported the -v option.
 
-       Shortly after Issue 7 was released,  Tru64  was  discontinued.   As  of
-       2019,  the  surviving  implementations  of tic are SVr4 (AIX, HP-UX and
+       Shortly  after  Issue 7  was  released,  Tru64 was discontinued.  As of
+       2019, the surviving implementations of tic are  SVr4  (AIX,  HP-UX  and
        Solaris), ncurses and NetBSD curses.  The SVr4 tic programs all support
        the  -v option.  The NetBSD tic program follows X/Open's documentation,
        omitting the -v option.
@@ -420,26 +418,26 @@
        System  V  Release  2  provided  a  tic  utility.  It accepted a single
        option: -v (optionally  followed  by  a  number).   According  to  Ross
        Ridge's comment in mytinfo, this version of tic was unable to represent
-       cancelled capabilities.
+       canceled capabilities.
 
-       System V Release 3 provided a different tic utility, written  by  Pavel
-       Curtis,  (originally named "compile" in pcurses).  This added an option
-       -c to check the file for errors, with the caveat that errors in  "use="
-       links  would  not  be  reported.   System  V Release 3 documented a few
-       warning messages which did not appear in pcurses.   While  the  program
-       itself  was  changed  little  as  development  continued  with System V
-       Release 4, the table of capabilities grew from  180  (pcurses)  to  464
+       System  V  Release 3 provided a different tic utility, written by Pavel
+       Curtis, (originally named "compile" in pcurses).  This added an  option
+       -c  to check the file for errors, with the caveat that errors in "use="
+       links would not be reported.  System  V  Release  3  documented  a  few
+       warning  messages  which  did not appear in pcurses.  While the program
+       itself was changed  little  as  development  continued  with  System  V
+       Release  4,  the  table  of capabilities grew from 180 (pcurses) to 464
        (Solaris).
 
-       In  early  development of ncurses (1993), Zeyd Ben-Halim used the table
-       from mytinfo to extend the  pcurses  table  to  469  capabilities  (456
-       matched  SVr4, 8 were only in SVr4, 13 were not in SVr4).  Of those 13,
-       11 were ultimately discarded (perhaps to  match  the  draft  of  X/Open
-       Curses).   The exceptions were memory_lock_above and memory_unlock (see
+       In early development of ncurses (1993), Zeyd Ben-Halim used  the  table
+       from  mytinfo  to  extend  the  pcurses  table to 469 capabilities (456
+       matched SVr4, 8 were only in SVr4, 13 were not in SVr4).  Of those  13,
+       11  were  ultimately  discarded  (perhaps  to match the draft of X/Open
+       Curses).  The exceptions were memory_lock_above and memory_unlock  (see
        user_caps(5)).
 
-       Eric Raymond incorporated parts of mytinfo into  ncurses  to  implement
-       the  termcap-to-terminfo  source conversion, and extended that to begin
+       Eric  Raymond  incorporated  parts of mytinfo into ncurses to implement
+       the termcap-to-terminfo source conversion, and extended that  to  begin
        development of the corresponding terminfo-to-termcap source conversion,
        Thomas  Dickey  completed  that  development over the course of several
        years.
@@ -454,21 +452,21 @@
        The  -c  option  tells tic to check for problems in the terminfo source
        file.  Continued development provides additional checks:
 
-       o   pcurses had 8 warnings
+       o   pcurses had 8 warnings.
 
-       o   ncurses in 1996 had 16 warnings
+       o   ncurses in 1996 had 16 warnings.
 
-       o   Solaris (SVr4) curses has 28 warnings
+       o   Solaris (SVr4) curses has 28 warnings.
 
-       o   NetBSD tic in 2019 has 19 warnings.
+       o   NetBSD tic in 2019 has 19 warnings.
 
-       o   ncurses in 2019 has 96 warnings
+       o   ncurses in 2019 has 96 warnings.
 
-       The checking done in ncurses' tic helps with the conversion to termcap,
-       as well as pointing out errors and inconsistencies.  It is also used to
-       ensure consistency with the user-defined capabilities.  There  are  527
-       distinct  capabilities  in ncurses' terminal database; 128 of those are
-       user-defined.
+       The checking done  in  ncurses's  tic  helps  with  the  conversion  to
+       termcap,  as  well  as  pointing out errors and inconsistencies.  It is
+       also used to ensure consistency  with  the  user-defined  capabilities.
+       There are 527 distinct capabilities in ncurses's terminal database; 128
+       of those are user-defined.

                                                                                                                                                                          AUTHORS

                                                                                                                                                                          @@ -480,9 +478,7 @@
        captoinfo(1m),   infocmp(1m),   infotocap(1m),   toe(1m),   curses(3x),
        term(5), terminfo(5), user_caps(5)
 
-
-
-ncurses 6.5                       2024-04-27                           tic(1m)
+ncurses 6.6                       2025-11-11                           tic(1m)
                                                                                                                                                                            diff --git a/doc/html/man/toe.1m.html b/doc/html/man/toe.1m.html index c3aca2c..14c82a9 100644 --- a/doc/html/man/toe.1m.html +++ b/doc/html/man/toe.1m.html @@ -1,7 +1,7 @@ -toe 1m 2024-04-20 ncurses 6.5 User commands +toe 1m 2025-11-11 ncurses 6.6 User commands -

                                                                                                                                                                            toe 1m 2024-04-20 ncurses 6.5 User commands

                                                                                                                                                                            +

                                                                                                                                                                            toe 1m 2025-11-11 ncurses 6.6 User commands

                                                                                                                                                                             toe(1m)                          User commands                         toe(1m)
 
 
-
-

                                                                                                                                                                            NAME

                                                                                                                                                                                    toe - list table of entries of terminfo terminal types
 
@@ -83,7 +81,7 @@
                 Without   the  -s  option,  toe  does  not  attempt  to  merge
                 duplicates in its report.
 
-       -h       writes a heading naming each each directory as it is accessed.
+       -h       writes a heading naming each directory as it is accessed.
 
        -s       sorts the output by the entry names.
 
@@ -91,25 +89,25 @@
                 source  or  termcap  database file.  The report summarizes the
                 "use"  (terminfo)  and  tc  (termcap)  relations:  each   line
                 comprises the primary name of a terminal type employing use/tc
-                capabilities, a colon, a  space-  and  tab-separated  list  of
+                capabilities,  a  colon,  a  space-  and tab-separated list of
                 primary names of terminal types thus named, and a newline.
 
-       -U file  lists  terminal  type reverse dependencies in file, a terminfo
-                entry source or termcap database file.  The report  summarizes
-                the  "use" (terminfo) and tc (termcap) reverse relations: each
-                line comprises the primary name of a terminal  type  occurring
-                in  use/tc  capabilities,  a colon, a space- and tab-separated
-                list of primary names of terminal types naming them thus,  and
+       -U file  lists terminal type reverse dependencies in file,  a  terminfo
+                entry  source or termcap database file.  The report summarizes
+                the "use" (terminfo) and tc (termcap) reverse relations:  each
+                line  comprises  the primary name of a terminal type occurring
+                in use/tc capabilities, a colon, a  space-  and  tab-separated
+                list  of primary names of terminal types naming them thus, and
                 a newline.
 
-       -v [n]   reports  verbose  status  information  to  the  standard error
+       -v [n]   reports verbose  status  information  to  the  standard  error
                 stream, showing toe's progress.
 
-                The optional parameter n  is  an  integer  between  1  and  10
-                inclusive,  interpreted  as  for tic(1m).  If ncurses is built
+                The  optional  parameter  n  is  an  integer  between 1 and 10
+                inclusive, interpreted as for tic(1m).  If  ncurses  is  built
                 without tracing support, n is ignored.
 
-       -V       reports the version of ncurses associated  with  this  program
+       -V       reports  the  version  of ncurses associated with this program
                 and exits with a successful status.
 
 
@@ -119,12 +117,12 @@

                                                                                                                                                                            PORTABILITY

                                                                                                                                                                            -       toe  is  not provided by other implementations.  There is no applicable
+       toe is not provided by other implementations.  There is  no  applicable
        X/Open or POSIX standard for it.

                                                                                                                                                                            HISTORY

                                                                                                                                                                            -       toe replaces a -T option that was  briefly  supported  by  the  ncurses
+       toe  replaces  a  -T  option  that was briefly supported by the ncurses
        infocmp utility in 1995.
 
        The -a and -s options were added in 2006 and 2011, respectively.
@@ -139,8 +137,8 @@

                                                                                                                                                                            EXAMPLES

                                                                                                                                                                            -       When  not  sorting with the -s option, the -a option reports all of the
-       names found in all of the terminal database directories  named  in  the
+       When not sorting with the -s option, the -a option reports all  of  the
+       names  found  in  all of the terminal database directories named in the
        TERMINFO and TERMINFO_DIRS environment variables.
 
            xterm-color     generic color xterm
@@ -157,13 +155,12 @@
            vt52            dec vt52
            ...
 
-       Use  the  -a  and  -s  options  together  to  show  where each terminal
+       Use the -a  and  -s  options  together  to  show  where  each  terminal
        description was found.
 
            --> /etc/terminfo
            ----> /lib/terminfo
            ------> /usr/share/terminfo
-
            --*---: vt100           dec vt100 (w/advanced video)
            --*---: vt102           dec vt102
            --*---: vt220           dec vt220
@@ -183,9 +180,7 @@
        captoinfo(1m),   infocmp(1m),   infotocap(1m),   tic(1m),   curses(3x),
        terminfo(5)
 
-
-
-ncurses 6.5                       2024-04-20                           toe(1m)
+ncurses 6.6                       2025-11-11                           toe(1m)
                                                                                                                                                                              diff --git a/doc/html/man/tput.1.html b/doc/html/man/tput.1.html index ed8fe38..0371e04 100644 --- a/doc/html/man/tput.1.html +++ b/doc/html/man/tput.1.html @@ -1,7 +1,7 @@ -tput 1 2024-04-20 ncurses 6.5 User commands +tput 1 2025-11-11 ncurses 6.6 User commands -

                                                                                                                                                                              tput 1 2024-04-20 ncurses 6.5 User commands

                                                                                                                                                                              +

                                                                                                                                                                              tput 1 2025-11-11 ncurses 6.6 User commands

                                                                                                                                                                               tput(1)                          User commands                         tput(1)
 
 
-
-

                                                                                                                                                                              NAME

                                                                                                                                                                                      tput - initialize a terminal, exercise its capabilities, or query term-
        info database

                                                                                                                                                                              SYNOPSIS

                                                                                                                                                                              -       tput [-T terminal-type] {cap-code [parameter ...]} ...
+       tput [-v] [-T terminal-type] {cap-code [parameter ...]} ...
 
-       tput [-T terminal-type] [-x] clear
+       tput [-v] [-T terminal-type] [-x] clear
 
-       tput [-T terminal-type] init
+       tput [-v] [-T terminal-type] init
 
-       tput [-T terminal-type] reset
+       tput [-v] [-T terminal-type] reset
 
-       tput [-T terminal-type] longname
+       tput [-v] [-T terminal-type] longname
 
-       tput -S
+       tput [-v] -S
 
-       tput -V
+       tput [-v] -V

                                                                                                                                                                              DESCRIPTION

                                                                                                                                                                              -       tput uses the terminfo library and database to  make  terminal-specific
-       capabilities  and  information available to the shell, to initialize or
-       reset the terminal, or to report  a  description  of  the  current  (or
-       specified)  terminal  type.  Terminal capabilities are accessed by cap-
+       tput  uses  the terminfo library and database to make terminal-specific
+       capabilities and information available to the shell, to  initialize  or
+       reset  the  terminal,  or  to  report  a description of the current (or
+       specified) terminal type.  Terminal capabilities are accessed  by  cap-
        code.
 
-       terminfo(5) discusses terminal capabilities at length  and  presents  a
-       complete list of cap-codes.
+       terminfo(5)  discusses  terminal  capabilities at length and presents a
+       complete list of standardized cap-codes.  user_caps(5)  presents  other
+       widely used but non-standard capabilities.
 
        When   retrieving  capability  values,  the  result  depends  upon  the
        capability's type.
@@ -99,28 +98,28 @@
        Generally,  an  operand  is  a  cap-code,  a  capability  code from the
        terminal database, or a parameter thereto.  Three others are  specially
        recognized by tput: init, reset, and longname.  Although these resemble
-       capability codes, they in fact receive special handling; we  term  them
+       capability  codes,  they in fact receive special handling; we term them
        "pseudo-capabilities".
 
        cap-code   indicates a capability from the terminal database.
 
-                  If  cap-code  is  of  string type and takes parameters, tput
-                  interprets arguments following cap-code as  the  parameters,
+                  If cap-code is of string type  and  takes  parameters,  tput
+                  interprets  arguments  following cap-code as the parameters,
                   up to the (fixed) quantity the capability requires.
 
-                  Most   parameters   are   numeric.    Only  a  few  terminal
+                  Most  parameters  are  numeric.    Only   a   few   terminal
                   capabilities require string parameters; tput uses a table to
                   decide  which  to  pass  as  strings.   Normally  tput  uses
                   tparm(3x) to perform the substitution.  If no parameters are
-                  given  for  the  capability,  tput writes the string without
+                  given for the capability, tput  writes  the  string  without
                   performing the substitution.
 
-       init       initializes the  terminal.   If  the  terminal  database  is
-                  present  and  an  entry for the user's terminal type exists,
+       init       initializes  the  terminal.   If  the  terminal  database is
+                  present and an entry for the user's  terminal  type  exists,
                   the following occur.
 
-                  (1)  tput  retrieves  the  terminal's  mode  settings.    It
-                       successively  tests  the file descriptors corresponding
+                  (1)  tput   retrieves  the  terminal's  mode  settings.   It
+                       successively tests the file  descriptors  corresponding
                        to
 
                        o   the standard error stream,
@@ -131,73 +130,69 @@
 
                        o   /dev/tty
 
-                       to obtain terminal settings.   Having  retrieved  them,
-                       tput  remembers  which  descriptor  to  use for further
+                       to  obtain  terminal  settings.  Having retrieved them,
+                       tput remembers which  descriptor  to  use  for  further
                        updates.
 
-                  (2)  If the terminal dimensions cannot be obtained from  the
-                       operating  system, but the environment or terminal type
-                       database  entry  describes  them,  tput   updates   the
+                  (2)  If  the terminal dimensions cannot be obtained from the
+                       operating system, but the environment or terminal  type
+                       database   entry   describes  them,  tput  updates  the
                        operating system's notion of them.
 
                   (3)  tput updates the terminal modes.
 
-                       o   Any  delays  specified  in  the entry (for example,
-                           when a newline is sent) are  set  in  the  terminal
-                           driver.
-
-                       o   Tab   expansion   is  turned  on  or  off  per  the
+                       o   Tab  expansion  is  turned  on  or  off   per   the
                            specification in the entry, and
 
-                       o   if tabs are not expanded, standard  tabs  (every  8
+                       o   if  tabs  are  not expanded, standard tabs (every 8
                            spaces) are set.
 
-                  (4)  If  initialization capabilities, detailed in subsection
-                       "Tabs and Initialization" of terminfo(5), are  present,
+                  (4)  If initialization capabilities, detailed in  subsection
+                       "Tabs  and Initialization" of terminfo(5), are present,
                        tput writes them to the standard output stream.
 
                   (5)  tput flushes the standard output stream.
 
-                  If  an  entry  lacks  the information needed for an activity
+                  If an entry lacks the information  needed  for  an  activity
                   above, that activity is silently skipped.
 
-       reset      re-initializes  the  terminal.    A   reset   differs   from
+       reset      re-initializes   the   terminal.    A   reset  differs  from
                   initialization in two ways.
 
-                  (1)  tput sets the the terminal modes to a "sane" state,
+                  (1)  tput sets the terminal modes to a "sane" state,
 
-                       o   enabling cooked and echo modes,
+                       o   enabling canonical ("cooked") and echo modes,
 
                        o   disabling cbreak and raw modes,
 
                        o   enabling newline translation, and
 
-                       o   setting  any  unset  special  characters  to  their
+                       o   setting  any  special  input  characters  to  their
                            default values.
 
-                  (2)  If any reset capabilities are defined for the  terminal
-                       type,   tput   writes   them   to  the  output  stream.
-                       Otherwise,  tput  uses   any   defined   initialization
-                       capabilities.    Reset  capabilities  are  detailed  in
+                  (2)  If  any reset capabilities are defined for the terminal
+                       type,  tput  writes  them   to   the   output   stream.
+                       Otherwise,   tput   uses   any  defined  initialization
+                       capabilities.   Reset  capabilities  are  detailed   in
                        subsection "Tabs and Initialization" of terminfo(5).
 
-       longname   A terminfo entry begins with one or more names by  which  an
-                  application  can  refer  to  the  entry,  before the list of
-                  terminal capabilities.   The  names  are  separated  by  "|"
-                  characters.   X/Open  Curses  terms  the last name the "long
+       longname   A  terminfo  entry begins with one or more names by which an
+                  application can refer to  the  entry,  before  the  list  of
+                  terminal  capabilities.   The  names  are  separated  by "|"
+                  characters.  X/Open Curses terms the  last  name  the  "long
                   name", and indicates that it may include blanks.
 
-                  tic warns if the last  name  does  not  include  blanks,  to
-                  accommodate  old terminfo entries that treated the long name
-                  as an optional feature.  The long name is often referred  to
+                  tic  warns  if  the  last  name  does not include blanks, to
+                  accommodate old terminfo entries that treated the long  name
+                  as  an optional feature.  The long name is often referred to
                   as the description field.
 
-                  If  the  terminal  database  is present and an entry for the
+                  If the terminal database is present and  an  entry  for  the
                   user's terminal type exists, tput reports its description to
                   the standard output stream, without a trailing newline.  See
                   terminfo(5).
 
-       Note: Redirecting the output of "tput init" or "tput reset" to  a  file
+       Note:  Redirecting  the output of "tput init" or "tput reset" to a file
        will capture only part of their actions.  Changes to the terminal modes
        are not affected by file descriptor  redirection,  since  the  terminal
        modes are altered via ioctl(2).
@@ -209,20 +204,20 @@
        operand.  For example, executing a link named reset that points to tput
        has the same effect as "tput reset".
 
-       This feature was introduced by ncurses 5.2 in 2000.  It is rarely used:
+       This feature was introduced by ncurses 5.2 in 2000.  It is rarely used.
 
        clear  is a separate program, which is both smaller and more frequently
               executed.
 
        init   has the same name as another program in widespread use.
 
-       reset  is  provided  by  the  tset(1)  utility  (also  via a link named
+       reset  is provided by the  tset(1)  utility  (also  via  a  link  named
               reset).

                                                                                                                                                                              Terminal Size

                                                                                                                                                                              -       Besides the pseudo-capabilities (such as init), tput treats  the  lines
-       and  cols  cap-codes specially: it may call setupterm(3x) to obtain the
+       Besides  the  pseudo-capabilities (such as init), tput treats the lines
+       and cols cap-codes specially: it may call setupterm(3x) to  obtain  the
        terminal size.
 
        o   First, tput attempts to obtain these capabilities from the terminal
@@ -259,6 +254,8 @@
                 environment variable.  If specified, the environment variables
                 LINES and COLUMNS are also ignored.
 
+       -v       causes tput to operate verbosely, reporting warnings.
+
        -V       reports the version of ncurses associated with tput, and exits
                 with a successful status.
 
@@ -288,10 +285,15 @@

                                                                                                                                                                              ENVIRONMENT

                                                                                                                                                                              -       tput reads one environment variable.
+       tput reads up to three environment variables if the -T  option  is  not
+       specified.
 
-       TERM    denotes the terminal type.  Each  terminal  type  is  distinct,
-               though many are similar.  The -T option overrides its value.
+       COLUMNS  specifies the width of the screen in characters.
+
+       LINES    specifies the height of the screen in characters.
+
+       TERM     denotes  the  terminal  type.  Each terminal type is distinct,
+                though many are similar.

                                                                                                                                                                              FILES

                                                                                                                                                                              @@ -303,56 +305,56 @@

                                                                                                                                                                              PORTABILITY

                                                                                                                                                                              -       Over  time  ncurses  tput  has  differed  from  that of System V in two
+       Over time ncurses tput has  differed  from  that  of  System V  in  two
        important respects, one now mostly historical.
 
-       o   "tput cap-code" writes to the standard output, which need not be  a
-           terminal  device.   However,  the operands that manipulate terminal
+       o   "tput  cap-code" writes to the standard output, which need not be a
+           terminal device.  However, the operands  that  manipulate  terminal
            modes might not use the standard output.
 
-           System V tput's init and reset  operands  use  logic  from  4.1cBSD
-           tset,  manipulating  terminal  modes.   It  checks  the  same  file
-           descriptors (and /dev/tty) for association with a  terminal  device
-           as  ncurses  now does, and if none are, finally assumes a 1200 baud
+           System V  tput's  init  and  reset  operands use logic from 4.1cBSD
+           tset,  manipulating  terminal  modes.   It  checks  the  same  file
+           descriptors  (and  /dev/tty) for association with a terminal device
+           as ncurses now does, and if none are, finally assumes a  1200  baud
            terminal.  When updating terminal modes, it ignores errors.
 
-           Until ncurses 6.1 (see  section  "HISTORY"  below),  tput  did  not
+           Until  ncurses  6.1  (see  section  "HISTORY"  below), tput did not
            modify  terminal  modes.   It  now  employs  a  scheme  similar  to
            System V, using functions shared with tset (and ultimately based on
-           4.4BSD  tset).  If it is not able to open a terminal (for instance,
+           4.4BSD  tset).  If it is not able to open a terminal (for instance,
            when run by cron(1)), tput exits with an error status.
 
-       o   System V tput assumes that  the  type  of  a  cap-code  operand  is
+       o   System V tput assumes that  the  type  of  a  cap-code  operand  is
            numeric  if all the characters of its value are decimal numbers; if
            they are not, it treats cap-code as a string capability.
 
            Most implementations that provide support for cap-code operands use
-           the  tparm(3x)  function  to  expand its parameters.  That function
-           expects a mixture of numeric and string parameters, requiring  tput
+           the tparm(3x) function to expand  its  parameters.   That  function
+           expects  a mixture of numeric and string parameters, requiring tput
            to know which type to use.
 
-           ncurses  tput uses a table to determine the parameter types for the
-           standard cap-code operands, and an  internal  function  to  analyze
+           ncurses tput uses a table to determine the parameter types for  the
+           standard  cap-code  operands,  and  an internal function to analyze
            nonstandard cap-code operands.
 
-           While  more reliable than System V's utility, a portability problem
-           is introduced by this analysis.  An OpenBSD developer  adapted  the
-           internal  library  function  from ncurses to port NetBSD's termcap-
-           based tput to terminfo, and modified it to interpret multiple  cap-
-           codes  (and parameters) on the command line.  Portable applications
-           should not rely upon this feature; ncurses  offers  it  to  support
+           While more reliable than System V's utility, a portability  problem
+           is  introduced  by this analysis.  An OpenBSD developer adapted the
+           internal library function from ncurses to  port  NetBSD's  termcap-
+           based  tput to terminfo, and modified it to interpret multiple cap-
+           codes (and parameters) on the command line.  Portable  applications
+           should  not  rely  upon  this feature; ncurses offers it to support
            applications written specifically for OpenBSD.
 
-       This  implementation,  unlike others, accepts both termcap and terminfo
-       cap-codes if termcap support is compiled in.  In  that  case,  however,
-       the predefined termcap and terminfo codes have two ambiguities; ncurses
+       ncurses's implementation of tput, unlike others, accepts  both  termcap
+       and  terminfo  cap-codes  if  termcap  support is compiled in.  In that
+       case, however, termcap and terminfo codes have two ambiguities; ncurses
        assumes the terminfo code.
 
        o   The cap-code dl means delete_line to termcap  but  parm_delete_line
            to terminfo.  termcap uses the code DL for parm_delete_line.  term-
            info uses the code dl1 for delete_line.
 
-       o   The cap-code ed means exit_delete_mode to termcap  but  clr_eos  to
+       o   The  cap-code  ed  means exit_delete_mode to termcap but clr_eos to
            terminfo.  termcap uses the code cd for clr_eos.  terminfo uses the
            code rmdc for exit_delete_mode.
 
@@ -362,24 +364,24 @@
        longname,  and  in  1994,  NetBSD  added  support  for  the  parameter-
        substitution features.
 
-       IEEE  Std  1003.1/The  Open   Group   Base   Specifications   Issue   7
-       (POSIX.1-2008)  documents  only the clear, init, and reset operands.  A
+       IEEE   Std   1003.1/The   Open   Group   Base   Specifications  Issue 7
+       (POSIX.1-2008) documents only the clear, init, and reset  operands.   A
        few observations of interest arise from that selection.
 
        o   ncurses supports clear as it does any other standard cap-code.  The
            others   (init   and   longname)  do  not  correspond  to  terminal
            capabilities.
 
-       o   The tput on SVr4-based systems such as Solaris, IRIX64, and  HP-UX,
+       o   The tput on SVr4-based systems such as Solaris, IRIX64, and  HP-UX,
            as well as others such as AIX and Tru64, also support standard cap-
            code operands.
 
        o   A few platforms such as FreeBSD recognize termcap codes rather than
-           terminfo capability codes in their respective tput commands.  Since
-           2010, NetBSD's tput uses terminfo codes.   Before  that,  it  (like
+           terminfo capability codes in their respective tput commands.  Since
+           2010,  NetBSD's  tput  uses  terminfo codes.  Before that, it (like
            FreeBSD) recognized termcap codes.
 
-           Beginning  in  2021, FreeBSD uses ncurses tput, configured for both
+           Beginning in 2021, FreeBSD uses ncurses tput, configured  for  both
            terminfo (tested first) and termcap (as a fallback).
 
        Because (apparently) all certified Unix systems support the full set of
@@ -389,16 +391,16 @@
        o   X/Open Curses Issue 7 documents tput differently, with cap-code and
            the other features used in this implementation.
 
-       o   That  is,  there  are  two standards for tput: POSIX (a subset) and
-           X/Open Curses (the full implementation).  POSIX documents a  subset
-           to  avoid  the  complication  of  including  X/Open  Curses and the
+       o   That is, there are two standards for tput:  POSIX  (a  subset)  and
+           X/Open  Curses (the full implementation).  POSIX documents a subset
+           to avoid the  complication  of  including  X/Open  Curses  and  the
            terminal capability database.
 
-       o   While it is certainly possible to  write  a  tput  program  without
-           using  curses,  no  system  with a curses implementation provides a
-           tput utility that does not also support standard cap-codes.
+       o   While  it  is  certainly  possible  to write a tput program without
+           using curses, no system with a  curses  implementation  provides  a
+           tput utility that does not also support standard cap-codes.
 
-       X/Open  Curses  Issue  7  (2009)  is  the  first  version  to  document
+       X/Open   Curses  Issue 7  (2009)  is  the  first  version  to  document
        utilities.  However that part of X/Open Curses does not follow existing
        practice (that is, System V curses behavior).
 
@@ -408,78 +410,78 @@
 
        o   It assigns exit status 255  to  a  numeric  variable  that  is  not
            specified in the terminfo database.  That likely is a documentation
-           error, mistaking  the  "-1"  written  to  the  standard  output  to
-           indicate   an   absent  or  cancelled  numeric  capability  for  an
-           (unsigned) exit status.
+           error,  mistaking  the  "-1"  written  to  the  standard  output to
+           indicate an absent or canceled numeric capability for an (unsigned)
+           exit status.
 
        The various System V implementations (AIX, HP-UX, Solaris) use the same
        exit statuses as ncurses.
 
-       NetBSD  curses  documents  exit  statuses  that  correspond  to neither
+       NetBSD curses  documents  exit  statuses  that  correspond  to  neither
        ncurses nor X/Open Curses.

                                                                                                                                                                              HISTORY

                                                                                                                                                                              -       Bill Joy wrote a tput command during development  of  4BSD  in  October
-       1980.   This  initial version only cleared the screen, and did not ship
+       Bill  Joy  wrote  a  tput command during development of 4BSD in October
+       1980.  This initial version only cleared the screen, and did  not  ship
        with official distributions.
 
-       System V developed a different tput command.
+       System V developed a different tput command.
 
-       o   SVr2 (1984) provided a rudimentary tput that checked the  parameter
-           against  each  predefined capability and returned the corresponding
-           value.   This  version  of  tput  did   not   use   tparm(3x)   for
-           parameterized capabilities.
+       o   SVr2  (1984) provided a rudimentary tput that checked the parameter
+           against each capability name and returned the corresponding  value.
+           This  version  of  tput  did  not  use  tparm(3x) for parameterized
+           capabilities.
 
-       o   SVr3  (1987)  replaced  that  with  a  more extensive program whose
-           support for init and reset operands (more than  half  the  program)
-           incorporated the reset feature of BSD tset written by Eric Allman.
+       o   SVr3 (1987) replaced that  with  a  more  extensive  program  whose
+           support  for  init  and reset operands (more than half the program)
+           incorporated the reset feature of BSD tset written by Eric Allman.
 
-       o   SVr4  (1989)  added  color  initialization by using the orig_colors
+       o   SVr4 (1989) added color initialization  by  using  the  orig_colors
            (oc) and orig_pair (op) capabilities in its init logic.
 
-       Keith Bostic refactored BSD tput for shipment in  4.3BSD-Tahoe  (1988),
-       then  replaced  it  the  next  year  with a new implementation based on
-       System V tput.  Bostic's version  similarly  accepted  some  parameters
-       named  for  terminfo  (pseudo-)capabilities: clear, init, longname, and
-       reset.  However, because he had only  termcap  available,  it  accepted
-       termcap  codes for other capabilities.  Also, Bostic's BSD tput did not
-       modify the terminal modes as the earlier BSD tset had done.
-
-       At the same time, Bostic added a shell script named "clear"  that  used
-       tput  to  clear the screen.  Both of these appeared in 4.4BSD, becoming
-       the "modern" BSD implementation of tput.
+       Keith  Bostic  refactored  BSD tput for shipment in 4.3BSD-Reno (1990),
+       making it follow the interface  of  System V  tput  by  accepting  some
+       parameters  named  for  terminfo  (pseudo-)capabilities:  clear,  init,
+       longname, and reset.  However, because he had only  termcap  available,
+       it  accepted  termcap codes for other capabilities.  Also, Bostic's BSD
+       tput did not modify the terminal modes as  the  earlier  BSD  tset  had
+       done.  At the same time, Bostic added a shell script named "clear" that
+       used  tput  to  clear  the  screen.   These  became  the  "modern"  BSD
+       implementation of tput.
 
        The origin of ncurses tput lies outside both System V and BSD, in  Ross
        Ridge's  mytinfo  package,  published  on comp.sources.unix in December
        1992.  Ridge's program made more  sophisticated  use  of  the  terminal
-       capabilities than the BSD program.  Eric Raymond used that tput program
-       (and other parts of mytinfo) in ncurses in  June  1995.   Incorporating
-       the  portions dealing with terminal capabilities almost without change,
-       Raymond made improvements  to  the  way  command-line  parameters  were
+       capabilities than the BSD program.  Eric Raymond used that tput program
+       (and  other  parts  of mytinfo) in ncurses in June 1995.  Incorporating
+       the portions dealing with terminal capabilities almost without  change,
+       Raymond  made  improvements  to  the  way  command-line parameters were
        handled.
 
        Before ncurses 6.1 (2018), its tset and tput utilities differed.
 
-       o   tset  was  more effective, resetting the terminal modes and special
-           characters.
+       o   tset was more effective, resetting the terminal's modes and special
+           input characters.
 
        o   On the other hand, tset's repertoire of terminal  capabilities  for
            resetting the terminal was more limited; it had only equivalents of
-           reset_1string (rs1), reset_2string (rs2), and reset_file (rf),  and
+           reset_1string  (rs1), reset_2string (rs2), and reset_file (rf), and
            not the tab stop and margin update features of tput.
 
-       The reset program is traditionally an alias for tset due to its ability
-       to reset terminal modes and special characters.
+       The reset program is traditionally an alias for tset due to its ability
+       to reset the terminal's modes and special input characters.
 
        As of ncurses 6.1,  the  "reset"  features  of  the  two  programs  are
        (mostly) the same.  Two minor differences remain.
 
-       o   The  tset  program  waits  one  second  when resetting, in case the
-           terminal happens to be a hardware device.
+       o   When  issuing  a  reset, the tset program checks whether the device
+           appears to be a pseudoterminal (as might  be  used  by  a  terminal
+           emulator program), and, if it does not, waits one second in case it
+           is communicating with a hardware terminal.
 
-       o   The two programs  write  the  terminal  initialization  strings  to
-           different  streams;  that  is, standard error for tset and standard
+       o   The  two  programs  write  the  terminal  initialization strings to
+           different streams; that is, standard error for  tset  and  standard
            output for tput.
 
 
@@ -498,8 +500,8 @@
               Set cursor to normal visibility.
 
        tput home
-              Move the cursor to row 0, column 0: the upper left corner of the
-              screen, usually known as the "home" cursor position.
+              Move the cursor to line 0, column 0: the upper  left  corner  of
+              the screen, usually known as the "home" cursor position.
 
        tput clear
               Clear  the  screen: write the clear_screen capability's value to
@@ -523,7 +525,7 @@
               device.
 
        tput cup 23 4
-              Move the cursor to row 23, column 4.
+              Move the cursor to line 23, column 4.
 
        tput cup
               Report  the  value  of the cursor_address (cup) capability (used
@@ -551,11 +553,10 @@

                                                                                                                                                                              SEE ALSO

                                                                                                                                                                              -       clear(1), stty(1), tabs(1), tset(1), curs_termcap(3x), terminfo(5)
+       clear(1),  stty(1),  tabs(1),  tset(1),  curs_termcap(3x), terminfo(5),
+       user_caps(5)
 
-
-
-ncurses 6.5                       2024-04-20                           tput(1)
+ncurses 6.6                       2025-11-11                           tput(1)
                                                                                                                                                                                diff --git a/doc/html/man/tset.1.html b/doc/html/man/tset.1.html index a566956..2ae0aff 100644 --- a/doc/html/man/tset.1.html +++ b/doc/html/man/tset.1.html @@ -1,6 +1,6 @@ -tset 1 2024-04-27 ncurses 6.5 User commands +tset 1 2025-01-18 ncurses 6.6 User commands -

                                                                                                                                                                                tset 1 2024-04-27 ncurses 6.5 User commands

                                                                                                                                                                                +

                                                                                                                                                                                tset 1 2025-01-18 ncurses 6.6 User commands

                                                                                                                                                                                 tset(1)                          User commands                         tset(1)
 
 
-
-

                                                                                                                                                                                NAME

                                                                                                                                                                                        tset, reset - initialize or reset terminal state
 
@@ -115,8 +113,10 @@
            kill characters (among many other things) are set
 
        o   unless   the   "-I"   option  is  enabled,  the  terminal  and  tab
-           initialization strings are sent to the standard error  output,  and
-           tset waits one second (in case a hardware reset was issued).
+           initialization strings are sent to the standard error output,  and,
+           if  the  terminal device does not appear to be a pseudoterminal (as
+           might be used by a  terminal  emulator  program),  tset  waits  one
+           second in case a hardware reset was issued.
 
        o   Finally,  if  the  erase,  interrupt  and line kill characters have
            changed, or are not set to their default values, their  values  are
@@ -126,19 +126,19 @@

                                                                                                                                                                                reset -- reinitialization

                                                                                                                                                                                        When invoked as reset, tset sets the terminal modes to "sane" values:
 
-       o   sets cooked and echo modes,
+       o   sets canonical ("cooked") and echo modes,
 
        o   turns off cbreak and raw modes,
 
        o   turns on newline translation and
 
-       o   resets any unset special characters to their default values
+       o   resets special input characters to their default values
 
        before doing the terminal initialization described above.  Also, rather
-       than using the terminal initialization strings, it  uses  the  terminal
+       than  using  the  terminal initialization strings, it uses the terminal
        reset strings.
 
-       The  reset command is useful after a program dies leaving a terminal in
+       The reset command is useful after a program dies leaving a terminal  in
        an abnormal state:
 
        o   you may have to type
@@ -157,10 +157,10 @@
        the terminal's capabilities into the shell's environment.  This is done
        using the -s option.
 
-       When the -s option is specified, the commands to enter the  information
-       into  the  shell's  environment are written to the standard output.  If
-       the SHELL environment variable ends in  "csh",  the  commands  are  for
-       csh(1),  otherwise, they are for sh(1).  The csh commands set and unset
+       When  the -s option is specified, the commands to enter the information
+       into the shell's environment are written to the  standard  output.   If
+       the  SHELL  environment  variable  ends  in "csh", the commands are for
+       csh(1), otherwise, they are for sh(1).  The csh commands set and  unset
        the shell variable noglob, leaving it unset.  The following line in the
        .login or .profile files will initialize the environment correctly:
 
@@ -179,31 +179,31 @@
        that is, to tell tset "If I'm on this port at a particular speed, guess
        that I'm on that kind of terminal".
 
-       The argument to the -m option consists of an  optional  port  type,  an
-       optional  operator,  an  optional  baud rate specification, an optional
-       colon (":") character and a terminal type.  The port type is  a  string
-       (delimited  by  either  the  operator  or  the  colon  character).  The
-       operator may be any combination of ">", "<", "@", and  "!";  ">"  means
-       greater  than,  "<" means less than, "@" means equal to and "!" inverts
-       the sense of the test.  The baud rate is specified as a number  and  is
-       compared  with  the speed of the standard error output (which should be
+       The  argument  to  the  -m option consists of an optional port type, an
+       optional operator, an optional baud  rate  specification,  an  optional
+       colon  (":")  character and a terminal type.  The port type is a string
+       (delimited by  either  the  operator  or  the  colon  character).   The
+       operator  may  be  any combination of ">", "<", "@", and "!"; ">" means
+       greater than, "<" means less than, "@" means equal to and  "!"  inverts
+       the  sense  of the test.  The baud rate is specified as a number and is
+       compared with the speed of the standard error output (which  should  be
        the control terminal).  The terminal type is a string.
 
-       If the terminal type is not specified  on  the  command  line,  the  -m
-       mappings  are  applied to the terminal type.  If the port type and baud
-       rate match the mapping, the terminal  type  specified  in  the  mapping
-       replaces  the current type.  If more than one mapping is specified, the
+       If  the  terminal  type  is  not  specified on the command line, the -m
+       mappings are applied to the terminal type.  If the port type  and  baud
+       rate  match  the  mapping,  the  terminal type specified in the mapping
+       replaces the current type.  If more than one mapping is specified,  the
        first applicable mapping is used.
 
-       For example, consider the following  mapping:  dialup>9600:vt100.   The
+       For  example,  consider  the following mapping: dialup>9600:vt100.  The
        port type is dialup , the operator is >, the baud rate specification is
        9600, and the terminal type is vt100.  The result of this mapping is to
-       specify  that  if  the  terminal  type  is dialup, and the baud rate is
+       specify that if the terminal type is  dialup,  and  the  baud  rate  is
        greater than 9600 baud, a terminal type of vt100 will be used.
 
-       If no baud rate is specified, the terminal type  will  match  any  baud
-       rate.   If  no port type is specified, the terminal type will match any
-       port type.  For example, -m dialup:vt100  -m  :?xterm  will  cause  any
+       If  no  baud  rate  is specified, the terminal type will match any baud
+       rate.  If no port type is specified, the terminal type will  match  any
+       port  type.   For  example,  -m  dialup:vt100 -m :?xterm will cause any
        dialup port, regardless of baud rate, to match the terminal type vt100,
        and any non-dialup port type to match the terminal type ?xterm.   Note,
        because  of  the  leading  question mark, the user will be queried on a
@@ -212,7 +212,7 @@
        No whitespace characters are  permitted  in  the  -m  option  argument.
        Also,  to avoid problems with meta-characters, it is suggested that the
        entire -m option argument be placed within single quote characters, and
-       that   csh   users  insert  a  backslash  character  ("\")  before  any
+       that  csh  users  insert  a  backslash  character  ("\")   before   any
        exclamation marks ("!").
 
 
@@ -224,7 +224,7 @@
        -e ch
             Set the erase character to ch.
 
-       -I   Do not send the terminal or  tab  initialization  strings  to  the
+       -I   Do  not  send  the  terminal  or tab initialization strings to the
             terminal.
 
        -i ch
@@ -234,15 +234,15 @@
             Set the line kill character to ch.
 
        -m mapping
-            Specify  a  mapping from a port type to a terminal; see subsection
+            Specify a mapping from a port type to a terminal;  see  subsection
             "Terminal Type Mapping".
 
-       -Q   Do not display any values for the erase, interrupt and  line  kill
-            characters.    Normally  tset  displays  the  values  for  control
+       -Q   Do  not  display any values for the erase, interrupt and line kill
+            characters.   Normally  tset  displays  the  values  for   control
             characters which differ from the system's default values.
 
-       -q   The terminal type is displayed to the  standard  output,  and  the
-            terminal  is not initialized in any way.  The option "-" by itself
+       -q   The  terminal  type  is  displayed to the standard output, and the
+            terminal is not initialized in any way.  The option "-" by  itself
             is equivalent but archaic.
 
        -r   Print the terminal type to the standard error output.
@@ -254,12 +254,12 @@
        -V   reports the version of ncurses which was used in this program, and
             exits.
 
-       -w   Resize  the  window  to  match the size deduced via setupterm(3x).
-            Normally this has no effect,  unless  setupterm  is  not  able  to
+       -w   Resize the window to match the  size  deduced  via  setupterm(3x).
+            Normally  this  has  no  effect,  unless  setupterm is not able to
             detect the window size.
 
-       The  arguments  for the -e, -i, and -k options may either be entered as
-       actual characters or by using the "hat" notation, i.e.,  control-h  may
+       The arguments for the -e, -i, and -k options may either be  entered  as
+       actual  characters  or by using the "hat" notation, i.e., control-h may
        be specified as "^H" or "^h".
 
        If neither -c or -w is given, both options are assumed.
@@ -269,16 +269,16 @@
        The tset command uses these environment variables:
 
        SHELL
-            tells  tset  whether  to  initialize  TERM  using  sh(1) or csh(1)
+            tells tset whether  to  initialize  TERM  using  sh(1)  or  csh(1)
             syntax.
 
-       TERM Denotes your terminal  type.   Each  terminal  type  is  distinct,
+       TERM Denotes  your  terminal  type.   Each  terminal  type is distinct,
             though many are similar.
 
        TERMCAP
-            may  denote  the  location of a termcap database.  If it is not an
-            absolute pathname, e.g., begins  with  a  "/",  tset  removes  the
-            variable  from  the  environment  before  looking for the terminal
+            may denote the location of a termcap database.  If it  is  not  an
+            absolute  pathname,  e.g.,  begins  with  a  "/", tset removes the
+            variable from the environment  before  looking  for  the  terminal
             description.
 
 
@@ -303,29 +303,29 @@
        tset.
 
        The tset utility provides backward compatibility with BSD environments;
-       under most modern  Unices,  /etc/inittab  and  getty(8)  can  set  TERM
-       appropriately  for  each  dial-up  line, obviating what was tset's most
-       important use.  This implementation behaves like 4.4BSD  tset,  with  a
+       under  most  modern  Unices,  /etc/inittab  and  getty(8)  can set TERM
+       appropriately for each dial-up line, obviating  what  was  tset's  most
+       important  use.   This  implementation behaves like 4.4BSD tset, with a
        few exceptions we shall consider now.
 
-       A  few  options are different because the TERMCAP variable is no longer
+       A few options are different because the TERMCAP variable is  no  longer
        supported under terminfo-based ncurses:
 
-       o   The -S option of BSD tset no  longer  works;  it  prints  an  error
+       o   The  -S  option  of  BSD  tset  no longer works; it prints an error
            message to the standard error and dies.
 
        o   The -s option only sets TERM, not TERMCAP.
 
-       There  was an undocumented 4.4BSD feature that invoking tset via a link
-       named "TSET" (or via  any  other  name  beginning  with  an  upper-case
+       There was an undocumented 4.4BSD feature that invoking tset via a  link
+       named  "TSET"  (or  via  any  other  name  beginning with an upper-case
        letter) set the terminal to use upper-case only.  This feature has been
        omitted.
 
        The -A, -E, -h, -u and -v options were deleted from the tset utility in
-       4.4BSD.   None of them were documented in 4.3BSD and all are of limited
-       utility at best.   The  -a,  -d,  and  -p  options  are  similarly  not
-       documented  or  useful,  but  were  retained  as  they  appear to be in
-       widespread use.  It is strongly recommended that  any  usage  of  these
+       4.4BSD.  None of them were documented in 4.3BSD and all are of  limited
+       utility  at  best.   The  -a,  -d,  and  -p  options  are similarly not
+       documented or useful, but  were  retained  as  they  appear  to  be  in
+       widespread  use.   It  is  strongly recommended that any usage of these
        three options be changed to use the -m option instead.  The -a, -d, and
        -p options are therefore omitted from the usage summary above.
 
@@ -339,7 +339,7 @@
        arguments, although it is strongly recommended that such usage be fixed
        to explicitly specify the character.
 
-       As of 4.4BSD, executing tset as reset no longer implies the -Q  option.
+       As  of 4.4BSD, executing tset as reset no longer implies the -Q option.
        Also, the interaction between the - option and the terminal argument in
        some historic implementations of tset has been removed.
 
@@ -391,9 +391,7 @@
        csh(1),   sh(1),   stty(1),   curs_terminfo(3x),  tty(4),  terminfo(5),
        ttys(5), environ(7)
 
-
-
-ncurses 6.5                       2024-04-27                           tset(1)
+ncurses 6.6                       2025-01-18                           tset(1)
                                                                                                                                                                                  diff --git a/doc/html/man/user_caps.5.html b/doc/html/man/user_caps.5.html index 10b6f77..5b00603 100644 --- a/doc/html/man/user_caps.5.html +++ b/doc/html/man/user_caps.5.html @@ -1,7 +1,7 @@ -user_caps 5 2024-03-16 ncurses 6.5 File formats +user_caps 5 2025-11-11 ncurses 6.6 File formats -

                                                                                                                                                                                  user_caps 5 2024-03-16 ncurses 6.5 File formats

                                                                                                                                                                                  +

                                                                                                                                                                                  user_caps 5 2025-11-11 ncurses 6.6 File formats

                                                                                                                                                                                   user_caps(5)                     File formats                     user_caps(5)
 
 
-
-

                                                                                                                                                                                  NAME

                                                                                                                                                                                          user_caps - user-defined terminfo capability format
 
@@ -60,225 +58,231 @@

                                                                                                                                                                                  DESCRIPTION

                                                                                                                                                                                  Background

                                                                                                                                                                                  -       Before  ncurses  5.0,  terminfo  databases  used  a fixed repertoire of
-       terminal capabilities designed for the SVr2 terminal database in  1984,
-       and  extended  in  stages  through SVr4 (1989), and standardized in the
-       Single Unix Specification beginning in 1995.
+       Prior to ncurses 5.0 (1999), terminfo databases used a fixed repertoire
+       of  terminal  capabilities  designed  for the SVr2 terminal database in
+       1984, added to in stages  through  SVr4  (1989),  and  standardized  in
+       X/Open Curses starting in 1995.
 
-       Most of the extensions in this fixed repertoire were additions  to  the
-       tables of Boolean, numeric and string capabilities.  Rather than change
-       the meaning of an existing capability,  a  new  name  was  added.   The
-       terminfo  database  uses  a  binary  format;  binary  compatibility was
-       ensured by using a header which gave the number of items in the  tables
-       for each type of capability.  The standardization was incomplete:
+       Most such additions to this fixed repertoire suppelmented the tables of
+       Boolean,  numeric,  and  string capabilities.  Rather than changing the
+       meaning of an existing capability, a new name was added.  The  terminfo
+       database  uses  a  binary  format;  binary compatibility was ensured by
+       using a header that counted the number of items in the tables for  each
+       type  of  capability.  Because each curses vendor extended the standard
+       capability lists in distinct ways, a library  could  be  programmed  to
+       recognize  only  compiled  terminfo  entries  that  it  was prepared to
+       interpret.  Standardization was incomplete.
 
-       o   The  binary  format  itself  is  not described in the X/Open Curses
-           documentation.  Only the source format is described.
+       o   X/Open Curses describes only the  source  format,  not  its  binary
+           representation on disk.
 
-           Library developers rely upon the SVr4 documentation,  and  reverse-
-           engineering the compiled terminfo files to match the binary format.
+           Library   developers  rely  upon  SVr4  documentation  and  reverse
+           engineering of compiled terminfo files to match the binary format.
 
        o   Lacking a standard for the binary format, most implementations copy
            the SVr2 binary format, which uses 16-bit signed integers,  and  is
            limited to 4096-byte entries.
 
-           The  format  cannot  represent very large numeric capabilities, nor
-           can it represent large numbers of special keyboard definitions.
+           The  SVr2  format  cannot  represent  very large numeric capability
+           values, nor can it represent large numbers of key  definitions,  as
+           are   required  to  distinguish  multiple  modifier  keys  used  in
+           combination with a function key.
 
        o   The tables of capability names differ between implementations.
 
-           Although they may provide all of the standard capability names, the
-           position  in the tables differs because some features were added as
-           needed, while others were added  (out  of  order)  to  comply  with
-           X/Open Curses.
+           Although they may provide all of  the  standard  capability  names,
+           each  arranges  its table entries differently because some features
+           were added as needed, while others were added -- out  of  order  --
+           for X/Open Curses conformance.
 
-           While  ncurses' repertoire of predefined capabilities is closest to
-           Solaris, Solaris's terminfo database has a few differences from the
-           list  published  by  X/Open  Curses.   For  example, ncurses can be
-           configured with tables which match the terminal databases for  AIX,
-           HP-UX or OSF/1, rather than the default Solaris-like configuration.
+           While  ncurses's  capability  repertoire  is  closest  to  that  of
+           Solaris, the set of capabilities supported by each  vendor's  term-
+           info  database  differs  from  the list published by X/Open Curses.
+           ncurses can be configured  with  tables  that  match  the  terminal
+           databases  for  AIX,  HP-UX,  or  OSF/1,  rather  than  the default
+           Solaris-like configuration.
 
-       o   In  SVr4  curses  and  ncurses, the terminal database is defined at
-           compile-time using a text file which lists the  different  terminal
-           capabilities.
+       o   In SVr4 curses and ncurses, the terminal  database  is  defined  at
+           compile  time by interpolating a text file that lists the different
+           terminal capabilities.
 
-           In  principle,  the  text-file  can  be  extended,  but  doing this
-           requires recompiling and reinstalling the library.   The  text-file
-           used  in  ncurses  for  terminal  capabilities includes details for
-           various systems past the documented X/Open  Curses  features.   For
-           example, ncurses supports these capabilities in each configuration:
+           In principle, the text file can be extended, but doing so  requires
+           recompiling  and  reinstalling  the library.  The text file used by
+           ncurses for terminal capabilities includes details of extensions to
+           X/Open Curses  made  by  various  systems.   For  example,  ncurses
+           supports   the   following   nonstandard   capabilities   in   each
+           configuration.
 
-               memory_lock
-                    (meml) lock memory above cursor
+               memory_lock
+                    (meml) lock memory above cursor
 
-               memory_unlock
-                    (memu) unlock memory
+               memory_unlock
+                    (memu) unlock memory
 
-               box_chars_1
-                    (box1) box characters primary set
+               box_chars_1
+                    (box1) box characters primary set
 
            The memory lock/unlock capabilities were included because they were
-           used in the X11R6 terminal  description  for  xterm(1).   The  box1
-           capability  is  used  in  tic  to  help  with terminal descriptions
-           written for AIX.
+           used in the X11R6 terminal description for xterm(1).  tic uses  the
+           box1 capability to cope with terminal descriptions written for AIX.
 
-       During the 1990s, some users were reluctant to use terminfo in spite of
-       its performance advantages over termcap:
+       During  the  1990s,  some  application developers were reluctant to use
+       terminfo in spite  of  its  performance  (and  other)  advantages  over
+       termcap.
 
-       o   The  fixed  repertoire  prevented  users  from  adding features for
-           unanticipated terminal improvements  (or  required  them  to  reuse
-           existing capabilities as a workaround).
+       o   The  fixed  repertoire  prevented  users  from  adding  support for
+           terminal features unanticipated by X/Open Curses (or required  them
+           to reuse existing capabilities as a workaround).
 
        o   The  limitation  to  16-bit  signed  integers  was  also mentioned.
-           Because termcap stores everything as a string, it  could  represent
+           Because termcap stores everything as a string, it  could  represent
            larger numbers.
 
-       Although  termcap's  extensibility  was  rarely  used (it was never the
-       speaker who had actually used the feature), the criticism had a  point.
-       ncurses   5.0  provided  a  way  to  detect  nonstandard  capabilities,
-       determine their type and optionally store and retrieve them  in  a  way
-       which did not interfere with other applications.  These are referred to
-       as user-defined capabilities because no modifications to the  toolset's
-       predefined capability names are needed.
+       Although  termcap's  extensibility  was rarely used -- the claimant was
+       never an implementor who had actually exercised it -- the criticism had
+       a  point.   ncurses  5.0  provided  a   way   to   detect   nonstandard
+       capabilities,  to  determine  their  type,  and to optionally store and
+       retrieve them in a way that did not interfere with other  applications.
+       ncurses  terms these user-defined capabilities because no modifications
+       to the standard capability list are needed.
 
-       The  ncurses  utilities tic and infocmp have a command-line option "-x"
-       to  control  whether  the  nonstandard  capabilities  are   stored   or
-       retrieved.   A  library function use_extended_names is provided for the
+       The ncurses utilities tic and infocmp have a command-line  option  "-x"
+       to   control   whether  the  nonstandard  capabilities  are  stored  or
+       retrieved.  ncurses provides use_extended_names(3x) to programs for the
        same purpose.
 
-       When compiling a terminal database, if "-x" is set, tic  will  store  a
-       user-defined  capability  if  the  capability  name  is  not one of the
-       predefined names.
+       When compiling a terminal database, if "-x" is used, tic stores a user-
+       defined capability if the capability name is not standard.
 
-       Because ncurses provides  a  termcap  library  interface,  these  user-
-       defined capabilities may be visible to termcap applications:
+       Because ncurses provides  a  termcap  library  interface,  these  user-
+       defined capabilities may be visible to termcap applications.
 
-       o   The   termcap  interface  (like  all  implementations  of  termcap)
-           requires that the capability names are 2-characters.
+       o   The   termcap  interface  (like  all  implementations  of  termcap)
+           restricts capability names to two characters.
 
-           When  the  capability  is  simple  enough  for  use  in  a  termcap
-           application, it is provided as a 2-character name.
+           When  the  capability  is  simple  enough  for  use  in  a  termcap
+           application, it is provided as a two-character name.
 
-       o   There  are  other user-defined capabilities which refer to features
-           not usable in termcap, e.g., parameterized strings  that  use  more
-           than two parameters or use more than the trivial expression support
-           provided by termcap.  For these, the terminfo database should  have
-           only capability names with 3 or more characters.
+       o   Other  user-defined  capabilities  employ  features  not  usable in
+           termcap, such as parameterized  strings  that  use  more  than  two
+           parameters  or  require  more  powerful  expressions  than  termcap
+           supports.  Such capabilities should, in the terminfo database, have
+           names at least three characters in length.
 
        o   Some terminals can send distinct strings for special keys (cursor-,
            keypad-  or  function-keys)  depending  on  modifier  keys  (shift,
-           control,  etc.).   While  terminfo  and  termcap  have  a set of 60
-           predefined function-key names, to which a series  of  keys  can  be
-           assigned,   that  is  insufficient  for  more  than  a  dozen  keys
-           multiplied by more than a couple  of  modifier  combinations.   The
-           ncurses  database  uses  a  convention based on xterm(1) to provide
-           extended special-key names.
+           control,  etc.).   While terminfo and termcap define a set of sixty
+           function key names, to which a series of keys can be assigned, that
+           is insufficient for more than a dozen keys multiplied by more  than
+           a  couple  of  modifier  combinations.  The ncurses database uses a
+           convention based on xterm(1) to provide extended special-key names.
 
-           Fitting that into termcap's limitation of 2-character  names  would
-           be   pointless.   These  extended  keys  are  available  only  with
-           terminfo.
+           Fitting that into termcap's limitation of 2-character  names  would
+           be  pointless.   These  extended keys are available only with term-
+           info.

                                                                                                                                                                                  Recognized Capabilities

                                                                                                                                                                                  -       The ncurses library uses the user-definable  capabilities.   While  the
-       terminfo  database  may  have  other extensions, ncurses makes explicit
-       checks for these:
+       The ncurses library employs  user-definable  capabilities.   While  the
+       terminfo  database  may  have  other extensions, ncurses makes explicit
+       checks for the following.
 
-          AX Boolean, asserts that the terminal interprets SGR 39 and  SGR  49
-             by  resetting  the foreground and background color, respectively,
+          AX (Boolean) asserts that the terminal interprets SGR 39 and SGR  49
+             by  resetting the foreground and background colors, respectively,
              to the default.
 
-             This is a feature recognized by the screen program as well.
+             screen(1) recognizes this capability as well.
 
-          E3 string, tells how to  clear  the  terminal's  scrollback  buffer.
-             When present, the clear(1) program sends this before clearing the
-             terminal.
+          E3 (string)  tells  an  application  how  to  clear  the  terminal's
+             scrollback buffer.  When present, the clear(1) program sends this
+             before clearing the terminal.
 
              The command "tput clear" does the same thing.
 
-          NQ Boolean, used to suppress a consistency  check  in  tic  for  the
-             ncurses  capabilities  in user6 through user9 (u6, u7, u8 and u9)
-             which tell how to query the terminal's cursor  position  and  its
+          NQ (Boolean)  suppresses  a consistency check in tic for the ncurses
+             string capabilities user6 (u6) through user9 (u9), which tell  an
+             application  how  to query the terminal's cursor position and its
              device attributes.
 
-          RGB
-             Boolean,   number   or   string,   used   to   assert   that  the
-             set_a_foreground and set_a_background capabilities correspond  to
-             direct  colors,  using  an RGB (red/green/blue) convention.  This
-             capability  allows   the   color_content   function   to   return
-             appropriate   values   without   requiring   the  application  to
-             initialize colors using init_color.
+          RGB
+             (Boolean, numeric, or string) asserts that  the  set_a_foreground
+             (setaf)  and  set_a_background (setab) capabilities employ direct
+             colors,  using  an   RGB   (red/green/blue)   convention.    This
+             capability  allows color_content(3x) to return appropriate values
+             without requiring the  application  to  initialize  colors  using
+             init_color(3x).
 
-             The capability type determines the values which ncurses sees:
+             The capability type determines the values ncurses sees.
 
-             Boolean
-                implies that the number of bits for red, green  and  blue  are
-                the  same.   Using  the maximum number of colors, ncurses adds
-                two, divides that sum by three, and assigns the result to red,
-                green and blue in that order.
+             Boolean
+                implies  that  the number of bits for red, green, and blue are
+                the  same.   Starting  with  the  value  of   the   capability
+                max_colors  (colors;  termcap:  co), ncurses adds two, divides
+                the sum by three, and assigns the result to  red,  green,  and
+                blue, in that order.
 
                 If the number of bits needed for the number of colors is not a
-                multiple of three, the blue (and  green)  components  lose  in
+                multiple of three, the blue (and green) color channels lose in
                 comparison to red.
 
-             number
-                tells  ncurses  what result to add to red, green and blue.  If
+             numeric
+                tells  ncurses what result to add to red, green, and blue.  If
                 ncurses runs out of bits, blue (and green) lose just as in the
-                Boolean case.
+                Boolean case.
 
-             string
-                explicitly  list  the  number  of bits used for red, green and
-                blue components as a slash-separated list of decimal integers.
+             string
+                specify the quantity of bits used for  red,  green,  and  blue
+                color channels as a slash-separated list of decimal integers.
 
-             Because there are several  RGB  encodings  in  use,  applications
-             which  make  assumptions  about  the number of bits per color are
-             unlikely to work reliably.  As a trivial case, for  example,  one
-             could  define  RGB#1 to represent the standard eight ANSI colors,
-             i.e., one bit per color.
+             Because there are several RGB encodings in use, applications that
+             make  assumptions  about the number of bits per color channel are
+             unlikely to work reliably.  As a trivial case, one  could  define
+             RGB#1 to represent the standard eight ANSI X3.64/ECMA-48/ISO 6429
+             colors using one bit per color channel.
 
-          U8 number, asserts that ncurses must use Unicode  values  for  line-
-             drawing  characters,  and  that  it  should  ignore the alternate
-             character set capabilities when the locale uses  UTF-8  encoding.
-             For  more  information, see the discussion of NCURSES_NO_UTF8_ACS
-             in ncurses(3x).
+          U8 (numeric)  asserts  whether  ncurses  must use Unicode values for
+             line-drawing characters, and that it should ignore the  alternate
+             character  set  (ACS)  capabilities  when  the  locale uses UTF-8
+             encoding.  See the discussion of NCURSES_NO_UTF8_ACS  in  section
+             "ENVIRONMENT" of ncurses(3x).
 
              Set this capability to a nonzero value to enable it.
 
-          XM string, override ncurses's built-in string which enables/disables
-             xterm(1) mouse mode.
+          XM (string) override ncurses's built-in string that directs xterm(1)
+             to enable or disable mouse mode.
 
              ncurses  sends a character sequence to the terminal to initialize
              mouse mode, and when the user clicks the  mouse  buttons  or  (in
              certain  modes) moves the mouse, handles the characters sent back
-             by the terminal to tell it what was done with the mouse.
+             by the terminal to tell the application what was  done  with  the
+             mouse.
 
-             The mouse protocol  is  enabled  when  the  mask  passed  in  the
-             mousemask  function  is nonzero.  By default, ncurses handles the
-             responses for the X11 xterm mouse protocol.  It also knows  about
-             the  SGR  1006  xterm mouse protocol, but must to be told to look
-             for this specifically.  It will not be able to guess  which  mode
-             is  used,  because  the  responses  are  enough  alike  that only
-             confusion would result.
+             The  mouse  protocol  is  enabled  when  the mask argument to the
+             mousemask(3x) function is nonzero.  By default,  ncurses  handles
+             the  responses  for  the X11 xterm mouse protocol.  It also knows
+             about the SGR 1006 xterm mouse protocol, but must to be  told  to
+             look  for it specifically.  ncurses is not be able to guess which
+             of the two modes is used, because the responses are enough  alike
+             that only confusion would result.
 
-             The XM capability has a single parameter.  If nonzero, the  mouse
-             protocol  should  be enabled.  If zero, the mouse protocol should
-             be disabled.  ncurses inspects this capability if it is  present,
-             to  see whether the 1006 protocol is used.  If so, it expects the
-             responses to use the SGR 1006 xterm mouse protocol.
+             The  XM  capability  has a single numeric parameter.  If nonzero,
+             the mouse  protocol  should  be  enabled.   If  zero,  the  mouse
+             protocol should be disabled.  ncurses inspects this capability if
+             it  is present, to see whether the 1006 protocol is used.  If so,
+             it  expects  the  responses  to  use  the  SGR 1006  xterm  mouse
+             protocol.
 
-             The xterm mouse protocol is used  by  other  terminal  emulators.
-             The  terminal database uses building-blocks for the various xterm
-             mouse  protocols  which  can  be  used  in  customized   terminal
-             descriptions.
+             The  xterm  mouse  protocol  is used by other terminal emulators.
+             The terminal database uses building blocks for the various  xterm
+             mouse protocols usable in customized terminal descriptions.
 
              The terminal database building blocks for this mouse feature also
-             have  an  experimental  capability  xm.   The   "xm"   capability
-             describes  the mouse response.  Currently there is no interpreter
-             which would use  this  information  to  make  the  mouse  support
-             completely data-driven.
+             have  an  experimental  capability,  xm, that describes the mouse
+             response.  No known  interpreter  uses  this  information,  which
+             could make mouse support completely data-driven.
 
-             xm shows the format of the mouse responses.  In this experimental
-             capability, the parameters are
+             xm shows the format of the mouse responses.  In this experimental
+             capability, the parameters are as follows.
 
                p1   y-ordinate
 
@@ -296,8 +300,8 @@
 
                p8   x-ordinate ending region
 
-             Here are  examples  from  the  terminal  database  for  the  most
-             commonly used xterm mouse protocols:
+             Here  are  examples  from  the  terminal  database  for  the most
+             commonly used xterm mouse protocols.
 
                xterm+x11mouse|X11 xterm mouse protocol,
                        kmous=\E[M, XM=\E[?1000%?%p1%{1}%=%th%el%;,
@@ -315,20 +319,20 @@

                                                                                                                                                                                  Extended Key Definitions

                                                                                                                                                                                  -       Several  terminals  provide  the  ability  to send distinct strings for
-       combinations of modified special keys.  There is no standard  for  what
+       Several terminals provide the ability  to  send  distinct  strings  for
+       combinations  of  modified special keys.  There is no standard for what
        those keys can send.
 
-       Since  1999,  xterm(1)  has  supported  shift,  control,  alt, and meta
-       modifiers which produce distinct special-key strings.   In  a  terminal
-       description,  ncurses  has  no special knowledge of the modifiers used.
-       Applications can use the naming convention  established  for  xterm  to
+       Since 1999, xterm(1)  has  supported  shift,  control,  alt,  and  meta
+       modifiers  which  produce  distinct special-key strings.  In a terminal
+       description, ncurses has no special knowledge of  the  modifiers  used.
+       Applications  can  use  the  naming convention established for xterm to
        find these special keys in the terminal description.
 
-       Starting  with  the  curses convention that capability codes describing
-       the input generated by a terminal's key caps begin with "k",  and  that
-       shifted  special  keys  use uppercase letters in their names, ncurses's
-       terminal database defines the following names  and  codes  to  which  a
+       Starting with the curses convention that  capability  codes  describing
+       the  input  generated by a terminal's key caps begin with "k", and that
+       shifted special keys use uppercase letters in  their  names,  ncurses's
+       terminal  database  defines  the  following  names and codes to which a
        suffix is added.
 
             Code   Description
@@ -343,8 +347,8 @@
             kRIT   shifted kcuf1 (cursor forward)
             kUP    shifted kcuu1 (cursor up)
 
-       Keycap  nomenclature on the Unix systems for which curses was developed
-       differs from today's ubiquitous descendants of the IBM  PC/AT  keyboard
+       Keycap nomenclature on the Unix systems for which curses was  developed
+       differs  from  today's ubiquitous descendants of the IBM PC/AT keyboard
        layout.  In the foregoing, interpret "backward" as "left", "forward" as
        "right", "next" as "page down", and "prev(ious)" as "page up".
 
@@ -368,20 +372,21 @@
             15      Meta + Ctrl + Alt
             16      Meta + Ctrl + Alt + Shift
 
-       None of these are predefined; terminal descriptions can refer to  names
-       which ncurses will allocate at runtime to key-codes.  To use these keys
-       in an ncurses program, an application could do this:
+       ncurses  defines  no  capabilities  for   modified   F-keys;   terminal
+       descriptions  can  refer  to names that ncurses allocates at runtime to
+       key codes.  To use these keys in an  ncurses  program,  an  application
+       could do this:
 
-       o   using a list of extended key  names,  ask  tigetstr(3x)  for  their
+       o   using  a  list  of  extended  key names, ask tigetstr(3x) for their
            values, and
 
-       o   given  the  list  of  values,  ask key_defined(3x) for the key-code
+       o   given the list of values,  ask  key_defined(3x)  for  the  key-code
            which would be returned for those keys by wgetch(3x).

                                                                                                                                                                                  PORTABILITY

                                                                                                                                                                                  -       The "-x" extension feature of tic  and  infocmp  has  been  adopted  in
-       NetBSD  curses.   That implementation stores user-defined capabilities,
+       The  "-x"  extension  feature  of  tic  and infocmp has been adopted in
+       NetBSD curses.  That implementation stores  user-defined  capabilities,
        but makes no use of these capabilities itself.
 
 
@@ -393,17 +398,15 @@

                                                                                                                                                                                  SEE ALSO

                                                                                                                                                                                          infocmp(1m), tic(1m)
 
-       The  terminal  database  section  NCURSES  USER-DEFINABLE  CAPABILITIES
-       summarizes  commonly-used  user-defined  capabilities which are used in
-       the terminal descriptions.  Some of those  features  are  mentioned  in
-       screen(1) or tmux(1).
+       In  the source form of the terminal database, terminfo.src, the section
+       "NCURSES USER-DEFINABLE CAPABILITIES".  summarizes commonly-used  user-
+       defined  capabilities  employed  in the terminal descriptions.  Some of
+       those features are mentioned in screen(1) or tmux(1).
 
-       XTerm  Control  Sequences  provides further information on the xterm(1)
+       XTerm Control Sequences provides further information  on  the  xterm(1)
        features that are used in these extended capabilities.
 
-
-
-ncurses 6.5                       2024-03-16                      user_caps(5)
+ncurses 6.6                       2025-11-11                      user_caps(5)
                                                                                                                                                                                    diff --git a/doc/html/man/wresize.3x.html b/doc/html/man/wresize.3x.html index b224fd3..1f444f4 100644 --- a/doc/html/man/wresize.3x.html +++ b/doc/html/man/wresize.3x.html @@ -1,6 +1,6 @@ -wresize 3x 2024-03-16 ncurses 6.5 Library calls +wresize 3x 2025-01-18 ncurses 6.6 Library calls -

                                                                                                                                                                                    wresize 3x 2024-03-16 ncurses 6.5 Library calls

                                                                                                                                                                                    +

                                                                                                                                                                                    wresize 3x 2025-01-18 ncurses 6.6 Library calls

                                                                                                                                                                                     wresize(3x)                      Library calls                     wresize(3x)
 
 
-
-

                                                                                                                                                                                    NAME

                                                                                                                                                                                            wresize - resize a curses window
 
@@ -54,48 +52,59 @@

                                                                                                                                                                                    SYNOPSIS

                                                                                                                                                                                            #include <curses.h>
 
-       int wresize(WINDOW *win, int lines, int columns);
+       int wresize(WINDOW * win, int lines, int columns);

                                                                                                                                                                                    DESCRIPTION

                                                                                                                                                                                    -       This  ncurses  extension  to  standard curses reallocates storage for a
-       curses window to adjust its dimensions to  the  specified  values.   If
-       either dimension is larger than its current value, the expanded part of
-       the window  is  filled  with  blanks  merged  with  current  background
-       rendition (as set by wbkgdset(3x)).
+       wresize,  an  ncurses  extension  to  the  curses  library, reallocates
+       storage for win, adjusting its dimensions to  lines  and  columns.   If
+       either  dimension  is  larger than its current value, ncurses fills the
+       expanded part of the window with the window's background  character  as
+       configured by wbkgdset(3x) (wide-character API: wbkgrndset(3x)).

                                                                                                                                                                                    RETURN VALUE

                                                                                                                                                                                    -       wresize  returns  ERR  upon failure and OK on success.  It will fail if
-       either of the dimensions is less than or equal to zero, or if an  error
-       occurs while (re)allocating memory for the window.
+       wresize  returns  OK on success and ERR on failure.  It fails if either
+       lines or columns is less than or equal to zero, or if an  error  occurs
+       while (re)allocating memory for win.

                                                                                                                                                                                    NOTES

                                                                                                                                                                                    -       The  only  restriction placed on the dimensions is that they be greater
-       than zero.  They are not compared to the curses screen dimensions; this
-       keeps  the logic of resizeterm(3x) simple.  The caller must ensure that
-       the window's dimensions fit within the actual screen dimensions.
+       The  only restriction placed on the values of lines and columns is that
+       they be greater than zero.  They are not compared to the dimensions  of
+       the  curses screen; this keeps the logic of resizeterm(3x) simple.  The
+       caller must ensure that  win's  dimensions  fit  within  those  of  the
+       screen.
+
+
+

                                                                                                                                                                                    EXTENSIONS

                                                                                                                                                                                    +       wresize  is  an ncurses(3x) extension, and is not found in SVr4 curses,
+       4.4BSD curses, or any other previous curses implementation.

                                                                                                                                                                                    PORTABILITY

                                                                                                                                                                                    +       Applications employing ncurses extensions should condition their use on
+       the visibility of the NCURSES_VERSION preprocessor macro.
+
+       NetBSD curses adopted wresize in 2001 (release 1.5.3), and PDCurses  in
+       2004 (version 2.7).
+
        It is not possible to resize windows with SVr4 curses.
 
-       ncurses introduced this extension in mid-1995.  NetBSD  curses  adopted
-       it in 2001, and PDCurses in 2003.
+
+

                                                                                                                                                                                    HISTORY

                                                                                                                                                                                    +       Thomas  Dickey developed wresize as an extension to BSD curses in 1988,
+       and brought it to ncurses in mid-1995.

                                                                                                                                                                                    AUTHORS

                                                                                                                                                                                    -       Thomas  Dickey  (from  an  equivalent  function written in 1988 for BSD
-       curses).
+       Thomas Dickey

                                                                                                                                                                                    SEE ALSO

                                                                                                                                                                                            resizeterm(3x)
 
-
-
-ncurses 6.5                       2024-03-16                       wresize(3x)
+ncurses 6.6                       2025-01-18                       wresize(3x)
                                                                                                                                                                                    diff --git a/doc/html/ncurses-intro.html b/doc/html/ncurses-intro.html index 1948502..d07f6f2 100644 --- a/doc/html/ncurses-intro.html +++ b/doc/html/ncurses-intro.html @@ -1,7 +1,7 @@