Ncurses - revision history

Dank at 20:49, 25 June 2021

2021-06-25T20:49:13Z

← Older revision		Revision as of 20:49, 25 June 2021
Line 80:		Line 80:
	* setlocale() needs have been called prior to calling any ncurses functions		* setlocale() needs have been called prior to calling any ncurses functions
	** ncurses assumes that the locale does not change once started		** ncurses assumes that the locale does not change once started

			[[CATEGORY: Terminals]]

Dank: discuss ncurses tracing functionality

2019-11-23T05:55:12Z

discuss ncurses tracing functionality

← Older revision		Revision as of 05:55, 23 November 2019
Line 1:		Line 1:
	Quality character cell graphics since [https://invisible-island.net/ncurses/ncurses.faq.html 1982]. NCURSES is an implementation and extension of [[Single UNIX Specification\|SUS4-2018]]'s X/Open Curses API, and is installed on pretty much every Linux machine in existence.		Quality character cell graphics since [https://invisible-island.net/ncurses/ncurses.faq.html 1982]. NCURSES is an implementation and extension of [[Single UNIX Specification\|SUS4-2018]]'s X/Open Curses API, and is installed on pretty much every Linux machine in existence.

			==Tracing==
			By either defining the symbol TRACE during compilation or linking against <tt>libncurses_g</tt>, tracing functionality becomes available to an Ncurses application (see <tt>trace(3NCURSES)</tt>). Either calling the <tt>trace()</tt> function or defining the <tt>NCURSES_TRACE</tt> environment variable is sufficient to initiate tracing, which will be logged to the file <tt>trace</tt> in the current directory (this file must not already exist).

	==Escape==		==Escape==

Dank at 05:51, 23 November 2019

2019-11-23T05:51:57Z

← Older revision		Revision as of 05:51, 23 November 2019
Line 1:		Line 1:
	Quality character cell graphics since [https://invisible-island.net/ncurses/ncurses.faq.html 1982]. NCURSES is an implementation and extension of [[Single UNIX Specification\|~~SUS42018~~]]'s X/Open Curses API, and is installed on pretty much every Linux machine in existence.		Quality character cell graphics since [https://invisible-island.net/ncurses/ncurses.faq.html 1982]. NCURSES is an implementation and extension of [[Single UNIX Specification\|SUS4-2018]]'s X/Open Curses API, and is installed on pretty much every Linux machine in existence.

	==Escape==		==Escape==

Dank at 05:49, 23 November 2019

2019-11-23T05:49:39Z

← Older revision		Revision as of 05:49, 23 November 2019
Line 1:		Line 1:
	Quality character cell graphics since [https://invisible-island.net/ncurses/ncurses.faq.html 1982].		Quality character cell graphics since [https://invisible-island.net/ncurses/ncurses.faq.html 1982]. NCURSES is an implementation and extension of [[Single UNIX Specification\|SUS42018]]'s X/Open Curses API, and is installed on pretty much every Linux machine in existence.

	==Escape==		==Escape==

Dank: escape sequences and terminfo

2019-11-18T17:10:14Z

escape sequences and terminfo

← Older revision		Revision as of 17:10, 18 November 2019
Line 3:		Line 3:
	==Escape==		==Escape==
	You can get Escape with no delay by using <tt>notimeout(3ncurses)</tt>, but this eliminates use of the function and arrow keys on terminals where those sequences are composed with Escape. You probably don't want that. You can use the ESCDELAY environment variable (see <tt>ncurses(3ncurses)</tt>) to change this (ncurses also provides a global of the same name). In a threaded environment, <tt>set_escdelay()</tt> ought be preferred. [[Vim]] uses a 25ms default. The ncurses default appears to be 1s (1000ms), which makes one's application feel kinda seasick when running on any reasonable connection (not to mention locally). This seems difficult to manipulate programaticly, though. :/		You can get Escape with no delay by using <tt>notimeout(3ncurses)</tt>, but this eliminates use of the function and arrow keys on terminals where those sequences are composed with Escape. You probably don't want that. You can use the ESCDELAY environment variable (see <tt>ncurses(3ncurses)</tt>) to change this (ncurses also provides a global of the same name). In a threaded environment, <tt>set_escdelay()</tt> ought be preferred. [[Vim]] uses a 25ms default. The ncurses default appears to be 1s (1000ms), which makes one's application feel kinda seasick when running on any reasonable connection (not to mention locally). This seems difficult to manipulate programaticly, though. :/

			===Escape codes===
			The primary means of communicating with terminals is via escape sequences. The terminfo library, shipped with ncurses, allows these sequences to be looked up based off the terminal type (usually encoded in the environment variable <tt>TERM</tt>). The <tt>infocmp</tt> program dumps terminfo entries. Many terminals and terminal emulators support only some escape sequences, and they are not effectively standardized across terminals. Embedding hard-coded escape sequences into your program is a recipe for pain.

			The "termcap" library is obsolete, superseded entirely by terminfo, and ought not be used in new programs.

	==Colors==		==Colors==

Dank: /* Escape */

2019-11-11T04:29:59Z

Escape

← Older revision		Revision as of 04:29, 11 November 2019
Line 2:		Line 2:

	==Escape==		==Escape==
	You can get Escape with no delay by using <tt>notimeout(3ncurses)</tt>, but this eliminates use of the function and arrow keys on terminals where those sequences are composed with Escape. You probably don't want that. You can use the ESCDELAY environment variable (see <tt>ncurses(3ncurses)</tt>) to change this (ncurses also provides a global of the same name). [[Vim]] uses a 25ms default. The ncurses default appears to be 1s (1000ms), which makes one's application feel kinda seasick when running on any reasonable connection (not to mention locally). This seems difficult to manipulate programaticly, though. :/		You can get Escape with no delay by using <tt>notimeout(3ncurses)</tt>, but this eliminates use of the function and arrow keys on terminals where those sequences are composed with Escape. You probably don't want that. You can use the ESCDELAY environment variable (see <tt>ncurses(3ncurses)</tt>) to change this (ncurses also provides a global of the same name). In a threaded environment, <tt>set_escdelay()</tt> ought be preferred. [[Vim]] uses a 25ms default. The ncurses default appears to be 1s (1000ms), which makes one's application feel kinda seasick when running on any reasonable connection (not to mention locally). This seems difficult to manipulate programaticly, though. :/

	==Colors==		==Colors==

Dank: /* Colors */

2019-11-10T22:25:20Z

Colors

← Older revision		Revision as of 22:25, 10 November 2019
Line 48:		Line 48:
	#define PAIR_NUMBER(a) (NCURSES_CAST(int,((NCURSES_CAST(unsigned long,(a)) & A_COLOR) >> NCURSES_ATTR_SHIFT)))		#define PAIR_NUMBER(a) (NCURSES_CAST(int,((NCURSES_CAST(unsigned long,(a)) & A_COLOR) >> NCURSES_ATTR_SHIFT)))
	</pre>		</pre>

			The default colors built into ncurses can be dumped with <tt>color_content -p</tt>.

	===True Color===		===True Color===

Dank at 22:22, 10 November 2019

2019-11-10T22:22:47Z

@@ Line 33: / Line 33: @@
 ===Color attributes===
 Using color pairs beyond 256 requires a 16-bit attribute. By default, only 8 bits are provided (see <tt>A_COLOR</tt>). Thus for instance <tt>wattron(w, COLOR_PAIR(260))</tt> is equivalent to <tt>wattron(w, COLOR_PAIR(4))</tt>. In order to use pairs above 256, drop <tt>COLOR_PAIR</tt>, and always refer to the pair via pointer using the <tt>void* opts</tt> parameter to functions like <tt>wattron</tt>. What, there is not such parameter? Ahhh, of course; you need to use <tt>wattr_on</tt>. Note the underscore, and hate life.
 ===True Color===

Dank at 21:51, 10 November 2019

2019-11-10T21:51:46Z

← Older revision		Revision as of 21:51, 10 November 2019
Line 1:		Line 1:
			Quality character cell graphics since [https://invisible-island.net/ncurses/ncurses.faq.html 1982].

	==Escape==		==Escape==
	You can get Escape with no delay by using <tt>notimeout(3ncurses)</tt>, but this eliminates use of the function and arrow keys on terminals where those sequences are composed with Escape. You probably don't want that. You can use the ESCDELAY environment variable (see <tt>ncurses(3ncurses)</tt>) to change this (ncurses also provides a global of the same name). [[Vim]] uses a 25ms default. The ncurses default appears to be 1s (1000ms), which makes one's application feel kinda seasick when running on any reasonable connection (not to mention locally). This seems difficult to manipulate programaticly, though. :/		You can get Escape with no delay by using <tt>notimeout(3ncurses)</tt>, but this eliminates use of the function and arrow keys on terminals where those sequences are composed with Escape. You probably don't want that. You can use the ESCDELAY environment variable (see <tt>ncurses(3ncurses)</tt>) to change this (ncurses also provides a global of the same name). [[Vim]] uses a 25ms default. The ncurses default appears to be 1s (1000ms), which makes one's application feel kinda seasick when running on any reasonable connection (not to mention locally). This seems difficult to manipulate programaticly, though. :/

Dank: /* Colors */

2019-11-10T21:46:35Z

Colors

@@ Line 31: / Line 31: @@
 ===Color attributes===
 Using color pairs beyond 256 requires a 16-bit attribute. By default, only 8 bits are provided (see <tt>A_COLOR</tt>). Thus for instance <tt>wattron(w, COLOR_PAIR(260))</tt> is equivalent to <tt>wattron(w, COLOR_PAIR(4))</tt>. In order to use pairs above 256, drop <tt>COLOR_PAIR</tt>, and always refer to the pair via pointer using the <tt>void* opts</tt> parameter to functions like <tt>wattron</tt>. What, there is not such parameter? Ahhh, of course; you need to use <tt>wattr_on</tt>. Note the underscore, and hate life.
 ==[[Unicode]]==