From c845245e43d23fbf65490dea94bcab2b51d37e31 Mon Sep 17 00:00:00 2001 From: Bartosz Sosnowski Date: Tue, 28 Nov 2017 14:48:09 +0100 Subject: doc: remove note about SIGWINCH on Windows SIGWINCH support was improved by https://github.com/libuv/libuv/commit/6ad1e81547c83f9fe7c5a806b6b282642e8d3bca PR-URL: https://github.com/libuv/libuv/pull/1638 Reviewed-By: Ben Noordhuis Reviewed-By: Colin Ihrig --- docs/src/signal.rst | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'docs/src') diff --git a/docs/src/signal.rst b/docs/src/signal.rst index 5b3b352b..24354e4f 100644 --- a/docs/src/signal.rst +++ b/docs/src/signal.rst @@ -17,13 +17,6 @@ Reception of some signals is emulated on Windows: program is given approximately 10 seconds to perform cleanup. After that Windows will unconditionally terminate it. -* SIGWINCH is raised whenever libuv detects that the console has been - resized. SIGWINCH is emulated by libuv when the program uses a :c:type:`uv_tty_t` - handle to write to the console. SIGWINCH may not always be delivered in a - timely manner; libuv will only detect size changes when the cursor is - being moved. When a readable :c:type:`uv_tty_t` handle is used in raw mode, - resizing the console buffer will also trigger a SIGWINCH signal. - Watchers for other signals can be successfully created, but these signals are never received. These signals are: `SIGILL`, `SIGABRT`, `SIGFPE`, `SIGSEGV`, `SIGTERM` and `SIGKILL.` @@ -36,6 +29,7 @@ not detected by libuv; these will not trigger a signal watcher. manage threads. Installing watchers for those signals will lead to unpredictable behavior and is strongly discouraged. Future versions of libuv may simply reject them. +.. versionchanged:: 1.15.0 SIGWINCH support on Windows was improved. Data types ---------- -- cgit v1.2.3