* Lead option description by stating what the option does.
* Note potential existence of "tinfo(w)" library.
* Clarify visibility of `curses_trace()` and `trace()`.
---
 man/ncurses.3x | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/man/ncurses.3x b/man/ncurses.3x
index f3f59b6d5..8d8d10dab 100644
--- a/man/ncurses.3x
+++ b/man/ncurses.3x
@@ -2017,9 +2017,19 @@ .SH "ALTERNATE CONFIGURATIONS"
 .RE
 .TP 5
 .B \-\-with\-trace
-The \fBcurses_trace\fP(3X) function is normally available
-only in the debugging library;
-this option exposes it in the shared and static libraries as well.
+Expose the \fBcurses_trace\fP(3X) function
+in the
+.I ncurses(w)
+shared and static libraries.
+Normally,
+it is available only in the debugging library.
+(If
+.B \-\-with\-termlib
+is also specified,
+.I tinfo(w)
+rather than
+.I ncurses(w)
+supplies the deprecated \fBtrace\fP(3X) function.)
 An application's configuration script should check
 for the function's existence
 rather than assuming its confinement to the debugging library.
-- 
2.30.2

Attachment: signature.asc
Description: PGP signature

Reply via email to