From c463be09eb74597309dc4014ac7f96d0b05ce01c Mon Sep 17 00:00:00 2001 From: Xue Fuqiao Date: Tue, 15 Oct 2013 06:20:52 +0800 Subject: [PATCH] Comment --- doc/lispref/display.texi | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi index 99cbb4d3458..ae24439c41f 100644 --- a/doc/lispref/display.texi +++ b/doc/lispref/display.texi @@ -611,6 +611,9 @@ program signals a Lisp error and then handles it with @code{condition-case}, the user won't see the error message; it could show the message to the user by reporting it as a warning.) +@c FIXME: Why use ‘(bytecomp)’ instead of ‘'bytecomp’ or simply +@c ‘bytecomp’ here? The parens are part of ‘warning-type-format’ but +@c not part of the warning type. --xfq @cindex warning type Each warning has a @dfn{warning type} to classify it. The type is a list of symbols. The first symbol should be the custom group that you -- 2.39.2