X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fterm.7.html;h=b63800579e6388261badd10a11d200a25648a88b;hp=bc4ede4fd2102994b38789edd9da1e813db2094e;hb=761e4f0825b330e970558e82a4bd638383914429;hpb=55ccd2b959766810cf7db8d1c4462f338ce0afc8 diff --git a/doc/html/man/term.7.html b/doc/html/man/term.7.html index bc4ede4f..b6380057 100644 --- a/doc/html/man/term.7.html +++ b/doc/html/man/term.7.html @@ -1,7 +1,7 @@ - +
--TERM(7) TERM(7) +term(7) term(7) @@ -59,7 +59,7 @@ mailer. A default TERM value will be set on a per-line basis by - either /etc/inittab (Linux and System-V-like UNIXes) or + either /etc/inittab (e.g., System-V-like UNIXes) or /etc/ttys (BSD UNIXes). This will nearly always suffice for workstation and microcomputer consoles. @@ -85,9 +85,9 @@ 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 line. + created a custom entry incorporating options (such as vis- + ual bell or reverse-video) which you wish to override the + system default type for your line. Terminal type descriptions are stored as files of capabil- ity data underneath /usr/share/terminfo. To browse a list @@ -98,12 +98,12 @@ 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(1) command. Invoke it as fol- + you must use the infocmp(1m) command. Invoke it as fol- lows: - infocmp entry-name + infocmp entry_name - where entry-name is the name of the type you wish to exam- + where entry_name is the name of the type you wish to exam- ine (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 @@ -152,16 +152,16 @@ 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 + 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 fol- lows, it should indicate either the OS release level or the console driver release level. - The root name for a terminal emulator (assuming it doesn't - fit one of the standard ANSI or vt100 types) should be the - program name or a readily recognizable abbreviation of it - (i.e. versaterm, ctrm). + The root name for a terminal emulator (assuming it does + not fit one of the standard ANSI or vt100 types) should be + the program name or a readily recognizable abbreviation of + it (i.e., versaterm, ctrm). Following the root name, you may add any reasonable number of hyphen-separated feature suffixes. @@ -240,7 +240,7 @@ - TERM(7) + term(7)